@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish env variance for a trusted long-running Splunk package, not a security regression. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ajv is a well-known, widely-used validation library. | 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 | |
| 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 | |
| dependencies | unvetted-dep:@splunk/splunk-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/ui-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 | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected for org-internal publishes. | ai | |
| provenance | no-provenance | AI (provenance): Splunk org packages historically published without Sigstore provenance; stable pattern. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 29.8.0 | 10 / 8 | |
| 29.7.0 | 10 / 8 | |
| 29.6.1 | 10 / 7 | |
| 29.6.0 | 10 / 7 | |
| 29.5.3 | 10 / 7 | |
| 29.5.2 | 10 / 7 | |
| 29.5.1 | 10 / 7 | |
| 29.5.0 | 10 / 7 | |
| 29.4.0 | 10 / 7 | |
| 29.3.5 | 10 / 7 | |
| 29.3.4 | 10 / 7 | |
| 29.3.3 | 10 / 7 | |
| 29.3.2 | 10 / 7 | |
| 29.3.1 | 10 / 7 | |
| 29.3.0 | 10 / 7 | |
| 29.2.1 | 10 / 7 | |
| 29.2.0 | 10 / 7 | |
| 29.1.0 | 11 / 7 | |
| 29.0.0 | 11 / 7 | |
| 28.6.4 | 11 / 7 | |
| 28.6.3 | 11 / 7 | |
| 28.6.2 | 11 / 7 | |
| 28.5.1 | 11 / 7 | |
| 28.2.3 | 11 / 7 | |
| 28.2.2 | 11 / 7 | |
| 27.3.2 | 9 / 5 |
v29.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.3
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.5
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.
[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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.6.4
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v28.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v27.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.