graphql-http
Simple, pluggable, zero-dependency, GraphQL over HTTP spec compliant server, client and audit suite.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transfer to enisdenjo (graphql-ws author, 6250 approved versions). Well-known GraphQL ecosystem maintainer took over abandoned package name. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from l8d to enisdenjo is a legitimate package transfer to a trusted, established npm publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): enisdenjo is the new legitimate maintainer after package transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous maintainers removed as part of legitimate package transfer/rewrite. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from complete rewrite: zero-dep implementation with CJS/ESM/UMD builds replacing minimal 0.2.0 version. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.22.4 | 0 / 38 | |
| 1.22.3 | 0 / 38 | |
| 1.22.2 | 0 / 38 | |
| 1.22.1 | 0 / 38 | |
| 1.22.0 | 0 / 38 | |
| 1.21.0 | 0 / 38 | |
| 1.20.0 | 0 / 47 | |
| 1.19.0 | 0 / 44 | |
| 1.18.0 | 0 / 42 | |
| 1.17.1 | 0 / 41 | |
| 1.17.0 | 0 / 41 | |
| 1.16.0 | 0 / 41 | |
| 1.15.0 | 0 / 41 | |
| 1.14.0 | 0 / 38 | |
| 1.13.0 | 0 / 38 | |
| 1.12.0 | 0 / 38 | |
| 1.11.0 | 0 / 38 | |
| 1.10.0 | 0 / 34 | |
| 1.9.0 | 0 / 33 | |
| 1.8.0 | 0 / 33 | |
| 1.7.2 | 0 / 33 | |
| 1.7.1 | 0 / 33 | |
| 1.7.0 | 0 / 33 | |
| 1.6.1 | 0 / 29 | |
| 1.6.0 | 0 / 30 | |
| 1.5.0 | 0 / 30 | |
| 1.4.0 | 0 / 30 | |
| 1.3.0 | 0 / 30 | |
| 1.2.0 | 0 / 30 | |
| 1.1.0 | 0 / 30 | |
| 1.0.0 | 0 / 30 | |
| 0.2.0 | 2 / 4 | |
| 0.1.1 | 2 / 4 | |
| 0.1.0 | 2 / 4 | |
| 0.0.5 | 1 / 7 | |
| 0.0.4 | 1 / 7 | |
| 0.0.3 | 1 / 7 | |
| 0.0.2 | 1 / 7 |
v1.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
3 findingsAll previous maintainers (ericf89, l8d, petermelias) were replaced by new maintainers (enisdenjo). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2022-08-04. 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.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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-11-01. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
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-09-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.