@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 51 of 610)
| Version | Deps | Published |
|---|---|---|
| 0.4.638 | 9 / 22 | |
| 0.4.637 | 9 / 22 | |
| 0.4.636 | 9 / 22 | |
| 0.4.635 | 9 / 22 | |
| 0.4.634 | 9 / 22 | |
| 0.4.633 | 9 / 22 | |
| 0.4.632 | 9 / 22 | |
| 0.4.631 | 9 / 22 | |
| 0.4.630 | 9 / 22 | |
| 0.4.629 | 9 / 22 | |
| 0.4.628 | 9 / 22 | |
| 0.4.627 | 9 / 22 | |
| 0.4.626 | 9 / 22 | |
| 0.4.625 | 9 / 22 | |
| 0.4.624 | 9 / 22 | |
| 0.4.623 | 9 / 22 | |
| 0.4.622 | 9 / 22 | |
| 0.4.621 | 9 / 17 | |
| 0.4.620 | 9 / 17 | |
| 0.4.619 | 9 / 17 | |
| 0.4.618 | 9 / 17 | |
| 0.4.617 | 9 / 17 | |
| 0.4.616 | 9 / 17 | |
| 0.4.615 | 9 / 17 | |
| 0.4.614 | 9 / 17 | |
| 0.4.613 | 9 / 17 | |
| 0.4.612 | 9 / 17 | |
| 0.4.611 | 9 / 17 | |
| 0.4.610 | 9 / 17 | |
| 0.4.609 | 9 / 17 | |
| 0.4.608 | 9 / 17 | |
| 0.4.607 | 9 / 17 | |
| 0.4.606 | 9 / 17 | |
| 0.4.605 | 9 / 17 | |
| 0.4.604 | 9 / 17 | |
| 0.4.603 | 9 / 17 | |
| 0.4.602 | 9 / 17 | |
| 0.4.601 | 9 / 17 | |
| 0.4.600 | 9 / 17 | |
| 0.4.599 | 9 / 17 | |
| 0.4.598 | 9 / 17 | |
| 0.4.597 | 9 / 17 | |
| 0.4.596 | 9 / 17 | |
| 0.4.595 | 9 / 17 | |
| 0.4.594 | 9 / 17 | |
| 0.4.593 | 9 / 17 | |
| 0.4.592 | 9 / 17 | |
| 0.4.591 | 9 / 17 | |
| 0.4.590 | 9 / 17 | |
| 0.4.589 | 9 / 17 | |
| 0.4.588 | 9 / 17 |
v0.4.638
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.637
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.636
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.635
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.634
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.633
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.632
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.631
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.630
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.629
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.628
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.627
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.626
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.625
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.624
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.623
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.622
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.621
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.620
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.619
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.618
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.617
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.