@splunk/dashboard-datasource-panel
Components for browsing and selecting data sources in the dashboard data overview panel
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @splunk/react-icons is a first-party Splunk package; consistent with this package's Splunk dashboard ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Internal Splunk package; provenance not standard for private ecosystem packages. | ai | |
| dependencies | unvetted-peer-dep:@splunk/dashboard-context | AI (dependencies): Internal Splunk peer dependency; stable across versions. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-icons | AI (phantom-deps): Same-org dep referenced in config but not directly imported; stable false positive for this Splunk package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a common React peer dep referenced in config; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): Legitimate Splunk UI library; part of the same ecosystem. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-ui | AI (dependencies): Sibling package in the same Splunk dashboard monorepo release. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-definition | AI (dependencies): Sibling package in the same Splunk dashboard monorepo release. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): Legitimate Splunk UI library; part of the same ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for internal/scoped packages. | ai | |
| dependencies | unvetted-dep:@splunk/react-ui | AI (dependencies): Legitimate Splunk UI library; part of the same ecosystem. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Legitimate Splunk UI library; part of the same ecosystem. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 8 / 18 | |
| 29.5.1 | 8 / 18 | |
| 29.5.0 | 8 / 18 | |
| 29.4.0 | 8 / 18 | |
| 29.3.4 | 8 / 17 | |
| 29.3.3 | 8 / 17 | |
| 29.3.2 | 8 / 17 | |
| 29.3.1 | 8 / 17 | |
| 29.3.0 | 8 / 17 | |
| 29.2.1 | 8 / 21 | |
| 29.2.0 | 8 / 21 | |
| 29.1.0 | 10 / 20 | |
| 29.0.0 | 9 / 20 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.