Componentpedia / Listings / r-efi

Last update: 28/04/2026

r-efi

UEFI Reference Specification Protocol Constants and Definitions

Latest version: 6.0.0 registry icon
Maintenance score
81
Safety score
100
Popularity score
75
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
De-risk your app now
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
6.0.0 0 0 0 0 0
5.3.0 0 0 0 0 0
5.2.0 0 0 0 0 0
5.1.0 0 0 0 0 0
5.0.0 0 0 0 0 0
4.5.0 0 0 0 0 0
4.4.0 0 0 0 0 0
4.3.0 0 0 0 0 0
4.2.0 0 0 0 0 0
4.1.0 0 0 0 0 0
4.0.0 0 0 0 0 0
3.2.0 0 0 0 0 0
3.1.0 0 0 0 0 0
3.0.0 0 0 0 0 0
2.2.0 0 0 0 0 0
2.1.0 0 0 0 0 0
2.0.0 0 0 0 0 0
1.0.0 0 0 0 0 0
0.1.1 0 0 0 0 0
0.1.0 0 0 0 0 0

Stability
Latest release:

6.0.0 - This version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

SSPL-1.0   -   Server Side Public License, v 1

Not a wildcard

Not proprietary

OSI Compliant

MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant

Apache-2.0   -   Apache License 2.0

Not a wildcard

Not proprietary

OSI Compliant

r-efi

UEFI Reference Specification Protocol Constants and Definitions

The r-efi project provides the protocol constants and definitions of the UEFI Reference Specification as native rust code. The scope of this project is limited to those protocol definitions. The protocols are not actually implemented. As such, this project serves as base for any UEFI application that needs to interact with UEFI, or implement (parts of) the UEFI specification.

Project

Requirements

The requirements for this project are:

  • rustc >= 1.68.0

Build

To build this project, run:

cargo build

Available configuration options are:

  • native: This feature-selector enables compilation of modules and examples that require native UEFI targets. Those will not compile on foreign targets and thus are guarded by this flag.
Build via: official toolchains

Starting with rust-version 1.68, rustup distributes pre-compiled toolchains for many UEFI targets. You can enumerate and install them via rustup. This example shows how to enumerate all available targets for your stable toolchain and then install the UEFI target for the x86_64 architecture:

rustup target list --toolchain=stable
rustup target add --toolchain=stable x86_64-unknown-uefi

This project can then be compiled directly for the selected target:

cargo +stable build \
    --examples \
    --features native \
    --lib \
    --target x86_64-unknown-uefi
Build via: cargo/rustc nightly with -Zbuild-std

If no pre-compiled toolchains are available for your selected target, you can compile the project and the required parts of the standard library via the experimental -Zbuild-std feature of rustc. This requires a nightly compiler:

cargo +nightly build \
    -Zbuild-std=core,compiler_builtins,alloc \
    -Zbuild-std-features=compiler-builtins-mem \
    --examples \
    --features native \
    --lib \
    --target x86_64-unknown-uefi
Build via: foreign target

The project can be built for non-UEFI targets via the standard rust toolchains. This allows non-UEFI targets to interact with UEFI systems or otherwise host UEFI operations. Furthermore, this allows running the foreign test-suite of this project as long as the target supports the full standard library:

cargo +stable build --all-targets
cargo +stable test --all-targets

Note that the native feature must not be enabled for foreign targets as it will not compile on non-UEFI systems.

Repository:

License:

  • MIT OR Apache-2.0 OR LGPL-2.1-or-later
  • See AUTHORS file for details.