@ruvector/sona
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:koa | AI (typosquat): Scoped package @ruvector/sona is a Rust/NAPI neural architecture lib; no relation to koa web framework. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used only to detect musl vs glibc via 'which ldd' — standard NAPI-RS platform detection pattern. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('which ldd') is a benign NAPI-RS runtime platform detection call, not arbitrary code execution. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Native Rust/NAPI binding; .node binary is the expected build artifact for this package type. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 0 / 1 | |
| 0.1.5 | 0 / 1 | |
| 0.1.4 | 0 / 1 | |
| 0.1.3 | 0 / 1 | |
| 0.1.2 | 0 / 1 | |
| 0.1.1 | 0 / 1 | |
| 0.1.0 | 0 / 1 |
v0.1.5
2 findingsPackage contains compiled binaries that could be backdoors: • sona.darwin-arm64.node • sona.darwin-x64.node • sona.linux-arm64-gnu.node • sona.linux-x64-gnu.node • sona.linux-x64-musl.node • sona.win32-arm64-msvc.node • sona.win32-x64-msvc.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage contains compiled binaries that could be backdoors: • sona.darwin-arm64.node • sona.darwin-x64.node • sona.linux-arm64-gnu.node • sona.linux-x64-gnu.node • sona.linux-x64-musl.node • sona.win32-arm64-msvc.node • sona.win32-x64-msvc.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage contains compiled binaries that could be backdoors: • sona.linux-x64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage contains compiled binaries that could be backdoors: • sona.linux-x64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • sona.linux-x64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • sona.linux-x64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.