react-relay
A framework for building GraphQL-driven React applications.
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 | publisher-changed | AI (provenance): Migration from relay-bot to GitHub Actions CI; SLSA provenance confirms legitimate publish. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Meta team reorganization; package remains under facebook/relay org. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI publish of multiple packages in the relay monorepo; expected pattern. | ai | |
| phantom-deps | phantom-dep:nullthrows | AI (phantom-deps): nullthrows is declared and used transitively in relay's compiled output. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 5 / 0 | |
| 21.0.0 | 5 / 0 | |
| 20.1.1 | 5 / 0 | |
| 20.1.0 | 5 / 0 | |
| 20.0.0 | 5 / 0 |
v21.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v21.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.