graphql-relay
A library to help construct a graphql-js server supporting react-relay.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Older publish (2017) by trusted Facebook engineer kassens; missing gitHead is expected for that era's tooling. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are all known Facebook engineers; kassens took over as part of normal team transition. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 encode/decode is core to GraphQL Relay's cursor-based pagination spec. This is expected, documented functionality. | ai | |
| provenance | no-provenance | AI (provenance): Older package predates Sigstore provenance; publisher is well-established with strong track record. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate Meta team transition from dschafer to wincent; both are known Meta/React engineers on the graphql org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all recognized Meta/React team members (fb, leebyron, josephsavona, etc.); legitimate org-level maintainer expansion. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.10.2 | 0 / 0 | |
| 0.10.1 | 0 / 0 | |
| 0.10.0 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.6.0 | 1 / 34 | |
| 0.5.5 | 0 / 34 | |
| 0.5.4 | 0 / 34 | |
| 0.5.3 | 0 / 34 | |
| 0.5.2 | 0 / 34 | |
| 0.5.1 | 0 / 34 | |
| 0.5.0 | 0 / 34 | |
| 0.4.4 | 0 / 34 | |
| 0.4.3 | 1 / 17 | |
| 0.4.2 | 1 / 17 | |
| 0.4.1 | 1 / 12 | |
| 0.4.0 | 1 / 12 | |
| 0.3.6 | 1 / 12 | |
| 0.3.5 | 1 / 12 | |
| 0.3.4 | 1 / 12 | |
| 0.3.3 | 1 / 12 | |
| 0.3.2 | 1 / 12 | |
| 0.3.1 | 1 / 12 | |
| 0.3.0 | 1 / 12 | |
| 0.2.0 | 1 / 10 | |
| 0.1.0 | 1 / 10 |
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-03-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
3 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: i1g.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-06-01. This could indicate a legitimate maintainer transition or an account compromise.
v0.6.0
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: kassens.
v0.5.5
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: kassens.
v0.5.4
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: kassens.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kassens.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-01. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-05-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-12-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsThis version was published by a different npm account than previous versions on 2015-10-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
v0.1.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.