@rnacanvas/draw.bases.numberings
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rnacanvas/boxes | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/points | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/vectors | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/draw.svg | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/utilities | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled TypeScript packages. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/vectors.oopified | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for bundled TypeScript packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 7 / 10 | |
| 4.0.1 | 7 / 10 | |
| 4.0.0 | 7 / 10 | |
| 3.3.0 | 7 / 10 | |
| 3.2.1 | 6 / 10 | |
| 3.2.0 | 6 / 10 | |
| 3.1.0 | 6 / 10 | |
| 3.0.0 | 6 / 10 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.