@umijs/preset-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): Provenance adoption is sparse; not a disqualifier for established packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): zoomdong07 added to a large, active monorepo team; no other compromise signals present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are within the @umijs ecosystem and @stagewise/toolbar; consistent with normal UmiJS feature additions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large UmiJS monorepo with 526 versions; publisher has established track record with 286 approved packages. | ai | |
| dependencies | unvetted-dep:@umijs/utils | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utils | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-esbuild | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/babel-preset-umi | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utoopack | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/ui | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/history | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/did-you-know | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/es-module-parser | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:less-plugin-resolve | AI (dependencies): Known build utility; no malware indicators. | ai | |
| dependencies | unvetted-dep:current-script-polyfill | AI (dependencies): Small polyfill; no malware indicators. | ai | |
| dependencies | unvetted-dep:click-to-react-component | AI (dependencies): Known dev-experience utility; no malware indicators. | ai | |
| phantom-deps | phantom-dep:babel-plugin-react-compiler | AI (phantom-deps): Listed as direct dep in package.json; phantom-dep heuristic false positive. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-mako | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@stagewise/toolbar | AI (dependencies): Dev toolbar utility; no malware indicators. | ai | |
| dependencies | unvetted-dep:@umijs/core | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| dependencies | unvetted-dep:@umijs/mfsu | AI (dependencies): Sibling monorepo package; expected unvetted dep for this package family. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Fires in compiled/os-locale — a bundled devDep for locale detection; not a runtime attack surface. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README/description is expected for internal preset packages. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in compiled vendor bundles (isnumber/queue-microtask); not malicious, standard minified library code. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Fires in compiled/body-parser — standard HTTP middleware; env read is benign config pattern. | ai |
Versions (showing 88 of 188)
| Version | Deps | Published |
|---|---|---|
| 4.0.88 | 35 / 12 | |
| 4.0.87 | 35 / 12 | |
| 4.0.86 | 33 / 12 | |
| 4.0.85 | 33 / 12 | |
| 4.0.84 | 33 / 12 | |
| 4.0.83 | 33 / 12 | |
| 4.0.82 | 33 / 12 | |
| 4.0.81 | 33 / 12 | |
| 4.0.80 | 33 / 12 | |
| 4.0.79 | 33 / 12 | |
| 4.0.78 | 33 / 12 | |
| 4.0.77 | 33 / 12 | |
| 4.0.76 | 33 / 12 | |
| 4.0.75 | 33 / 12 | |
| 4.0.74 | 33 / 12 | |
| 4.0.73 | 33 / 12 | |
| 4.0.72 | 33 / 12 | |
| 4.0.71 | 33 / 12 | |
| 4.0.70 | 33 / 12 | |
| 4.0.69 | 32 / 12 | |
| 4.0.68 | 32 / 12 | |
| 4.0.67 | 32 / 12 | |
| 4.0.66 | 32 / 12 | |
| 4.0.65 | 32 / 12 | |
| 4.0.64 | 32 / 12 | |
| 4.0.63 | 31 / 12 | |
| 4.0.62 | 30 / 12 | |
| 4.0.61 | 30 / 12 | |
| 4.0.60 | 30 / 12 | |
| 4.0.59 | 29 / 12 | |
| 4.0.58 | 29 / 12 | |
| 4.0.57 | 29 / 12 | |
| 4.0.56 | 29 / 12 | |
| 4.0.55 | 29 / 12 | |
| 4.0.54 | 29 / 12 | |
| 4.0.53 | 30 / 11 | |
| 4.0.52 | 30 / 11 | |
| 4.0.51 | 30 / 11 | |
| 4.0.50 | 30 / 11 | |
| 4.0.49 | 30 / 11 | |
| 4.0.48 | 30 / 11 | |
| 4.0.47 | 30 / 11 | |
| 4.0.46 | 30 / 11 | |
| 4.0.45 | 30 / 11 | |
| 4.0.44 | 30 / 11 | |
| 4.0.43 | 30 / 11 | |
| 4.0.41 | 28 / 11 | |
| 4.0.40 | 28 / 11 | |
| 4.0.39 | 28 / 11 | |
| 4.0.38 | 28 / 11 | |
| 4.0.37 | 28 / 11 | |
| 4.0.36 | 28 / 11 | |
| 4.0.35 | 28 / 11 | |
| 4.0.34 | 28 / 11 | |
| 4.0.33 | 28 / 11 | |
| 4.0.32 | 28 / 11 | |
| 4.0.31 | 28 / 11 | |
| 4.0.30 | 28 / 11 | |
| 4.0.29 | 28 / 11 | |
| 4.0.28 | 27 / 11 | |
| 4.0.27 | 27 / 11 | |
| 4.0.26 | 27 / 11 | |
| 4.0.25 | 26 / 11 | |
| 4.0.24 | 26 / 11 | |
| 4.0.23 | 26 / 11 | |
| 4.0.22 | 26 / 11 | |
| 4.0.21 | 27 / 11 | |
| 4.0.20 | 27 / 11 | |
| 4.0.19 | 27 / 11 | |
| 4.0.18 | 26 / 11 | |
| 4.0.17 | 26 / 11 | |
| 4.0.16 | 26 / 11 | |
| 4.0.15 | 24 / 11 | |
| 4.0.14 | 24 / 11 | |
| 4.0.13 | 22 / 11 | |
| 4.0.12 | 22 / 11 | |
| 4.0.11 | 22 / 11 | |
| 4.0.10 | 22 / 11 | |
| 4.0.9 | 22 / 11 | |
| 4.0.8 | 22 / 11 | |
| 4.0.7 | 22 / 11 | |
| 4.0.6 | 22 / 11 | |
| 4.0.5 | 21 / 11 | |
| 4.0.4 | 21 / 11 | |
| 4.0.3 | 20 / 11 | |
| 4.0.2 | 20 / 11 | |
| 4.0.1 | 20 / 11 | |
| 4.0.0 | 20 / 11 |
v4.0.88
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.87
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.86
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.85
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.84
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.83
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.82
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.81
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.80
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.79
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.78
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.77
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.76
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.75
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.74
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.73
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.72
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.71
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.70
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.69
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.68
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.67
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.66
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.65
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.64
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.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.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.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.