Verus
Hacker ApprovedRanked 3 of 4 verification languages by recommenders
Lets Rust programmers prove code correct against specifications kept beside the implementation. Most common caveat: its verus! macro wrapping all code unsettles rust-analyzer and tooling.
Lets Rust programmers prove code correct against specifications kept beside the implementation. Most common caveat: its verus! macro wrapping all code unsettles rust-analyzer and tooling.
27 people gave an opinion
- recommend it
- 23
- criticize it
- 4
- approval share
- 85%
Recommended in 10 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 23 people recommend itNeeds 10 or more, met.
- 5.8 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 10 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Useful and impressive in practice
“Verus is making our verification story extremely compelling”
Comment from 17 Sep 2026 in “Developing provably correct Rust code with Verus” “I uncovered a few interesting bugs this way.”
Comment from 8 Sep 2026 in “How well do agents use test/verification techniques?” “Genuinely impressive and massively useful.”
Comment from 17 Sep 2026 in “Developing provably correct Rust code with Verus” Integrates proofs with the Rust language
“it has made me think deeper about the structure and semantics of Rust code”
Comment from 23 Apr 2026 in “Verus is a tool for verifying the correctness of code written in Rust” “I think they found a nice way to integrate proofs with the language.”
Comment from 23 Oct 2026 in “LLMs are making formal software verification feasible at a much larger scale” “It augments Rust with Z3 and is not a pile of unverified slop.”
Comment from 2 Jul 2026 in “Salt v1.0.0 – a systems language with Z3 theorem proving in the compiler” Verifies the real implementation
“couple the implementation and verification so you can't end up with a model that diverges from the actual implementation”
Comment from 9 May 2026 in “Can LLMs model real-world systems in TLA+?” “You can use a refinement style system like Verus in which your spec is a very high level statement of system behavior”
Comment from 17 Jan 2026 in “Lies, Damned Lies and Proofs: Formal Methods Are Not Slopless” Works well with AI agents
“I let the AI bang on the proof and trust the proof assistant to confirm it.”
Comment from 4 Mar 2026 in “When AI Writes the Software, Who Verifies It?” “agents are good at writing Verus proofs in a Rust code base”
Comment from 14 Oct 2026 in “What agents mean for Rust (and vice versa)”
What people warn about
Each mark is one comment
Macro wrapping hurts tooling and builds
“The macro system looks very nice if it doesn't slow down the normal build.”
Comment from 17 Sep 2026 in “Developing provably correct Rust code with Verus” “a `verus! {}` macro wrapping everything was never gonna be a viable way forward”
Comment from 17 Aug 2026 in “The Case Against Formal Verification, 50 Years Later” “Verus wraps everything in its macro that makes rust-analyzer etc unhappy.”
Comment from 23 Apr 2026 in “Verus is a tool for verifying the correctness of code written in Rust” Standalone language, not Rust-integrated
“it's really cool just a tad sad that the rust eco-system didn't allow verus to be more streamlined”
Comment from 23 Apr 2026 in “Verus is a tool for verifying the correctness of code written in Rust” “is a good start for the rust ecosystem, but it's essentially a standalone language today”
Comment from 27 Jul 2026 in “We have proof automation now” Doesn't match clippy or Kani
“seems like it needs more work to do the same thing clippy does”
Comment from 23 Apr 2026 in “Verus is a tool for verifying the correctness of code written in Rust” “it doesn't seem to do the thing I love about Kani”
Comment from 22 Dec 2025 in “AI will make formal verification go mainstream” Nothing new versus other verifiers
“Even Verus itself doesn't really change this.”
Comment from 17 Sep 2026 in “Developing provably correct Rust code with Verus” “There is nothing special about Verus, it works in the same way other program verification frameworks”
Comment from 17 Sep 2026 in “Developing provably correct Rust code with Verus”
Other verification languages people recommend
The three most recommended other verification languages, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 4 verification languages, rankedWhat people said
30 of the 34 comments that mention it, newest first. Each links to the original comment.
“I think they found a nice way to integrate proofs with the language.”
“agents are good at writing Verus proofs in a Rust code base”
“Genuinely impressive and massively useful.”
“Verus is making our verification story extremely compelling”
“the annotations are manual and inherently prone to error.”
“The macro system looks very nice if it doesn't slow down the normal build.”
“Even Verus itself doesn't really change this.”
“or is integrated with specific programming languages like SPARK, Frama-C or this Verus”
“There is nothing special about Verus, it works in the same way other program verification frameworks”
“Verus seems to be exactly what I have been looking for!”
“I uncovered a few interesting bugs this way.”
“a `verus! {}` macro wrapping everything was never gonna be a viable way forward”
“is a good start for the rust ecosystem, but it's essentially a standalone language today”
“are trying to enable exactly what the author is discussing”
“I know that experts thought about how to structure the system”
“It augments Rust with Z3 and is not a pile of unverified slop.”
“Verus looks more promising. It is more Rust-like in syntax”
“couple the implementation and verification so you can't end up with a model that diverges from the actual implementation”
“it just piggybacks on Rust's type system to assume references don't alias”
“Verus wraps everything in its macro that makes rust-analyzer etc unhappy.”
“It's much more programmer-friendly than some other approaches.”
“I have written complex proofs for distributed system using verus which are certainly not expressed by clippy”
“it's really cool just a tad sad that the rust eco-system didn't allow verus to be more streamlined”
“seems like it needs more work to do the same thing clippy does”
“it has made me think deeper about the structure and semantics of Rust code”
“I let the AI bang on the proof and trust the proof assistant to confirm it.”
“auto-active like Verus is used for Rust pretty successfully”
“You can use a refinement style system like Verus in which your spec is a very high level statement of system behavior”
“it doesn't seem to do the thing I love about Kani”
“It's really a cool system for verified programs.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.