New-finding gates
Compare stable fingerprints against the baseline and block regressions rather than historical debt.
Platform / 03 Enforce
Stop regressions at the pull request.
Baselines, new-finding gates, SARIF annotations, required checks, and release policy.
03Connected platform workflow
VyperLanguage-native context
Built into the release workflow.
Baselines, new-finding gates, SARIF annotations, required checks, and release policy. 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
Pull-request annotations
Put source-linked findings into the review surface where engineering decisions already happen.
Required checks
Fail releases on supported severity, compiler-health, or protocol-policy conditions.
SARIF and CI
Integrate with code scanning while retaining Vyper Guard's richer JSON evidence.
Immutable policy versions
Record which detector and policy versions governed each release decision.
Gradual rollout
Adopt visibility first, then enable enforcement as findings and suppressions are reviewed.
Vyper Guard / Enforce