@splunk/dashboard-action-buttons
Action buttons and menus for dashboard visualizations and containers
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Splunk org package published via internal pipeline; provenance attestation not used by this publisher across versions. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): Internal @splunk scoped dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-ui | AI (dependencies): Internal @splunk scoped dependency; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Config-file reference pattern; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@splunk/themes | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-file reference pattern; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-icons | AI (phantom-deps): Same-org monorepo dep; declared but may be transitively used via @splunk/dashboard-ui. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-telemetry | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for enterprise internal packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 7 / 17 | |
| 29.5.0 | 7 / 17 | |
| 29.4.0 | 7 / 17 | |
| 29.3.4 | 7 / 17 | |
| 29.3.3 | 7 / 17 | |
| 29.3.2 | 7 / 17 | |
| 29.3.1 | 7 / 17 | |
| 29.3.0 | 7 / 17 | |
| 29.2.1 | 7 / 20 | |
| 29.2.0 | 7 / 20 | |
| 29.1.0 | 10 / 20 | |
| 29.0.0 | 10 / 20 | |
| 28.6.2 | 10 / 16 | |
| 28.2.2 | 10 / 16 |
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.