@splunk/dashboard-context
React contexts and APIs for dashboard state, plugins, data sources, and interactions
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Consistent with unchanged provenance direction for this trusted Splunk package. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): First-party Splunk package; stable dependency for this package family. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): First-party Splunk package; stable dependency for this package family. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): First-party Splunk package; stable dependency for this package family. | ai | |
| dependencies | unvetted-dep:@splunk/splunk-utils | AI (dependencies): First-party Splunk package; stable dependency for this package family. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a common peer/config-only reference in React component libraries; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Splunk internal package; sparse metadata is a consistent pattern across its 144 versions, not a spam indicator. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 29.8.0 | 19 / 21 | |
| 29.7.0 | 19 / 21 | |
| 29.6.1 | 19 / 19 | |
| 29.6.0 | 19 / 19 | |
| 29.5.3 | 19 / 19 | |
| 29.5.2 | 19 / 19 | |
| 29.5.1 | 19 / 19 | |
| 29.5.0 | 19 / 19 | |
| 29.4.0 | 19 / 19 | |
| 29.3.5 | 19 / 19 | |
| 29.3.4 | 19 / 19 | |
| 29.3.3 | 19 / 19 | |
| 29.3.2 | 19 / 19 | |
| 29.3.1 | 19 / 19 | |
| 29.3.0 | 19 / 19 | |
| 29.2.1 | 19 / 19 | |
| 29.2.0 | 19 / 19 | |
| 29.1.0 | 20 / 19 | |
| 29.0.0 | 20 / 18 | |
| 28.6.4 | 19 / 17 | |
| 28.6.3 | 19 / 17 | |
| 28.6.2 | 19 / 17 | |
| 28.5.1 | 19 / 17 | |
| 28.2.3 | 19 / 17 | |
| 28.2.2 | 19 / 17 | |
| 27.3.2 | 19 / 16 |
v29.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 findingPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 findingPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
2 findingsPackage 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 findingsPackage 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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.2
2 findingsPackage 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.