987bda5d6a feat: Add dependency cooldown for npm packages (#200)
* feat: Add dependency cooldown for npm packages

Strip recently-published package versions from npm registry metadata
responses so npm's resolver naturally falls back to older versions.
Overrides the Accept header to force full packument responses (which
include the "time" field needed for publish-date checks).

Reports cooldown blocks only when all versions are stripped (remaining == 0),
matching npm's --min-release-age behavior for silent fallback.

* fix: Report oldest version in cooldown block (shortest wait)

When all versions are blocked by cooldown, report the oldest version
since it exits the cooldown window first — giving the user the
shortest wait time instead of the longest.

* fix: Handle resp.Body.Close error return for errcheck linter

* test: Add dependency cooldown assertions to template config tests

* fix: config template for dependency cooldown

* fix: Prevent npm from caching cooldown-stripped metadata responses

* fix: Restore body on ReadAll failure and log Close errors in response modifier

* fix: Close response body before replacing to prevent connection leak

* fix: Correct daysLeft ceiling math and update ContentLength on error recovery

* fix: Clear Status on status code change and update ContentLength in modifier error path

* refactor: address review comments on dependency cooldown PR

- Make NpmCooldownHandler and constructor package-private
- Pass cooldown days as parameter instead of reading config internally
- Convert standalone functions to methods on npmCooldownHandler
- Set Accept-Encoding: identity to prevent gzip responses breaking JSON parsing
- Return 503 with descriptive message when upstream body read fails

* fix: log errors in stripCooldownVersions instead of swallowing them

* fix: Config preserve fallback defaults

* fix: Code review fixes

* fix: correct cooldown tip to show wait time instead of incorrect trusted_packages advice

* fix: prevent integer overflow in cooldown duration calculation with large days values

* refactor: deduplicate CooldownBlock into internal/models, fix misleading variable names

- Move CooldownBlock struct to internal/models to eliminate duplication
  between proxy/interceptors and internal/ui packages
- Simplify proxy_flow.go by using direct assignment instead of field copy
- Rename latestStripped/latestDate to oldestVer/oldestDate for clarity

* fix: Dependency Cooldown Check Encapsulation (#207)

* fix: Encapsulate cooldown check

* feat: Add --skip-dependency-cooldown override

* fix: Code review fixes

---------

Co-authored-by: Abhisek Datta <abhisek.datta@gmail.com>
2026-04-08 21:04:17 +05:30
2026-02-16 13:35:58 +05:30
2026-04-07 00:56:21 +05:30
2026-04-07 00:56:21 +05:30

PMG GitHub Banner

Package Manager Guard (PMG)

Docs Website Discord

Go Report Card License Release OpenSSF Scorecard CodeQL


pmg in action

Why PMG?

Developers and AI coding agents install packages every day. Each npm install or pip install executes thousands of lines of code that nobody reviews.

Malicious packages ship constantly in popular ecosystems:

  • litellm 1.82.8 - a popular AI proxy library compromised to exfiltrate credentials
  • telnyx 4.87.2 - a legitimate telecom SDK hijacked on PyPI
  • pino-sdk-v2 - a typosquat package disguised as the popular pino logger

PMG intercepts every package install and checks it for malware before code executes. Install it once, and every npm install, pip install, and poetry add is protected automatically.

Featured in tl;dr sec and used by engineering teams worldwide.

How PMG Works

  • Transparent Protection - PMG wraps npm, pip, and other package managers to transparently apply protection. Developers and AI agents use their tools as usual with no workflow changes.
  • Malicious Package Protection - Every intercepted package is analyzed against SafeDep's real-time threat intelligence before installation. Malicious packages are blocked before code executes on the system.
  • Sandboxed Installation - Package installation runs inside OS-native sandboxes (macOS Seatbelt, Linux Bubblewrap), preventing install scripts from modifying the system even if a threat evades detection.
  • Audit Logging - Every package installation event is logged, providing a verifiable trail of what was installed, when, and from where.

Quick Start

Get protected in seconds.

1. Install

MacOS / Linux (Homebrew)

brew install safedep/tap/pmg

NPM

npm install -g @safedep/pmg

See Installation for additional methods.

2. Setup

Configure your shell to use PMG automatically.

pmg setup install
# Restart your terminal to apply changes

Tip: Re-run pmg setup install after upgrading PMG to pick up new configuration options.

3. Use

Use your package managers as usual or let your AI coding agent use them. PMG works silently in the background.

npm install express
# or
pip install requests

Verify PMG is working by installing a test package. This is a harmless package flagged as malicious in the SafeDep database, specifically meant for testing:

npm i safedep-test-pkg@0.1.3
Expected output
✗ Malicious package blocked

  - safedep-test-pkg@0.1.3
    Reference: https://app.safedep.io/community/malysis/01KF5JYDND9XR94WNEJ2G74KY2

✗ PMG: 1 packages analyzed, 1 blocked

Features

Feature Description
AI Agent Safety Net Protects against malicious packages installed by AI coding agents (Claude Code, Cursor, Copilot, Windsurf).
Malicious Package Protection Real-time protection against malicious packages using SafeDep.
Sandboxing Enforces least privilege using OS native sandboxing to contain installation scripts.
Dependency Analysis Deep scans of direct and transitive dependencies before they hit your disk.
Event Logging Keeps a verifiable audit trail of all installed packages.
Zero Config Works out of the box with sensible security defaults.
Cross-Shell Seamlessly integrates with Zsh, Bash, Fish, and more.

Supported Package Managers

PMG supports the tools you already use:

Ecosystem Tools Status Command Example
Node.js npm Yes npm install <pkg>
pnpm Yes pnpm add <pkg>
yarn Yes yarn add <pkg>
bun Yes bun add <pkg>
npx Yes npx <pkg>
pnpx Yes pnpx <pkg>
Python pip Yes pip install <pkg>
poetry Yes poetry add <pkg>
uv Yes uv add <pkg>

Installation

Homebrew (MacOS/Linux)
brew tap safedep/tap
brew install safedep/tap/pmg
NPM (Cross-Platform)
npm install -g @safedep/pmg
Go (Build from Source)
# Ensure $(go env GOPATH)/bin is in your $PATH
go install github.com/safedep/pmg@latest
Binary Download

Download the latest binary for your platform from the Releases Page.

Uninstallation

Remove shell integration:

pmg setup remove

To also remove the PMG configuration file:

pmg setup remove --config-file

Then uninstall PMG itself:

# Homebrew
brew uninstall safedep/tap/pmg

# NPM
npm uninstall -g @safedep/pmg

Trust and Security

Security is our first class requirement. PMG builds are reproducible and signed.

  • Attestations: GitHub and npm attestations are used to guarantee artifact integrity.
  • Verification: Users can cryptographically prove the binary matches the source code.
  • See Trusting PMG for verification steps.

User Guide

Support

If PMG saved you from a bad package, star this repo — it helps others find it.

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines on how to build and test PMG locally.

Telemetry

PMG collects anonymous usage data to improve project stability and reliability. To disable: export PMG_DISABLE_TELEMETRY=true.

Languages
Go 98.1%
JavaScript 1%
Shell 0.8%