godot-rust/gdext

Rust bindings for Godot 4

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 13th, 2026
Created on July 6th, 2022
Open Issues & Pull Requests: 67 (+0)
GitHub issues: Enabled
Number of forks: 307
Total Stargazers: 5,191 (+0)
Total Subscribers: 36 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

gdext is a Rust bindings library for Godot 4 that enables developers to write game code and extensions in Rust instead of GDScript.

The library solves the problem of integrating Rust with Godot by providing a pragmatic API that prioritizes type safety, scalability, and performance. It leverages Godot's GDExtension API to allow Rust and GDScript to coexist in the same project, with custom Rust code callable type-safely from GDScript. The design philosophy emphasizes minimal boilerplate for common workflows while maintaining idiomatic Rust patterns, even where unconventional approaches are needed to accommodate Godot's C++ engine architecture.

The tool is suitable for developers building games, editor plugins, tools, and other Godot-based applications who value Rust's safety guarantees and performance characteristics. It has reached a usable state with the vast majority of Godot APIs mapped to Rust. Developers should be aware that breaking changes occur occasionally, though these are typically minor and accompanied by migration guides. Experimental support exists for WebAssembly, Android, and iOS platforms, though documentation and tooling for these targets remain incomplete. The project provides a book, API documentation, and demo projects to support adoption.

Development activity shows a focus on improving the user experience through more natural Rust idioms and design patterns suited to game development workflows. The project maintains an elaborate continuous integration suite covering static analysis, unit tests, engine integration tests, and memory sanitizers, with hot-reload functionality also tested. The vast majority of Godot APIs have been mapped, indicating comprehensive coverage of the engine's capabilities.