@ruvector/core
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:cors | AI (typosquat): Scoped package @ruvector/core is a Rust vector DB, not a typosquat of cors; name collision is coincidental. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard napi-rs platform-binary loader pattern; loads platform-specific optional dep by name, not user input. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.31 | 0 / 1 | |
| 0.1.30 | 0 / 1 | |
| 0.1.29 | 0 / 1 | |
| 0.1.28 | 0 / 1 | |
| 0.1.27 | 0 / 1 |
v0.1.30
2 findingsPackage name '@ruvector/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
2 findingsPackage name '@ruvector/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
2 findingsPackage name '@ruvector/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
2 findingsPackage name '@ruvector/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.