@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.136 | 9 / 17 | |
| 0.4.135 | 9 / 17 | |
| 0.4.134 | 9 / 17 | |
| 0.4.133 | 9 / 17 | |
| 0.4.132 | 9 / 17 | |
| 0.4.131 | 9 / 17 | |
| 0.4.130 | 9 / 17 | |
| 0.4.129 | 9 / 17 | |
| 0.4.128 | 9 / 17 | |
| 0.4.127 | 9 / 17 | |
| 0.4.126 | 9 / 17 | |
| 0.4.125 | 9 / 17 | |
| 0.4.124 | 9 / 17 | |
| 0.4.123 | 9 / 17 | |
| 0.4.122 | 9 / 17 | |
| 0.4.121 | 9 / 17 | |
| 0.4.120 | 9 / 17 | |
| 0.4.119 | 9 / 17 | |
| 0.4.118 | 9 / 17 | |
| 0.4.117 | 9 / 17 | |
| 0.4.116 | 9 / 17 | |
| 0.4.115 | 9 / 17 | |
| 0.4.114 | 9 / 17 | |
| 0.4.113 | 9 / 17 | |
| 0.4.112 | 9 / 17 | |
| 0.4.111 | 9 / 17 | |
| 0.4.110 | 9 / 17 | |
| 0.4.109 | 9 / 17 | |
| 0.4.108 | 9 / 17 | |
| 0.4.107 | 9 / 17 | |
| 0.4.106 | 9 / 17 | |
| 0.4.105 | 9 / 17 | |
| 0.4.104 | 9 / 17 | |
| 0.4.103 | 9 / 17 | |
| 0.4.102 | 9 / 17 | |
| 0.4.101 | 9 / 17 | |
| 0.4.100 | 9 / 17 | |
| 0.4.99 | 9 / 17 | |
| 0.4.98 | 9 / 17 | |
| 0.4.97 | 9 / 17 | |
| 0.4.96 | 9 / 17 | |
| 0.4.95 | 9 / 17 | |
| 0.4.94 | 9 / 17 | |
| 0.4.93 | 9 / 17 | |
| 0.4.92 | 9 / 17 | |
| 0.4.91 | 9 / 17 | |
| 0.4.90 | 9 / 17 | |
| 0.4.89 | 9 / 17 | |
| 0.4.88 | 9 / 17 | |
| 0.4.87 | 9 / 17 | |
| 0.4.86 | 9 / 17 | |
| 0.4.85 | 9 / 17 | |
| 0.4.84 | 9 / 17 | |
| 0.4.83 | 9 / 17 | |
| 0.4.82 | 9 / 17 | |
| 0.4.81 | 9 / 17 | |
| 0.4.80 | 9 / 17 | |
| 0.4.79 | 9 / 17 | |
| 0.4.78 | 9 / 17 | |
| 0.4.77 | 9 / 17 | |
| 0.4.76 | 9 / 17 | |
| 0.4.75 | 9 / 17 | |
| 0.4.74 | 9 / 17 | |
| 0.4.73 | 9 / 17 | |
| 0.4.72 | 9 / 17 | |
| 0.4.71 | 9 / 17 | |
| 0.4.70 | 9 / 17 | |
| 0.4.69 | 9 / 17 | |
| 0.4.68 | 9 / 17 | |
| 0.4.67 | 9 / 17 | |
| 0.4.66 | 9 / 17 | |
| 0.4.65 | 9 / 17 | |
| 0.4.64 | 9 / 17 | |
| 0.4.63 | 9 / 17 | |
| 0.4.62 | 9 / 17 | |
| 0.4.61 | 9 / 17 | |
| 0.4.60 | 9 / 17 | |
| 0.4.59 | 9 / 17 | |
| 0.4.58 | 9 / 17 | |
| 0.4.57 | 9 / 17 | |
| 0.4.56 | 9 / 17 | |
| 0.4.55 | 9 / 17 | |
| 0.4.54 | 9 / 17 | |
| 0.4.53 | 9 / 17 | |
| 0.4.52 | 9 / 17 | |
| 0.4.51 | 9 / 17 | |
| 0.4.50 | 9 / 17 | |
| 0.4.49 | 9 / 17 | |
| 0.4.48 | 9 / 17 | |
| 0.4.47 | 9 / 17 | |
| 0.4.46 | 9 / 17 | |
| 0.4.45 | 9 / 17 | |
| 0.4.44 | 9 / 17 | |
| 0.4.43 | 9 / 17 | |
| 0.4.42 | 9 / 16 | |
| 0.4.41 | 9 / 16 | |
| 0.4.40 | 9 / 16 | |
| 0.4.39 | 9 / 16 | |
| 0.4.38 | 9 / 16 | |
| 0.4.37 | 9 / 16 |
v0.4.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.