Vyper semantics
Use source or matching compiler semantics and retain effective analysis health.
Open-source CLI
Vyper-native security, directly in the repository.
Scan locally, preserve structured evidence, and enforce new-finding policy in CI without uploading source code.
Recommended scan
$ vyper-guard analyze contracts/ --detectors recommendedDetector profiles
Run supported defaults and opt into experimental review rules deliberately.
Baseline and diff
Separate existing reviewed findings from risk introduced by a change.
Portable output
Generate terminal, JSON, SARIF, Markdown, and standalone HTML.
Bounded remediation
Preview eligible corrections without hiding the original finding context.
Contract metrics
Inspect state, functions, calls, complexity, and project relationships.
One finding model across every surface.
Terminal triage, GitHub annotations, automation, and audit evidence retain the same source and analysis context.
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