@graphql-inspector/validate-command
Validate Documents in GraphQL Inspector
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@graphql-inspector/logger | AI (dependencies): Sibling monorepo package from the same trusted publisher; not an independent risk. | ai | |
| dependencies | unvetted-dep:@graphql-inspector/commands | AI (dependencies): Sibling monorepo package from the same trusted publisher; not an independent risk. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dep used implicitly by TypeScript compiled output; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.0.20 | 5 / 0 | |
| 5.0.16 | 5 / 0 | |
| 5.0.11 | 5 / 0 | |
| 5.0.10 | 5 / 0 | |
| 5.0.9 | 5 / 0 |
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.