@sqlrooms/cosmos
GPU-accelerated graph visualization components and slice for SQLRooms (powered by Cosmograph Cosmos).
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cosmograph/cosmos | AI (dependencies): @sqlrooms/cosmos is a direct wrapper around @cosmograph/cosmos; this dependency is intentional and stable across all versions. | ai | |
| phantom-deps | phantom-dep:@sqlrooms/project-config | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a stable pattern across this org's packages. | ai | |
| phantom-deps | phantom-dep:@sqlrooms/room-config | AI (phantom-deps): Same-org monorepo package; declared as dependency, phantom-dep is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all 97 versions and is not a security signal here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 7 / 0 | |
| 0.27.0 | 7 / 0 | |
| 0.26.0 | 8 / 0 | |
| 0.24.27 | 8 / 0 | |
| 0.24.24 | 8 / 0 | |
| 0.24.22 | 8 / 0 | |
| 0.24.19 | 8 / 0 | |
| 0.24.16 | 8 / 0 | |
| 0.24.10 | 8 / 0 | |
| 0.24.9 | 8 / 0 | |
| 0.24.5 | 8 / 0 | |
| 0.24.1 | 8 / 0 | |
| 0.24.0 | 8 / 0 | |
| 0.19.1 | 8 / 0 | |
| 0.18.1 | 8 / 0 | |
| 0.17.0 | 8 / 0 | |
| 0.16.4 | 8 / 0 | |
| 0.16.3 | 8 / 0 | |
| 0.16.0 | 8 / 0 | |
| 0.14.0 | 8 / 0 | |
| 0.13.1 | 8 / 0 | |
| 0.13.0 | 8 / 0 |
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.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.
v0.24.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.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.
v0.24.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.
v0.19.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.
v0.18.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.
v0.17.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.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.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.
v0.14.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.
v0.13.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.
v0.13.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.