@graphql-hive/yoga
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): theguild-bot is The Guild's official CI publisher; transition from dotansimha is a known org-level change, not a compromise. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @graphql-hive/yoga is a legitimate The Guild package; Levenshtein match to 'koa' is a false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package with 2010 versions; sparse README is a style choice, not a spam indicator. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.48.2 | 3 / 0 | |
| 0.48.1 | 3 / 0 | |
| 0.48.0 | 3 / 0 | |
| 0.47.3 | 3 / 0 | |
| 0.47.2 | 3 / 0 | |
| 0.47.1 | 3 / 0 | |
| 0.47.0 | 3 / 0 | |
| 0.46.1 | 3 / 0 | |
| 0.46.0 | 3 / 0 | |
| 0.45.0 | 3 / 0 | |
| 0.44.0 | 3 / 0 | |
| 0.43.1 | 2 / 0 | |
| 0.43.0 | 2 / 0 | |
| 0.42.5 | 2 / 0 | |
| 0.42.4 | 2 / 0 | |
| 0.42.3 | 2 / 0 | |
| 0.42.2 | 2 / 0 | |
| 0.42.1 | 2 / 0 | |
| 0.42.0 | 2 / 0 | |
| 0.41.1 | 2 / 0 | |
| 0.41.0 | 2 / 0 | |
| 0.40.1 | 2 / 0 | |
| 0.40.0 | 2 / 0 | |
| 0.39.4 | 2 / 0 | |
| 0.39.3 | 2 / 0 | |
| 0.39.2 | 2 / 0 | |
| 0.39.1 | 3 / 0 | |
| 0.39.0 | 3 / 0 | |
| 0.38.2 | 3 / 0 | |
| 0.38.1 | 3 / 0 | |
| 0.38.0 | 3 / 0 | |
| 0.37.0 | 3 / 0 | |
| 0.36.0 | 3 / 0 | |
| 0.35.0 | 3 / 0 | |
| 0.34.1 | 3 / 0 | |
| 0.34.0 | 3 / 0 | |
| 0.33.3 | 2 / 0 | |
| 0.33.2 | 2 / 0 | |
| 0.33.1 | 2 / 0 |
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.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.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
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.