@rnacanvas/tooltips
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:jquery | AI (phantom-deps): Bundled via webpack; direct imports may not be visible to static import analysis. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/boxes | AI (phantom-deps): Same-org dep bundled via webpack; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 2 / 13 | |
| 1.6.0 | 2 / 13 | |
| 1.5.1 | 2 / 13 | |
| 1.5.0 | 2 / 13 | |
| 1.4.0 | 2 / 13 | |
| 1.3.0 | 2 / 13 |
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.