hyperdrive-schemas
Protobuf schemas for Hyperdrive and its daemon.
hyperdrive-schemas@2.0.0 was published on 2020-07-14. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All hyperdrive-schemas versions · Permanent reference to 2.0.0
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2020-07-14T11:16:33.671Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 19.26 KiB |
| Published file count | 7 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 14 |
| Repository forks | 7 |
Install hyperdrive-schemas 2.0.0
npm install hyperdrive-schemas@2.0.0 pnpm add hyperdrive-schemas@2.0.0 yarn add hyperdrive-schemas@2.0.0
Runtime dependencies
- protocol-buffers-encodings ^1.1.0
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.
- b4a@1.9.0 — indirect
- protocol-buffers-encodings@1.2.0 — direct
- signed-varint@2.0.1 — indirect
- varint@5.0.0 — indirect
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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/hyperdrive-schemas/2.0.0 — retrieved 2026-10-29T20:28:37.159Z
- https://api.deps.dev/v3/systems/npm/packages/hyperdrive-schemas/versions/2.0.0 — retrieved 2026-10-29T20:28:37.699Z
- https://api.deps.dev/v3/systems/npm/packages/hyperdrive-schemas/versions/2.0.0:dependencies — retrieved 2026-10-29T20:28:37.714Z
- https://api.deps.dev/v3/projects/github.com%2Fandrewosh%2Fhyperdrive-schemas — retrieved 2026-10-29T20:28:37.858Z