See the contract the way the compiler does.
Vyper-aware parsing and optional compiler semantics preserve the language context generic smart-contract scanners flatten.
Vyper Guard 0.6 is availableCompiler health, project analysis, and evidence-rich reportsSee what changed →
The Vyper security platformSecure every
Secure every
Vyper release.
Analyze contracts with Vyper-native context, review real evidence, and enforce security policy before code reaches production.
Open-source CLI Runs locally Python 3.10+
feature/fee-policyGuard withdrawal accounting
+42 −8118
@external119
def set_fee(new_fee: uint256):120
assert new_fee <= MAX_FEE121
log FeeUpdated(old_fee, new_fee)122
self.fee = new_feeV
Vyper Guardcompleted in 48s
PassedRelease policy4 / 4 checks
Compiler semantics availablePASS
No new supported findingsPASS
Protocol rules satisfiedPASS
Resolved in this PR
Administrative fee update lacked an eventReviewers can now trace every fee-policy change on-chain.
Release 1.12.0Ready to merge
Fits the stack you already useVYPER GITHUB SARIFCI / CDJSON WEBHOOKS
01 / PLATFORMOne security system.
One security system.
Every release decision.
Vyper Guard connects analysis, review, enforcement, and governance so findings do not disappear between tools.
01Explore Analyze
Understand Vyper as Vyper.
Compiler-aware source analysis, project context, verification signals, and explicit semantic health.
contracts/Vault.vyCOMPILER
Pull request policyENFORCED
Evidence recordVERSIONED
02 / WHY VYPER GUARDSecurity that moves
Security that moves
at protocol speed.
Purpose-built workflow keeps developers moving while preserving the evidence security teams need.
Review a decision, not an alert count.
Source evidence, confidence, maturity, baseline state, and ownership give every finding a place in engineering review.
Block only what changed.
Stable fingerprints and new-finding policy keep existing debt visible without turning every pull request red.
Carry security evidence into the release.
Versioned reports, policy results, and review state remain available when auditors or stakeholders need the record.
03 / OPEN COREStart local.
Start local.
Scale the workflow.
The analyzer is free and open source. Teams pay when security decisions need shared policy, ownership, history, and operational support.
$ pip install vyper-guardCommunity
For every Vyper developer
Local analysis, structured reports, baselines, detector registry, and CI execution.
Install the CLITeam
For protocols shipping together
Managed pull-request review, central findings, policy, evidence, onboarding, and protocol-specific rules.
Book a demoEnterprise
For controlled environments
SSO, audit logs, self-hosting, deployment controls, custom rule packs, and SLA.
Compare plans04 / RESEARCHSecurity knowledge,
Security knowledge,
published in the open.
Detector design, evaluation notes, and engineering decisions live in a reproducible research library.
Evaluating detector signal on Curve DAO
A reproducible, internally reviewed comparison at Trail of Bits' audited commit.
Detector maturity is an evidence standard
Why rule availability, promotion status, and review support are separate product concepts.
Stable findings make regression policy possible
How fingerprints separate accepted debt from code introduced in a pull request.
Vyper Guard 0.6.0
Compiler health, project analysis, evidence-rich output, and a quieter default review path.
05 / MISSION
Vyper deserves security tooling designed around the language, not adapted to it as an afterthought.
Vyper Guard exists to turn deep language analysis into a reliable release workflow: transparent when evidence is weak, precise when policy needs to block, and open where developers need to inspect it.
Why we are building Vyper GuardYour next Vyper releaseStart with
Start with
the code.
Run the open-source analyzer today. Bring the workflow to your team when shared policy matters.