vega-voronoi
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Growth is a new sourcemap file, not injected payload. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known monorepo maintainer addition, consistent with vega org practices. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty index.js is intentional — package uses ESM exports map pointing to build/vega-voronoi.js. Sparse README is typical for Vega monorepo sub-packages. Not a spam/bogus package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.1.2 | 3 / 1 | |
| 5.1.1 | 3 / 1 | |
| 5.1.0 | 3 / 1 | |
| 5.0.0 | 3 / 1 | |
| 4.2.5 | 3 / 1 |
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.
v4.2.5
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-01-06, 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.