@umijs/renderer-react
@umijs/renderer-react
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:@types/react | AI (phantom-deps): Framework-scoped types; stable pattern for React renderer packages. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Framework-scoped types; stable pattern for React renderer packages. | ai | |
| phantom-deps | phantom-dep:@types/react-router-config | AI (phantom-deps): Framework-scoped types; stable pattern for React renderer packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal README typical of internal monorepo packages; not indicative of spam. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 4.6.61 | 5 / 2 | |
| 4.6.59 | 5 / 2 | |
| 4.6.58 | 5 / 2 | |
| 4.6.57 | 5 / 2 | |
| 4.6.56 | 5 / 2 | |
| 3.5.42 | 5 / 0 | |
| 4.5.1-canary.20250928.1 | 5 / 2 | |
| 4.4.13-canary.20250917.1 | 5 / 2 | |
| 4.4.13-canary.20250915.3 | 5 / 2 | |
| 4.4.13-canary.20250915.2 | 5 / 2 | |
| 4.4.13-canary.20250915.1 | 5 / 2 | |
| 4.4.13-canary.20250912.1 | 5 / 2 | |
| 4.4.13-canary.20250911.1 | 5 / 2 | |
| 4.4.13-canary.20250910.1 | 5 / 2 | |
| 4.0.0-canary.20260325.1 | 5 / 2 | |
| 4.0.0-canary.20260303.1 | 5 / 2 | |
| 4.0.0-canary.20260106.2 | 5 / 2 | |
| 4.0.0-canary.20260106.1 | 5 / 2 | |
| 4.0.0-canary.20260105.1 | 5 / 2 | |
| 4.0.0-canary.20260105.0 | 5 / 2 | |
| 4.0.0-canary.20251209.1 | 5 / 2 | |
| 4.0.0-canary.20251124.1 | 5 / 2 | |
| 4.0.0-canary.20251120.1 | 5 / 2 | |
| 4.0.0-canary.20251116.1 | 5 / 2 | |
| 4.0.0-canary.20251113.1 | 5 / 2 | |
| 4.0.0-canary.20251110.1 | 5 / 2 | |
| 4.0.0-canary.20251104.1 | 5 / 2 | |
| 4.0.0-canary.20251102.1 | 5 / 2 | |
| 4.0.0-canary.20251027.1 | 5 / 2 | |
| 4.0.0-canary.20250918.1 | 5 / 2 | |
| 4.0.0-canary.20250731.1 | 5 / 2 | |
| 4.0.0-canary.20250413.1 | 5 / 2 |
v4.6.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.