@rnacanvas/paste-interface
Paste things
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Publisher consistently publishes without provenance; stable pattern across all approved versions. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/layout | AI (phantom-deps): Same org scope (@rnacanvas); consistent with other accepted phantom-deps in this package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/dot-bracket | AI (phantom-deps): Same-org package; phantom-dep heuristic unreliable for monorepo-style scoped packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/ct | AI (phantom-deps): Same-org bundled package; phantom-dep heuristic unreliable for bundled dist output. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/value-check | AI (phantom-deps): Same-org bundled package; phantom-dep heuristic unreliable for bundled dist output. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/parse | AI (phantom-deps): Same-org bundled package; phantom-dep heuristic unreliable for bundled dist output. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/utilities | AI (phantom-deps): Same-org bundled package; phantom-dep heuristic unreliable for bundled dist output. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 6 / 12 | |
| 9.0.0 | 6 / 12 | |
| 8.0.0 | 5 / 12 | |
| 7.0.0 | 5 / 12 | |
| 6.2.2 | 5 / 12 | |
| 6.2.1 | 5 / 12 | |
| 6.2.0 | 5 / 12 | |
| 6.1.0 | 5 / 12 | |
| 6.0.0 | 5 / 12 | |
| 5.1.0 | 5 / 12 | |
| 5.0.0 | 5 / 12 | |
| 4.0.0 | 1 / 12 |
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.