@rue-js/jsx-dev-runtime
@rue-js/jsx-dev-runtime
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rue-js | AI (dependencies): rue-js is a sibling package in the same rue-js monorepo; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.8.5 | 1 / 0 | |
| 0.1.1 | 1 / 0 | |
| 0.0.39 | 1 / 0 | |
| 0.0.33 | 1 / 0 | |
| 0.0.32 | 1 / 0 | |
| 0.0.31 | 1 / 0 | |
| 0.0.30 | 1 / 0 | |
| 0.0.29 | 1 / 0 | |
| 0.0.28 | 1 / 0 | |
| 0.0.27 | 1 / 0 | |
| 0.0.25 | 1 / 0 | |
| 0.0.21 | 1 / 0 | |
| 0.0.20 | 1 / 0 |
v0.8.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (xiangminliu1990) on 2026-07-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.