@mirai/core
# 1. Installation
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): Pinned to a specific react-icons release tarball; stable workaround for that package's registry distribution issue. | ai | |
| dependencies | unvetted-dep:@mirai/ui | AI (dependencies): Sibling package in the same @mirai org monorepo. | ai | |
| dependencies | unvetted-dep:@mirai/icons | AI (dependencies): Sibling package in the same @mirai org monorepo. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @mirai/core is a scoped monorepo package, not a typosquat of cors; Levenshtein match is coincidental. | ai | |
| dependencies | unvetted-dep:@mirai/services | AI (dependencies): Sibling package in the same @mirai org monorepo. | ai | |
| dependencies | unvetted-dep:@mirai/data-sources | AI (dependencies): Sibling package in the same @mirai org monorepo. | ai | |
| dependencies | unvetted-dep:@mirai/locale | AI (dependencies): Sibling package in the same @mirai org monorepo. | ai |
Versions (showing 100 of 610)
| Version | Deps | Published |
|---|---|---|
| 0.4.237 | 9 / 17 | |
| 0.4.236 | 9 / 17 | |
| 0.4.235 | 9 / 17 | |
| 0.4.234 | 9 / 17 | |
| 0.4.233 | 9 / 17 | |
| 0.4.232 | 9 / 17 | |
| 0.4.230 | 9 / 17 | |
| 0.4.229 | 9 / 17 | |
| 0.4.228 | 9 / 17 | |
| 0.4.227 | 9 / 17 | |
| 0.4.226 | 9 / 17 | |
| 0.4.225 | 9 / 17 | |
| 0.4.224 | 9 / 17 | |
| 0.4.223 | 9 / 17 | |
| 0.4.222 | 9 / 17 | |
| 0.4.221 | 9 / 17 | |
| 0.4.220 | 9 / 17 | |
| 0.4.219 | 9 / 17 | |
| 0.4.218 | 9 / 17 | |
| 0.4.217 | 9 / 17 | |
| 0.4.216 | 9 / 17 | |
| 0.4.215 | 9 / 17 | |
| 0.4.214 | 9 / 17 | |
| 0.4.213 | 9 / 17 | |
| 0.4.212 | 9 / 17 | |
| 0.4.211 | 9 / 17 | |
| 0.4.210 | 9 / 17 | |
| 0.4.209 | 9 / 17 | |
| 0.4.208 | 9 / 17 | |
| 0.4.207 | 9 / 17 | |
| 0.4.206 | 9 / 17 | |
| 0.4.205 | 9 / 17 | |
| 0.4.204 | 9 / 17 | |
| 0.4.203 | 9 / 17 | |
| 0.4.202 | 9 / 17 | |
| 0.4.201 | 9 / 17 | |
| 0.4.200 | 9 / 17 | |
| 0.4.199 | 9 / 17 | |
| 0.4.198 | 9 / 17 | |
| 0.4.197 | 9 / 17 | |
| 0.4.196 | 9 / 17 | |
| 0.4.195 | 9 / 17 | |
| 0.4.194 | 9 / 17 | |
| 0.4.193 | 9 / 17 | |
| 0.4.192 | 9 / 17 | |
| 0.4.191 | 9 / 17 | |
| 0.4.190 | 9 / 17 | |
| 0.4.189 | 9 / 17 | |
| 0.4.188 | 9 / 17 | |
| 0.4.187 | 9 / 17 | |
| 0.4.186 | 9 / 17 | |
| 0.4.185 | 9 / 17 | |
| 0.4.184 | 9 / 17 | |
| 0.4.183 | 9 / 17 | |
| 0.4.182 | 9 / 17 | |
| 0.4.181 | 9 / 17 | |
| 0.4.180 | 9 / 17 | |
| 0.4.179 | 9 / 17 | |
| 0.4.178 | 9 / 17 | |
| 0.4.177 | 9 / 17 | |
| 0.4.176 | 9 / 17 | |
| 0.4.175 | 9 / 17 | |
| 0.4.174 | 9 / 17 | |
| 0.4.173 | 9 / 17 | |
| 0.4.172 | 9 / 17 | |
| 0.4.171 | 9 / 17 | |
| 0.4.170 | 9 / 17 | |
| 0.4.169 | 9 / 17 | |
| 0.4.168 | 9 / 17 | |
| 0.4.167 | 9 / 17 | |
| 0.4.166 | 9 / 17 | |
| 0.4.165 | 9 / 17 | |
| 0.4.164 | 9 / 17 | |
| 0.4.163 | 9 / 17 | |
| 0.4.162 | 9 / 17 | |
| 0.4.161 | 9 / 17 | |
| 0.4.160 | 9 / 17 | |
| 0.4.159 | 9 / 17 | |
| 0.4.158 | 9 / 17 | |
| 0.4.157 | 9 / 17 | |
| 0.4.156 | 9 / 17 | |
| 0.4.155 | 9 / 17 | |
| 0.4.154 | 9 / 17 | |
| 0.4.153 | 9 / 17 | |
| 0.4.152 | 9 / 17 | |
| 0.4.151 | 9 / 17 | |
| 0.4.150 | 9 / 17 | |
| 0.4.149 | 9 / 17 | |
| 0.4.148 | 9 / 17 | |
| 0.4.147 | 9 / 17 | |
| 0.4.146 | 9 / 17 | |
| 0.4.145 | 9 / 17 | |
| 0.4.144 | 9 / 17 | |
| 0.4.143 | 9 / 17 | |
| 0.4.142 | 9 / 17 | |
| 0.4.141 | 9 / 17 | |
| 0.4.140 | 9 / 17 | |
| 0.4.139 | 9 / 17 | |
| 0.4.138 | 9 / 17 | |
| 0.4.137 | 9 / 17 |
v0.4.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.