@graphcommerce/graphql-codegen-near-operation-file
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package; missing description is a consistent pattern across the graphcommerce org, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with clean track record; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@types/parse-filepath | AI (dependencies): Companion @types package for the declared parse-filepath runtime dep; no risk. | ai | |
| phantom-deps | phantom-dep:@types/parse-filepath | AI (phantom-deps): Type-only dependency; not imported at runtime, false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.0.3 | 7 / 0 | |
| 10.0.2 | 7 / 0 | |
| 10.0.1 | 7 / 0 | |
| 10.0.0 | 7 / 0 |
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.