@graphql-hive/cli MIT 34 versions

@graphql-hive/cli

npm Repository Homepage

A CLI util to manage and control your GraphQL Hive

34

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

dotansimhakamilkisielaardatanenisdenjotheguild-bot

Keywords

graphql

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@graphql-hive/core	AI (dependencies): First-party sibling package from the same graphql-hive org; not a third-party risk.	ai	2026/05/03
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	2026/04/29
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	2026/04/29
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	2026/04/29

Versions (showing 34 of 34)

Version	Deps	Published
0.60.0	20 / 6	2026-06-01
0.59.2	20 / 6	2026-05-12
0.59.1	20 / 6	2026-04-30
0.59.0	20 / 6	2026-03-17
0.58.5	20 / 6	2026-03-06
0.58.4	20 / 6	2026-03-05
0.58.3	20 / 6	2026-02-20
0.58.2	20 / 6	2026-02-19
0.58.1	20 / 6	2026-02-18
0.58.0	20 / 6	2026-02-03
0.57.4	20 / 6	2026-01-27
0.57.3	20 / 6	2026-01-21
0.57.2	20 / 6	2026-01-20
0.57.1	20 / 6	2026-01-12
0.57.0	20 / 6	2026-01-07
0.56.0	20 / 6	2025-12-01
0.55.1	20 / 6	2025-12-01
0.55.0	20 / 6	2025-11-27
0.54.0	20 / 6	2025-11-25
0.53.5	20 / 6	2025-11-24
0.53.4	20 / 6	2025-11-18
0.53.3	20 / 6	2025-11-17
0.53.2	20 / 6	2025-11-12
0.53.1	20 / 6	2025-11-11
0.53.0	20 / 6	2025-11-10
0.52.1	19 / 6	2025-11-07
0.52.0	19 / 6	2025-10-27
0.51.0	19 / 6	2025-10-13
0.50.5	19 / 6	2025-10-07
0.50.4	19 / 6	2025-08-28
0.50.3	19 / 6	2025-07-10
0.50.2	19 / 6	2025-06-30
0.50.1	19 / 6	2025-05-21
0.50.0	19 / 6	2025-05-14

v0.60.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.59.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.59.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.58.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.57.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.57.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.57.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.57.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.57.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.56.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.55.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.55.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.54.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.53.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.53.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.52.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.52.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.51.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.50.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.50.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.50.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.50.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.50.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.50.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.