@graphql-hive/cli
A CLI util to manage and control your GraphQL Hive
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:graphql-tag | AI (phantom-deps): Likely used indirectly via GraphQL tooling/codegen; established package with no malicious indicators. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Used for TS execution tooling, not a runtime import; benign for this CLI. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Used in build scripts (prebuild), config-referenced not import-referenced. | ai | |
| dependencies | unvetted-dep:git-parse | AI (dependencies): Small utility dep for git metadata parsing, long-standing use in this CLI. | ai | |
| dependencies | unvetted-dep:@graphql-hive/core | AI (dependencies): First-party sibling package from the same graphql-hive org; not a third-party risk. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Levenshtein distance match is spurious; @graphql-hive/cli is a well-known GraphQL Hive CLI, not a typosquat of joi. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-update | AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable pattern for this package. | ai |
Versions (showing 100 of 161)
| Version | Deps | Published |
|---|---|---|
| 0.61.0 | 20 / 6 | |
| 0.60.3 | 20 / 6 | |
| 0.60.2 | 20 / 6 | |
| 0.60.1 | 20 / 6 | |
| 0.60.0 | 20 / 6 | |
| 0.59.2 | 20 / 6 | |
| 0.59.1 | 20 / 6 | |
| 0.59.0 | 20 / 6 | |
| 0.58.5 | 20 / 6 | |
| 0.58.4 | 20 / 6 | |
| 0.58.3 | 20 / 6 | |
| 0.58.2 | 20 / 6 | |
| 0.58.1 | 20 / 6 | |
| 0.58.0 | 20 / 6 | |
| 0.57.4 | 20 / 6 | |
| 0.57.3 | 20 / 6 | |
| 0.57.2 | 20 / 6 | |
| 0.57.1 | 20 / 6 | |
| 0.57.0 | 20 / 6 | |
| 0.56.0 | 20 / 6 | |
| 0.55.1 | 20 / 6 | |
| 0.55.0 | 20 / 6 | |
| 0.54.0 | 20 / 6 | |
| 0.53.5 | 20 / 6 | |
| 0.53.4 | 20 / 6 | |
| 0.53.3 | 20 / 6 | |
| 0.53.2 | 20 / 6 | |
| 0.53.1 | 20 / 6 | |
| 0.53.0 | 20 / 6 | |
| 0.52.1 | 19 / 6 | |
| 0.52.0 | 19 / 6 | |
| 0.51.0 | 19 / 6 | |
| 0.50.5 | 19 / 6 | |
| 0.50.4 | 19 / 6 | |
| 0.50.3 | 19 / 6 | |
| 0.50.2 | 19 / 6 | |
| 0.50.1 | 19 / 6 | |
| 0.50.0 | 19 / 6 | |
| 0.49.1 | 19 / 6 | |
| 0.49.0 | 19 / 6 | |
| 0.48.3 | 19 / 6 | |
| 0.48.2 | 19 / 6 | |
| 0.48.1 | 19 / 6 | |
| 0.48.0 | 19 / 6 | |
| 0.47.0 | 19 / 6 | |
| 0.46.1 | 19 / 6 | |
| 0.46.0 | 20 / 6 | |
| 0.45.0 | 20 / 6 | |
| 0.44.5 | 20 / 6 | |
| 0.44.4 | 20 / 6 | |
| 0.44.3 | 20 / 6 | |
| 0.44.2 | 20 / 7 | |
| 0.44.1 | 20 / 7 | |
| 0.44.0 | 20 / 7 | |
| 0.43.0 | 20 / 7 | |
| 0.42.1 | 20 / 7 | |
| 0.42.0 | 20 / 7 | |
| 0.41.0 | 20 / 7 | |
| 0.40.1 | 20 / 7 | |
| 0.40.0 | 20 / 7 | |
| 0.39.0 | 20 / 7 | |
| 0.38.5 | 19 / 6 | |
| 0.38.4 | 19 / 6 | |
| 0.38.3 | 20 / 6 | |
| 0.38.2 | 20 / 6 | |
| 0.38.1 | 20 / 6 | |
| 0.38.0 | 20 / 6 | |
| 0.37.0 | 20 / 6 | |
| 0.36.0 | 20 / 6 | |
| 0.35.0 | 20 / 6 | |
| 0.34.1 | 20 / 6 | |
| 0.34.0 | 20 / 6 | |
| 0.33.1 | 21 / 6 | |
| 0.33.0 | 21 / 6 | |
| 0.32.1 | 21 / 6 | |
| 0.32.0 | 21 / 6 | |
| 0.31.0 | 21 / 6 | |
| 0.30.4 | 21 / 6 | |
| 0.30.3 | 22 / 6 | |
| 0.30.2 | 22 / 6 | |
| 0.30.1 | 22 / 6 | |
| 0.30.0 | 22 / 6 | |
| 0.29.0 | 22 / 5 | |
| 0.28.0 | 22 / 5 | |
| 0.27.1 | 22 / 5 | |
| 0.27.0 | 22 / 5 | |
| 0.26.0 | 22 / 5 | |
| 0.25.1 | 21 / 6 | |
| 0.25.0 | 21 / 6 | |
| 0.24.0 | 21 / 6 | |
| 0.23.0 | 21 / 6 | |
| 0.22.0 | 24 / 4 | |
| 0.21.0 | 24 / 4 | |
| 0.20.2 | 22 / 4 | |
| 0.20.1 | 22 / 4 | |
| 0.20.0 | 22 / 4 | |
| 0.19.12 | 22 / 4 | |
| 0.19.11 | 22 / 4 | |
| 0.19.10 | 22 / 4 | |
| 0.19.9 | 22 / 4 |
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dotansimha) than the most recent previously approved version (kamilkisiela) on 2025-03-20, but dotansimha is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.