@umijs/runtime
@umijs/runtime
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): peachscript is a known UmiJS team member who has been publishing @umijs/* packages since 2022-07-04 across many versions. This is a legitimate team publishing arrangement, not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @umijs/runtime is a monorepo sub-package; sparse README and description are typical for internal scoped packages in the UmiJS ecosystem. | ai | |
| phantom-deps | phantom-dep:@types/react-router | AI (phantom-deps): TypeScript type definitions for react-router, a direct dependency; standard practice for typed routing support. | ai | |
| phantom-deps | phantom-dep:@types/react-router-dom | AI (phantom-deps): TypeScript type definitions for react-router-dom, a direct dependency; standard practice for typed routing support. | ai |
Versions (showing 100 of 138)
| Version | Deps | Published |
|---|---|---|
| 3.5.43 | 6 / 0 | |
| 3.5.42 | 6 / 0 | |
| 3.5.41 | 6 / 0 | |
| 3.5.40 | 6 / 0 | |
| 3.5.39 | 6 / 0 | |
| 3.5.38 | 6 / 0 | |
| 3.5.37 | 6 / 0 | |
| 3.5.36 | 6 / 0 | |
| 3.5.35 | 6 / 0 | |
| 3.5.34 | 6 / 0 | |
| 3.5.33 | 6 / 0 | |
| 3.5.32 | 6 / 0 | |
| 3.5.31 | 6 / 0 | |
| 3.5.30 | 6 / 0 | |
| 3.5.29 | 6 / 0 | |
| 3.5.28 | 6 / 0 | |
| 3.5.27 | 6 / 0 | |
| 3.5.26 | 6 / 0 | |
| 3.5.25 | 6 / 0 | |
| 3.5.24 | 6 / 0 | |
| 3.5.23 | 6 / 0 | |
| 3.5.22 | 6 / 0 | |
| 3.5.21 | 6 / 0 | |
| 3.5.20 | 6 / 0 | |
| 3.5.19 | 6 / 0 | |
| 3.5.18 | 6 / 0 | |
| 3.5.17 | 6 / 0 | |
| 3.5.16 | 6 / 0 | |
| 3.5.15 | 6 / 0 | |
| 3.5.14 | 6 / 0 | |
| 3.5.13 | 6 / 0 | |
| 3.5.12 | 6 / 0 | |
| 3.5.11 | 6 / 0 | |
| 3.5.10 | 6 / 0 | |
| 3.5.9 | 6 / 0 | |
| 3.5.8 | 6 / 0 | |
| 3.5.7 | 6 / 0 | |
| 3.5.6 | 6 / 0 | |
| 3.5.5 | 6 / 0 | |
| 3.5.4 | 6 / 0 | |
| 3.5.3 | 6 / 0 | |
| 3.5.2 | 6 / 0 | |
| 3.5.1 | 6 / 0 | |
| 3.5.0 | 6 / 0 | |
| 3.4.25 | 6 / 0 | |
| 3.4.24 | 6 / 0 | |
| 3.4.23 | 6 / 0 | |
| 3.4.22 | 6 / 0 | |
| 3.4.21 | 6 / 0 | |
| 3.4.20 | 6 / 0 | |
| 3.4.19 | 6 / 0 | |
| 3.4.18 | 6 / 0 | |
| 3.4.17 | 6 / 0 | |
| 3.4.16 | 6 / 0 | |
| 3.4.15 | 6 / 0 | |
| 3.4.14 | 6 / 0 | |
| 3.4.13 | 6 / 0 | |
| 3.4.12 | 6 / 0 | |
| 3.4.11 | 6 / 0 | |
| 3.4.10 | 6 / 0 | |
| 3.4.9 | 6 / 0 | |
| 3.4.8 | 6 / 0 | |
| 3.4.7 | 6 / 0 | |
| 3.4.6 | 6 / 0 | |
| 3.4.5 | 6 / 0 | |
| 3.4.4 | 6 / 0 | |
| 3.4.3 | 6 / 0 | |
| 3.4.2 | 6 / 0 | |
| 3.4.1 | 6 / 0 | |
| 3.4.0 | 6 / 0 | |
| 3.3.15 | 6 / 0 | |
| 3.3.14 | 6 / 0 | |
| 3.3.12 | 6 / 0 | |
| 3.3.11 | 6 / 0 | |
| 3.3.10 | 6 / 0 | |
| 3.3.9 | 6 / 0 | |
| 3.3.8 | 6 / 0 | |
| 3.3.7 | 6 / 0 | |
| 3.3.6 | 6 / 0 | |
| 3.3.5 | 6 / 0 | |
| 3.3.4 | 6 / 0 | |
| 3.3.3 | 6 / 0 | |
| 3.3.2 | 6 / 0 | |
| 3.3.1 | 6 / 0 | |
| 3.3.0 | 6 / 0 | |
| 3.2.28 | 6 / 0 | |
| 3.2.27 | 6 / 0 | |
| 3.2.26 | 6 / 0 | |
| 3.2.25 | 6 / 0 | |
| 3.2.24 | 6 / 0 | |
| 3.2.23 | 6 / 0 | |
| 3.2.22 | 6 / 0 | |
| 3.2.21 | 6 / 0 | |
| 3.2.20 | 6 / 0 | |
| 3.2.19 | 6 / 0 | |
| 3.2.18 | 6 / 0 | |
| 3.2.17 | 6 / 0 | |
| 3.2.16 | 6 / 0 | |
| 3.2.15 | 6 / 0 | |
| 3.2.14 | 6 / 0 |
v3.5.43
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.40
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-13. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.39
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-31. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.38
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.37
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.34
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.33
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-25. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.32
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.31
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-29. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.30
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.29
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.27
2 findingsThis version was published by a different npm account than previous versions on 2022-07-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.26
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-08. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.25
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-05-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.