redzip
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redis | AI (typosquat): redzip is a zip-file utility; name similarity to redis is purely coincidental with no brand impersonation. | ai | |
| phantom-deps | phantom-dep:once | AI (phantom-deps): once is a declared runtime dep; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:yauzl | AI (phantom-deps): yauzl is a declared runtime dep; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:totalist | AI (phantom-deps): totalist is a declared runtime dep; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:wraptile | AI (phantom-deps): wraptile is a declared runtime dep; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.6.1 | 13 / 12 | |
| 4.6.0 | 13 / 12 | |
| 4.5.1 | 13 / 12 | |
| 4.5.0 | 13 / 12 | |
| 4.4.0 | 13 / 12 | |
| 4.3.0 | 13 / 12 | |
| 4.2.0 | 13 / 12 | |
| 4.1.0 | 13 / 12 | |
| 4.0.1 | 13 / 12 | |
| 4.0.0 | 13 / 12 |
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.