@scalprum/react-core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD with SLSA attestation is a legitimate and expected supply chain improvement. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA provenance; consistent with a legitimate pipeline migration rather than account takeover. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived scalprum monorepo package; provenance not historically provided, stable false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 3 / 3 | |
| 0.12.0 | 3 / 3 | |
| 0.11.3 | 3 / 2 | |
| 0.11.2 | 3 / 2 | |
| 0.11.1 | 3 / 2 | |
| 0.11.0 | 3 / 2 | |
| 0.10.2 | 3 / 2 | |
| 0.10.1 | 3 / 2 | |
| 0.10.0 | 3 / 2 | |
| 0.9.5 | 3 / 2 | |
| 0.9.4 | 3 / 2 | |
| 0.9.3 | 3 / 2 | |
| 0.9.2 | 3 / 2 | |
| 0.9.1 | 3 / 2 | |
| 0.9.0 | 3 / 2 | |
| 0.8.0 | 3 / 2 |
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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.