← Home

graphql-language-service-config

npm Repository Homepage

A tool-kit for accessing and using `.graphqlrc` configuration files

18
Versions
—
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

asiandrummerwincentleebyronfb

Keywords

graphql

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change (asiandrummer → wincent) occurred in 2017; wincent (Greg Hurrell) is listed as a contributor in package.json and has a strong track record (1023 approved packages). Legitimate maintainer transition. ai
phantom-deps phantom-dep:graphql-language-service-types AI (phantom-deps): graphql-language-service-types is declared as a runtime dependency in package.json; it's used as a type dependency rather than a direct import, which is expected for this config/types package. ai

Versions (showing 18 of 18)

Version Deps Published
0.0.19 1 / 0
0.0.18 1 / 0
0.0.17 1 / 0
0.0.16 1 / 0
0.0.15 1 / 0
0.0.13 1 / 0
0.0.12 1 / 0
0.0.11 1 / 0
0.0.10 1 / 0
0.0.9 1 / 0
0.0.8 1 / 0
0.0.7 1 / 0
0.0.6 1 / 0
0.0.5 1 / 0
0.0.4 1 / 33
0.0.3 1 / 31
0.0.2 1 / 31
0.0.1 1 / 31

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

1 finding
LOW No provenance attestation provenance

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

v0.0.17

1 finding
LOW No provenance attestation provenance

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

v0.0.16

1 finding
LOW No provenance attestation provenance

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

v0.0.15

2 findings
HIGH Publisher changed: wincent → asiandrummer (on 2017-06-01) provenance

This version was published by a different npm account than previous versions on 2017-06-01. 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.13

1 finding
LOW No provenance attestation provenance

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

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

2 findings
HIGH Publisher changed: wincent → asiandrummer (on 2017-04-02) provenance

This version was published by a different npm account than previous versions on 2017-04-02. 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.5

2 findings
HIGH Publisher changed: asiandrummer → wincent (on 2017-03-29) provenance

This version was published by a different npm account than previous versions on 2017-03-29. 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.4

2 findings
HIGH Publisher changed: wincent → asiandrummer (on 2017-02-19) provenance

This version was published by a different npm account than previous versions on 2017-02-19. 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.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
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.