@umijs/plugins
@umijs/plugins
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established UmiJS monorepo package; no material changes from prior version; publisher has approved track record. | ai | |
| dependencies | unvetted-dep:dva-immer | AI (dependencies): Known UmiJS ecosystem dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:dva-core | AI (dependencies): Known UmiJS ecosystem dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:dva-loading | AI (dependencies): Known UmiJS ecosystem dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@umijs/valtio | AI (dependencies): First-party @umijs scoped package; stable for this package. | ai | |
| dependencies | unvetted-dep:@umijs/bundler-utils | AI (dependencies): First-party @umijs scoped package; stable for this package. | ai | |
| dependencies | unvetted-dep:antd-dayjs-webpack-plugin | AI (dependencies): Known Ant Design ecosystem plugin; stable for this package. | ai | |
| dependencies | unvetted-dep:@ant-design/antd-theme-variable | AI (dependencies): Known Ant Design scoped package; stable for this package. | ai | |
| dependencies | unvetted-dep:@ant-design/moment-webpack-plugin | AI (dependencies): Known Ant Design scoped package; stable for this package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query-devtools | AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Plugin package; referenced in generated config/templates, not directly imported. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dependency for TypeScript compiled output. | ai | |
| phantom-deps | phantom-dep:@ant-design/pro-components | AI (phantom-deps): Plugin package; dependency is injected into user projects, not directly imported. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; sparse metadata is consistent across all @umijs/* packages. | ai |
Versions (showing 100 of 225)
| Version | Deps | Published |
|---|---|---|
| 4.3.6 | 30 / 2 | |
| 4.3.5 | 30 / 2 | |
| 4.3.4 | 30 / 2 | |
| 4.3.3 | 30 / 2 | |
| 4.3.2 | 30 / 2 | |
| 4.3.1 | 30 / 2 | |
| 4.3.0 | 30 / 2 | |
| 4.2.15 | 30 / 2 | |
| 4.2.14 | 30 / 2 | |
| 4.2.13 | 30 / 2 | |
| 4.2.12 | 30 / 2 | |
| 4.2.11 | 30 / 2 | |
| 4.2.10 | 30 / 2 | |
| 4.2.9 | 30 / 2 | |
| 4.2.8 | 30 / 2 | |
| 4.2.7 | 30 / 2 | |
| 4.2.6 | 30 / 2 | |
| 4.2.5 | 30 / 2 | |
| 4.2.4 | 30 / 2 | |
| 4.2.3 | 30 / 2 | |
| 4.2.2 | 30 / 2 | |
| 4.2.1 | 30 / 2 | |
| 4.2.0 | 30 / 2 | |
| 4.1.10 | 30 / 2 | |
| 4.1.9 | 30 / 2 | |
| 4.1.8 | 30 / 2 | |
| 4.1.7 | 30 / 2 | |
| 4.1.6 | 30 / 2 | |
| 4.1.5 | 30 / 2 | |
| 4.1.4 | 30 / 2 | |
| 4.1.3 | 30 / 2 | |
| 4.1.2 | 30 / 2 | |
| 4.1.1 | 30 / 2 | |
| 4.1.0 | 30 / 2 | |
| 4.0.90 | 30 / 2 | |
| 4.0.89 | 30 / 2 | |
| 4.0.88 | 30 / 2 | |
| 4.0.87 | 29 / 2 | |
| 4.0.86 | 29 / 2 | |
| 4.0.85 | 29 / 2 | |
| 4.0.84 | 29 / 2 | |
| 4.0.83 | 29 / 2 | |
| 4.0.82 | 29 / 2 | |
| 4.0.81 | 29 / 2 | |
| 4.0.80 | 29 / 2 | |
| 4.0.79 | 29 / 2 | |
| 4.0.78 | 29 / 2 | |
| 4.0.77 | 29 / 2 | |
| 4.0.76 | 29 / 2 | |
| 4.0.75 | 29 / 2 | |
| 4.0.74 | 29 / 2 | |
| 4.0.73 | 29 / 2 | |
| 4.0.72 | 29 / 2 | |
| 4.0.71 | 29 / 2 | |
| 4.0.70 | 29 / 2 | |
| 4.0.69 | 28 / 2 | |
| 4.0.68 | 28 / 2 | |
| 4.0.67 | 28 / 2 | |
| 4.0.66 | 27 / 2 | |
| 4.0.65 | 27 / 2 | |
| 4.0.64 | 27 / 2 | |
| 4.0.63 | 27 / 2 | |
| 4.0.62 | 27 / 2 | |
| 4.0.61 | 27 / 2 | |
| 4.0.60 | 27 / 2 | |
| 4.0.59 | 27 / 2 | |
| 4.0.58 | 27 / 2 | |
| 4.0.57 | 27 / 2 | |
| 4.0.56 | 27 / 2 | |
| 4.0.55 | 27 / 2 | |
| 4.0.54 | 27 / 2 | |
| 4.0.53 | 27 / 2 | |
| 4.0.52 | 27 / 2 | |
| 4.0.51 | 27 / 2 | |
| 4.0.50 | 27 / 2 | |
| 4.0.49 | 27 / 2 | |
| 4.0.48 | 27 / 2 | |
| 4.0.47 | 27 / 2 | |
| 4.0.46 | 27 / 2 | |
| 4.0.45 | 27 / 2 | |
| 4.0.44 | 27 / 2 | |
| 4.0.43 | 27 / 2 | |
| 4.0.42 | 24 / 2 | |
| 4.0.41 | 24 / 2 | |
| 4.0.40 | 24 / 2 | |
| 4.0.39 | 24 / 2 | |
| 4.0.38 | 24 / 2 | |
| 4.0.37 | 24 / 2 | |
| 4.0.36 | 24 / 2 | |
| 4.0.35 | 24 / 2 | |
| 4.0.34 | 23 / 2 | |
| 4.0.33 | 23 / 2 | |
| 4.0.32 | 23 / 2 | |
| 4.0.31 | 23 / 2 | |
| 4.0.30 | 23 / 2 | |
| 4.0.29 | 23 / 1 | |
| 4.0.28 | 23 / 1 | |
| 4.0.27 | 23 / 1 | |
| 4.0.26 | 22 / 1 | |
| 4.0.25 | 22 / 1 |
v4.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.