capnp-ts 0.1.0
Strongly typed Cap'n Proto implementation for the browser and Node.js using TypeScript
capnp-ts@0.1.0 was published on 2017-08-31. Its manifest declares 4 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All capnp-ts versions · Permanent reference to 0.1.0 · Latest release
Package specifications
| Version | 0.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-08-31T15:06:23.721Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 167 |
| Repository forks | 42 |
Install capnp-ts 0.1.0
npm install capnp-ts@0.1.0 pnpm add capnp-ts@0.1.0 yarn add capnp-ts@0.1.0
Runtime dependencies
- debug ^2.6.3
- tslib ^1.7.1
- format ^0.2.2
- utf8-encoding ^0.1.2
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- debug@2.6.9 — direct
- format@0.2.2 — direct
- ms@2.0.0 — indirect
- obtain-unicode@0.0.5 — indirect
- tslib@1.14.1 — direct
- utf8-encoding@0.1.2 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Security-Policy | 4/10 — security policy file detected |
|---|---|
| Code-Review | 1/10 — Found 3/26 approved changesets -- score normalized to 1 |
| Maintained | 10/10 — 23 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/capnp-ts/0.1.0 — retrieved 2026-10-30T23:21:32.763Z
- https://api.deps.dev/v3/systems/npm/packages/capnp-ts/versions/0.1.0 — retrieved 2026-10-30T23:21:33.214Z
- https://api.deps.dev/v3/systems/npm/packages/capnp-ts/versions/0.1.0:dependencies — retrieved 2026-10-30T23:21:33.264Z
- https://api.deps.dev/v3/projects/github.com%2Fjdiaz5513%2Fcapnp-ts — retrieved 2026-10-30T23:21:33.652Z