json-stream
New line-delimeted JSON parser with a stream interface
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is ~14 years old from a well-established publisher; 0.0.0 reflects early npm conventions, not malicious intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Very old package (~2011) predates modern npm metadata conventions; missing repo/keywords/deps is typical for that era, not a spam indicator. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from mmalecki to jcrugzz occurred in Dec 2014 — a historical, legitimate maintainer transition. jcrugzz has a strong track record (522 approved packages). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same historical 2014 maintainer transition; jcrugzz is a well-established publisher. Not indicative of compromise. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 0 | |
| 0.2.2 | 0 / 0 | |
| 0.2.1 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2014-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.