@rnacanvas/draw
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): No provenance is common; no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/math | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled/re-exported packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/layout | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled/re-exported packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/draw.svg | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled/re-exported packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/ct | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled/re-exported packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/position-pairs | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled/re-exported packages. | ai | |
| phantom-deps | phantom-dep:@svgdotjs/svg.js | AI (phantom-deps): Referenced in config files; webpack bundling means direct import may not appear in source scan. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/base-pairs | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled/re-exported packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 14.5.3 | 13 / 10 | |
| 14.5.2 | 13 / 10 | |
| 14.5.1 | 13 / 10 | |
| 14.5.0 | 13 / 10 | |
| 14.4.0 | 12 / 10 | |
| 14.3.0 | 12 / 10 | |
| 14.2.0 | 12 / 10 | |
| 14.1.0 | 12 / 10 | |
| 14.0.0 | 11 / 10 | |
| 13.3.4 | 11 / 10 | |
| 13.3.3 | 11 / 10 | |
| 13.3.2 | 11 / 10 | |
| 13.3.1 | 11 / 10 | |
| 13.3.0 | 11 / 10 | |
| 13.2.0 | 11 / 10 | |
| 13.1.2 | 11 / 10 | |
| 13.1.1 | 11 / 10 | |
| 13.1.0 | 11 / 10 | |
| 13.0.0 | 11 / 10 | |
| 12.10.0 | 11 / 10 |
v14.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.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.
v13.0.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.
v12.10.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.