@zipwire/zw-linux-arm64
Zipwire CLI binary for linux/arm64
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific CLI binary distribution package; bundled binary is the intended artifact. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Optional-dep sub-package pattern; no repo/keywords/deps is normal for scoped platform binary packages. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.5.5 | 0 / 0 | |
| 1.5.4 | 0 / 0 | |
| 1.5.3 | 0 / 0 | |
| 1.5.2 | 0 / 0 | |
| 1.5.1 | 0 / 0 | |
| 1.5.0 | 0 / 0 | |
| 1.4.9 | 0 / 0 | |
| 1.4.8 | 0 / 0 | |
| 1.4.7 | 0 / 0 | |
| 1.4.6 | 0 / 0 | |
| 1.4.5 | 0 / 0 | |
| 1.4.4 | 0 / 0 | |
| 1.4.3 | 0 / 0 | |
| 1.4.2 | 0 / 0 | |
| 1.4.1 | 0 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.1 | 0 / 0 | |
| 1.3.0 | 0 / 0 | |
| 1.2.2 | 0 / 0 | |
| 1.2.1 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.5 | 0 / 0 | |
| 1.1.4 | 0 / 0 | |
| 1.1.3 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.