@rpldy/abort
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established react-uploady monorepo package; no provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@rpldy/simple-state | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.13.0 | 3 / 1 | |
| 1.12.0 | 3 / 1 | |
| 1.11.0 | 3 / 1 | |
| 1.10.0 | 3 / 1 | |
| 1.9.1 | 3 / 1 | |
| 1.9.0 | 3 / 1 | |
| 1.8.3 | 3 / 1 | |
| 1.8.2 | 3 / 1 | |
| 1.8.1 | 3 / 1 |
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.