@graphiql/plugin-history
## 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; legitimate automation change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-compiler-runtime is the official React compiler runtime, matching the devDep babel-plugin-react-compiler. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the official graphql/graphiql monorepo. leebyron is a GraphQL co-creator and legitimate maintainer; spam flag is a false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is a minor quality issue for this well-known GraphiQL plugin; not a security signal. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 3 / 8 | |
| 0.4.1 | 2 / 7 | |
| 0.4.0 | 2 / 7 | |
| 0.3.0 | 4 / 7 | |
| 0.2.2 | 4 / 7 | |
| 0.2.1 | 4 / 7 | |
| 0.2.0 | 4 / 7 | |
| 0.1.0 | 4 / 7 | |
| 0.0.2 | 3 / 7 | |
| 0.0.1 | 3 / 7 | |
| 0.0.0 | 3 / 7 |
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.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.