gunzip-maybe
Transform stream that gunzips its input if it is gzipped and just echoes it if not
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): gunzip-maybe 0.0.0 is a 12-year-old package with 2.7M weekly downloads published by a trusted maintainer. The 0.0.0 version is a historical initial release convention, not a malware indicator. | ai | |
| provenance | publisher-changed | AI (provenance): watson is a known co-maintainer of mafintosh packages; this transfer from 2016 is legitimate and well-established. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): watson added as maintainer in 2016; long-standing legitimate collaboration with mafintosh. | ai | |
| phantom-deps | phantom-dep:browserify-zlib | AI (phantom-deps): browserify-zlib is referenced via the browser field in package.json for browser builds; not a direct import. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 6 / 3 | |
| 1.4.1 | 6 / 3 | |
| 1.4.0 | 6 / 3 | |
| 1.3.1 | 6 / 3 | |
| 1.3.0 | 4 / 3 | |
| 1.2.1 | 4 / 2 | |
| 1.2.0 | 4 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.3 | 3 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 1 / 2 | |
| 0.0.0 | 1 / 2 |
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2016-01-23. 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.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2016-01-17. 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.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.