Are We Safety Critical Yet?
Tracking Rust's readiness for safety-critical development across industry standards.
Standards-Based Evaluations
Safety-critical readiness is measured by how well Rust's language design, toolchain, and ecosystem enable developers to meet the requirements of the relevant safety standards. For more context, see the full overview.
ISO 26262
Achievable with moderate additional effort
Rust's core language features - memory safety, strong typing, and data race prevention - provide an excellent basis for ISO 26262 compliance. Critical gaps exist in qualified tools, control/data flow analysis, and qualified RTOS/HAL/PAC support.
View detailed analysis →Consortium Working Groups
Coding Guidelines
Develops and maintains coding guidelines focused on safety-critical applications in Rust.
Tooling
Aims to define and maintain a minimal, community-identified set of tools suggested for certifying Rust in safety-critical applications. It maintains documentation on these tools and their development status, helping guide adoption and compliance efforts.
Liaison
The liaison subcommittee will both proactively and reactively collaborate with other subcommittees in the consortium and outside groups such as standards committees, the Rust Project. The committee will work to drive agreement on various, potentially similar, safety critical efforts pertaining to Rust. The committee will also be the point of contact for any potential legal issues that may arise around IP as it pertains to references, upstreaming content and more.