← Home

apollo-server-module-graphiql

npm Repository Homepage

GraphiQL renderer for Apollo GraphQL Server

13
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

abernixfreiksenetjbaxleyiiimartijnwalravenmdgsashko

Keywords

GraphQLGraphiQLApolloJavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from sashko to martijnwalraven occurred in 2017 as a known legitimate Apollo team transition. martijnwalraven has 829 approved packages and has been active since the package's inception. ai

Versions (showing 13 of 13)

Version Deps Published
1.4.0 0 / 0
1.3.4 0 / 0
1.3.3 0 / 0
1.3.2 0 / 0
1.3.0 0 / 0
1.2.0 0 / 0
1.1.6 0 / 0
1.1.3 0 / 0
1.1.2 0 / 0
1.1.0 0 / 0
1.0.5 0 / 0
1.0.4 0 / 0
1.0.2 0 / 0

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.4

1 finding
LOW No provenance attestation provenance

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

v1.3.3

1 finding
LOW No provenance attestation provenance

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

v1.3.2

2 findings
HIGH Publisher changed: martijnwalraven → mdg (on 2017-12-19) provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.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.6

1 finding
LOW No provenance attestation provenance

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

v1.1.3

2 findings
HIGH Publisher changed: sashko → martijnwalraven (on 2017-10-05) provenance

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

v1.1.2

2 findings
HIGH Publisher changed: martijnwalraven → sashko (on 2017-08-24) provenance

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

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.5

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

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.

v1.0.2

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.