There is an ongoing public supply-chain compromise affecting axios@1.14.1 and axios@0.30.4 on npm.
axios/axios#10604
This repository currently declares:
So even if the current lockfile is still safe, future lockfile refreshes / fresh installs that re-resolve dependencies may pick up a compromised Axios release.
Would you consider urgently:
- pinning Axios to a known-good version,
- checking that neither
axios@1.14.1 / 0.30.4 nor plain-crypto-js appears in the dependency tree?
This seems worth addressing quickly because many users self-host or fork this project and may run fresh installs.
There is an ongoing public supply-chain compromise affecting
axios@1.14.1andaxios@0.30.4on npm.axios/axios#10604
This repository currently declares:
So even if the current lockfile is still safe, future lockfile refreshes / fresh installs that re-resolve dependencies may pick up a compromised Axios release.
Would you consider urgently:
axios@1.14.1/0.30.4norplain-crypto-jsappears in the dependency tree?This seems worth addressing quickly because many users self-host or fork this project and may run fresh installs.