@mirai/ui
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@react-icons/all-files | AI (npm-metadata): Points to a pinned versioned release tarball on the official react-icons GitHub repo; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of yup. | ai | |
| dependencies | unvetted-dep:@mirai/icons | AI (dependencies): Internal sibling package under the same @mirai org namespace; stable pattern across versions. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of joi. | ai |
Versions (showing 100 of 142)
| Version | Deps | Published |
|---|---|---|
| 2.1.100 | 5 / 15 | |
| 2.1.99 | 5 / 15 | |
| 2.1.98 | 5 / 15 | |
| 2.1.97 | 5 / 15 | |
| 2.1.96 | 5 / 15 | |
| 2.1.95 | 5 / 15 | |
| 2.1.94 | 5 / 15 | |
| 2.1.93 | 5 / 15 | |
| 2.1.92 | 5 / 15 | |
| 2.1.91 | 5 / 15 | |
| 2.1.90 | 5 / 15 | |
| 2.1.89 | 5 / 15 | |
| 2.1.88 | 5 / 15 | |
| 2.1.87 | 5 / 15 | |
| 2.1.86 | 5 / 15 | |
| 2.1.85 | 5 / 15 | |
| 2.1.84 | 5 / 15 | |
| 2.1.83 | 5 / 15 | |
| 2.1.82 | 5 / 15 | |
| 2.1.81 | 5 / 15 | |
| 2.1.80 | 5 / 15 | |
| 2.1.79 | 5 / 15 | |
| 2.1.78 | 5 / 15 | |
| 2.1.77 | 5 / 15 | |
| 2.1.76 | 5 / 15 | |
| 2.1.75 | 5 / 15 | |
| 2.1.74 | 5 / 15 | |
| 2.1.73 | 5 / 15 | |
| 2.1.72 | 5 / 15 | |
| 2.1.71 | 5 / 15 | |
| 2.1.70 | 5 / 15 | |
| 2.1.69 | 5 / 15 | |
| 2.1.68 | 5 / 15 | |
| 2.1.67 | 5 / 15 | |
| 2.1.66 | 5 / 15 | |
| 2.1.65 | 5 / 15 | |
| 2.1.64 | 5 / 15 | |
| 2.1.63 | 5 / 15 | |
| 2.1.62 | 5 / 15 | |
| 2.1.61 | 5 / 15 | |
| 2.1.60 | 5 / 15 | |
| 2.1.59 | 5 / 15 | |
| 2.1.58 | 5 / 15 | |
| 2.1.57 | 5 / 15 | |
| 2.1.56 | 5 / 15 | |
| 2.1.55 | 5 / 15 | |
| 2.1.54 | 5 / 15 | |
| 2.1.53 | 5 / 16 | |
| 2.1.52 | 5 / 16 | |
| 2.1.51 | 5 / 16 | |
| 2.1.50 | 5 / 16 | |
| 2.1.49 | 5 / 16 | |
| 2.1.48 | 5 / 16 | |
| 2.1.47 | 5 / 15 | |
| 2.1.46 | 5 / 15 | |
| 2.1.45 | 5 / 15 | |
| 2.1.44 | 5 / 15 | |
| 2.1.43 | 5 / 15 | |
| 2.1.42 | 5 / 15 | |
| 2.1.41 | 5 / 15 | |
| 2.1.40 | 5 / 15 | |
| 2.1.39 | 5 / 15 | |
| 2.1.38 | 5 / 15 | |
| 2.1.37 | 5 / 15 | |
| 2.1.36 | 5 / 15 | |
| 2.1.35 | 5 / 15 | |
| 2.1.34 | 5 / 15 | |
| 2.1.33 | 5 / 15 | |
| 2.1.32 | 5 / 15 | |
| 2.1.31 | 5 / 15 | |
| 2.1.30 | 5 / 15 | |
| 2.1.29 | 5 / 15 | |
| 2.1.28 | 5 / 15 | |
| 2.1.27 | 5 / 15 | |
| 2.1.26 | 5 / 15 | |
| 2.1.25 | 5 / 15 | |
| 2.1.24 | 5 / 15 | |
| 2.1.23 | 5 / 15 | |
| 2.1.22 | 5 / 15 | |
| 2.1.21 | 5 / 15 | |
| 2.1.20 | 5 / 15 | |
| 2.1.19 | 5 / 15 | |
| 2.1.18 | 5 / 15 | |
| 2.1.17 | 5 / 15 | |
| 2.1.16 | 5 / 15 | |
| 2.1.15 | 5 / 15 | |
| 2.1.14 | 5 / 15 | |
| 2.1.13 | 5 / 15 | |
| 2.1.12 | 5 / 15 | |
| 2.1.11 | 5 / 15 | |
| 2.1.10 | 5 / 15 | |
| 2.1.9 | 5 / 15 | |
| 2.1.8 | 5 / 15 | |
| 2.1.7 | 5 / 15 | |
| 2.1.5 | 5 / 15 | |
| 2.1.4 | 5 / 15 | |
| 2.1.3 | 5 / 15 | |
| 2.1.2 | 5 / 15 | |
| 2.1.1 | 5 / 15 | |
| 2.0.43 | 5 / 13 |
v2.1.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.