through2-filter 4.0.0
A through2 to create an Array.prototype.filter analog for streams.
through2-filter@4.0.0 was published on 2024-04-20. 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 >= 6.
All through2-filter versions · Permanent reference to 4.0.0 · Latest release
Package specifications
| Version | 4.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2024-04-20T17:44:59.803Z |
| Node.js requirement | >= 6 |
| 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 | 5.40 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 34 |
| Repository forks | 4 |
Install through2-filter 4.0.0
npm install through2-filter@4.0.0 pnpm add through2-filter@4.0.0 yarn add through2-filter@4.0.0
Runtime dependencies
- through2 ^4.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.
- inherits@2.0.4 — indirect
- readable-stream@3.6.2 — indirect
- safe-buffer@5.2.1 — indirect
- string_decoder@1.3.0 — indirect
- through2@4.0.2 — direct
- 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.
| Code-Review | 1/10 — Found 4/24 approved changesets -- score normalized to 1 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- 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 |
| 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/through2-filter/4.0.0 — retrieved 2026-10-29T09:24:16.265Z
- https://api.deps.dev/v3/systems/npm/packages/through2-filter/versions/4.0.0:dependencies — retrieved 2026-10-29T08:00:51.179Z
- https://api.deps.dev/v3/systems/npm/packages/through2-filter/versions/4.0.0 — retrieved 2026-10-29T08:00:51.164Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fbrycebaril%2Fthrough2-filter — retrieved 2026-10-29T08:00:51.373Z