@splunk/dashboard-presets
Preset mappings that wire dashboard visualizations, layouts, inputs, event handlers, and data sources
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 dependency; consistent with the package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-ui | AI (dependencies): Internal Splunk dependency; consistent with the package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@splunk/visualizations | AI (dependencies): Internal Splunk dependency; consistent with the package's ecosystem context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Corporate @splunk scoped package; missing repo/keywords is normal for enterprise monorepo artifacts. | ai | |
| phantom-deps | phantom-dep:@splunk/react-icons | AI (phantom-deps): Same-org scope; likely re-exported or used indirectly via bundled output in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-icons | AI (phantom-deps): Same-org scope; consistent with monorepo indirect usage pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 11 / 6 | |
| 29.4.0 | 11 / 6 | |
| 29.3.3 | 10 / 6 | |
| 29.3.2 | 10 / 6 | |
| 29.1.0 | 11 / 6 | |
| 29.0.0 | 11 / 6 |
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.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.