@graphql-hive/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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate org-wide transition from dotansimha to theguild-bot; bot account has strong approval history across The Guild packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): js-md5 is a well-established hashing library; addition is consistent with schema fingerprinting in a GraphQL observability package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @graphql-hive package from The Guild; Levenshtein match to 'cors' is a false positive with no semantic relationship. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.21.0 | 9 / 0 | |
| 0.20.2 | 9 / 0 | |
| 0.20.1 | 9 / 0 | |
| 0.20.0 | 9 / 0 | |
| 0.19.0 | 9 / 0 | |
| 0.18.0 | 9 / 0 | |
| 0.17.0 | 9 / 0 | |
| 0.16.0 | 9 / 0 | |
| 0.15.1 | 8 / 0 | |
| 0.15.0 | 8 / 0 | |
| 0.14.0 | 6 / 0 | |
| 0.13.2 | 6 / 0 | |
| 0.13.1 | 6 / 0 | |
| 0.13.0 | 6 / 0 | |
| 0.12.0 | 5 / 0 | |
| 0.11.0 | 5 / 0 |
v0.21.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
2 findingsPackage name '@graphql-hive/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
2 findingsThis version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.