All ecosystems
Package ecosystems supported by the Bytesafe Dependency Firewall and how to point each client at your firewall.
Each firewall endpoint proxies one package ecosystem. Configure your package manager to use the firewall endpoint instead of the public registry, authenticate with an access token, and every install goes through your rules.
No firewall yet? Start with the quickstart, which creates a firewall, installs a package through it, and adds a first rule. New to the product? What is a dependency firewall? explains the model first.
Supported ecosystems and clients
| Ecosystem | Clients | Firewall endpoint |
|---|---|---|
| npm | npm, yarn, pnpm, Bun | /v1/<namespace-id>/npm/<firewall-id>/ |
| PyPI | pip, uv, Poetry | /v1/<namespace-id>/pypi/<firewall-id>/simple/ |
| Maven | Maven, Gradle | /v1/<namespace-id>/maven/<firewall-id>/ |
| NuGet | dotnet, nuget.exe, Visual Studio | /v1/<namespace-id>/nuget/<firewall-id>/index.json |
| Go | go toolchain via GOPROXY | /v1/<namespace-id>/go/<firewall-id> |
| Conda (beta) | conda, mamba, micromamba | /v1/<namespace-id>/conda/<firewall-id> |
The endpoints in the table are paths. The full URL is https://eu-sov-1.bytesafecloud.eu followed by the path, with your own namespace and firewall IDs filled in. Each firewall's Setup tab shows that URL ready to copy, so you never have to assemble it by hand.
Container image (OCI) firewalling is coming to the Dependency Firewall; see Containers.
Using Artifactory, Nexus, or another repository manager? The firewall can sit behind it, in front of it, or on both sides; see Integrate with repository managers.
The pattern
Regardless of ecosystem, setup is the same three steps:
- Replace the registry URL. Point the client at your firewall endpoint instead of the public registry.
- Authenticate. Supply an access token in the client's credential config.
- Prevent bypass. Commit the config to the repository or enforce it in CI. A machine-local config only protects that machine, and an install that falls back to the public registry never reaches your rules.
Rule support differences
Rules and exceptions work the same in every ecosystem. Some selector functions are ecosystem-specific: unlisted exists only for NuGet, trust-downgrade only for npm, and vulnerabilities is not available for Conda in the beta. The full matrix is in the selector functions reference.