@splunk/dashboard-core
Core dashboard rendering components for layouts, visualizations, inputs, and action menus
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:prop-types | AI (phantom-deps): Config-file-only reference; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise Splunk package; sparse metadata is expected for org-internal npm distributions. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-telemetry | AI (phantom-deps): Same @splunk org scope; likely used transitively or conditionally in this monorepo package. | ai | |
| phantom-deps | phantom-dep:hash-it | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@splunk/datasources | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for peer/config-only deps in this package. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-search | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for peer/config-only deps in this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 29.3.4 | 19 / 27 | |
| 29.3.3 | 19 / 27 | |
| 29.3.2 | 19 / 27 | |
| 29.2.0 | 19 / 31 | |
| 29.1.0 | 23 / 32 | |
| 28.6.3 | 21 / 31 | |
| 28.6.2 | 21 / 31 | |
| 28.2.2 | 21 / 31 |
v29.3.4
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.2.0
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.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.