@graphprotocol/gds-react
React components for The Graph Design System
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Local file-only skill updater with strict exit conditions; no network/exec of remote code. | ai | |
| provenance | missing-githead | AI (provenance): CI-published monorepo package; benign metadata gap, no behavior change. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dep rename (@base-ui-components -> @base-ui) not a novel malicious dependency. | ai | |
| dependencies | unvetted-dep:ts-extras | AI (dependencies): ts-extras is a well-known TypeScript utility library; low risk for a React component package. | ai | |
| phantom-deps | phantom-dep:@graphprotocol/gds-icons | AI (phantom-deps): Same-org scoped package; declared as a dep and re-exported via ./icons export — phantom-dep is a false positive here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 18 / 24 | |
| 0.3.4 | 18 / 21 | |
| 0.3.2 | 18 / 21 | |
| 0.2.6 | 17 / 20 | |
| 0.2.5 | 16 / 20 | |
| 0.2.4 | 16 / 20 | |
| 0.2.3 | 16 / 20 | |
| 0.2.2 | 16 / 20 | |
| 0.2.1 | 16 / 20 | |
| 0.2.0 | 16 / 20 | |
| 0.1.2 | 16 / 20 | |
| 0.1.1 | 16 / 20 | |
| 0.1.0 | 16 / 19 | |
| 0.0.1 | 16 / 19 |
v0.5.3
2 findingsScript: node scripts/update-skill.cjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
3 findingsScript: node scripts/update-skill.cjs
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.