Radar · Rust · Archive · Week 21 · May 18 – 24, 2026
OmniScope – Cross‑Language LLVM IR Static Analyzer
Nice to knowtooling
- What changed
- OmniScope targets unsafe/FFI boundaries in LLVM IR.
- Production impact
- The source does not say.
- Try it
- Run OmniScope on a compiled binary to look for unsafe patterns.
- Source
- this-week-in-rust.org/blog/2026/05/20/this-week-in-rust-652/
Understand it, then run it
OmniScope is a new tool that looks at the low‑level code generated by the Rust compiler, called LLVM IR. It focuses on places where Rust code calls into other languages or uses unsafe operations. With OmniScope you can see where those boundaries happen and get warnings if something looks risky. The tool is still in development, so it is not yet part of the standard Rust toolchain.
Run it now
// This program demonstrates how OmniScope would be invoked on a Rust crate.
// Since OmniScope is not yet shipped, we show the command that would be run
// after building the crate. In a real environment you would replace
// `my_crate` with your crate name and run this from the crate root.
fn main() {
// Build the crate first
println!("Running: cargo build --release");
// Then run OmniScope on the generated LLVM IR
println!("Running: omniscape analyze target/release/deps/my_crate");
// The output would list unsafe/FFI boundaries found in the IR.
}
What it printed when we ran it on Rust 1.98.1 (edition 2024)
Running: cargo build --release Running: omniscape analyze target/release/deps/my_crate
Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.
Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed