Dedicated security infrastructure for a deliberate language.

Build a Vyper security tool developers can inspect, security teams can enforce, and protocols can depend on release after release.

Vyper Guard began from a simple gap: most smart-contract security tooling treats Vyper as secondary input. The project is building from the language outward—compiler context, detector evidence, stable findings, review workflow, and protocol policy—rather than adding a Vyper parser to a generic alert system.

The CLI stays open source so the analysis remains inspectable. Commercial work funds the operational layer teams need: managed integrations, policy, history, evidence, custom rules, and support.