derive-key
Derive a named key from a master key
derive-key@1.0.1 was published on 2020-05-13. 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 derive-key versions · Permanent reference to 1.0.1
Package specifications
| Version | 1.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2020-05-13T19:08:44.187Z |
| 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 | 3.49 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 25 |
| Repository forks | 1 |
Install derive-key 1.0.1
npm install derive-key@1.0.1 pnpm add derive-key@1.0.1 yarn add derive-key@1.0.1
Runtime dependencies
- blake2b-universal ^1.0.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
- blake2b@2.1.4 — indirect
- blake2b-universal@1.0.1 — direct
- blake2b-wasm@2.4.0 — indirect
- nanoassert@2.0.0 — indirect
- node-gyp-build@4.8.4 — indirect
- sodium-native@3.4.1 — 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.
| SAST | 0/10 — no SAST tool detected |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 0/10 — Found 0/5 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not 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 |
Evidence and freshness
- https://registry.npmjs.org/derive-key/1.0.1 — retrieved 2026-10-29T15:18:55.978Z
- https://api.deps.dev/v3/systems/npm/packages/derive-key/versions/1.0.1 — retrieved 2026-10-29T15:18:56.610Z
- https://api.deps.dev/v3/systems/npm/packages/derive-key/versions/1.0.1:dependencies — retrieved 2026-10-29T15:18:56.620Z
- https://api.deps.dev/v3/projects/github.com%2Fhyperdivision%2Fderive-key — retrieved 2026-10-29T15:18:56.901Z