@miurajs/miura-render
The rendering engine for the miura framework. Provides tagged template literals (`html`/`css`), a state-machine parser, a binding manager, structural directives, and performance utilities including LIS-based keyed diffing, async rendering, and virtual scr
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@miura/miura-debugger | AI (phantom-deps): workspace:* monorepo internal dep; not directly imported in published code by design. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the initial version of an established monorepo package with 65 versions and 103 approved packages from the publisher. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 0.4.7 | 1 / 5 | |
| 0.4.6 | 1 / 5 | |
| 0.4.5 | 1 / 5 | |
| 0.4.4 | 1 / 5 | |
| 0.4.3 | 1 / 5 | |
| 0.4.2 | 1 / 5 | |
| 0.4.1 | 1 / 5 | |
| 0.4.0 | 1 / 5 | |
| 0.3.33 | 1 / 5 | |
| 0.3.32 | 1 / 5 | |
| 0.3.31 | 1 / 5 | |
| 0.3.30 | 1 / 5 | |
| 0.3.29 | 1 / 5 | |
| 0.3.28 | 1 / 5 | |
| 0.3.27 | 1 / 5 | |
| 0.3.26 | 1 / 5 | |
| 0.3.25 | 1 / 5 | |
| 0.3.24 | 1 / 5 | |
| 0.3.23 | 1 / 5 | |
| 0.3.22 | 1 / 5 | |
| 0.3.21 | 1 / 5 | |
| 0.3.20 | 1 / 5 | |
| 0.3.19 | 1 / 5 | |
| 0.3.18 | 1 / 5 | |
| 0.3.17 | 1 / 5 | |
| 0.3.16 | 1 / 5 | |
| 0.3.15 | 1 / 5 | |
| 0.3.14 | 1 / 5 | |
| 0.3.13 | 1 / 5 | |
| 0.3.12 | 1 / 5 | |
| 0.3.11 | 1 / 5 | |
| 0.3.10 | 1 / 5 | |
| 0.3.9 | 1 / 5 | |
| 0.3.8 | 1 / 5 | |
| 0.3.7 | 1 / 5 | |
| 0.3.6 | 1 / 5 | |
| 0.3.5 | 1 / 5 | |
| 0.3.4 | 1 / 5 | |
| 0.3.3 | 1 / 5 | |
| 0.3.2 | 1 / 5 | |
| 0.3.1 | 1 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.2.20 | 1 / 5 | |
| 0.2.19 | 1 / 5 | |
| 0.2.18 | 1 / 5 | |
| 0.2.17 | 1 / 5 | |
| 0.2.16 | 1 / 5 | |
| 0.2.15 | 1 / 5 | |
| 0.2.14 | 1 / 5 | |
| 0.2.13 | 1 / 5 | |
| 0.2.12 | 1 / 5 | |
| 0.2.11 | 1 / 5 | |
| 0.2.10 | 1 / 5 | |
| 0.2.9 | 1 / 5 | |
| 0.2.8 | 1 / 5 | |
| 0.2.7 | 1 / 5 | |
| 0.2.6 | 1 / 5 | |
| 0.2.5 | 1 / 5 | |
| 0.2.4 | 1 / 5 | |
| 0.2.3 | 1 / 5 | |
| 0.2.2 | 1 / 5 | |
| 0.2.0 | 1 / 5 | |
| 0.1.1 | 1 / 5 | |
| 0.1.0 | 1 / 5 | |
| 0.0.0 | 1 / 5 |
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.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.