@gravity-ui/graph
Modern graph editor component
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is declared and used in build/export system; stable false positive. | ai | |
| dependencies | unvetted-dep:intersects | AI (dependencies): intersects is a benign geometry utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Gravity-UI org packages consistently lack provenance; not a risk signal for this publisher. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.10.3 | 5 / 58 | |
| 1.10.2 | 5 / 58 | |
| 1.10.1 | 5 / 58 | |
| 1.10.0 | 5 / 58 | |
| 1.7.1 | 5 / 55 | |
| 1.6.1 | 5 / 55 | |
| 1.6.0 | 5 / 55 | |
| 1.3.6 | 4 / 56 | |
| 1.0.0 | 4 / 59 |
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.