This project is a static taint analysis tool for the Rust programming language. We use Rust compiler internals to inspect MIR, which is an intermediate representation of Rust, useful for dataflow analysis.
If you want to read more on how this works, read the master thesis "Static Taint Analysis in Rust: Using Rusts Ownership System for Precise Static Analysis" that this code was developed for. The thesis was written by Emil Jørgensen Njor and Hilmar Gústafsson on June 2021.
For examples of how this tool can be used, and what the expected results would be, please have a look at the tests/ folder.
We have examples of programs which should emit no errors, and programs where the taint analysis should detect a sink receiving possibly tainted data.
We use the rust-toolchain file to manage which version of the compiler we use, as well as any additional components.
Since this project uses compiler internals and the #![feature(rustc_private)] feature, we must use nightly.
Cargo should automatically recognize the toolchain file, and download the necessary toolchain and components when you build the project.
We have tried to make sure that running tests does not deviate from the typical Rust project experience, and should be as simple as typing in the following command:
cargo test
We use the MIT license, available in the LICENSE file.
rustc_driver allows us to run the compiler, and rustc_interface provides APIs for hooking into the right places to perform the analysis.