@umijs/max
@umijs/max
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): @umijs/max is a scoped UmiJS framework package, not a typosquat of mobx; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:antd | AI (phantom-deps): antd is an intentional re-exported/peer dependency in the UmiJS max meta-framework. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): eslint is exposed via eslint.js config re-export; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:stylelint | AI (phantom-deps): stylelint is exposed via stylelint.js config re-export; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:@umijs/lint | AI (phantom-deps): Same-org scoped dep re-exported through lint config files; stable false positive. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 4.6.56 | 6 / 0 | |
| 4.6.55 | 6 / 0 | |
| 4.6.54 | 6 / 0 | |
| 4.6.53 | 6 / 0 | |
| 4.6.52 | 6 / 0 | |
| 4.6.51 | 6 / 0 | |
| 4.6.50 | 6 / 0 | |
| 4.6.49 | 6 / 0 | |
| 4.6.48 | 6 / 0 | |
| 4.6.47 | 6 / 0 | |
| 4.6.46 | 6 / 0 | |
| 4.6.45 | 6 / 0 | |
| 4.6.44 | 6 / 0 | |
| 4.6.43 | 6 / 0 | |
| 4.6.42 | 6 / 0 | |
| 4.6.41 | 6 / 0 | |
| 4.6.40 | 6 / 0 | |
| 4.6.39 | 6 / 0 | |
| 4.6.38 | 6 / 0 | |
| 4.6.37 | 6 / 0 | |
| 4.6.36 | 6 / 0 | |
| 4.6.35 | 6 / 0 | |
| 4.6.34 | 6 / 0 | |
| 4.6.33 | 6 / 0 | |
| 4.6.32 | 6 / 0 | |
| 4.6.31 | 6 / 0 | |
| 4.6.30 | 6 / 0 | |
| 4.6.29 | 6 / 0 | |
| 4.6.28 | 6 / 0 | |
| 4.6.27 | 6 / 0 | |
| 4.6.26 | 6 / 0 | |
| 4.6.25 | 6 / 0 | |
| 4.6.24 | 6 / 0 | |
| 4.6.23 | 6 / 0 | |
| 4.6.22 | 6 / 0 | |
| 4.6.21 | 6 / 0 | |
| 4.6.20 | 6 / 0 | |
| 4.6.19 | 6 / 0 | |
| 4.6.18 | 6 / 0 | |
| 4.6.17 | 6 / 0 | |
| 4.6.16 | 6 / 0 | |
| 4.6.15 | 6 / 0 | |
| 4.6.14 | 6 / 0 | |
| 4.6.13 | 6 / 0 | |
| 4.6.12 | 6 / 0 | |
| 4.6.11 | 6 / 0 | |
| 4.6.10 | 6 / 0 | |
| 4.6.9 | 6 / 0 | |
| 4.6.8 | 6 / 0 | |
| 4.6.7 | 6 / 0 | |
| 4.6.6 | 6 / 0 |
v4.6.56
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.38
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.