@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 2.11.1 | 4 / 2 | |
| 2.11.0 | 4 / 2 | |
| 2.10.24 | 4 / 2 | |
| 2.10.22 | 4 / 2 | |
| 2.10.21 | 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 | |
| 2.10.4 | 3 / 0 | |
| 2.10.3 | 3 / 0 | |
| 2.10.2 | 3 / 0 | |
| 2.10.1 | 3 / 0 | |
| 2.10.0 | 3 / 0 | |
| 2.9.73 | 3 / 0 | |
| 2.9.72 | 3 / 0 | |
| 2.9.71 | 3 / 0 | |
| 2.9.70 | 3 / 0 | |
| 2.9.69 | 3 / 0 | |
| 2.9.67 | 3 / 0 | |
| 2.9.66 | 3 / 0 | |
| 2.9.65 | 3 / 0 | |
| 2.9.64 | 3 / 0 | |
| 2.9.62 | 3 / 0 | |
| 2.9.59 | 3 / 0 | |
| 2.9.58 | 3 / 0 | |
| 2.9.57 | 3 / 0 | |
| 2.9.50 | 3 / 0 | |
| 2.9.48 | 3 / 0 | |
| 2.9.47 | 3 / 0 | |
| 2.9.46 | 3 / 0 | |
| 2.9.43 | 3 / 0 | |
| 2.9.42 | 3 / 0 | |
| 2.9.41 | 3 / 0 | |
| 2.9.39 | 3 / 0 | |
| 2.9.38 | 3 / 0 | |
| 2.9.36 | 3 / 0 | |
| 2.9.35 | 3 / 0 | |
| 2.9.33 | 3 / 0 | |
| 2.9.32 | 3 / 0 |
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.