Auditing crates for unsafe code which can be safely replaced
☆569Mar 25, 2022Updated 3 years ago
Alternatives and similar repositories for safety-dance
Users that are interested in safety-dance are comparing it to the libraries listed below
Sorting:
- Detects usage of unsafe Rust in a Rust crate and its dependencies.☆1,567Jan 11, 2026Updated 2 months ago
- RustSec API & Tooling☆1,852Mar 13, 2026Updated last week
- Make production Rust binaries auditable☆812Mar 4, 2026Updated 2 weeks ago
- Gather author, contributor and publisher data on crates in your dependency graph.☆350Feb 5, 2026Updated last month
- Runtime for executing procedural macros as WebAssembly☆1,474Jan 21, 2026Updated last month
- Modular, structure-aware, and feedback-driven fuzzing engine for Rust functions☆449Jan 22, 2026Updated last month
- Execute your code on the Rust ecosystem.☆191Feb 12, 2026Updated last month
- Ensure correct assumptions about constants, types, and more in Rust☆648Nov 18, 2023Updated 2 years ago
- "Freedom from syn": Proc macro tools for operating on token trees☆107Mar 21, 2020Updated 5 years ago
- A cryptographically verifiable code review system for the cargo (Rust) package manager.☆2,276Nov 21, 2025Updated 3 months ago
- Rust Memory Safety & Undefined Behavior Detection☆1,368Mar 9, 2024Updated 2 years ago
- Attribute macro to require that the compiler prove a function can't ever panic☆1,186Feb 8, 2026Updated last month
- A rust crate to offer compile-time assistance for working with unsafe code.☆122Oct 11, 2021Updated 4 years ago
- Conditional compilation according to rustc compiler version☆393Feb 16, 2026Updated last month
- Coordination repository for the Secure Code Working Group☆163Jun 2, 2021Updated 4 years ago
- This crate guarantees that your application is free of panicking branches☆178May 23, 2019Updated 6 years ago
- Forum for discussion about what unsafe code can and can't do☆735Aug 19, 2025Updated 7 months ago
- Execute Rust code carefully, with extra checking along the way☆481Jan 3, 2026Updated 2 months ago
- Build and verify byte-for-byte reproducible Rust packages using a Cargo-based workflow☆59Mar 11, 2021Updated 5 years ago
- Cargo subcommand `release`: everything about releasing a rust crate.☆1,540Mar 13, 2026Updated last week
- A cargo subcommand for displaying when Rust dependencies are out of date☆1,383Feb 5, 2026Updated last month
- A collection of open source Rust crates from iqlusion☆559Mar 12, 2026Updated last week
- A code coverage tool for Rust projects☆2,929Updated this week
- Type-safe transmutations between layout-compatible types.☆122Aug 11, 2020Updated 5 years ago
- Rust implementation of Project Fluent☆1,296Nov 10, 2025Updated 4 months ago
- Experimental one-shot benchmarking/profiling harness for Rust☆645Aug 14, 2024Updated last year
- Rust derive-based argument parsing optimized for code size☆1,896Mar 12, 2026Updated last week
- Command line helpers for fuzzing☆1,772Feb 10, 2026Updated last month
- Security advisory database for Rust crates published through crates.io☆1,093Updated this week
- A safe and fast multi-producer, multi-consumer channel.☆2,971Dec 22, 2025Updated 2 months ago
- Effortlessly fuzz libraries with large API surfaces☆71Aug 18, 2021Updated 4 years ago
- Implements a fixed-capacity stack-allocated Vec alternative backed by an array, using const generics.☆265May 29, 2023Updated 2 years ago
- A collection of small utilities for working with pointer types in Rust.☆133Jan 17, 2025Updated last year
- mdbook on common pitfalls in unsafe rust code☆11May 24, 2019Updated 6 years ago
- Faster, more compact implementation of std::Cow☆374Apr 13, 2023Updated 2 years ago
- Concurrency permutation testing tool for Rust.☆2,640Feb 20, 2026Updated last month
- Rust support for the coz Causal profiler, code now lives upstream -- https://github.com/plasma-umass/coz☆218Oct 7, 2019Updated 6 years ago
- A `#[safe]` attribute for explaining why `unsafe { ... }` is OK.☆81Jun 17, 2019Updated 6 years ago
- Generating structured data from arbitrary, unstructured input.☆853Mar 13, 2026Updated last week