@rnacanvas/position-pairs
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rnacanvas/math | AI (phantom-deps): Same org scope; likely used transitively or via re-exports rather than direct import. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/value-check | AI (phantom-deps): Same org scope; likely used transitively or via re-exports rather than direct import. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 2 / 9 | |
| 2.6.1 | 2 / 9 | |
| 2.6.0 | 2 / 9 | |
| 2.5.1 | 2 / 9 | |
| 2.5.0 | 2 / 9 | |
| 2.4.0 | 2 / 9 |
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.