@stackwright/icons
Lucide-based icon registry for Stackwright
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small org package; no CI provenance configured but no other risk signals present. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped icon library for Stackwright; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.5.2 | 1 / 9 | |
| 0.5.1 | 1 / 10 | |
| 0.5.0 | 1 / 10 | |
| 0.4.0 | 1 / 10 | |
| 0.3.0 | 1 / 10 | |
| 0.2.3 | 0 / 8 | |
| 0.2.0 | 3 / 5 |
v0.5.2
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: stackwright.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.