level-sublevel 4.0.2
Separate sections of levelup, with hooks!
level-sublevel@4.0.2 was published on 2013-03-19. Its manifest declares 2 runtime dependencies 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 level-sublevel versions · Permanent reference to 4.0.2 · Latest release
Package specifications
| Version | 4.0.2 |
|---|---|
| License declaration | MIT |
| Published | 2013-03-19T00:47:38.218Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 195 |
| Repository forks | 37 |
Install level-sublevel 4.0.2
npm install level-sublevel@4.0.2 pnpm add level-sublevel@4.0.2 yarn add level-sublevel@4.0.2
Runtime dependencies
- level-hooks ~4.1.0
- string-range ~1.1
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.
- deep-equal@0.0.0 — indirect
- defined@0.0.0 — indirect
- jsonify@0.0.1 — indirect
- level-hooks@4.1.10 — direct
- lock@0.0.3 — indirect
- string-range@1.1.0 — direct
- string-range@1.2.2 — indirect
- tape@0.2.2 — 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.
| Code-Review | 1/10 — Found 4/21 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — project is archived |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/level-sublevel/4.0.2 — retrieved 2026-10-29T21:46:39.308Z
- https://api.deps.dev/v3/projects/github.com%2Fdominictarr%2Flevel-sublevel — retrieved 2026-10-29T19:14:17.844Z
- https://api.deps.dev/v3/systems/npm/packages/level-sublevel/versions/4.0.2 — retrieved 2026-10-29T21:46:39.906Z
- https://api.deps.dev/v3/systems/npm/packages/level-sublevel/versions/4.0.2:dependencies — retrieved 2026-10-29T21:46:39.918Z