@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 — 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 |
|---|---|---|---|---|
| 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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 19 / 19 | |
| 29.5.1 | 19 / 19 | |
| 29.3.3 | 19 / 19 | |
| 29.3.0 | 19 / 19 | |
| 29.2.0 | 19 / 19 | |
| 29.1.0 | 20 / 19 | |
| 29.0.0 | 20 / 18 | |
| 28.6.2 | 19 / 17 |
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.3
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. 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.