@splunk/dashboard
Dashboard authoring components and APIs for building and editing interactive dashboards
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/dashboard-telemetry | AI (phantom-deps): Same org scope; likely used indirectly via peer/optional dependency chain, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/test | AI (phantom-deps): Storybook test dep referenced only in config files, not runtime code; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Enterprise Splunk SDK package; sparse metadata is typical for internal packages not meant for public npm discovery. | ai | |
| phantom-deps | phantom-dep:memoize-one | AI (phantom-deps): Declared but used only in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@splunk/datasource-utils | AI (phantom-deps): Same-org scoped dep; likely used transitively or in config; stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 29.3.4 | 21 / 31 | |
| 29.3.1 | 21 / 31 | |
| 29.3.0 | 21 / 31 | |
| 29.2.0 | 21 / 31 | |
| 29.1.0 | 22 / 30 | |
| 29.0.0 | 20 / 30 |
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.