@react-spring/core
The platform-agnostic core of `react-spring`
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence reflects CI publish change, not a supply chain concern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): The Levenshtein match to 'cors' is a false positive; '@react-spring/core' is clearly react-spring related, not a cors typosquat. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.1.0 | 3 / 1 | |
| 10.0.4 | 3 / 1 | |
| 10.0.2 | 3 / 0 | |
| 10.0.1 | 3 / 0 |
v10.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.