graphql-ruby-client
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): CLI loads local operation file paths by design; not attacker-controlled remote code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README is normal for this long-standing official client, not spam. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.15.2 | 2 / 23 | |
| 1.15.1 | 2 / 23 | |
| 1.15.0 | 2 / 23 | |
| 1.14.9 | 2 / 23 | |
| 1.14.8 | 2 / 23 | |
| 1.14.7 | 2 / 23 | |
| 1.14.6 | 2 / 23 | |
| 1.14.5 | 2 / 23 | |
| 1.14.4 | 2 / 23 | |
| 1.14.1 | 2 / 23 | |
| 1.14.0 | 2 / 23 |
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rmosolgo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.