@miurajs/miura-ui
Miura UI should be rebuilt as a workspace-grade design system for Miura applications: fast web components, accessible interaction primitives, and higher-level surfaces for admin, editorial, notebook, kanban, calendar, and graph-like product UIs.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.4.5 | 2 / 5 | |
| 0.4.4 | 2 / 5 | |
| 0.2.4 | 2 / 5 | |
| 0.2.3 | 2 / 5 | |
| 0.2.2 | 2 / 5 | |
| 0.2.1 | 2 / 5 | |
| 0.2.0 | 2 / 5 | |
| 0.1.19 | 2 / 5 | |
| 0.1.18 | 2 / 5 | |
| 0.1.17 | 2 / 5 | |
| 0.1.16 | 1 / 5 | |
| 0.1.15 | 1 / 5 | |
| 0.1.14 | 1 / 5 | |
| 0.1.13 | 1 / 5 | |
| 0.1.12 | 1 / 5 | |
| 0.1.11 | 1 / 5 | |
| 0.1.10 | 1 / 5 | |
| 0.1.9 | 1 / 5 | |
| 0.1.8 | 1 / 5 | |
| 0.1.7 | 1 / 5 | |
| 0.1.6 | 1 / 5 | |
| 0.1.5 | 1 / 5 | |
| 0.1.4 | 1 / 5 | |
| 0.1.3 | 1 / 5 | |
| 0.1.0 | 1 / 5 | |
| 0.0.1 | 1 / 5 |
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.