vega-scale
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 | encoded-string-file:build/vega-scale.js | AI (source-diff): Hex-encoded color scheme palette data, not payloads; inherent to this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Bundled color palette data drives size; benign for vega-scale. | ai | |
| provenance | no-provenance | AI (provenance): vega-scale is a long-established Vega ecosystem package; lack of Sigstore provenance is consistent with its historical publishing pattern and not a security concern. | ai | |
| dependencies | unvetted-dep:vega-time | AI (dependencies): vega-time is a sibling package in the official Vega monorepo; it is a legitimate and expected dependency for this package. | ai |
v8.1.2
2 findings[Accepted risk] Package 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-22, 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.
v8.1.1
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package 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 unknown date, 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.
v8.0.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.