Policy engine
Rules by package name, version range, age, source, license and custom criteria. Block or log-only, with time-limited exceptions. Re-evaluated on every request.
Beta
Cargo Dependency Firewall
Rust compiles its dependencies from source, and a crate's build script runs on your machine during cargo build. Bytesafe checks every crate against your firewall rules before it downloads, so a blocked version never reaches the compiler.
Bytesafe Dependency Firewall sits in front of your existing repository, protecting developers, CI/CD pipelines and AI agents.
npm dependency firewallMaven dependency firewallPyPI dependency firewallNuGet dependency firewallGo dependency firewallComposer dependency firewallCargoConda dependency firewallContainers dependency firewall
EU-based company · Software supply chain security since 2018.
bytesafe.dev / Firewall
47
Blocked today
1,284
Requests today
12
Active rules
Package
Rule
Status
malicious-pkg@2.1.0
Malware scan
BLOCKED
lodash@4.17.20
CVSS ≥ 7.0
BLOCKED
react@19.1.1
Allowlist
APPROVED
new-release@0.0.1
Age < 7 days
DELAYED
axios@1.7.9
Allowlist
APPROVED
Blocked
malicious-pkg@2.1.0
By Exception
lodash@4.17.21
Delayed
new-release@0.0.1
Approved
react@19.1.1
Offer now
50% off your base fee for 3 months + €100 usage credit.
Supply chain attacks on crates.io
A selection of documented supply chain attacks on crates.io. Malicious releases, account takeovers and dependency confusion have all been used against packages there.
arrayref, proc-macro12026
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.
Build-time dropperfaster_log, async_println2025
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.
Credential theftrustdecimal2022
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.
TyposquattingDependency confusionOngoing
crates.io has no namespaces or scopes, so any internal crate name can also be registered publicly. A cargo add that omits --registry, or a Cargo.toml entry with no registry key, resolves against crates.io instead of your private registry.
Namespace attackDependency Firewall does not prevent all attacks, but blocks packages that match known malware signatures or violate your policies.
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
Risky packages
Dependency Firewall
Policy engineVetted packages only
Developers and CI/CD
Internal environment
Dependency Firewall capabilities
Policy controls, malware blocking, package delay, dependency confusion protection, and full audit visibility across every Cargo request.
Vulnerability blocking
Block packages with known CVEs before install. Filter by CVSS and EPSS severity per registry or team. New advisories take effect immediately.
Malware scanning
Detect malicious payloads, suspicious install hooks and obfuscated code before execution. Quarantined packages are logged and never silently dropped.
Dependency confusion
Block namespace attacks where public packages impersonate your internal ones. Configurable upstream priority rules ensure private packages always win.
Zero-day safety delay
Hold newly published versions for a configurable window (7 or 14 days) before they reach developers or pipelines. Gives the ecosystem time to surface threats.
Package observations
Every package is fingerprinted: first-seen date, download frequency, requester, version age. Know exactly what passed through and when.
Audit logging
Every block, allow and exception is recorded and exportable to your SIEM. Built to make security teams and auditors happy out of the box.
Publish scanning
Packages are scanned for malware, secrets, and sensitive data before they are published to an upstream registry.
Time-limited exceptions
Unblock a package with a reason and an expiry date. The exception lapses on its own, so a temporary allowance does not quietly become permanent policy.
Add a security layer to Cargo
Route Cargo package traffic through Dependency Firewall, define policies for what's allowed and let the firewall block the rest. Developers and pipelines keep their existing package manager commands.
01
Route Cargo requests through Dependency Firewall
Point your Cargo configuration at Dependency Firewall. Every install request passes through the firewall before reaching the registry or your environment.
02
Define your security policies
Set vulnerability thresholds, enable malware scanning, configure safety delays for new versions and write allowlist or blocklist rules. Create multiple firewalls with individual rules for different teams or projects.
03
Bad packages are blocked. Safe ones flow through.
Every request is evaluated in real time. Blocked packages are logged with the policy that triggered them. Approved packages are served transparently.
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
JFrog Artifactory
Sonatype Nexus
GitLab
GitHub Packages
Azure Artifacts
AWS CodeArtifact
Firewall rules
Each rule targets an ecosystem and applies a condition: vulnerability severity, package age, license type or name pattern. Rules either block or log. Stack multiple rules per firewall. Changes take effect immediately.
Security teams can start with broad guardrails, then narrow policies by upstream, package, version range, internal status, maximum age, CVSS score and EPSS score.
Live firewall logs
Every blocked package is logged: package name, version, status, ecosystem, which firewall evaluated it, which rule triggered and who requested it. Filter by firewall or user.
The log view gives developers a fast answer when an install fails and gives AppSec a complete audit trail for policy enforcement.
Package details and scorecards
Open a package to review advisories, licenses, project metadata, OpenSSF Scorecard checks, dependency counts and source links before deciding whether to block, allow or investigate further.
The package page brings runtime firewall context together with upstream project health. Security teams can compare CVEs, maintainer signals, and repository hygiene from the same screen.
Sits in front of what you already run
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 |
Cargo Dependency Firewall: frequently asked questions
Common questions from security and engineering teams.
How do I point Cargo at Bytesafe Dependency Firewall?
Add the firewall as a registry in .cargo/config.toml and set it to replace crates.io as the source. Every dependency you already have then resolves through the firewall, with no Cargo.toml changes and no loss of lockfile portability. The dashboard generates the exact config for your firewall when you create it.
Can a Cargo.lock pull a crate the firewall blocked?
No. A lockfile names an exact version and goes straight to the download, so the firewall applies your rules to the download itself, not only to the index it resolved from. A blocked version fails either way.
Does cargo publish work through the firewall?
Yes. Publish, yank and unyank are forwarded to the registry you configure as the publish target. Published crates are scanned for malware and secrets first, and yanks are logged like any other write.
Is Cargo support production ready?
Cargo is the newest ecosystem we support, which is why it is marked beta. The full rule set applies: vulnerabilities, malware, licenses, name and version rules, and release delay, on the same advisory and malicious package data as every other ecosystem. Rust 1.74 or newer is required.
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 configurable window (7 or 14 days) before they reach developers or pipelines. Centralizing delay rules means the protection applies automatically across all teams and pipelines without each project configuring it separately.
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.
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 fully transparent to enterprise repository platforms and package registries, including JFrog Artifactory, Sonatype Nexus, GitLab, GitHub Packages and Azure Artifacts.
How is licensing structured?
Two plans: Cloud for SaaS and Enterprise for custom deployment, Managed Cloud or On-Premise. Cloud is priced on whichever you use most: active users, packages scanned or downloads served. See pricing for plan details and add-ons.
Watch it block Cargo threats
Book a 30-minute session and we'll show you how Dependency Firewall fits into your existing setup. Your registries stay unchanged.