@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 — the axios compromise (March 2026) relied on exactly this gap.
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 8 of 312)
| Version | Deps | Published |
|---|---|---|
| 0.4.305 | 9 / 17 | |
| 0.4.304 | 9 / 17 | |
| 0.4.303 | 9 / 17 | |
| 0.4.302 | 9 / 17 | |
| 0.4.301 | 9 / 17 | |
| 0.4.300 | 9 / 17 | |
| 0.4.299 | 9 / 17 | |
| 0.4.298 | 9 / 17 |
v0.4.305
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.304
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.303
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.302
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.301
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.300
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.299
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.298
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.