@miurajs/miura-framework
**The Declarative Framework Base Class** - Extend `MiuraFramework` to create your application with static configurations, making framework setup as simple as class inheritance.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the standard initial version for monorepo workspace packages; consistent with workspace:* deps pattern. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-ui | AI (phantom-deps): workspace:* monorepo sibling; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-render | AI (phantom-deps): workspace:* monorepo sibling; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-router | AI (phantom-deps): workspace:* monorepo sibling; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-element | AI (phantom-deps): workspace:* monorepo sibling; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-debugger | AI (phantom-deps): workspace:* monorepo sibling; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@miurajs/miura-data-flow | AI (phantom-deps): workspace:* monorepo sibling; not directly imported by design. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.4.7 | 4 / 1 | |
| 0.4.6 | 4 / 1 | |
| 0.4.5 | 4 / 1 | |
| 0.4.4 | 4 / 1 | |
| 0.4.3 | 4 / 1 | |
| 0.4.2 | 4 / 1 | |
| 0.4.1 | 4 / 1 | |
| 0.4.0 | 4 / 1 | |
| 0.3.47 | 4 / 1 | |
| 0.3.46 | 4 / 1 | |
| 0.3.45 | 4 / 1 | |
| 0.3.44 | 4 / 1 | |
| 0.3.43 | 4 / 1 | |
| 0.3.42 | 4 / 1 | |
| 0.3.41 | 4 / 1 | |
| 0.3.40 | 4 / 1 | |
| 0.3.39 | 4 / 1 | |
| 0.3.38 | 4 / 1 | |
| 0.3.37 | 4 / 1 | |
| 0.3.36 | 4 / 1 | |
| 0.3.35 | 4 / 1 | |
| 0.3.34 | 4 / 1 | |
| 0.3.33 | 4 / 1 | |
| 0.3.32 | 4 / 1 | |
| 0.3.31 | 4 / 1 | |
| 0.3.30 | 4 / 1 | |
| 0.3.29 | 4 / 1 | |
| 0.3.28 | 4 / 1 | |
| 0.3.27 | 4 / 1 | |
| 0.3.26 | 4 / 1 | |
| 0.3.25 | 4 / 1 | |
| 0.3.24 | 4 / 1 | |
| 0.3.23 | 4 / 1 | |
| 0.3.22 | 4 / 1 | |
| 0.3.21 | 4 / 1 | |
| 0.3.20 | 4 / 1 | |
| 0.3.19 | 4 / 1 | |
| 0.3.18 | 4 / 1 | |
| 0.3.17 | 4 / 1 | |
| 0.3.16 | 4 / 1 | |
| 0.3.15 | 4 / 1 | |
| 0.3.14 | 4 / 1 | |
| 0.3.13 | 4 / 1 | |
| 0.3.12 | 4 / 1 | |
| 0.3.11 | 4 / 1 | |
| 0.3.10 | 4 / 1 | |
| 0.3.9 | 4 / 1 | |
| 0.3.8 | 4 / 1 | |
| 0.3.7 | 4 / 1 | |
| 0.3.6 | 4 / 1 | |
| 0.3.5 | 4 / 1 |
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.