@splunk/dashboard-ui
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise SDK; sparse metadata is expected for private-org packages not intended for public discovery. | ai | |
| phantom-deps | phantom-dep:memoize-one | AI (phantom-deps): Declared in package.json deps; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): Declared in package.json deps; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-telemetry | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 29.7.0 | 21 / 27 | |
| 29.6.0 | 20 / 27 | |
| 29.3.4 | 20 / 32 | |
| 29.1.0 | 20 / 32 |
v29.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.