Cargo Dependency Firewall
Rust crates can include build scripts that execute before the package is compiled. Bytesafe blocks malware, packages with known vulnerabilities and policy violations before they reach your build.
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 | clap | 4.5.48 | Log all downloads |
| 09:58:12 | Allowed | hyper | 1.7.0 | Exception |
| 09:58:09 | Blocked | reqwest | 0.12.24 | Delay 7 days |
| 09:58:06 | Allowed | tokio | 1.47.1 | Log all downloads |
| 09:58:03 | Blocked | rustdecimal | 1.23.1 | Known malware |
| 09:58:00 | Allowed | serde | 1.0.228 | Log all downloads |
| 09:57:57 | Allowed | tracing | 0.1.41 | Log all downloads |
| 09:57:54 | Allowed | anyhow | 1.0.100 | Log all downloads |
Intercepts every Cargo 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 Cargo 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 Cargo registry. No agent installs. No workflow changes.
Public crates.io registry
Vulnerable and malicious versions included
Dependency Firewall
Policy engineDevelopers and CI/CD
Internal environment
What Dependency Firewall does for Cargo
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.
- Exception workflow
- Developers request an exception from the blocked install. The team you choose approves it, adjusting scope or expiry, or denies it with a comment. Every request and decision is in the audit log.
- 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.
- 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.
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. See what's new
How Cargo 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 Cargo at the firewall, on laptops and CI runners. Lockfiles, manifests and install commands stay the same.
Developer or CI job
cargo build
Dependency Firewall
Checks your rules
Public registry
crates.io
- 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. Shown for npm. - 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. Shown for npm.
Point Cargo at Bytesafe Dependency Firewall
Point Cargo at the firewall in .cargo/config.toml and it takes over from crates.io as the source for every dependency. No Cargo.toml edits, no change to how anyone builds, and lockfiles stay portable. Requires Rust 1.74 or newer.
Works with the repositories you already use
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 package, how old the release is, the rule that stopped it and when it will be allowed.
Add or request 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.
Known attacks on crates.io
Malicious releases, account takeovers and dependency confusion have all been used against packages there.
arrayref, proc-macro1
Build-time dropper
- A compromised maintainer account published new versions of arrayref, internment and append-only-vec, each adding one dependency: proc-macro1, a typosquat of proc-macro2. Its build script assembled a command and control address, disabled certificate checks and ran a payload during compilation. Nothing in the crates had to be called. arrayref alone has around 245 million downloads. The versions were live for 86 to 107 minutes.
faster_log, async_println
Credential theft
- Two crates cloned the fast_log logging library and kept it working as cover. Alongside it they scanned source files for Ethereum private keys and Base58 Solana keys and posted matches to an endpoint named to look like Solana RPC infrastructure. Published in May 2025, they reached 8,424 downloads before removal in September.
rustdecimal
Typosquatting
- A crate named to be misread as rust_decimal shipped the real library's source with one function changed. Decimal::new checked for the GITLAB_CI environment variable and, when it found it, downloaded and ran a Mythic Poseidon payload on Linux and macOS. It had under 500 downloads across six weeks before the crates.io team removed it.
Also blocks vulnerable and malicious container images before they reach a build agent or production node.
Container Dependency FirewallCompared 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 most often |
| Deploys in minutes | Yes | Usually weeks of platform work most often |
| Predictable pricing | One meter sets the price, no overage | Several axes with overage most often |
| EU data residency | Yes | No, US-based most often |
Frequently asked questions
How do I point Cargo at Bytesafe Dependency Firewall?
Can a Cargo.lock pull a crate the firewall blocked?
Does cargo publish work through the firewall?
Is Cargo support production ready?
Can different Cargo projects have different policies?
Can Cargo packages be delayed before they reach developers?
What happens if a Cargo package passes through but malware is found later?
Can firewall rules be automated?
Does Dependency Firewall work with enterprise repository platforms?
How is licensing structured?
Put Cargo installs behind the firewall
Try the setup above on one project and check the firewall log after the next install. Or book a demo and go through your registries and rules with an engineer.