Skip to main content

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.

Well supported Achievable with effort Gap Not yet rated

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 →

IEC 61508

Analysis in preparation

Contributions welcome.

Contribute on GitHub →

DO-178C

Analysis in preparation

Contributions welcome.

Contribute on GitHub →

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

Collaborates with other consortium subcommittees and outside groups, including standards committees and the Rust Project, to align related safety-critical Rust efforts.