Bytesafe Dependency Firewall
Control which open source packages reach your builds. Documentation for the Bytesafe Dependency Firewall.
The Bytesafe Dependency Firewall sits between your package managers and public registries. Every install and publish goes through a firewall you configure with rules: delay new versions, block known vulnerabilities and malware, and keep an audit trail of every decision.
Previous-generation docs: docs-v1.bytesafe.dev. Migrating? See the migration guide.
See how it works
Read What is a dependency firewall? for a short introduction and video.
Start here
Quickstart
From zero to your first firewall, rule, and exception.
What is a dependency firewall?
How the firewall works and where it fits in your toolchain.
Set up your ecosystem
Point npm, PyPI, Maven, NuGet, Go, or Conda at your firewall.
Access Tokens
Tokens for developers and CI.
Common tasks
Delay new versions
Delay new releases before they reach developers.
Block vulnerable packages
Block downloads based on CVSS and EPSS thresholds.
Manage exceptions
Grant scoped, expiring waivers when a rule blocks something you need.
Investigate a blocked install
Trace a failed install back to the rule that caused it.