@primate/ruby
Ruby backend for Primate
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rcompat/stdio | AI (phantom-deps): Declared dep used via config/indirect import pattern in this package; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:@ruby/head-wasm-wasi | AI (phantom-deps): Platform-specific binary package; not directly imported but legitimately declared as a runtime dep for WASM support. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 11 / 1 | |
| 0.6.0 | 8 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.0 | 6 / 0 | |
| 0.3.0 | 7 / 0 | |
| 0.2.0 | 7 / 0 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.