copy-webpack-plugin
Copy files && directories with webpack
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-dir | AI (phantom-deps): node-dir is a legitimate runtime dependency for directory traversal; declared and used by the plugin. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is a legitimate runtime dependency for file operations; declared and used by the plugin. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change reflects documented transfer to webpack-contrib org; evilebottnawi is a known webpack-contrib maintainer with strong track record. Stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (globby, cacache, is-glob, p-limit, etc.) are all well-known webpack/Node.js ecosystem packages, consistent with v4.x rewrite adding caching and improved glob support. | ai | |
| dependencies | unvetted-dep:bluebird | AI (dependencies): bluebird is a well-known, widely-used Promise library with no malicious history; flagging it as unvetted is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is not yet widespread on npm; absence is not a security signal for established packages like copy-webpack-plugin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original authors transferred the package to webpack-contrib org; removal is part of the documented legitimate handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are core webpack-contrib contributors (sokra=webpack author, evilebottnawi=long-standing webpack-contrib maintainer). Legitimate org transfer. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): The webpack-contrib org takeover of copy-webpack-plugin from original authors is a well-documented, legitimate organizational transfer. sokra/evilebottnawi/jhnns are core webpack ecosystem maintainers. | ai | |
| dependencies | unvetted-dep:serialize-javascript | AI (dependencies): serialize-javascript is a well-known, widely-used npm package appropriate for webpack plugin use; not a security concern for this package. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 14.0.0 | 5 / 28 | |
| 13.0.1 | 5 / 40 | |
| 13.0.0 | 5 / 30 | |
| 12.0.2 | 6 / 30 | |
| 12.0.1 | 6 / 30 | |
| 12.0.0 | 6 / 30 | |
| 11.0.0 | 6 / 29 | |
| 10.2.4 | 6 / 29 | |
| 10.2.3 | 6 / 29 | |
| 10.2.2 | 6 / 29 | |
| 10.2.1 | 6 / 29 | |
| 10.2.0 | 6 / 29 | |
| 10.1.0 | 6 / 29 | |
| 10.0.0 | 6 / 25 | |
| 9.1.0 | 6 / 24 | |
| 9.0.1 | 7 / 24 | |
| 9.0.0 | 7 / 24 | |
| 8.1.1 | 7 / 24 | |
| 8.1.0 | 7 / 24 | |
| 8.0.0 | 7 / 25 | |
| 7.0.0 | 8 / 25 | |
| 6.4.1 | 11 / 26 | |
| 6.4.0 | 11 / 26 | |
| 6.3.2 | 11 / 26 | |
| 6.3.1 | 11 / 26 | |
| 6.3.0 | 11 / 26 | |
| 6.2.1 | 11 / 25 | |
| 6.2.0 | 11 / 25 | |
| 6.1.1 | 11 / 25 | |
| 6.1.0 | 11 / 25 | |
| 6.0.4 | 11 / 25 | |
| 6.0.3 | 11 / 25 | |
| 6.0.2 | 11 / 26 | |
| 6.0.1 | 11 / 25 | |
| 6.0.0 | 10 / 25 | |
| 5.1.2 | 12 / 27 | |
| 5.1.1 | 12 / 27 | |
| 5.1.0 | 12 / 27 | |
| 5.0.5 | 12 / 27 | |
| 5.0.4 | 12 / 27 | |
| 5.0.3 | 12 / 24 | |
| 5.0.2 | 11 / 24 | |
| 5.0.1 | 11 / 26 | |
| 5.0.0 | 10 / 26 | |
| 4.6.0 | 8 / 11 | |
| 4.5.4 | 8 / 11 | |
| 4.5.3 | 8 / 11 | |
| 4.5.2 | 8 / 11 | |
| 4.5.1 | 8 / 9 | |
| 4.5.0 | 8 / 9 | |
| 4.4.3 | 8 / 9 |
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsThis version was published by a different npm account than previous versions on 2019-12-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findingsThis version was published by a different npm account than previous versions on 2019-11-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findingsThis version was published by a different npm account than previous versions on 2019-07-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
2 findingsThis version was published by a different npm account than previous versions on 2019-04-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2019-03-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2019-03-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-31. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
2 findingsThis version was published by a different npm account than previous versions on 2018-10-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
2 findingsThis version was published by a different npm account than previous versions on 2018-10-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
2 findingsThis version was published by a different npm account than previous versions on 2018-06-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
2 findingsThis version was published by a different npm account than previous versions on 2018-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
2 findingsThis version was published by a different npm account than previous versions on 2018-03-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
2 findingsThis version was published by a different npm account than previous versions on 2018-03-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.