Enterprise
Proxy and policy-enforce dependencies across 23 package ecosystems — npm, PyPI, Cargo, Go, Maven, NuGet, Homebrew, Arch Linux, Docker/OCI and more.
The Vulnetix Package Firewall sits between your package manager and its upstream registry. It authenticates your organization, evaluates each requested package against your policy, and proxies allowed packages from trusted mirrors at https://packages.vulnetix.com.
One proxy fronts 23 ecosystems. Point a package manager at the firewall (the vulnetix package-firewall command writes the config for you) and every install is checked before it reaches your build.
orgUUID:apiKey).| Mode | What a developer sees | Ecosystems |
|---|---|---|
| Filter (unsigned metadata) | Blocked versions are removed from the index/metadata, so your resolver never selects them. A version you pin explicitly returns a policy status. | npm, PyPI, Cargo, Go, RubyGems, pub.dev, Maven, NuGet, Composer, Conda, CRAN, Helm, Chef, Terraform |
| Gate (signed / digest-addressed metadata) | The index is served unchanged so signature verification still passes; a blocked version’s download returns a policy status. | Hex, Conan, Julia, Docker/OCI, Debian, RPM, Alpine, Homebrew, Arch Linux |
You don’t configure the mode — it’s chosen per ecosystem so the firewall never breaks a registry’s signature checks.
Go and Arch Linux are free for every community account. All other ecosystems require a paid plan; container and OS ecosystems require Enterprise. Requests for an ecosystem outside your plan return 402 Payment Required.
| Tier | Ecosystems |
|---|---|
| Community (free) | Go, Arch Linux |
| Pro (and Teams) | npm, PyPI, Cargo, RubyGems, Hex, pub.dev, Maven, NuGet, Composer, Conan, Conda, CRAN, Julia, Homebrew |
| Enterprise | Docker/OCI, Debian/Ubuntu, RPM, Alpine, Helm, Chef, Terraform |
See vulnetix.com/pricing for details.
Every ecosystem authenticates with the same organization credentials — your org UUID as the username and your API key as the password — against the host packages.vulnetix.com.
vulnetix package-firewall <ecosystem> resolves your credentials (from the environment, ~/.vulnetix/credentials.json, or ~/.netrc), writes them to ~/.netrc for tools that honour it, and writes the ecosystem-specific registry config. Run vulnetix auth status to see which package managers are currently pointed at the firewall.
See each ecosystem page for the exact files and commands.