@cloudtower/icons-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual publisher to GitHub Actions CI with SLSA attestation is a legitimate and expected supply chain improvement. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI with Sigstore attestation; stable positive signal. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI pipeline explains rapid successive publishes for this icon library. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4100.0.9 | 0 / 5 | |
| 4100.0.8 | 0 / 5 | |
| 4100.0.7 | 0 / 5 | |
| 4100.0.6 | 0 / 5 | |
| 4100.0.5 | 0 / 5 | |
| 4100.0.3 | 0 / 5 | |
| 4100.0.2 | 0 / 5 | |
| 4100.0.1 | 0 / 5 | |
| 4100.0.0 | 0 / 5 | |
| 490.0.15 | 0 / 5 | |
| 490.0.14 | 0 / 5 | |
| 490.0.13 | 0 / 5 | |
| 490.0.12 | 0 / 5 | |
| 490.0.11 | 0 / 5 | |
| 490.0.10 | 0 / 5 | |
| 490.0.9 | 0 / 5 |
v4100.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4100.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4100.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4100.0.6
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v4100.0.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v4100.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4100.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4100.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v490.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v490.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v490.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v490.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v490.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v490.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v490.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.