@rnacanvas/forms.layout
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): jquery is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/jquery | AI (phantom-deps): Type-only dep loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/forms | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@svgdotjs/svg.js | AI (phantom-deps): Declared runtime dep referenced via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/layout | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/value-check | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.13.0 | 8 / 11 | |
| 2.12.3 | 8 / 11 | |
| 2.12.2 | 8 / 11 | |
| 2.12.1 | 8 / 11 | |
| 2.12.0 | 8 / 11 | |
| 2.11.1 | 8 / 11 | |
| 2.11.0 | 8 / 11 | |
| 2.10.1 | 8 / 11 | |
| 2.10.0 | 8 / 11 | |
| 2.9.1 | 8 / 11 | |
| 2.9.0 | 8 / 11 | |
| 2.8.3 | 8 / 11 | |
| 2.8.2 | 8 / 11 | |
| 2.8.1 | 8 / 11 | |
| 2.8.0 | 8 / 11 | |
| 2.7.7 | 7 / 11 |
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.