@rnacanvas/code
Flexible nucleic acid structure drawing
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @rnacanvas package; Levenshtein match to 'cors' is a false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @rnacanvas package; Levenshtein match to 'zod' is a false positive for this namespace. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/boxes | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/layout | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/utilities | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/app-object | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/base-pairs | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/code.url-params | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/paste-interface | AI (phantom-deps): Same-org @rnacanvas dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 17.10.1 | 7 / 4 | |
| 17.10.0 | 7 / 4 | |
| 17.9.2 | 7 / 4 | |
| 17.9.1 | 7 / 4 | |
| 17.9.0 | 7 / 4 | |
| 17.8.0 | 7 / 4 | |
| 17.7.10 | 7 / 4 | |
| 17.7.9 | 7 / 4 | |
| 17.7.8 | 7 / 4 | |
| 17.7.7 | 7 / 4 | |
| 17.7.6 | 7 / 4 | |
| 17.7.5 | 7 / 4 | |
| 17.7.4 | 7 / 4 | |
| 17.7.3 | 7 / 4 | |
| 17.7.2 | 7 / 4 | |
| 17.7.1 | 7 / 4 | |
| 17.7.0 | 7 / 4 | |
| 17.6.0 | 7 / 4 | |
| 17.5.3 | 7 / 4 | |
| 17.5.2 | 7 / 4 | |
| 17.5.1 | 7 / 4 | |
| 17.5.0 | 7 / 4 | |
| 17.4.0 | 7 / 4 | |
| 17.3.0 | 7 / 4 | |
| 17.2.1 | 7 / 4 | |
| 17.2.0 | 7 / 4 | |
| 17.1.0 | 7 / 4 | |
| 17.0.0 | 7 / 4 | |
| 16.8.1 | 7 / 4 | |
| 16.8.0 | 7 / 4 | |
| 16.7.0 | 7 / 4 | |
| 16.6.0 | 7 / 4 | |
| 16.5.0 | 7 / 4 | |
| 16.4.0 | 7 / 4 | |
| 16.3.0 | 7 / 4 | |
| 16.2.0 | 7 / 4 | |
| 16.1.1 | 7 / 4 | |
| 16.1.0 | 7 / 4 | |
| 16.0.3 | 7 / 4 | |
| 16.0.2 | 7 / 4 | |
| 16.0.1 | 7 / 4 | |
| 16.0.0 | 7 / 4 | |
| 15.0.1 | 7 / 4 | |
| 15.0.0 | 7 / 4 | |
| 14.0.0 | 7 / 4 | |
| 13.7.1 | 7 / 4 | |
| 13.7.0 | 7 / 4 |
v17.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.