to-through
Wrap a Readable stream in a Transform stream.
to-through@3.0.0 was published on 2022-09-07. 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 >=10.13.0.
All to-through versions · Permanent reference to 3.0.0
Package specifications
| Version | 3.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2022-09-07T22:38:12.909Z |
| Node.js requirement | >=10.13.0 |
| 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 | 6.99 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 | 6 |
| Repository stars | 10 |
| Repository forks | 6 |
Install to-through 3.0.0
npm install to-through@3.0.0 pnpm add to-through@3.0.0 yarn add to-through@3.0.0
Runtime dependencies
- streamx ^2.12.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.
- b4a@1.9.0 — indirect
- bare-events@2.9.2 — indirect
- events-universal@1.0.1 — indirect
- fast-fifo@1.3.2 — indirect
- streamx@2.28.1 — direct
- text-decoder@1.2.7 — 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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 2/10 — Found 3/14 approved changesets -- score normalized to 2 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| 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 | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/to-through/3.0.0 — retrieved 2026-10-29T09:39:56.145Z
- https://api.deps.dev/v3/systems/npm/packages/to-through/versions/3.0.0 — retrieved 2026-10-29T09:39:56.669Z
- https://api.deps.dev/v3/systems/npm/packages/to-through/versions/3.0.0:dependencies — retrieved 2026-10-29T09:39:56.700Z
- https://api.deps.dev/v3/projects/github.com%2Fgulpjs%2Fto-through — retrieved 2026-10-29T09:39:56.835Z