@splunk/dashboard-validation
Dashboard definition validation components, hooks, and worker-backed validators
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk UI utility; stable dependency across this package's version history. | ai | |
| provenance | no-provenance | AI (provenance): Splunk dashboard packages consistently lack Sigstore provenance; not a risk signal for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; missing repo/keywords/README details are consistent across the Splunk dashboard package family. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 3 / 10 | |
| 29.5.1 | 3 / 10 | |
| 29.5.0 | 3 / 10 | |
| 29.4.0 | 3 / 10 | |
| 29.3.4 | 3 / 10 | |
| 29.3.3 | 3 / 10 | |
| 29.3.2 | 3 / 10 | |
| 29.3.1 | 3 / 10 | |
| 29.3.0 | 3 / 10 | |
| 29.2.1 | 3 / 10 | |
| 29.2.0 | 3 / 10 | |
| 29.1.0 | 3 / 10 | |
| 29.0.0 | 3 / 10 | |
| 28.6.3 | 3 / 10 | |
| 28.6.2 | 3 / 10 | |
| 28.2.2 | 3 / 10 |
v29.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.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.
v29.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.
v28.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.