inflation
Easily unzip an HTTP stream
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): fengmk2 is a known co-maintainer of stream-utils/koa ecosystem packages; transfer from jongleberry is a documented legitimate transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fengmk2 is a trusted, long-standing npm publisher (643 approved, 0 rejected) and known Koa ecosystem maintainer. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is typical for stable utility packages; new publish by trusted ecosystem co-maintainer adding brotli support. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 5 | |
| 2.0.0 | 0 / 4 | |
| 1.0.2 | 0 / 4 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-10-14. 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.
v2.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-09. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-06-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.