@mpxjs/webpack-plugin
mpx compile 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mpxjs/perf | AI (dependencies): First-party @mpxjs scoped package from the same monorepo, versioned in lockstep. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): url-loader fallback pattern; loads a known fallback module, not arbitrary user input. | ai | |
| phantom-deps | phantom-dep:css | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:de-indent | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:html-minifier | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:object-assign | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:source-list-map | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:lodash.camelcase | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in CSS conditional expression evaluator — standard template engine pattern, not arbitrary user input execution. | ai | |
| phantom-deps | phantom-dep:@better-scroll/zoom | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/slide | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/wheel | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/movable | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:css-selector-tokenizer | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/pull-down | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/mouse-wheel | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/observe-dom | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@better-scroll/core | AI (phantom-deps): Monorepo package; config-file references cause false phantom-dep detection. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.10.21 | 47 / 19 | |
| 2.10.20 | 46 / 19 | |
| 2.10.19 | 46 / 18 | |
| 2.10.14 | 45 / 14 | |
| 2.10.10 | 45 / 14 | |
| 2.10.9 | 45 / 14 | |
| 2.10.8 | 45 / 14 | |
| 2.10.7 | 45 / 14 | |
| 2.10.5 | 45 / 14 |
v2.10.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.