@splunk/react-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Splunk SUI publish pipeline consistently lacks Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.13.0 | 3 / 45 | |
| 5.12.0 | 3 / 45 | |
| 5.11.0 | 3 / 50 | |
| 5.10.0 | 3 / 51 | |
| 5.9.0 | 3 / 51 | |
| 5.8.0 | 3 / 51 | |
| 5.7.0 | 3 / 51 | |
| 5.6.0 | 3 / 51 | |
| 5.0.0 | 3 / 50 |
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.