@sqlrooms/vega
Vega-Lite chart components and AI chart tool integration for SQLRooms.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vega | AI (phantom-deps): vega is a declared dep used via react-vega wrapper; phantom-dep heuristic fires but it's a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vega-lite | AI (phantom-deps): vega-lite is a declared dep used via react-vega/config; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@openassistant/utils | AI (dependencies): Alpha utility dep from a known ecosystem; low risk given publisher track record and no other indicators. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common; no other risk signals present for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 13 / 1 | |
| 0.26.0 | 10 / 0 | |
| 0.24.23 | 9 / 0 | |
| 0.24.22 | 9 / 0 | |
| 0.24.11 | 9 / 0 | |
| 0.24.7 | 9 / 0 | |
| 0.24.6 | 9 / 0 | |
| 0.24.2 | 9 / 0 | |
| 0.24.0 | 9 / 0 | |
| 0.22.0 | 9 / 0 | |
| 0.21.0 | 9 / 0 | |
| 0.19.2 | 8 / 0 | |
| 0.19.1 | 8 / 0 | |
| 0.19.0 | 8 / 0 | |
| 0.18.1 | 8 / 0 | |
| 0.18.0 | 8 / 0 | |
| 0.17.0 | 8 / 0 | |
| 0.16.4 | 8 / 0 | |
| 0.16.3 | 8 / 0 | |
| 0.16.2 | 8 / 0 | |
| 0.16.1 | 8 / 0 | |
| 0.16.0 | 8 / 0 | |
| 0.15.0 | 8 / 0 | |
| 0.14.0 | 8 / 0 | |
| 0.13.2 | 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.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.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.