What does npm v12 actually change by default?
npm v12 turns off three defaults that have existed since npm's early days: automatic install/postinstall scripts (allowScripts now defaults to off), Git dependencies, and sourcing packages from remote URLs. Developers must explicitly allowlist any of the three in package.json if their project genuinely needs them.
Answered in
npm's Biggest Security Overhaul in 16 Years Is Here — Attackers Are Already Adaptingnpm v12 blocks install scripts, Git dependencies, and remote sources by default. Researchers say attackers are already routing around it.
Read the full analysisOther questions this article answers
More development best practices questions
- Why is a large-scale test framework migration usually so slow to do by hand?
- Why did retry loops with error feedback outperform carefully engineered prompts?
- When does a migration pipeline need rich prompt context instead of just retries?
- How do you migrate the last 3% of files that automation can't fully finish?
- Does this approach only work for test framework migrations?
- What is Project Polaris and how does it relate to GitHub Copilot?
- What architecture does Project Polaris use?
- How does Project Polaris perform compared to GPT-4 Turbo on coding benchmarks?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.