@tabler/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established icon package; missing gitHead reflects publish-env change, no behavioral risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @tabler/icons is a legitimate, long-established icon library; Levenshtein match against 'cors' is a false positive for scoped packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.45.0 | 0 / 0 | |
| 3.44.0 | 0 / 0 | |
| 3.43.0 | 0 / 0 | |
| 3.42.0 | 0 / 0 | |
| 3.41.1 | 0 / 0 | |
| 3.41.0 | 0 / 0 | |
| 3.40.0 | 0 / 0 | |
| 3.39.0 | 0 / 0 | |
| 3.38.0 | 0 / 0 | |
| 3.37.1 | 0 / 0 | |
| 3.37.0 | 0 / 0 | |
| 3.36.1 | 0 / 0 | |
| 3.36.0 | 0 / 0 |
v3.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.41.0
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: codecalm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.0
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: codecalm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.0
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: codecalm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.0
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: codecalm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.1
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: codecalm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
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: codecalm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.