stream-json 1.4.0
stream-json is the micro-library of Node.js stream components for creating custom JSON processing pipelines with a minimal memory footprint. It can parse JSON files far exceeding available memory streaming individual primitives using a SAX-inspired API. I
stream-json@1.4.0 was published on 2020-04-26. Its manifest declares 1 runtime dependency 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 stream-json versions · Permanent reference to 1.4.0 · Latest release
Package specifications
| Version | 1.4.0 |
|---|---|
| License declaration | BSD-3-Clause |
| Published | 2020-04-26T01:04:27.238Z |
| Node.js requirement | Not declared |
| 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 | 208.09 KiB |
| Published file count | 48 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 3 |
| Resolved graph dependencies | 1 |
| Repository stars | 1205 |
| Repository forks | 57 |
Install stream-json 1.4.0
npm install stream-json@1.4.0 pnpm add stream-json@1.4.0 yarn add stream-json@1.4.0
Runtime dependencies
- stream-chain ^2.2.1
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.
- stream-chain@2.2.5 — 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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 0/10 — Found 0/24 approved changesets -- score normalized to 0 |
|---|---|
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Maintained | 10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 10/10 — SAST tool is run on all commits |
Evidence and freshness
- https://registry.npmjs.org/stream-json/1.4.0 — retrieved 2026-10-29T14:37:28.126Z
- https://api.deps.dev/v3/projects/github.com%2Fuhop%2Fstream-json — retrieved 2026-10-29T12:17:31.511Z
- https://api.deps.dev/v3/systems/npm/packages/stream-json/versions/1.4.0 — retrieved 2026-10-29T14:37:28.635Z
- https://api.deps.dev/v3/systems/npm/packages/stream-json/versions/1.4.0:dependencies — retrieved 2026-10-29T14:37:28.752Z