Guard your dependencies against supply chain attacks.

Prevent the next npm supply chain compromise from impacting you. One command to scan and fix npm, pnpm, yarn, bun, and uv configs for security best practices. Zero dependencies. MIT.

macOS Linux Windows Cargo

Install

brew tap arnica/depsguard https://github.com/arnica/depsguard
brew install depsguard

Homebrew tap. Works on Apple Silicon and Intel.

Direct binaries · Full install guide

How to use

  1. Install – pick your platform above.
  2. Run depsguard in your terminal to launch the interactive TUI. It scans your system and shows a table of findings. Press any key to continue to the fix selector. Repo-level config discovery starts from the current directory and searches downward. Use depsguard scan for a read-only report, or depsguard --no-search to skip the recursive file search and only check user-level configs.
    Note: some settings require a minimum version. If your version is too old you'll see:
    ℹ min-release-age – requires npm ≥ 11.10 (have 10.2.0)
    Upgrade with npm install -g npm@latest and re-run.
  3. Navigate & select – use ↑↓ to move through the list (^u^d to page). Press Space to toggle a fix on or off. Use quick-filter keys to bulk-select by file: a all, n .npmrc, u uv.toml, etc. – press once to select, again to deselect, a third time to clear the filter. Press f to show only currently selected fixes.
  4. Preview – press d to see a diff of what will change before you commit to anything.
  5. Apply – press Enter to apply the selected fixes. A timestamped backup is created before any file is written.
  6. Rescan – DepsGuard automatically reruns the scan after applying, so you can verify everything is green.
  7. Restore – run depsguard restore at any time to roll back from the backup list. Press q or Esc to quit.

Full documentation, config file locations, and troubleshooting tips are in the README.

Why this exists

Software supply chain attacks are increasing. On March 31, 2026, a compromised maintainer account was used to publish malicious versions of axios. The bad versions were live for ~3 hours before removal. Similar short-lived attacks hit ua-parser-js, colors, and node-ipc. The pattern is the same: an attacker publishes a poisoned version, and every npm install that runs before it's caught pulls it in.

Many modern package managers now ship with built-in defenses, but they’re not always enabled by default. DepsGuard checks whether those settings are enabled and helps you turn them on.

Supported settings

Manager Config file Setting What it does Docs
npm .npmrc min-release-age=7 Delay new versions by 7 days (npm ≥ 11.10)
npm / pnpm .npmrc ignore-scripts=true Block malicious install scripts
pnpm .npmrc minimum-release-age=10080 Delay new versions by 7 days (in minutes) (pnpm ≥ 10.16)
pnpm rc (pnpm ≤ 10; pnpm ≥ 11 uses config.yaml with camelCase keys) ignore-scripts=true Block malicious install scripts
minimum-release-age=10080 Delay new versions by 7 days (pnpm ≥ 10.16)
block-exotic-subdeps=true Block untrusted transitive deps (pnpm ≥ 10.26)
trust-policy=no-downgrade Block provenance downgrades (pnpm ≥ 10.21)
strict-dep-builds=true Fail on unreviewed build scripts (pnpm ≥ 10.3)
pnpm pnpm-workspace.yaml minimumReleaseAge: 10080 Delay new versions by 7 days (in minutes) (pnpm ≥ 10.16)
strictDepBuilds: true Stricter build scripts (pnpm ≥ 10.3)
trustPolicy: "no-downgrade" Block provenance downgrades (pnpm ≥ 10.21)
blockExoticSubdeps: true Block exotic sub-dependencies (pnpm ≥ 10.26)
Yarn .yarnrc.yml npmMinimalAgeGate: "7d" Delay new versions by 7 days (yarn ≥ 4.10)
bun .bunfig.toml install.minimumReleaseAge = 604800 Delay new versions by 7 days (in seconds)
uv uv.toml exclude-newer = "7 days" Delay new versions by 7 days (uv ≥ 0.9.17)
Renovate renovate.json "minimumReleaseAge": "7 days" Delay dependency update PRs
Dependabot dependabot.yml cooldown.default-days: 7 Delay dependency update PRs

User-level config locations

