chakra-react-select
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 is a minor metadata gap, not a supply chain risk. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump (v5→v6) with SLSA attestation explains the gap; not indicative of takeover. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 6.1.3 | 1 / 21 | |
| 6.1.1 | 1 / 22 | |
| 5.1.1 | 1 / 12 | |
| 5.1.0 | 1 / 21 |
v6.1.3
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.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.