usearch
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is documented and consistent with SLSA provenance attestation on this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation via GitHub Actions CI confirms legitimate release pipeline despite dormancy gap. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Explicitly a ncc bundler workaround (guarded by process.uptime() < 0); not reachable at runtime. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 (localhost) in a benchmark tool; not a network exfiltration risk. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the standard prebuilt binary loader for native addons; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a build-time dependency referenced in binding.gyp, not imported in JS source. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in benchmark/probe utility scripts, not in the main library code. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries are expected for this native addon; published via CI with SLSA provenance. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.25.3 | 3 / 5 | |
| 2.25.1 | 3 / 5 | |
| 2.25.0 | 3 / 5 | |
| 2.21.4 | 3 / 5 | |
| 2.21.3 | 3 / 5 | |
| 2.21.0 | 3 / 5 | |
| 2.20.7 | 3 / 5 | |
| 2.20.5 | 3 / 5 | |
| 2.20.1 | 3 / 5 | |
| 2.19.21 | 3 / 5 | |
| 2.19.14 | 3 / 5 | |
| 2.19.6 | 3 / 5 | |
| 2.19.4 | 3 / 5 |
v2.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.25.1
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/linux-arm64/usearch.node • prebuilds/linux-x64/usearch.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.25.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.