Rythe is a data-oriented C++20 game engine built to make optimal use of modern hardware.
A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in Rythe-Engine's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
fix erasure in hash_map, fix \0 being copied when appending string literals to contiguous containers, rythe_debugbreak_if_debugger_attached, fix string_view natvis, some validation tools
fix compiler_dependent_templated_type_name for gcc and clang, add rythe_defer_execution
rename is_integral->is_integer, align_value, align_pointer, versioned_handle, fix make_partial_result, add cleaning intermediate files in rrg, ...
circumvent issue with clang-cl and isa extensions, various filesystem improvements for rsl
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.