@rnacanvas/base-pairs
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; author does not use Sigstore attestation but package is otherwise clean. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.10.1 | 2 / 9 | |
| 2.10.0 | 1 / 9 | |
| 2.9.0 | 1 / 9 | |
| 2.8.0 | 1 / 9 | |
| 2.7.0 | 1 / 9 | |
| 2.6.0 | 1 / 9 | |
| 2.5.0 | 1 / 9 | |
| 2.4.0 | 1 / 9 | |
| 2.3.0 | 1 / 9 |
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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.