@splunk/visualization-themes
Dashboard themes for visualizations
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Custom Splunk license reference; consistent across versions. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): First-party Splunk dependency consistent with this visualization-themes package; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Splunk org package; provenance attestation not used across their npm publishing pipeline. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 28.6.0 | 2 / 1 | |
| 28.5.3 | 2 / 1 | |
| 28.5.2 | 2 / 1 | |
| 28.5.1 | 2 / 1 | |
| 28.5.0 | 2 / 1 | |
| 28.4.0 | 2 / 1 | |
| 28.3.0 | 2 / 1 | |
| 28.2.3 | 2 / 1 | |
| 28.2.2 | 2 / 1 | |
| 28.2.1 | 2 / 1 | |
| 28.2.0 | 2 / 1 | |
| 28.1.0 | 2 / 1 | |
| 28.0.0 | 2 / 1 | |
| 27.5.2 | 1 / 1 | |
| 27.5.1 | 1 / 1 | |
| 27.2.3 | 1 / 1 | |
| 27.2.2 | 1 / 1 | |
| 26.4.2 | 2 / 3 | |
| 26.2.2 | 2 / 3 | |
| 25.13.2 | 2 / 5 |
v28.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.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.
v28.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.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.
v28.1.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.
v28.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.
v27.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.