through2 0.2.2
A tiny wrapper around Node streams2 Transform to avoid explicit subclassing noise
through2@0.2.2 was published on 2013-09-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 through2 versions · Permanent reference to 0.2.2 · Latest release
Package specifications
| Version | 0.2.2 |
|---|---|
| License declaration | MIT |
| Published | 2013-09-19T06:04:57.568Z |
| 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 | through2.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 1907 |
| Repository forks | 106 |
Install through2 0.2.2
npm install through2@0.2.2 pnpm add through2@0.2.2 yarn add through2@0.2.2
Runtime dependencies
- xtend ~2.1.1
- readable-stream ~1.0.2
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@0.0.1 — indirect
- object-keys@0.4.0 — indirect
- readable-stream@1.0.34 — direct
- string_decoder@0.10.31 — indirect
- xtend@2.1.2 — direct
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 |
|---|---|
| Code-Review | 0/10 — Found 1/17 approved changesets -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 10/10 — 24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| 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 |
| Packaging | 10/10 — packaging workflow detected |
Evidence and freshness
- https://registry.npmjs.org/through2/0.2.2 — retrieved 2026-10-29T13:43:13.469Z
- https://api.deps.dev/v3/projects/github.com%2Frvagg%2Fthrough2 — retrieved 2026-10-29T13:18:51.530Z
- https://api.deps.dev/v3/systems/npm/packages/through2/versions/0.2.2 — retrieved 2026-10-29T13:43:13.963Z
- https://api.deps.dev/v3/systems/npm/packages/through2/versions/0.2.2:dependencies — retrieved 2026-10-29T13:43:13.984Z