Download: Release 0.2026.11.02.8bf68eerelease/0.2026.11.02.8bf68ee ↓release/0.2026.11.02.8bf68ee2026-11-02
+13
Daily
3,807
stars
264
forks
31
watchers
2,212
prs
1,075
issues
91
releases
README
Verus is a tool for verifying the correctness of code written in Rust. Developers write specifications of what their code should do, and Verus statically checks that the executable Rust code will always satisfy the specifications for all possible executions of the code. Rather than adding run-time checks, Verus instead relies on powerful solvers to prove the code is correct. Verus currently supports a subset of Rust (which we are working to expand), and in some cases, it allows developers to go beyond the standard Rust type system and statically check the correctness of code that, for example, manipulates raw pointers. !VS Code Demo Status Verus is under active development. Features may be broken and/or missing, and the documentation is still incomplete. If you want to try Verus, please be prepared to ask for help in the 💬 Zulip. The Verus community has published a number of research papers, and there are a variety of industry and academic projects using Verus. We maintain a list of them, along with recent news coverage. If you're using Verus please consider adding your project to that list (see the instructions there). Try Verus To try Verus in your browser, please visit the Verus Playground. For more involved development, please follow our installation instructions. Then you can dive into the documentation below, starting with the 📖 Tutorial and reference. We also support an auto-formatter (verusfmt) for your Verus code. Documentation Our (work-in-progress) documentation resources include: 📖 Tutorial and reference 📖 API documentation for Verus's standard library 📖 Guide for verifying concurrent code Contributing to Verus Best Practices for publishing Verus-related crates on crates.io. Verus License Verus Logos Examples of Using Verus In addition to the documentation above, it can be helpful to see Verus used in action. Here are some starting points. Publications and projects using Verus. Videos, slides, and exercises from a day-long Verus tutorial. Standalone examples showing Verus in use for small, concrete tasks. Small and medium-sized examples illustrating various Verus features Unit tests for Verus, containing examples of Verus syntax and features. Verus in the news Getting in touch, reporting issues, and starting discussions Please report issues or start discussions here on GitHub, or join us on 💬 Zulip for more realtime discussions and if you need help. Thank you for using and contributing to Verus! We use GitHub discussions for feature requests and more open-ended conversations about upcoming features, and we reserve GitHub issues for actionable issues (bugs) with existing features. Don't worry though: if we think an issue should be a discussion (or vice versa) we can always move it later. We welcome contributions! If you'd like to contribute code, have a look at the tips in Contributing to Verus. --- Zulip sponsors free hosting for Verus. Zulip is an open-source modern team chat app de
Top issues
#1428Triggering on nested index broken18 comments · 2025-02-04#2458Parallel verification at function granularity10 comments · 2026-05-16#1854Support for mixed sign and size in integer type conversions10 comments · 2025-08-06#587Verus not inlining constants?9 comments · 2023-06-07#469verus nondeterminism9 comments · 2023-03-28#2187Improvement: report multiple errors whenever possible8 comments · 2026-02-16#3299tracked types dropped from Future opaque impls across crates7 comments · 2026-10-21#1982`#[verus_spec]` for `const fn`s6 comments · 2025-11-15
Discussions
#3442Any strategy to prevent unsoundness from the rust type checker0 comments · 2026-11-06#3261Support datatype constructors as function values0 comments · 2026-10-18#3149Internal Verus names and attributes generated by Verus macro are visible to Rust code3 comments · 2026-10-12#2971What is the intended refinement path from std::sync::atomic to PAtomic / atomic_ghost?1 comments · 2026-09-23#2930feat: More explicit alternative to unused `let` expressions for triggering quantifier instantiation1 comments · 2026-09-04#2663Naming for Verus-related attributes0 comments · 2026-07-15#2662Refactoring vstd1 comments · 2026-07-15#2661Cycle checking for trait specifications3 comments · 2026-07-15