@xstate/react
XState tools for React
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): Established XState monorepo package with strong publisher track record; missing gitHead likely reflects a CI/CD pipeline change for the v5 major release, not a supply chain concern. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a best-practice gap, not a security risk, for this well-established package with a trusted automated publisher. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 2 / 8 | |
| 6.0.0 | 2 / 8 | |
| 5.0.5 | 2 / 9 | |
| 5.0.4 | 2 / 9 | |
| 5.0.3 | 2 / 9 | |
| 5.0.2 | 2 / 9 | |
| 5.0.1 | 2 / 9 | |
| 5.0.0 | 2 / 9 | |
| 4.1.3 | 2 / 9 | |
| 4.1.2 | 2 / 8 | |
| 4.1.1 | 2 / 10 | |
| 4.1.0 | 2 / 10 | |
| 4.0.3 | 2 / 10 | |
| 4.0.2 | 2 / 10 | |
| 4.0.1 | 2 / 10 | |
| 4.0.0 | 2 / 10 | |
| 3.2.2 | 2 / 21 | |
| 3.2.1 | 2 / 21 | |
| 3.2.0 | 2 / 21 | |
| 3.1.2 | 2 / 21 | |
| 3.1.1 | 2 / 21 | |
| 3.1.0 | 2 / 21 | |
| 3.0.2 | 2 / 21 | |
| 3.0.1 | 2 / 21 | |
| 3.0.0 | 2 / 21 | |
| 2.0.1 | 2 / 20 | |
| 2.0.0 | 2 / 20 | |
| 1.6.3 | 2 / 20 | |
| 1.6.2 | 2 / 20 | |
| 1.6.1 | 2 / 20 | |
| 1.6.0 | 2 / 20 | |
| 1.5.1 | 2 / 20 | |
| 1.5.0 | 2 / 20 | |
| 1.4.0 | 2 / 20 | |
| 1.3.4 | 2 / 20 | |
| 1.3.3 | 2 / 20 | |
| 1.3.2 | 2 / 20 | |
| 1.3.1 | 2 / 20 | |
| 1.3.0 | 2 / 20 | |
| 1.2.2 | 2 / 20 | |
| 1.2.1 | 2 / 18 | |
| 1.2.0 | 2 / 17 | |
| 1.1.0 | 2 / 14 | |
| 1.0.3 | 2 / 14 | |
| 1.0.2 | 2 / 14 | |
| 1.0.1 | 2 / 14 | |
| 1.0.0 | 2 / 14 | |
| 0.8.1 | 0 / 15 | |
| 0.8.0 | 0 / 14 | |
| 0.7.1 | 0 / 14 | |
| 0.7.0 | 0 / 14 |
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.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: xstate-release-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
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: xstate-release-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
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: xstate-release-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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: xstate-release-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xstate-release-bot.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.