Dependency Proxy with Malicious Package Firewall

DevGuard includes a built-in dependency proxy that acts as a protective layer between your development environment and public package registries. It helps prevent supply chain attacks by blocking malicious packages before they reach your systems.

How It Works

  1. Request Interception: When you install a package, the proxy intercepts the request
  2. Database Check: The package is checked against the OSV dataset, which includes GitHub malware advisories — kept current via the vulndb sync
  3. Blocking: If flagged as malicious, the request is blocked and logged
  4. Package Rules: Your package rules decide whether the package is allowed, e.g. based on its release age
  5. Caching: Safe packages are cached with SHA256 integrity verification
  6. Metrics: All blocked attempts are recorded in Prometheus metrics

Supported Ecosystems

EcosystemRegistry URL
npm/api/v1/dependency-proxy/<secret>/npm
Go modules/api/v1/dependency-proxy/<secret>/go
PyPI/api/v1/dependency-proxy/<secret>/pypi/simple
Maven/api/v1/dependency-proxy/<secret>/maven
Composer (Packagist)/api/v1/dependency-proxy/<secret>/composer
Debian (apt)/api/v1/dependency-proxy/<secret>/deb/debian
Alpine (apk)/api/v1/dependency-proxy/<secret>/apk/alpine
OCI (container images)/v2/<secret>/ — pull <your-devguard-host>/<secret>/<registry>/<image>:<tag>

<secret> is the dependency proxy secret of your organization, project or repository. It links the requests to the rules configured there, and the proxy rejects requests without a valid secret. The complete proxy URLs are shown in its Dependency Proxy Settings in DevGuard.

For setup instructions, see the ecosystem-specific guides:

To route all CI jobs through the proxy at once, see Self-Hosted CI Runners. To let Renovate propose only allowed versions, see Use Renovate with the Dependency Proxy.

Package Rules

Package rules allow or deny packages with CEL expressions. They are configured per organization, project or repository and apply to requests using its proxy URL, which contains a secret. Rules are evaluated top to bottom and the last matching rule wins.

A minimum release age is the most common rule. It refuses versions published more recently than a given time, which gives the security community time to detect and flag malicious releases before they reach your teams:

Versions that are blocked are hidden from the package metadata, so version ranges resolve to an allowed version; a download of a blocked version is rejected with 403 Forbidden. For Debian, the proxy replaces blocked versions in the package list with the newest allowed older version, see Setup Debian Proxy. OCI registries expose no reliable publish date, so the release age cannot be checked for container images.

See Package Rules for the available fields, functions and more examples.

Cache & Security

The proxy enforces security at the caching layer — malicious packages are never cached, and the database must be fully loaded before any requests are served. See Cache Management for details.

Have feedback? We want to hear from you!

Fields marked with * are required