@splunk/visualization-encoding-parsers
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:@splunk/visualizations-shared | AI (phantom-deps): Same-org Splunk dep; likely a peer/shared dep used transitively in this monorepo package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 26.4.2 | 3 / 15 | |
| 26.4.1 | 3 / 15 | |
| 26.2.2 | 4 / 15 | |
| 25.13.2 | 4 / 17 |
v26.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.