@graphql-typed-document-node/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @graphql-typed-document-node/core; 'core' vs 'cors' is a spurious Levenshtein match. 13M weekly downloads, established package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Types-only GraphQL package; tiny payload, no description, no keywords are all expected for a .d.ts-only utility package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Well-known types-only package in the GraphQL ecosystem; missing description is not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 0 / 0 | |
| 3.1.2 | 0 / 0 | |
| 3.1.1 | 0 / 3 | |
| 3.1.0 | 0 / 0 | |
| 3.0.0 | 0 / 3 | |
| 2.1.0 | 2 / 10 | |
| 2.0.0 | 2 / 10 | |
| 1.0.0 | 0 / 6 | |
| 0.0.1 | 0 / 5 |
v3.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.