@graphiql/plugin-doc-explorer
## API
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from maintainer to GitHub Actions CI/CD with SLSA provenance; expected for graphql org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-compiler-runtime is the official React compiler runtime, consistent with React 19 adoption. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is part of the official graphiql monorepo. Flagged maintainer 'leebyron' is Lee Byron, GraphQL co-creator — spam flag is a false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 3 / 11 | |
| 0.4.1 | 2 / 10 | |
| 0.4.0 | 2 / 10 | |
| 0.3.0 | 4 / 10 | |
| 0.2.2 | 4 / 10 | |
| 0.2.1 | 4 / 10 | |
| 0.2.0 | 4 / 10 | |
| 0.1.0 | 4 / 10 | |
| 0.0.2 | 3 / 10 | |
| 0.0.1 | 3 / 10 |
v0.4.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.