bevyengine/bevy

A refreshingly simple data-driven game engine built in Rust

View on GitHub ↗Jump to charts ↓Open shareable report →

bevyengine/bevy has 49k+ stars and 4.5k+ forks on GitHub, is written in Rust, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 51 minutes ago
Type:FrameworkCategory(s):Game DevelopmentMedia, Graphics & Games
Added to GitGenius on August 31st, 2026
Created on January 18th, 2020
Open Issues & Pull Requests: 3,525 (+1)
GitHub issues: Enabled
Number of forks: 4,944
Total Stargazers: 49,099 (+3)
Total Subscribers: 327 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.8 hours
Mean response time: 32.2 days
90th percentile: 49.3 days
Tracked items: 3,869

Maintainer activity

58 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in five opened in the past year never receives a reply. 81% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "S-Needs-Design" is answered fastest, typically in about 5 hours, while "D-Straightforward" waits about 29 hours. 62% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 51% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,953
New in 7 days: 42
Closed in 7 days: 15
Avg open age: 530 days
Stale 30+ days: 1,836
Stale 90+ days: 1,598

Recent activity

Opened in 7 days: 38
Closed in 7 days: 13
Comments in 7 days: 12
Events in 7 days: 76

Top labels

  • C-Bug (2,077)
  • S-Ready-For-Implementation (1,377)
  • A-Rendering (1,235)
  • C-Feature (1,082)
  • A-ECS (821)
  • D-Straightforward (703)
  • S-Needs-Design (667)
  • S-Needs-Investigation (610)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Bevy is a data-driven game engine built in Rust that emphasizes simplicity and modularity for both 2D and 3D game development.

The engine solves the problem of creating games with a modern, approachable architecture by adopting an Entity Component System paradigm. This data-oriented design allows developers to structure game logic around composable components rather than deep inheritance hierarchies, making it easier to reason about and modify game behavior. The engine prioritizes fast compilation times and parallel execution of application logic to reduce iteration friction during development.

Bevy suits developers comfortable with Rust who want a lightweight, modular foundation they can extend or replace as needed. It works well for projects where you value compile speed and architectural flexibility over stability guarantees. The engine is still in early development stages with sparse documentation, and the API receives breaking changes approximately every three months, so it is best suited for teams willing to maintain migrations and adapt to evolving APIs. The project requires staying close to the latest stable Rust release due to its reliance on recent language and compiler improvements.

Development activity shows a mature community infrastructure with official Discord, Reddit, and GitHub Discussions channels for support and collaboration. The project maintains a dedicated contributor's guide and encourages both simple issue fixes and complex architectural discussions through GitHub Discussions. Migration guides are provided alongside breaking changes to help users adapt between releases. The team publishes a development blog covering progress, plans, and new features to keep the community informed of direction and upcoming work.