Why did npm update not fix my vulnerable dependency?
npm update respects the semver ranges in package.json and does not edit them by default. Why a vulnerable version stays put, and the steps that move it.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
npm update respects the semver ranges in package.json and does not edit them by default. Why a vulnerable version stays put, and the steps that move it.
Use 2FA for sign-in and writes, add a security key, and keep recovery codes off your phone. What npm says about modes, codes and the 72-hour hold.
A checklist for the CI side of an npm to pnpm move: installing pnpm, the packageManager field, frozen lockfile in CI, auth tokens and caching.
When npm rejects your internal mirror's certificate, trust the CA with cafile instead of switching off strict-ssl. Steps, risks and a CI-safe setup.
Without a lockfile the dependency tree is rebuilt each time, so two scanners can see two trees. Learn how version ranges and package-lock fix the drift.
For npm projects, the lockfile shows what should install and node_modules shows what did. Learn which source to trust and when to compare both.
npm has a built-in sbom command and the CycloneDX project ships its own npm tool. Compare formats, options and when each is the simpler choice.
npm query uses CSS-style selectors to list dependencies by type, name, script or license. Copyable queries for git deps, install scripts and duplicates.
npm's package-lock-only flag updates or reads package-lock.json without touching node_modules. When it helps, what it skips, and how to review the result.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.