tar.gz
⚠️ DEPRECATED ⚠️ Pure javascript tarball tools for Node.js
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:fstream | AI (dependencies): fstream is a known Node.js streaming library appropriate for this tar/gzip utility. No malicious signals; stable dependency for this package's purpose. | ai | |
| license | uncommon-license:MIT <http://opensource.org/licenses/MIT> | AI (license): License is clearly MIT; the non-standard formatting (inline URL) triggers the rule but this is a false positive. Stable across all versions of this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is used in the bin/targz CLI entry point; phantom dep finding is a false positive for CLI tools. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): alanhoff is the documented author; addition reflects a legitimate 2015 account transition, not a compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): cranic removal is part of the same 2015 legitimate transition to the author's personal account. | ai | |
| phantom-deps | phantom-dep:chai | AI (phantom-deps): chai is a test assertion library listed in dependencies instead of devDependencies — a packaging quality issue, not a security risk. | ai | |
| phantom-deps | phantom-dep:mocha | AI (phantom-deps): mocha is a test runner listed in dependencies instead of devDependencies — a packaging quality issue, not a security risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to alanhoff occurred in 2015; alanhoff has a clean 10-approved/0-rejected track record and the repo URL matches. Stable historical transition. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Takeover occurred ~2015 (3910+ days ago); alanhoff has since maintained the package with 10 approved versions and 0 rejections. Historical transition, not an active threat. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 5 / 5 | |
| 1.0.6 | 5 / 5 | |
| 1.0.5 | 5 / 5 | |
| 1.0.3 | 7 / 3 | |
| 1.0.2 | 7 / 3 | |
| 1.0.1 | 7 / 3 | |
| 1.0.0 | 7 / 3 | |
| 0.1.1 | 3 / 4 | |
| 0.1.0 | 3 / 4 |
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
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
3 findingsAll previous maintainers (cranic) were replaced by new maintainers (alanhoff). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2015-08-31. 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.0.0
3 findingsAll previous maintainers (cranic) were replaced by new maintainers (alanhoff). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2015-08-10. 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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.