tarr
tarr for node
2
Versions
BSD
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
sintaxi
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:http-module-request | AI (semgrep): The HTTP request is in old/doc/example.js — a documentation example showing how to pipe an HTTP response into a tar parser. Not production code; no exfiltration risk. | ai | |
| dependencies | unvetted-dep:fstream | AI (dependencies): fstream is a legitimate npm package from the isaacs ecosystem, appropriate for this old tar utility targeting Node 0.5-0.8. | ai |
v1.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.