← Home

graphql-client

npm Repository Homepage

Small http client based on the fetch api. Uses isomorphic-fetch for wider support

8
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

nordsimonsimon.nord

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change (simon.nord → nordsimon) occurred in 2016 and aligns with the GitHub repo URL; consistent with a username rename. No compromise indicators across 8+ years of history. ai
bogus-package bogus-package AI (bogus-package): Package is 10+ years old with consistent downloads and 8 approved versions. Missing metadata reflects early npm publishing norms, not spam or malicious intent. ai
npm-metadata no-description AI (npm-metadata): Established package with long history; missing description is a metadata quality issue, not a security signal. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence is expected for packages of this age. ai

Versions (showing 8 of 8)

Version Deps Published
2.0.1 1 / 0
2.0.0 1 / 0
1.1.0 1 / 0
1.0.4 1 / 0
1.0.3 1 / 0
1.0.2 1 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

2 findings
HIGH Publisher changed: simon.nord → nordsimon (on 2016-05-24) provenance

This version was published by a different npm account than previous versions on 2016-05-24. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.