@umijs/max
@umijs/max
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 |
|---|---|---|---|---|
| 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 100 of 247)
| Version | Deps | Published |
|---|---|---|
| 4.6.82 | 6 / 0 | |
| 4.6.81 | 6 / 0 | |
| 4.6.80 | 6 / 0 | |
| 4.6.79 | 6 / 0 | |
| 4.6.78 | 6 / 0 | |
| 4.6.77 | 6 / 0 | |
| 4.6.76 | 6 / 0 | |
| 4.6.75 | 6 / 0 | |
| 4.6.69 | 6 / 0 | |
| 4.6.68 | 6 / 0 | |
| 4.6.67 | 6 / 0 | |
| 4.6.66 | 6 / 0 | |
| 4.6.65 | 6 / 0 | |
| 4.6.64 | 6 / 0 | |
| 4.6.63 | 6 / 0 | |
| 4.6.62 | 6 / 0 | |
| 4.6.61 | 6 / 0 | |
| 4.6.59 | 6 / 0 | |
| 4.6.58 | 6 / 0 | |
| 4.6.57 | 6 / 0 | |
| 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 | |
| 4.6.5 | 6 / 0 | |
| 4.6.4 | 6 / 0 | |
| 4.6.3 | 6 / 0 | |
| 4.6.2 | 6 / 0 | |
| 4.6.1 | 6 / 0 | |
| 4.6.0 | 6 / 0 | |
| 4.5.3 | 6 / 0 | |
| 4.5.2 | 6 / 0 | |
| 4.5.1 | 6 / 0 | |
| 4.5.0 | 6 / 0 | |
| 4.4.12 | 6 / 0 | |
| 4.4.11 | 6 / 0 | |
| 4.4.10 | 6 / 0 | |
| 4.4.9 | 6 / 0 | |
| 4.4.8 | 6 / 0 | |
| 4.4.7 | 6 / 0 | |
| 4.4.6 | 6 / 0 | |
| 4.4.5 | 6 / 0 | |
| 4.4.4 | 6 / 0 | |
| 4.4.3 | 6 / 0 | |
| 4.4.2 | 6 / 0 | |
| 4.4.1 | 6 / 0 | |
| 4.4.0 | 6 / 0 | |
| 4.3.36 | 6 / 0 | |
| 4.3.35 | 6 / 0 | |
| 4.3.34 | 6 / 0 | |
| 4.3.33 | 6 / 0 | |
| 4.3.32 | 6 / 0 | |
| 4.3.31 | 6 / 0 |
v4.6.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.80
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.75
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (zoomdong07) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v4.6.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.