Gate
Gate is a local HTTP proxy in front of your package registry. When tooling requests packages, Veln can evaluate each dependency through the same policy pipeline used elsewhere — so fetches are checked, not only on-disk lockfiles after the fact.
Supported upstreams
Enforcement paths are built around npm-style and PyPI registry traffic. Point your package manager at the gate address and upstream (for example the public npm or PyPI base URL) per your environment.
Enforcement flags
Gate can enforce tarball and metadata paths for npm, and wheel/sdist GETs for PyPI, subject to license and safe mode. Run veln help gate for -enforce-npm, -enforce-pypi, listen address, and upstream options on your binary.
Relationship to verify
Use verify for project-wide lockfile runs; use gate when you want automatic checks on what the client is downloading in real time. Many teams use both.
Protection levels (local config)
Set gate_protection in ~/.veln/config.toml to light, medium, or total to tune how hard the proxy works on npm/PyPI traffic. veln verify always runs full depth; only Gate follows this preset. Run veln onboarding to pick a level interactively, or see veln help gate for the matrix.