Manager macOS Linux Windows $XDG_CONFIG_HOME
npm ~/.npmrc —
pnpm ~/.npmrc (shared with npm) —
pnpm global, ≤ 10 ~/Library/Preferences/pnpm/rc ~/.config/pnpm/rc %LOCALAPPDATA%\pnpm\config\rc $XDG_CONFIG_HOME/pnpm/rc
pnpm global, ≥ 11 ~/Library/Preferences/pnpm/config.yaml ~/.config/pnpm/config.yaml %LOCALAPPDATA%\pnpm\config\config.yaml $XDG_CONFIG_HOME/pnpm/config.yaml
Yarn ~/.yarnrc.yml —
bun ~/.bunfig.toml $XDG_CONFIG_HOME/.bunfig.toml *
uv ~/.config/uv/uv.toml %APPDATA%\uv\uv.toml $XDG_CONFIG_HOME/uv/uv.toml *

* When $XDG_CONFIG_HOME is set, DepsGuard checks both the XDG path and the default path; whichever files exist on disk are each scanned independently. If neither exists, the XDG path is used as the default for new fixes.

FAQ

Will this protect against all supply chain attacks?

No. DepsGuard focuses on one specific layer: delaying the adoption of brand-new package versions and disabling risky install scripts. This buys you time when an attacker publishes a poisoned release, because your package manager won't pull it in immediately. It does not protect against compromised packages that go undetected for weeks, typosquatting, or attacks that don't involve publishing a new version.

How would this have helped during the axios compromise?

On March 31, 2026, a compromised maintainer account published malicious versions of axios. The bad versions were live for roughly 3 hours before being removed from the registry. If your package manager was configured with a 7-day minimum release age (like min-release-age=7 in .npmrc), it would have refused to download the new version during that window. The same logic applies to incidents like ua-parser-js (compromised for ~4 hours in Oct 2021) and node-ipc (caught within days in Mar 2022) – in each case, the poisoned version was removed well within a 7-day quarantine period. Note: this would not have helped with attacks like event-stream, where the malicious code went undetected for months.

Why can this protect me against future attacks?

Many supply chain attacks follow the same pattern: an attacker publishes a poisoned package version and relies on automated installs pulling it in before anyone notices. Registry security teams, community reports, and automated scanners often catch and remove these within hours or days. A minimum release age means your package manager won't pull in a version that hasn't been publicly available for at least 7 days, giving that detection window time to work. This is effective against fast-response attacks (like axios, ua-parser-js, node-ipc) but does not help if malicious code goes undetected for longer than the quarantine period.

What's the difference between this and Software Composition Analysis (SCA)?

SCA tools (like npm audit, OWASP dep-scan, Grype, Arnica, or Snyk) scan your existing dependencies for known vulnerabilities after you've already installed them. DepsGuard works before installation – it configures your package manager to avoid pulling in newly published versions until they've had time to be vetted. They're complementary: SCA finds known CVEs in your current lockfile, DepsGuard reduces the chance that a freshly poisoned version gets installed in the first place.

What else can I do to protect myself?

DepsGuard covers package manager config, but there's more you can do:

  • Pin GitHub Actions by commit SHA (uses: actions/checkout@a81bbb...) instead of a tag like @v4. Tags can be moved to point at different commits; SHAs can't.
  • Use npm ci, pnpm install --frozen-lockfile, or yarn install --immutable in CI. These commands fail if the lockfile is out of date, so CI never resolves new versions on its own.
  • Don't auto-merge Dependabot or Renovate PRs without reviewing changelogs, diffs, and provenance.
  • Audit your dependency tree periodically with npm ls or pnpm why. Fewer dependencies means fewer places an attacker can hide.

Is this free?

Yes. DepsGuard is free and open source under the MIT license.

Can I use this commercially?

Yes. The MIT license permits commercial use, modification, and distribution with no restrictions.

Who made this?

Arnica, an application security company based in Atlanta. DepsGuard is a free, open-source tool we built to help anyone harden their package manager config.

I found a bug. What should I do?

Open an issue on GitHub. For security vulnerabilities, please use GitHub Security Advisories to report privately.

See also

Dependency Cooldowns (cooldowns.dev) – a reference guide and companion shell helper (cooldowns.sh) focused specifically on minimum-release-age cooldowns. It complements DepsGuard: cooldowns.dev covers a broader set of ecosystems on the cooldown axis (pip, uv, npm, pnpm, Yarn, Bun, Deno, Cargo), while DepsGuard covers npm/pnpm/yarn/bun/uv plus Renovate and Dependabot and adds other hardening settings (ignore-scripts, block-exotic-subdeps, trust-policy, strict-dep-builds) with an interactive TUI, diff preview, and backup/restore.

Help & feedback

Report a bug or request a feature Report a security vulnerability