@mpxjs/mpx-cube-ui
mpx components library
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
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 1.4.17 | 0 / 1 | |
| 1.4.16 | 0 / 1 | |
| 1.4.15 | 0 / 1 | |
| 1.4.14 | 0 / 1 | |
| 1.4.13 | 0 / 1 | |
| 1.4.12 | 0 / 1 | |
| 1.4.11 | 0 / 1 | |
| 1.4.10 | 0 / 1 | |
| 1.4.9 | 0 / 1 | |
| 1.4.8 | 0 / 1 | |
| 1.4.7 | 0 / 1 | |
| 1.4.6 | 0 / 1 | |
| 1.4.5 | 0 / 1 | |
| 1.4.4 | 0 / 1 | |
| 1.4.3 | 0 / 1 | |
| 1.4.2 | 0 / 1 | |
| 1.4.1 | 0 / 1 | |
| 1.4.0 | 0 / 1 | |
| 1.3.17 | 0 / 1 | |
| 1.3.16 | 0 / 1 | |
| 1.3.15 | 0 / 1 | |
| 1.3.14 | 0 / 1 | |
| 1.3.13 | 0 / 1 | |
| 1.3.12 | 0 / 1 | |
| 1.3.11 | 0 / 1 | |
| 1.3.10 | 0 / 1 | |
| 1.3.9 | 0 / 1 | |
| 1.3.8 | 0 / 1 | |
| 1.3.7 | 0 / 1 | |
| 1.3.6 | 0 / 1 | |
| 1.3.5 | 0 / 1 | |
| 1.3.4 | 0 / 1 | |
| 1.3.3 | 0 / 1 | |
| 1.3.2 | 0 / 1 | |
| 1.3.1 | 0 / 1 | |
| 1.3.0 | 0 / 1 | |
| 1.2.9 | 0 / 1 | |
| 1.2.8 | 0 / 1 | |
| 1.2.7 | 0 / 1 | |
| 1.2.6 | 0 / 1 | |
| 1.2.5 | 0 / 1 | |
| 1.2.4 | 0 / 1 | |
| 1.2.3 | 0 / 1 | |
| 1.2.2 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.17 | 0 / 1 | |
| 1.1.16 | 0 / 1 | |
| 1.1.15 | 0 / 1 | |
| 1.1.14 | 0 / 1 | |
| 1.1.13 | 0 / 1 | |
| 1.1.12 | 0 / 1 | |
| 1.1.11 | 0 / 1 | |
| 1.1.10 | 0 / 1 | |
| 1.1.9 | 0 / 1 | |
| 1.1.8 | 0 / 1 | |
| 1.1.7 | 0 / 1 | |
| 1.1.6 | 0 / 1 | |
| 1.1.5 | 0 / 1 | |
| 1.1.4 | 0 / 1 | |
| 1.1.3 | 0 / 1 | |
| 1.1.2 | 0 / 1 | |
| 1.1.1 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.3 | 0 / 1 | |
| 1.0.1 | 0 / 1 |
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (qiushuibai) than the most recent previously approved version (xbup) on 2025-04-14, but qiushuibai is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (qiushuibai) than the most recent previously approved version (xbup) on 2025-04-02, but qiushuibai is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xbup) than the most recent previously approved version (qiushuibai) on 2025-03-27, but xbup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.