@mirai/locale No license 42 versions

@mirai/locale

npm Repository

42

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mirai

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): React library; react-dom is a peer dependency used via re-exports.	ai	2026/05/10
phantom-deps	phantom-dep:react-icons	AI (phantom-deps): React library; react-icons used via re-exports or build config.	ai	2026/05/10
phantom-deps	phantom-dep:@mirai/data-sources	AI (phantom-deps): Same-org scoped dependency; used via re-exports in library pattern.	ai	2026/05/10

Versions (showing 42 of 42)

Version	Deps	Published
0.3.24	3 / 12	2026-06-01
0.3.23	3 / 12	2026-01-12
0.3.22	3 / 12	2025-12-22
0.3.21	3 / 13	2025-11-14
0.3.20	3 / 13	2025-09-01
0.3.19	3 / 13	2025-08-13
0.3.18	3 / 13	2025-08-07
0.3.17	3 / 13	2025-08-07
0.3.16	3 / 13	2025-07-21
0.3.15	3 / 13	2025-07-02
0.3.14	3 / 13	2025-06-25
0.3.13	3 / 13	2025-06-18
0.3.12	4 / 13	2025-06-06
0.3.11	4 / 13	2025-01-23
0.3.10	4 / 13	2025-01-03
0.3.9	4 / 13	2024-12-19
0.3.8	4 / 13	2024-12-19
0.3.7	4 / 13	2024-12-19
0.3.6	4 / 13	2024-12-18
0.3.5	4 / 13	2024-12-18
0.3.4	4 / 13	2024-12-18
0.3.3	4 / 13	2024-12-18
0.3.2	4 / 13	2024-12-17
0.3.1	4 / 13	2024-11-28
0.2.43	4 / 11	2024-11-05
0.2.42	4 / 11	2024-09-03
0.2.41	4 / 11	2024-07-15
0.2.40	4 / 11	2024-07-09
0.2.39	4 / 11	2024-07-09
0.2.38	4 / 11	2024-05-14
0.2.37	4 / 11	2024-04-29
0.2.9	4 / 10	2022-05-30
0.2.8	4 / 10	2022-05-28
0.2.4	4 / 8	2022-05-09
0.2.3	4 / 9	2022-04-26
0.2.2	4 / 9	2022-04-26
0.2.0	4 / 9	2022-04-25
0.1.18	0 / 6	2022-04-22
0.1.16	0 / 6	2022-04-21
0.1.14	0 / 6	2022-04-21
0.1.2	0 / 6	2022-03-29
0.1.1	0 / 6	2022-03-21

v0.3.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mirai.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.