lincheck
kani
lincheck | kani | |
---|---|---|
1 | 47 | |
8 | 1,932 | |
- | 5.0% | |
7.1 | 9.5 | |
10 months ago | 4 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lincheck
kani
-
The C Bounded Model Checker: Criminally Underused
This is also the backend for Kani - Amazon's formal verification tool for Rust.
https://github.com/model-checking/kani
- BoletÃn AWS Open Source, Christmas Edition
-
The Wizardry Frontier
Nice read! Rust has pushed, and will continue to push, the limits of practical, bare metal, memory safe languages. And it's interesting to think about what's next, maybe eventually there will be some form of practical theorem proving "for the masses". Lean 4 looks great and has potential, but it's still mostly a language for mathematicians. There has been some research on AI constructed proofs, which could be the best of both worlds because then the type checker can verify that the AI generated code/proof is indeed correct. Tools like Kani are also a step forward in program correctness.
-
Kani 0.40.0 has been released!
Ease setup in Amazon Linux 2 by @adpaco-aws in #2833
-
Kani 0.39.0 has been released!
Limit --exclude to workspace packages by @tautschnig in #2808
-
Kani 0.38.0 has been released !
Here's a summary of what's new in version 0.38.0:
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
> those applications need the proof for correctness so that more dangerous code---say, what would need `unsafe` in Rust---can be safely added
There are actually already tools built for this very purpose in Rust (see Kani [1] for instance).
Formal verification has a serious scaling problem, so forming programs in such a way that there are a few performance-critical areas that use unsafe routines seems like the best route. I feel like Rust leans into this paradigm with `unsafe` blocks.
[1] - https://github.com/model-checking/kani
-
Kani 0.36.0 has been released!
Enable concrete playback for failure of UB checks by @zhassan-aws in https://github.com/model-checking/kani/pull/2727
-
Kani 0.34.0 has been released!
Change default solver to CaDiCaL by @celinval in https://github.com/model-checking/kani/pull/2557 By default, Kani will now run CBMC with CaDiCaL, since this solver has outperformed Minisat in most of our benchmarks. User's should still be able to select Minisat (or a different solver) either by using #[solver] harness attribute, or by passing --solver= command line option.
-
Kani 0.33.0 has been released!
Add support for sysconf by feliperodri in #2557
What are some alternatives?
sled - the champagne of beta embedded databases
prusti-dev - A static verifier for Rust, based on the Viper verification infrastructure.
rmc - Kani Rust Verifier [Moved to: https://github.com/model-checking/kani]
awesome-rust-formalized-reasoning - An exhaustive list of all Rust resources regarding automated or semi-automated formalization efforts in any area, constructive mathematics, formal algorithms, and program verification.
crossbeam - Tools for concurrent programming in Rust
MIRAI - Rust mid-level IR Abstract Interpreter
left-right - A lock-free, read-optimized, concurrency primitive.
gdbstub - An ergonomic, featureful, and easy-to-integrate implementation of the GDB Remote Serial Protocol in Rust (with no-compromises #![no_std] support)
cargo-check-deadlock - Find deadlocks in Rust code with Petri net model checking
watt - Runtime for executing procedural macros as WebAssembly
rustig - A tool to detect code paths leading to Rust's panic handler