Vyper is not immune to compiler bugs: certain older compiler versions had subtle issues (e.g. incorrect reentrancy-lock storage-slot collisions in specific versions in 2023 that led to real fund losses in some deployed pools). This is a reminder that language safety features reduce, but never eliminate, the need for careful auditing and using well-tested compiler versions.
# Pin and test against the exact compiler version you plan to deploy with # @version 0.3.10
Track the official Vyper security advisories, avoid bleeding-edge compiler versions for production deployments, and re-audit if you must upgrade compiler versions on an already-designed contract.