graphql-zeus
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:graphql-zeus-core | AI (dependencies): First-party sibling package in the graphql-zeus ecosystem; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:graphql-zeus-jsonschema | AI (dependencies): First-party sibling package in the graphql-zeus ecosystem; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:graphql-js-tree | AI (dependencies): First-party graphql-editor org package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:config-maker | AI (dependencies): Long-standing dependency in this package; no material change from prior approved version. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 7 / 0 | |
| 7.2.0 | 7 / 0 | |
| 7.1.9 | 7 / 0 | |
| 7.1.8 | 7 / 0 | |
| 7.1.6 | 6 / 0 | |
| 7.1.5 | 6 / 0 | |
| 7.1.4 | 6 / 0 | |
| 7.1.3 | 6 / 0 | |
| 7.1.2 | 5 / 0 | |
| 7.1.1 | 5 / 0 | |
| 7.1.0 | 5 / 0 | |
| 7.0.10 | 5 / 0 | |
| 7.0.9 | 5 / 0 | |
| 7.0.8 | 5 / 0 | |
| 7.0.7 | 5 / 0 | |
| 7.0.6 | 5 / 0 |
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.