Bevy Engine
@bevyengine • A modular game engine built in Rust, with a focus on developer productivity and performance . Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
98%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
22 repos
Visible snapshot
13 repositories updated in the last 90 days.
Leading language
Rust
Portfolio mix
Rust (12), Unknown (3), JavaScript (2)
Average size
2.3K
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-03-30(194d ago)GitHub API fallback22 repositories
98%
of the visible star count comes from this organization's top three repositories.
2.3K
stars per repository in this same snapshot.
Rust
is the most common language here, with 13 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 95% of its visible star count.
Flagship share 95%Breakout repo: bevy
Organization pages work best when you separate portfolio breadth from flagship concentration. In Bevy Engine's case, the visible top three repositories account for about 98% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Rust (12), Unknown (3), JavaScript (2). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | bevyengine/bevy A refreshingly simple data-driven game engine built in Rust | Rust | 48.8K |
| 2 | bevyengine/bevy-assets A collection of Bevy assets, plugins, learning resources, and apps made by the community | 1.1K | |
| 3 | bevyengine/bevy_editor_prototypes Low-friction experiments for the bevy_editor | Rust | 419 |
| 4 | bevyengine/bevy_github_ci_template | JavaScript | 261 |
| 5 | bevyengine/bevy-website The source files for the official Bevy website | JavaScript | 249 |
| 6 | bevyengine/naga_oil | Rust | 225 |
| 7 | bevyengine/rfcs Suggest changes to Bevy and view accepted designs | 116 | |
| 8 | bevyengine/dlss_wgpu | Rust | 58 |
| 9 | bevyengine/atomicow A `Cow`-like data structure where owned data is stored inside an `Arc`. | Rust | 36 |
| 10 | bevyengine/variadics_please | Rust | 27 |
| 11 | bevyengine/bevy-community A listing of Bevy community members which is displayed on the Bevy website | 26 | |
| 12 | bevyengine/bevy-example-runner run example from Bevy and check for issues | HTML | 16 |
| 13 | bevyengine/disqualified Lazily shortens a "fully qualified" Rust type name to remove all module paths. | Rust | 14 |
| 14 | bevyengine/twitcher Metrics about Bevy | HTML | 12 |
| 15 | bevyengine/web-task A task executor for wasm | Rust | 11 |
| 16 | bevyengine/bevy-crate-reservations Reserved crates.io crate names. Contact us if you think your project needs one of these names! | Shell | 11 |
| 17 | bevyengine/bevy_mikktspace A safe Rust implementation of the Mikkelsen Tangent Space Algorithm. | Rust | 10 |
| 18 | bevyengine/bevy-donors | Rust | 9 |
| 19 | bevyengine/bevy_asset_files | Python | 2 |
| 20 | bevyengine/mikktspace Rust MikkTSpace implementation | Rust | 2 |
| 21 | bevyengine/bevy-releasability CI to check Bevy releasability | Python | 1 |
| 22 | bevyengine/cratesio-dbdump-csvtab Fork to fix a dependency issue | Rust | 0 |
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.