@likec4/icons
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package in the legitimate likec4 org; Levenshtein match to 'cors' is coincidental. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 1.46.4 | 0 / 11 | |
| 1.45.0 | 0 / 11 | |
| 1.44.0 | 0 / 11 | |
| 1.43.0 | 0 / 11 | |
| 1.42.1 | 0 / 11 | |
| 1.42.0 | 0 / 11 | |
| 1.41.0 | 0 / 10 | |
| 1.40.0 | 0 / 10 | |
| 1.39.5 | 0 / 10 | |
| 1.39.4 | 0 / 10 | |
| 1.39.3 | 0 / 10 | |
| 1.39.2 | 0 / 10 | |
| 1.39.1 | 0 / 10 | |
| 1.39.0 | 0 / 10 | |
| 1.38.1 | 0 / 10 | |
| 1.38.0 | 0 / 10 | |
| 1.37.0 | 0 / 10 | |
| 1.36.1 | 0 / 10 | |
| 1.36.0 | 0 / 10 | |
| 1.35.0 | 0 / 10 | |
| 1.34.2 | 0 / 10 | |
| 1.34.1 | 0 / 10 | |
| 1.34.0 | 0 / 10 | |
| 1.33.0 | 0 / 10 | |
| 1.32.2 | 0 / 10 | |
| 1.32.1 | 0 / 10 | |
| 1.32.0 | 0 / 10 | |
| 1.31.0 | 0 / 10 | |
| 1.22.1 | 0 / 9 | |
| 1.22.0 | 0 / 9 | |
| 1.21.1 | 0 / 9 | |
| 1.21.0 | 0 / 9 | |
| 1.20.3 | 0 / 9 | |
| 1.20.2 | 0 / 9 | |
| 1.20.1 | 0 / 9 | |
| 1.20.0 | 0 / 9 | |
| 1.19.2 | 0 / 9 | |
| 1.19.1 | 0 / 9 | |
| 1.19.0 | 0 / 9 | |
| 1.18.0 | 0 / 9 | |
| 1.17.1 | 0 / 9 | |
| 1.17.0 | 0 / 9 | |
| 1.16.0 | 0 / 9 | |
| 1.15.1 | 0 / 9 | |
| 1.15.0 | 0 / 9 | |
| 1.14.0 | 0 / 9 | |
| 1.13.0 | 0 / 9 | |
| 1.12.2 | 0 / 9 | |
| 1.12.1 | 0 / 9 | |
| 1.12.0 | 0 / 9 | |
| 1.11.0 | 0 / 9 | |
| 1.10.1 | 0 / 9 | |
| 1.10.0 | 0 / 9 | |
| 1.9.0 | 0 / 9 | |
| 1.8.1 | 0 / 9 | |
| 1.8.0 | 0 / 9 |
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.