@xhmikosr/bin-check
Check if a binary is working
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
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 8.2.1 | 2 / 2 | |
| 8.2.0 | 2 / 2 | |
| 8.1.0 | 2 / 2 | |
| 8.0.0 | 2 / 2 | |
| 7.1.0 | 2 / 2 | |
| 7.0.3 | 2 / 2 | |
| 7.0.2 | 2 / 2 | |
| 7.0.1 | 2 / 2 | |
| 7.0.0 | 2 / 2 | |
| 6.0.0 | 2 / 2 | |
| 5.0.2 | 2 / 2 | |
| 5.0.1 | 2 / 2 | |
| 5.0.0 | 2 / 2 |
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.