@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ruby/head-wasm-wasi | AI (dependencies): Official ruby.wasm runtime package, expected for this module's stated purpose. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are legitimate WASM ruby runtime packages matching package's function. | ai | |
| 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 11 / 1 | |
| 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 | |
| 0.1.4 | 3 / 0 | |
| 0.1.3 | 3 / 0 | |
| 0.1.2 | 3 / 0 | |
| 0.1.1 | 1 / 0 | |
| 0.1.0 | 1 / 0 |
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.