Dependency Firewall for
Blocks malicious, vulnerable and policy-violating packages at install.
Dependency Firewall sits in front of your existing repository, protecting developers, CI/CD pipelines and AI agents.
EU-based company · Software supply chain security since 2018.
Logs
| Time | Status | Package | Version | Rule |
|---|---|---|---|---|
| 09:58:15 | Allowed | minimist | 1.2.5 | Exception |
| 09:58:12 | Blocked | org. | 2.14.1 | Block CVSS ≥ 7 |
| 09:58:09 | Allowed | requests | 2.32.5 | Log all downloads |
| 09:58:06 | Blocked | nx | 21.6.4 | Delay 7 days |
| 09:58:03 | Blocked | event-stream | 3.3.6 | Known malware |
| 09:58:00 | Allowed | react | 19.1.1 | Log all downloads |
Intercepts every package request before it reaches you.
Every package install is a potential entry point. Traditional SCA tools find problems after packages are already in your environment. Dependency Firewall intercepts every request before it reaches your developers, CI/CD pipelines or AI agents.
You define the rules: block packages with known CVEs, block known malicious packages or delay newly published versions for a configurable period to give the ecosystem community time to surface zero-day threats.
Works in front of enterprise repository platforms and any package registry. No agent installs. No workflow changes.
Ecosystems
npm, PyPI, Maven, NuGet, Go, plus many other
Your repositories
Enterprise platforms and mirrors
Dependency Firewall
Policy engineDevelopers and CI/CD
Internal network
What Dependency Firewall does
Each firewall runs the checks you turn on, on every package request. Rules block or log, and every decision is recorded.
- Malware blocking
- Blocks packages that match malware data, including malicious payloads and suspicious install hooks. Every block is logged with the package and the rule.
- Vulnerability blocking
- Blocks versions with CVEs above a CVSS or EPSS score you set, per firewall. New advisories apply on the next request.
- Package delay
- Holds newly published versions for a window you set, so malware feeds can catch a bad release before your builds install it.
- Time-limited exceptions
- Unblock one package or version with a reason and an expiry date. The rule keeps applying to everything else, and the exception lapses on its own.
- Dependency confusion
- Upstream priority rules make internal package names always resolve from your private registry. A public package with the same name cannot take its place.
- Package observations
- Every package that passes records first-seen and last-seen time and request counts. When a new advisory lands, you see which firewalls served the package and since when.
- Audit log
- Every allow, block and exception is logged with the package, version, rule, requester and time. Export it to your SIEM.
- A firewall per team
- Run a separate firewall per team, pipeline or registry. A shared baseline firewall runs first, and team firewalls add rules on top without weakening it.
- Trust downgrades
- Flags releases published with weaker provenance than the version before them, the pattern behind account takeovers.
- Licenses
- Blocks packages with licenses you have not approved before they reach a build.
- Rules as code
- Every firewall is a small JSON configuration. Keep it in Git, deploy it through your automation over the API and roll back to any earlier version.
- Publish scanning
- Packages are scanned for malware, secrets and sensitive data before they are published to an upstream registry.
Inside Dependency Firewall
The screens your developers and security team work with.
1 of 7 · Logs
Live firewall logs
Every request is logged: package name, version, status, ecosystem, which firewall evaluated it, which rule triggered and who requested it. Filter by firewall or user, and tail live during incidents or CI/CD runs.
Developers get a fast answer when an install fails, and AppSec gets an audit trail for every decision.
Why a package was blocked
Open a blocked request to see the ecosystem, version, publish date, the rule that triggered and whether its effect is block, log or both.
Add a time-limited exception from the same drawer to let one package or version through while the rule keeps applying to everything else. The decision stays attached to the original request, so nothing has to be reconstructed from CI output later.
Firewall rules
Each rule targets an ecosystem and applies a condition: vulnerability severity, package age, license or name pattern. Rules block or log, stack per firewall and take effect immediately.
Start with broad guardrails, then narrow by upstream, package, version range, internal status, maximum age, CVSS score and EPSS score.
See everything a rule can match on
A firewall per team or pipeline
Each firewall carries its own rules, exceptions and upstreams, so a CI firewall can be stricter than a local dev one.
A firewall can inherit from another. Set one baseline with the rules every project must follow and point team firewalls at it. Inherited rules run first and can only be changed on the parent.
Every package that passed through
See which packages each firewall served over a period, with ecosystem, version, first-seen and last-seen time, vulnerability signals and request counts.
When a new advisory or malware report appears, search for the package and see where it was observed and when exposure started.
Package details and scorecards
Review advisories, licenses, project metadata, OpenSSF Scorecard checks, dependency counts and source links before you block, allow or investigate further.
Security dashboard
Rules triggered, exceptions granted and package requests over time. See which firewalls are most active and confirm your policies work after rollout.
Dependency Firewall offer
Half the base fee for your first 3 months
€49.50 instead of €99 per month, plus €100 usage credit. Start with a 14-day trial, no card required. See what's new
The same firewall for Docker and OCI images
A container image is a dependency like any other, and it brings an operating system and several hundred packages with it. Bytesafe reads the apk, dpkg and rpm databases out of the image layers and blocks images with vulnerable OS packages, malware or leaked secrets, before the image reaches a build agent or a production node.
The same policy engine, the same advisory data and the same audit log as your package registries.
Docker
OCILogs
| Time | Status | Package | Version | Rule |
|---|---|---|---|---|
| 09:58:15 | Allowed | library/ | 17.6 | Log all downloads |
| 09:58:12 | Blocked | library/ | 7 | Block CVSS > 8.5 |
| 09:58:09 | Allowed | ghcr. | 1.4 | Exception |
| 09:58:06 | Blocked | node | 22-slim | Delay 7 days |
| 09:58:03 | Blocked | library/ | 9 | Block CVSS > 8.5 |
| 09:58:00 | Allowed | library/ | 3.20 | Log all downloads |
See how Dependency Firewall works
Covers the architecture, what gets checked on every request, how decisions are made and logged, and how it fits in front of your existing registry setup.
How it works →How package installs go through the firewall
Your package manager asks the firewall instead of the public registry. The firewall fetches the package from upstream, checks it against your rules and serves it only if it passes.
- 1
Change the registry setting
Point npm, pip, Maven and your other clients at the firewall, on laptops and CI runners. Lockfiles, manifests and install commands stay the same.
Developer or CI job
npm install
Dependency Firewall
Checks your rules
Public registry
registry.npmjs.org
Shown for npm. pip, Maven, NuGet, Go, Cargo, Composer, RubyGems, Conda and containers work the same way. - 2
Set the rules
Block by CVSS or EPSS score, known malware, license or package age. Shared rules go on a baseline firewall that team and CI firewalls inherit, and they run first.
Rules on the npm-ci firewall. The 7-day delay is inherited from npm-baseline. - 3
Read the log
A version held back by a rule is left out of the version list, so the package manager resolves an older one. A blocked download fails the install. Every decision is logged with the rule and who asked.
New versions held by the delay rule, next to allowed downloads.
Works with the repositories you already use
Compared with other enterprise dependency firewalls
Other enterprise dependency firewalls are often bundled into repository platforms. Dependency Firewall is an independent firewall that works with any registry and is built in the EU.
| Criterion | Dependency Firewall | Other enterprise firewalls |
|---|---|---|
| Works with your existing repository | Yes, as a proxy in front of it | Bundled into their platform |
| Deploys in minutes | Yes | Usually weeks of platform work |
| Predictable pricing | One meter sets the price, no overage | Several axes with overage most often |
| EU data residency | Yes | No, US-based most of the time |
Frequently asked questions
Can different projects have different policies?
Can packages be delayed before they reach developers?
How does malware detection work?
What happens if a package passes through but malware is found later?
Are there alerts when a package is blocked?
Can firewall rules be automated?
Does Dependency Firewall work with enterprise repository platforms?
How is licensing structured?
Bytesafe Platform
Software Supply Chain Security and Transparency
Three products that block risky packages at install, collect supplier transparency documents, and analyze them.
Dependency Firewall
Block vulnerable and malicious packages before they reach your developers. Sits in front of your existing repository.
You are on this pageTrust Repository
Collect SBOM, VEX and end-of-life documents from your suppliers, and publish your own to your customers.
Product pageSBOM Observer
Analyze SBOMs from your builds and suppliers for vulnerabilities, licenses and policy violations. Keep a record per release.
Product page
Point one registry at the firewall
Change the registry URL for npm, pip or Maven and your rules apply from the next install. Start a trial, or book a demo to go through your registry setup with an engineer.