lazystream
Open Node Streams on demand.
lazystream@1.0.1 was published on 2021-10-23. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.6.3.
All lazystream versions · Permanent reference to 1.0.1
Package specifications
| Version | 1.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2021-10-23T09:04:15.234Z |
| Node.js requirement | >= 0.6.3 |
| 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 | 15.28 KiB |
| Published file count | 10 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/lazystream.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 55 |
| Repository forks | 14 |
Install lazystream 1.0.1
npm install lazystream@1.0.1 pnpm add lazystream@1.0.1 yarn add lazystream@1.0.1
Runtime dependencies
- readable-stream ^2.0.5
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.
- core-util-is@1.0.3 — indirect
- inherits@2.0.4 — indirect
- isarray@1.0.0 — indirect
- process-nextick-args@2.0.1 — indirect
- readable-stream@2.3.8 — direct
- safe-buffer@5.1.2 — indirect
- string_decoder@1.1.1 — indirect
- util-deprecate@1.0.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.
| Maintained | 0/10 — project is archived |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 1/25 approved changesets -- score normalized to 0 |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/lazystream/1.0.1 — retrieved 2026-10-29T06:02:17.896Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/lazystream/versions/1.0.1:dependencies — retrieved 2026-10-29T06:02:17.973Z
- https://api.deps.dev/v3/systems/npm/packages/lazystream/versions/1.0.1 — retrieved 2026-10-29T06:02:17.972Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fjpommerening%2Fnode-lazystream — retrieved 2026-10-29T06:02:18.441Z