Dependency Firewallfor packages and containers
Your rules check every request and block risky versions before install.
- Built in Sweden and hosted in the EU
- Supply chain security since 2018
Works with what you already run
- npm dependency firewallYarn, pnpm, Bun
- Maven dependency firewallGradle
- PyPI dependency firewallpip, uv, Poetry
- NuGet dependency firewall.NET
- Go dependency firewallGo modules
- Composer dependency firewallPHP
- Cargo dependency firewallRust
- RubyGems dependency firewallBundler, gem
- Conda dependency firewallmamba, micromamba
- Docker / OCI dependency firewalldocker, crane, oras
Repository platforms
JFrog Artifactory, Sonatype Nexus, GitLab, GitHub Packages and Azure Artifacts.
Container registries
Docker Hub, GitHub Container Registry, Amazon ECR, Google Artifact Registry and self-hosted registries.
Deployment
Cloud as EU-hosted SaaS. Enterprise as Managed Cloud, BYO Cloud or On-Premise.
Guides and updates
- Guide
AI coding agents still need a dependency firewall
npm, pnpm, Yarn, Bun and uv can each skip versions younger than a set age, but only where the setting is in place. Dependency Firewall applies the same rule, and its vulnerability and malware rules, to every install that goes through it, whichever machine the agent runs on. - Product update · September 2026
Introducing Docker and OCI firewalling
Dependency Firewall now checks Docker and OCI images before a build or a cluster pulls them. Rules stop images with vulnerable OS packages, malware, leaked secrets or a tag published too recently. - Guide
Delay new package versions without breaking every build
A compromised release is usually found and removed some time after it goes live. Dependency Firewall holds every new version for a window you set, and builds keep working on the newest version that has aged.
Can different projects have different policies?
Yes. You can create separate firewalls per project. They are lightweight and easy to clone. You can also differentiate by the user or token used for the session. Firewall configurations are small JSON files that can be managed in Git.
Can packages be delayed before they reach developers?
Yes. Dependency Firewall can hold newly published package versions for a window you configure before they reach developers or pipelines. Attacks on packages like shai-hulud, axios and tanstack exploited the gap between publish and detection. Centralizing delay rules means the protection applies automatically across all teams and pipelines without each project configuring it separately.
How does malware detection work?
A malware rule checks every package when it is downloaded or published. It matches versions already reported as malicious, and findings from analysis of the package content. You choose the weakest finding that should match, starting at known malware. A release delay covers the versions nobody has flagged yet.
What happens if a package passes through but malware is found later?
The firewall tracks all packages via observations: first-seen date, last-seen date, and which firewalls they passed through. When new malware data surfaces, you can see exactly which projects downloaded the affected package and when. This gives your AppSec team a clear investigation trail.
How do we know when a package is blocked?
Every block shows in the firewall logs. The package manager reports that the version could not be found, which fails the build. The log entry has the package name, version, user, IP and the rule that blocked it. Read it in the UI or with the CLI.
Can firewall rules be automated?
Yes. All configuration is available via API. Configurations can be version-controlled in Git and deployed through your existing automation. All changes are tracked with full rollback support.
Does Dependency Firewall work with enterprise repository platforms?
Yes. Dependency Firewall speaks the same protocols as your package managers, so it is transparent to enterprise repository platforms and package registries, including JFrog Artifactory, Sonatype Nexus, GitLab, GitHub Packages and Azure Artifacts. It evaluates each package against your defined policies before it is served.
How is licensing structured?
Cloud is the SaaS plan. Enterprise is for custom deployment, Managed Cloud or On-Premise. Cloud is priced on whichever you use most: active users, packages scanned or downloads served. Plan details and add-ons
Start with one firewall
Point one pipeline at Dependency Firewall and read the decisions in the log. The trial runs for 14 days.