← Home

@graphql-hive/core

npm Repository Homepage
33
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

dotansimhakamilkisielaardatanenisdenjotheguild-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 33 of 33)

Version Deps Published
0.21.1 9 / 0
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
0.10.1 5 / 0
0.10.0 5 / 0
0.9.1 5 / 0
0.9.0 5 / 0
0.8.4 5 / 0
0.8.3 5 / 0
0.8.2 5 / 0
0.8.1 5 / 0
0.8.0 5 / 0
0.7.1 5 / 0
0.7.0 5 / 0
0.6.1 5 / 0
0.6.0 5 / 0
0.5.0 5 / 0
0.4.0 5 / 0
0.3.1 5 / 0

v0.10.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: kamilkisiela → dotansimha (on 2025-03-20, known maintainer) provenance

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.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.4

1 finding
LOW No provenance attestation provenance

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

v0.8.3

1 finding
LOW No provenance attestation provenance

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

v0.8.2

1 finding
LOW No provenance attestation provenance

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

v0.8.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.8.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.7.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.7.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.6.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.6.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.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.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.3.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.