@mpxjs/core
mpx runtime core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package in the @mpxjs namespace; legitimate Didi MPX framework, not a typosquat of cors. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.10.24 | 4 / 2 | |
| 2.10.22 | 4 / 2 | |
| 2.10.20 | 3 / 2 | |
| 2.10.19 | 3 / 2 | |
| 2.10.18 | 3 / 2 | |
| 2.10.17 | 3 / 2 | |
| 2.10.16 | 3 / 0 | |
| 2.10.15 | 3 / 0 | |
| 2.10.13 | 3 / 0 | |
| 2.10.12 | 3 / 0 | |
| 2.10.11 | 3 / 0 | |
| 2.10.10 | 3 / 0 | |
| 2.10.9 | 3 / 0 | |
| 2.10.8 | 3 / 0 | |
| 2.10.7 | 3 / 0 | |
| 2.10.6 | 3 / 0 | |
| 2.10.5 | 3 / 0 |
v2.10.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.20
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.18
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.17
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.16
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.15
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.13
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.12
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.11
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.10
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.9
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.8
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.7
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.6
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.5
2 findingsPackage name '@mpxjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.