@vscode/ripgrep-linux-arm64
1
Versions
—
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
vscode-botmicrosoft1es
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 binary package; bin/rg is the expected ripgrep executable for linux-arm64, published by Microsoft. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals are all consistent with a legitimate platform-specific binary split package (no deps, sparse README, inflated semver matching upstream ripgrep version). | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.18.0 | 0 / 0 |
v1.18.0
2 findings
HIGH
Bundled binary files (1)
npm-metadata
Package contains compiled binaries that could be backdoors: • bin/rg
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.