umi
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; provenance attestation is a best-practice signal, not a blocker. | ai | |
| dependencies | unvetted-dep:@umijs/core | AI (dependencies): Internal monorepo sub-package pinned to same version; expected pattern for umi releases. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utils | AI (dependencies): Internal monorepo sub-package pinned to same version; expected pattern for umi releases. | ai | |
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): Internal monorepo sub-package pinned to same version; expected pattern for umi releases. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Umi is an active monorepo; version gaps are common between major release cycles for this established package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): umi is a well-known React framework brand, not a typo of uuid. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is typical for monorepo sub-packages; umi is a legitimate established framework. | ai | |
| phantom-deps | phantom-dep:@umijs/renderer-react | AI (phantom-deps): @umijs/renderer-react is a runtime dep used indirectly via config; stable false positive for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): umi is a well-known React framework brand, not a typo of joi. | ai |
Versions (showing 52 of 252)
| Version | Deps | Published |
|---|---|---|
| 4.0.51 | 12 / 0 | |
| 4.0.50 | 12 / 0 | |
| 4.0.49 | 12 / 0 | |
| 4.0.48 | 12 / 0 | |
| 4.0.47 | 12 / 0 | |
| 4.0.46 | 12 / 0 | |
| 4.0.45 | 12 / 0 | |
| 4.0.44 | 12 / 0 | |
| 4.0.43 | 12 / 0 | |
| 4.0.42 | 12 / 0 | |
| 4.0.41 | 12 / 0 | |
| 4.0.40 | 12 / 0 | |
| 4.0.39 | 12 / 0 | |
| 4.0.38 | 12 / 0 | |
| 4.0.37 | 12 / 0 | |
| 4.0.36 | 12 / 0 | |
| 4.0.35 | 12 / 0 | |
| 4.0.34 | 12 / 0 | |
| 4.0.33 | 12 / 0 | |
| 4.0.32 | 12 / 0 | |
| 4.0.31 | 12 / 0 | |
| 4.0.30 | 12 / 0 | |
| 4.0.29 | 12 / 0 | |
| 4.0.28 | 12 / 0 | |
| 4.0.27 | 12 / 0 | |
| 4.0.26 | 12 / 0 | |
| 4.0.25 | 12 / 0 | |
| 4.0.24 | 12 / 0 | |
| 4.0.23 | 12 / 0 | |
| 4.0.22 | 12 / 0 | |
| 4.0.21 | 12 / 0 | |
| 4.0.20 | 12 / 0 | |
| 4.0.19 | 12 / 0 | |
| 4.0.18 | 12 / 0 | |
| 4.0.17 | 12 / 0 | |
| 4.0.16 | 12 / 0 | |
| 4.0.15 | 12 / 0 | |
| 4.0.14 | 12 / 0 | |
| 4.0.13 | 12 / 0 | |
| 4.0.12 | 12 / 0 | |
| 4.0.11 | 12 / 0 | |
| 4.0.10 | 12 / 0 | |
| 4.0.9 | 12 / 0 | |
| 4.0.8 | 12 / 0 | |
| 4.0.7 | 11 / 0 | |
| 4.0.6 | 11 / 0 | |
| 4.0.5 | 11 / 0 | |
| 4.0.4 | 11 / 0 | |
| 4.0.3 | 11 / 0 | |
| 4.0.2 | 11 / 0 | |
| 4.0.1 | 11 / 0 | |
| 4.0.0 | 11 / 0 |
v4.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.