Background
Recently, there have been multiple npm supply-chain poisoning incidents, and occasional npm users—especially newcomers—are feeling anxious.
How do you all respond to such threats?
A few examples of poisoning incidents (many more can be found with a quick Google search):
- TanStack npm supply chain poisoned – Frontier News – LINUX DO
- axios npm supply chain poisoned!!! – Frontier News – LINUX DO
Related Resources Compiled
- Reflecting on npm poisoning incidents: I built Shield, a macOS file-guarding tool based on FUSE – V2EX
- Add a security layer to
npm installusing socket.dev – V2EX - Introducing “safe npm”, a Socket npm wrapper – Socket
- A lightweight CLI tool to quickly scan local npm packages for poisoning (pnpm) – Development Optimization – LINUX DO