@splunk/datasources
Splunk search and snapshot datasource implementations for dashboard queries
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): New dep is a first-party Splunk auth client; consistent with this package's cloud-data-source scope. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Splunk org publisher with 57 approved packages; dormancy consistent with versioned release cadence for internal tooling. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large Splunk SDK package; incremental source file additions are expected across minor versions. | ai | |
| dependencies | unvetted-dep:@splunk/splunk-utils | AI (dependencies): Splunk-scoped sibling dependency in the same monorepo ecosystem. | ai | |
| dependencies | unvetted-dep:@splunkdev/cloud-sdk | AI (dependencies): Splunkdev-scoped dependency consistent with Splunk cloud SDK ecosystem. | ai | |
| dependencies | unvetted-dep:@splunk/moment | AI (dependencies): Splunk-scoped sibling dependency in the same monorepo ecosystem. | ai | |
| dependencies | unvetted-dep:@splunkdev/cloud-auth-client | AI (dependencies): Splunkdev-scoped dependency consistent with Splunk cloud SDK ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for org-internal packages. | ai | |
| dependencies | unvetted-dep:@splunk/dashboard-definition | AI (dependencies): Splunk dashboard monorepo sibling at exact pinned version. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Splunk-scoped sibling dependency in the same monorepo ecosystem. | ai | |
| dependencies | unvetted-dep:@splunk/search-job | AI (dependencies): Splunk-scoped sibling dependency in the same monorepo ecosystem. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 29.5.2 | 14 / 10 | |
| 29.5.1 | 14 / 10 | |
| 29.5.0 | 14 / 10 | |
| 29.4.0 | 14 / 10 | |
| 29.3.4 | 14 / 10 | |
| 29.3.3 | 14 / 10 | |
| 29.3.2 | 14 / 10 | |
| 29.3.1 | 14 / 10 | |
| 29.3.0 | 14 / 10 | |
| 29.2.1 | 14 / 10 | |
| 29.2.0 | 14 / 10 | |
| 29.1.0 | 13 / 10 | |
| 29.0.0 | 13 / 10 | |
| 28.6.3 | 13 / 10 | |
| 28.6.2 | 13 / 10 | |
| 28.2.2 | 13 / 10 |
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.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.4
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. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.0
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. 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. 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.
v28.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.