vega-geo
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:vega-util | AI (dependencies): vega-util is a first-party Vega monorepo sub-package; a stable, expected dependency for vega-geo. | ai | |
| dependencies | unvetted-dep:vega-canvas | AI (dependencies): vega-canvas is a first-party Vega monorepo sub-package; a stable, expected dependency for vega-geo. | ai | |
| dependencies | unvetted-dep:vega-dataflow | AI (dependencies): vega-dataflow is a first-party Vega monorepo sub-package; a stable, expected dependency for vega-geo. | ai | |
| dependencies | unvetted-dep:vega-projection | AI (dependencies): vega-projection is a first-party Vega monorepo sub-package; a stable, expected dependency for vega-geo. | ai | |
| dependencies | unvetted-dep:vega-statistics | AI (dependencies): vega-statistics is a first-party Vega monorepo sub-package; a stable, expected dependency for vega-geo. | ai |
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (domoritz) than the most recent previously approved version (lhermann) on 2026-07-21, but domoritz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.