@mirai/ui No license 51 versions

@mirai/ui

npm Repository

51

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mirai

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): Points to a pinned versioned release tarball on the official react-icons GitHub repo; stable pattern for this package.	ai	2026/05/10
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of pg.	ai	2026/04/29
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of qs.	ai	2026/04/29
typosquat	typosquat.levenshtein:uuid	AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of uuid.	ai	2026/04/29
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of yup.	ai	2026/04/29
dependencies	unvetted-dep:@mirai/icons	AI (dependencies): Internal sibling package under the same @mirai org namespace; stable pattern across versions.	ai	2026/04/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @mirai/ui package with 428 versions; not a typosquat of joi.	ai	2026/04/29

Versions (showing 51 of 61)

View all versions

Version	Deps	Published
2.1.97	5 / 15	2026-06-01
2.1.96	5 / 15	2026-05-25
2.1.95	5 / 15	2026-04-20
2.1.94	5 / 15	2026-04-08
2.1.93	5 / 15	2026-03-31
2.1.92	5 / 15	2026-03-30
2.1.91	5 / 15	2026-03-20
2.1.90	5 / 15	2026-03-10
2.1.89	5 / 15	2026-02-12
2.1.88	5 / 15	2026-01-20
2.1.87	5 / 15	2025-12-26
2.1.86	5 / 15	2025-12-17
2.1.85	5 / 15	2025-12-17
2.1.84	5 / 15	2025-12-16
2.1.83	5 / 15	2025-12-09
2.1.82	5 / 15	2025-11-27
2.1.81	5 / 15	2025-11-07
2.1.80	5 / 15	2025-10-29
2.1.79	5 / 15	2025-10-20
2.1.78	5 / 15	2025-10-03
2.1.77	5 / 15	2025-09-30
2.1.76	5 / 15	2025-09-30
2.1.75	5 / 15	2025-09-29
2.1.74	5 / 15	2025-09-29
2.1.73	5 / 15	2025-09-29
2.1.72	5 / 15	2025-09-12
2.1.71	5 / 15	2025-08-28
2.1.70	5 / 15	2025-08-27
2.1.69	5 / 15	2025-08-25
2.1.68	5 / 15	2025-08-19
2.1.67	5 / 15	2025-07-31
2.1.66	5 / 15	2025-06-26
2.1.65	5 / 15	2025-06-25
2.1.64	5 / 15	2025-06-24
2.1.63	5 / 15	2025-06-19
2.1.62	5 / 15	2025-06-19
2.1.61	5 / 15	2025-06-18
2.1.60	5 / 15	2025-06-18
2.1.59	5 / 15	2025-06-18
2.1.58	5 / 15	2025-06-18
2.1.57	5 / 15	2025-06-17
2.1.56	5 / 15	2025-06-17
2.1.55	5 / 15	2025-06-11
2.1.54	5 / 15	2025-06-10
2.1.53	5 / 16	2025-06-09
2.1.52	5 / 16	2025-06-06
2.1.51	5 / 16	2025-06-06
2.1.50	5 / 16	2025-06-06
2.1.49	5 / 16	2025-06-06
2.1.48	5 / 16	2025-06-05
2.1.47	5 / 15	2025-06-04

v2.1.97

1 finding

LOW No provenance attestation provenance

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

v2.1.96

1 finding

LOW No provenance attestation provenance

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

v2.1.94

1 finding

LOW No provenance attestation provenance

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

v2.1.93

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.

v2.1.92

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.

v2.1.90

1 finding

LOW No provenance attestation provenance

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

v2.1.89

1 finding

LOW No provenance attestation provenance

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

v2.1.88

1 finding

LOW No provenance attestation provenance

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

v2.1.86

1 finding

LOW No provenance attestation provenance

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

v2.1.85

1 finding

LOW No provenance attestation provenance

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

v2.1.84

1 finding

LOW No provenance attestation provenance

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

v2.1.83

1 finding

LOW No provenance attestation provenance

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

v2.1.82

1 finding

LOW No provenance attestation provenance

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

v2.1.81

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.

v2.1.80

1 finding

LOW No provenance attestation provenance

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

v2.1.79

1 finding

LOW No provenance attestation provenance

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

v2.1.78

1 finding

LOW No provenance attestation provenance

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

v2.1.77

1 finding

LOW No provenance attestation provenance

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

v2.1.76

1 finding

LOW No provenance attestation provenance

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

v2.1.75

1 finding

LOW No provenance attestation provenance

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

v2.1.74

1 finding

LOW No provenance attestation provenance

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

v2.1.73

1 finding

LOW No provenance attestation provenance

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

v2.1.72

1 finding

LOW No provenance attestation provenance

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

v2.1.71

1 finding

LOW No provenance attestation provenance

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

v2.1.70

1 finding

LOW No provenance attestation provenance

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

v2.1.69

1 finding

LOW No provenance attestation provenance

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

v2.1.68

1 finding

LOW No provenance attestation provenance

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

v2.1.67

1 finding

LOW No provenance attestation provenance

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

v2.1.66

1 finding

LOW No provenance attestation provenance

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

v2.1.65

1 finding

LOW No provenance attestation provenance

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

v2.1.64

1 finding

LOW No provenance attestation provenance

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

v2.1.63

1 finding

LOW No provenance attestation provenance

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

v2.1.62

1 finding

LOW No provenance attestation provenance

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

v2.1.61

1 finding

LOW No provenance attestation provenance

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

v2.1.60

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.

v2.1.59

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.

v2.1.58

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.

v2.1.57

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.

v2.1.56

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.

v2.1.55

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.

v2.1.54

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.

v2.1.53

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.

v2.1.52

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.

v2.1.51

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.

v2.1.50

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.

v2.1.49

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.

v2.1.48

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.

v2.1.47

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.