@splunk/datasource-utils
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 deps are first-party @splunk/* packages; low risk for this Splunk-maintained package. | ai | |
| provenance | no-provenance | AI (provenance): Splunk internal publisher; provenance attestation not used across this package's history. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk ecosystem dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@splunk/splunk-utils | AI (dependencies): Internal Splunk ecosystem dependency; expected for this package family. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 29.6.0 | 4 / 6 | |
| 29.5.2 | 4 / 6 | |
| 29.5.1 | 4 / 6 | |
| 29.5.0 | 4 / 6 | |
| 29.4.0 | 4 / 6 | |
| 29.3.4 | 4 / 6 | |
| 29.3.3 | 4 / 6 | |
| 29.3.2 | 4 / 6 | |
| 29.3.1 | 4 / 6 | |
| 29.3.0 | 4 / 6 | |
| 29.2.1 | 4 / 6 | |
| 29.2.0 | 4 / 6 | |
| 29.1.0 | 4 / 6 | |
| 29.0.0 | 3 / 7 | |
| 28.6.3 | 4 / 6 | |
| 28.6.2 | 4 / 6 | |
| 28.2.2 | 2 / 7 |
v29.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.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 findingPackage 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 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.3
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.