@splunk/dashboard-icons
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Same-org sibling package dependency, normal for Splunk monorepo releases. | ai | |
| provenance | missing-githead | AI (provenance): Publish-environment quirk for trusted Splunk monorepo publisher, not tampering evidence. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library packages routinely add many new SVG/component files per release; not indicative of injected code. | ai | |
| dependencies | unvetted-dep:@splunk/react-icons | AI (dependencies): Internal Splunk org dependency; stable sibling package pattern across this publisher's releases. | ai | |
| dependencies | unvetted-dep:@splunk/themes | AI (dependencies): Internal Splunk org dependency; stable sibling package pattern across this publisher's releases. | ai | |
| dependencies | unvetted-dep:@splunk/ui-utils | AI (dependencies): Internal Splunk org dependency; stable sibling package pattern across this publisher's releases. | ai | |
| phantom-deps | phantom-dep:@splunk/dashboard-utils | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Splunk monorepo package; sparse metadata is expected, not indicative of spam. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 29.8.0 | 4 / 8 | |
| 29.7.0 | 4 / 8 | |
| 29.6.1 | 3 / 6 | |
| 29.6.0 | 3 / 6 | |
| 29.5.3 | 3 / 6 | |
| 29.5.2 | 3 / 6 | |
| 29.5.1 | 3 / 6 | |
| 29.5.0 | 3 / 6 | |
| 29.4.0 | 3 / 6 | |
| 29.3.5 | 3 / 6 | |
| 29.3.4 | 3 / 6 | |
| 29.3.3 | 3 / 6 | |
| 29.3.2 | 3 / 6 | |
| 29.3.1 | 3 / 6 | |
| 29.3.0 | 3 / 6 | |
| 29.2.1 | 3 / 11 | |
| 29.2.0 | 3 / 11 | |
| 29.1.0 | 4 / 11 | |
| 29.0.0 | 3 / 12 | |
| 28.6.4 | 3 / 12 | |
| 28.6.3 | 3 / 12 | |
| 28.6.2 | 3 / 12 | |
| 28.5.1 | 3 / 12 | |
| 28.2.3 | 3 / 12 | |
| 28.2.2 | 3 / 12 | |
| 27.3.2 | 4 / 11 |
v29.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.3
1 findingPackage 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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.5.1
2 findingsPackage 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 findingsPackage 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 findingsPackage 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.