@cosmos.gl/graph
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is consistent across all versions and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:d3-ease | AI (phantom-deps): d3 modules are bundled/tree-shaken; phantom-dep fires on config references, not missing imports. | ai | |
| phantom-deps | phantom-dep:d3-array | AI (phantom-deps): Same bundled d3 pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-color | AI (phantom-deps): Same bundled d3 pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:random | AI (phantom-deps): random is a runtime dep used indirectly via bundled output; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:gl-bench | AI (phantom-deps): gl-bench is a benchmarking dep referenced in config; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:d3-selection | AI (phantom-deps): Same bundled d3 pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-transition | AI (phantom-deps): Same bundled d3 pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-scale | AI (phantom-deps): Same bundled d3 pattern; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.6.4 | 13 / 44 | |
| 2.6.2 | 13 / 44 | |
| 2.6.1 | 13 / 44 | |
| 2.6.0 | 13 / 44 | |
| 2.5.0 | 13 / 44 | |
| 2.4.0 | 13 / 44 | |
| 2.3.1 | 13 / 44 | |
| 2.3.0 | 13 / 44 | |
| 2.2.1 | 12 / 43 | |
| 2.2.0 | 12 / 43 | |
| 2.1.0 | 12 / 43 | |
| 2.0.0 | 12 / 43 |
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.