stream-to-promise
Convert streams (readable or writable) to promises
stream-to-promise@3.0.0 was published on 2020-05-25. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 10.
Deprecated: Deprecated. Use node:stream/promises and node:stream/consumers instead.
All stream-to-promise versions · Permanent reference to 3.0.0
Package specifications
| Version | 3.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2020-05-25T19:54:05.040Z |
| Node.js requirement | >= 10 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 3.93 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 139 |
| Repository forks | 10 |
Install stream-to-promise 3.0.0
npm install stream-to-promise@3.0.0 pnpm add stream-to-promise@3.0.0 yarn add stream-to-promise@3.0.0
Runtime dependencies
- any-promise ~1.3.0
- end-of-stream ~1.4.1
- stream-to-array ~2.3.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.
- any-promise@1.3.0 — direct
- end-of-stream@1.4.5 — direct
- once@1.4.0 — indirect
- stream-to-array@2.3.0 — direct
- wrappy@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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Maintained | 0/10 — project is archived |
| Code-Review | 2/10 — Found 5/20 approved changesets -- score normalized to 2 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/stream-to-promise/3.0.0 — retrieved 2026-10-29T18:09:20.251Z
- https://api.deps.dev/v3/systems/npm/packages/stream-to-promise/versions/3.0.0:dependencies — retrieved 2026-10-29T18:09:20.853Z
- https://api.deps.dev/v3/systems/npm/packages/stream-to-promise/versions/3.0.0 — retrieved 2026-10-29T18:09:20.884Z
- https://api.deps.dev/v3/projects/github.com%2Fbendrucker%2Fstream-to-promise — retrieved 2026-10-29T18:09:20.972Z