← Home

graphql-compiler

npm

A Code-generation toolkit for GraphQL

6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

fbjstejadakassens

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): The 'fb' spam flag is a false positive — fb is Facebook's legitimate npm org. Missing metadata fields are a minor gap in an old, established package, not a spam indicator. ai
semgrep semgrep:child-process-import AI (semgrep): child_process usage is expected in this package due to fb-watchman dependency, which uses it to communicate with the watchman file-watching daemon. Consistent with documented purpose. ai

Versions (showing 6 of 6)

Version Deps Published
1.7.0 3 / 0
1.6.2 3 / 0
1.6.1 3 / 0
1.6.0 3 / 0
1.5.0 3 / 0
0.0.1 0 / 0

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

2 findings
HIGH Publisher changed: yanj → jstejada (on 2018-04-26) provenance

This version was published by a different npm account than previous versions on 2018-04-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.1

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.