@splunk/dashboard-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 | dormant-publish | AI (publish-pattern): Splunk internal monorepo package; irregular publish cadence is normal for enterprise tooling, not an account-takeover indicator. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files consistent with added jspdf/fflate functionality; no obfuscation or suspicious payloads detected. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk scoped dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@splunk/moment | AI (dependencies): Internal Splunk scoped dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@splunk/splunk-utils | AI (dependencies): Internal Splunk scoped dependency; expected for this package family. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv referenced in config files only; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Splunk org packages historically published without Sigstore provenance; stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for org-internal publishes. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 29.6.0 | 10 / 7 | |
| 29.5.2 | 10 / 7 | |
| 29.5.1 | 10 / 7 | |
| 29.3.3 | 10 / 7 | |
| 29.3.0 | 10 / 7 | |
| 29.2.0 | 10 / 7 | |
| 29.0.0 | 11 / 7 | |
| 28.6.3 | 11 / 7 | |
| 28.6.2 | 11 / 7 |
v29.6.0
1 finding[Accepted risk] Package 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.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.