umi
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 |
|---|---|---|---|---|
| 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 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 4.6.57 | 12 / 0 | |
| 4.6.56 | 12 / 0 | |
| 4.6.55 | 12 / 0 | |
| 4.6.54 | 12 / 0 | |
| 4.6.53 | 12 / 0 | |
| 4.6.52 | 12 / 0 | |
| 4.6.51 | 12 / 0 | |
| 4.6.50 | 12 / 0 | |
| 4.6.49 | 12 / 0 | |
| 4.6.48 | 12 / 0 | |
| 4.6.47 | 12 / 0 | |
| 4.6.46 | 12 / 0 | |
| 4.6.45 | 12 / 0 | |
| 4.6.44 | 12 / 0 | |
| 4.6.43 | 12 / 0 | |
| 4.6.42 | 12 / 0 | |
| 4.6.41 | 12 / 0 | |
| 4.6.40 | 12 / 0 | |
| 4.6.39 | 12 / 0 | |
| 4.6.38 | 12 / 0 | |
| 4.6.37 | 12 / 0 | |
| 4.6.36 | 12 / 0 | |
| 4.6.35 | 12 / 0 | |
| 4.6.34 | 12 / 0 | |
| 4.6.33 | 12 / 0 | |
| 4.6.32 | 12 / 0 | |
| 4.6.31 | 12 / 0 | |
| 4.6.30 | 12 / 0 | |
| 4.6.29 | 12 / 0 | |
| 4.6.28 | 12 / 0 | |
| 4.6.27 | 12 / 0 | |
| 4.6.26 | 12 / 0 | |
| 4.6.25 | 12 / 0 | |
| 4.6.24 | 12 / 0 | |
| 4.6.23 | 12 / 0 | |
| 4.6.22 | 12 / 0 | |
| 4.6.21 | 12 / 0 | |
| 4.6.20 | 12 / 0 | |
| 4.6.19 | 12 / 0 | |
| 4.6.18 | 12 / 0 | |
| 4.6.17 | 12 / 0 | |
| 4.6.16 | 12 / 0 | |
| 4.6.15 | 12 / 0 | |
| 4.6.14 | 12 / 0 | |
| 4.6.13 | 12 / 0 | |
| 4.6.12 | 12 / 0 | |
| 4.6.11 | 12 / 0 | |
| 4.6.10 | 12 / 0 | |
| 4.6.9 | 12 / 0 | |
| 4.6.8 | 12 / 0 | |
| 4.6.7 | 12 / 0 |
v4.6.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.