@rnacanvas/forms.edit
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): Consistent across all 126 versions from this publisher; not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/forms | AI (phantom-deps): Same-org scoped dep; heuristic false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/draw.svg | AI (phantom-deps): Same-org scoped dep; heuristic false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/base-pairs | AI (phantom-deps): Same-org scoped dep; heuristic false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/consensize | AI (phantom-deps): Same-org scoped dep; heuristic false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@rnacanvas/value-check | AI (phantom-deps): Same-org scoped dep; heuristic false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash declared as runtime dep; phantom-dep heuristic fires on config-only reference but dep is legitimately declared. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Type-only package; framework-scoped convention, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@svgdotjs/svg.js | AI (phantom-deps): Declared runtime dep used via config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 18.1.3 | 10 / 13 | |
| 18.1.2 | 10 / 13 | |
| 18.1.1 | 10 / 13 | |
| 18.1.0 | 10 / 13 | |
| 18.0.6 | 10 / 13 | |
| 18.0.5 | 10 / 13 | |
| 18.0.4 | 10 / 13 | |
| 18.0.3 | 10 / 13 | |
| 18.0.2 | 10 / 13 | |
| 18.0.1 | 10 / 13 | |
| 18.0.0 | 11 / 13 | |
| 17.0.2 | 11 / 13 | |
| 17.0.1 | 11 / 13 | |
| 17.0.0 | 11 / 13 | |
| 16.1.3 | 11 / 13 | |
| 16.1.2 | 11 / 13 | |
| 16.1.1 | 11 / 13 | |
| 16.1.0 | 11 / 13 | |
| 16.0.1 | 11 / 13 | |
| 16.0.0 | 11 / 13 | |
| 15.1.0 | 11 / 13 | |
| 15.0.0 | 11 / 13 | |
| 14.1.0 | 11 / 13 |
v18.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.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.
v14.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.