Compiler-aware semantics
Use matching Vyper compiler semantics when available and report honest fallback health when they are not.
Platform / 01 Analyze
Understand Vyper as Vyper.
Compiler-aware source analysis, project context, verification signals, and explicit semantic health.
01Connected platform workflow
VyperLanguage-native context
Built into the release workflow.
Compiler-aware source analysis, project context, verification signals, and explicit semantic health. The result remains inspectable by developers and enforceable by security teams.
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
Project context
Resolve contracts, interfaces, internal calls, external call targets, state writes, and project relationships.
Focused detector profiles
Separate supported and experimental rules so default reviews optimize signal rather than detector count.
Verification signals
Bring configured unit and fuzz results into the same release evidence.
Deployed source
Resolve verified source and preserve chain and compiler context for investigation.
Portable analysis
Emit terminal, JSON, SARIF, Markdown, and standalone HTML without changing the underlying finding record.
Vyper Guard / Analyze