@miurajs/miura
The main package for the miura framework, bundling all core modules.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@miurajs/miura-framework | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-ui | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-render | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-router | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-element | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-debugger | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-security | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-data-flow | AI (phantom-deps): Monorepo aggregator; same-org dependencies intentionally bundled for re-export. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 127 versions of this package; not a per-version concern. | ai |
Versions (showing 51 of 125)
| Version | Deps | Published |
|---|---|---|
| 2.5.12 | 12 / 1 | |
| 2.5.11 | 12 / 1 | |
| 2.5.10 | 12 / 1 | |
| 2.5.9 | 12 / 1 | |
| 2.5.8 | 8 / 1 | |
| 2.5.7 | 8 / 1 | |
| 2.5.5 | 8 / 1 | |
| 2.5.4 | 8 / 1 | |
| 2.5.3 | 8 / 1 | |
| 2.5.2 | 8 / 1 | |
| 2.5.1 | 8 / 1 | |
| 2.5.0 | 8 / 1 | |
| 2.4.51 | 8 / 1 | |
| 2.4.50 | 8 / 1 | |
| 2.4.49 | 8 / 1 | |
| 2.4.48 | 8 / 1 | |
| 2.4.47 | 8 / 1 | |
| 2.4.46 | 8 / 1 | |
| 2.4.45 | 8 / 1 | |
| 2.4.44 | 8 / 1 | |
| 2.4.43 | 8 / 1 | |
| 2.4.42 | 8 / 1 | |
| 2.4.41 | 8 / 1 | |
| 2.4.40 | 8 / 1 | |
| 2.4.39 | 8 / 1 | |
| 2.4.38 | 8 / 1 | |
| 2.4.37 | 8 / 1 | |
| 2.4.36 | 8 / 1 | |
| 2.4.35 | 8 / 1 | |
| 2.4.34 | 8 / 1 | |
| 2.4.33 | 8 / 1 | |
| 2.4.32 | 8 / 1 | |
| 2.4.31 | 8 / 1 | |
| 2.4.30 | 8 / 1 | |
| 2.4.29 | 8 / 1 | |
| 2.4.28 | 8 / 1 | |
| 2.4.27 | 8 / 1 | |
| 2.4.26 | 8 / 1 | |
| 2.4.25 | 8 / 1 | |
| 2.4.24 | 8 / 1 | |
| 2.4.22 | 8 / 1 | |
| 2.4.21 | 8 / 1 | |
| 2.4.20 | 8 / 1 | |
| 2.4.19 | 8 / 1 | |
| 2.4.18 | 8 / 1 | |
| 2.4.17 | 8 / 1 | |
| 2.4.16 | 8 / 1 | |
| 2.4.15 | 8 / 1 | |
| 2.4.14 | 8 / 1 | |
| 2.4.13 | 8 / 1 | |
| 2.4.12 | 8 / 1 |
v2.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.