@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are common, well-known libraries (lodash, prop-types, themes). | ai | |
| provenance | missing-githead | AI (provenance): Trusted long-running Splunk publisher; no behavioral indicator of tampering. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-ui | AI (dependencies): Internal @splunk scoped dependency; stable pattern across all versions of this package. | ai | |
| 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 | |
| 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:prop-types | AI (phantom-deps): Config-file reference pattern; stable false positive for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for enterprise internal packages. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-telemetry | AI (phantom-deps): Same-org monorepo dep; stable false positive for this 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 |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 29.8.0 | 8 / 20 | |
| 29.7.0 | 8 / 20 | |
| 29.6.1 | 7 / 17 | |
| 29.6.0 | 7 / 17 | |
| 29.5.3 | 7 / 17 | |
| 29.5.2 | 7 / 17 | |
| 29.5.1 | 7 / 17 | |
| 29.5.0 | 7 / 17 | |
| 29.4.0 | 7 / 17 | |
| 29.3.5 | 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.4 | 10 / 16 | |
| 28.6.3 | 10 / 16 | |
| 28.6.2 | 10 / 16 | |
| 28.5.1 | 10 / 16 | |
| 28.2.3 | 10 / 16 | |
| 28.2.2 | 10 / 16 | |
| 27.3.2 | 11 / 15 |
v29.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.
v28.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.
v27.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: splunk_dashboard_publisher.