@itcase/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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @itcase/icons package; Levenshtein match to 'cors' is coincidental, no impersonation intent. | ai | |
| phantom-deps | phantom-dep:@itcase/config | AI (phantom-deps): Same-org build/config tooling; declared but used indirectly as dev dependency. | ai | |
| phantom-deps | phantom-dep:@itcase/storybook-config | AI (phantom-deps): Same-org Storybook config; dev-only tooling, not a runtime import. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.2.29 | 2 / 34 | |
| 1.2.28 | 2 / 37 | |
| 1.2.27 | 2 / 37 | |
| 1.2.23 | 2 / 37 | |
| 1.2.20 | 2 / 37 | |
| 1.2.19 | 2 / 37 | |
| 1.2.16 | 2 / 37 | |
| 1.2.15 | 2 / 37 | |
| 1.2.13 | 2 / 36 | |
| 1.2.12 | 2 / 36 | |
| 1.2.11 | 2 / 36 | |
| 1.2.6 | 2 / 36 | |
| 1.2.5 | 2 / 36 | |
| 1.2.4 | 2 / 36 | |
| 1.2.3 | 2 / 36 | |
| 1.2.2 | 2 / 36 | |
| 1.1.6 | 2 / 36 | |
| 1.1.5 | 2 / 36 | |
| 1.1.4 | 2 / 35 | |
| 1.1.3 | 2 / 35 | |
| 1.1.2 | 2 / 35 | |
| 1.1.1 | 2 / 35 | |
| 1.1.0 | 2 / 36 | |
| 1.0.31 | 2 / 35 | |
| 1.0.30 | 2 / 35 | |
| 1.0.29 | 2 / 35 | |
| 1.0.28 | 2 / 35 | |
| 1.0.27 | 2 / 35 | |
| 1.0.26 | 2 / 35 | |
| 1.0.25 | 2 / 35 | |
| 1.0.23 | 2 / 35 | |
| 1.0.21 | 2 / 59 | |
| 1.0.20 | 0 / 66 | |
| 1.0.19 | 0 / 66 | |
| 1.0.18 | 0 / 66 | |
| 1.0.17 | 0 / 66 | |
| 1.0.16 | 0 / 66 | |
| 1.0.15 | 0 / 66 | |
| 1.0.14 | 0 / 66 | |
| 1.0.13 | 0 / 66 | |
| 1.0.12 | 0 / 66 | |
| 1.0.11 | 0 / 66 | |
| 1.0.10 | 0 / 66 | |
| 1.0.9 | 0 / 66 | |
| 1.0.8 | 0 / 65 | |
| 1.0.7 | 0 / 65 | |
| 1.0.6 | 0 / 65 | |
| 1.0.5 | 0 / 65 | |
| 1.0.4 | 0 / 66 | |
| 1.0.3 | 0 / 66 | |
| 1.0.2 | 0 / 31 | |
| 1.0.1 | 0 / 31 |
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.