← Home

@rnacanvas/layout

2
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pzhaojohnson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@rnacanvas/math AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/points AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/circles AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/vectors AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/utilities AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/base-pairs AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/value-check AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/position-pairs AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
phantom-deps phantom-dep:@rnacanvas/points.oopified AI (phantom-deps): Same-org dep; heuristic false positive for this package family. ai
provenance no-provenance AI (provenance): Consistent with all prior approved versions of this publisher; not a risk signal here. ai

Versions (showing 2 of 2)

Version Deps Published
1.1.1 9 / 10
1.1.0 9 / 10

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.