A reliable coding agent for complex software engineering tasks.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 70%
Response Time: 9h
First Timer Success: 40%
esengine/DeepSeek-Reasonix has a recorded first-timer success rate of 40.1%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in esengine/DeepSeek-Reasonix respond to incoming external pull requests in approximately 8.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 73.0 places esengine/DeepSeek-Reasonix in the S tier.
The external contributor pull request merge rate for esengine/DeepSeek-Reasonix is 69.9%, based on public PR activity from non-core contributors.
esengine/DeepSeek-Reasonix currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in esengine/DeepSeek-Reasonix. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/esengine/DeepSeek-Reasonix?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (87% approval). Large PRs (>500 lines) take ~42 hours (31% approval). Keep your diff compact for rapid review.
Version line v2 — Go rewrite (1.x), main-v2 (active development) Exact version 1.38.12 What happened? Steps to reproduce 1.打开应用 2.程序CPU高位，并且界面无响应 ３.历史加载不出来 ４.新会话失败，添加新项目失败，无响应； OS / platform WIN10 Relevant logs or output
Version line v2 — Go rewrite (1.x), main-v2 (active development) Exact version v1.38.10（git 366e0eb6b86b，构建 2026-09-18T02:26:50Z，windows/amd64，桌面端） What happened? 升级到 v1.38.10 后，v5 会话存储迁移中断，导致该工作区永久只读（既不能打开会话、也不能新建会话），并连带该工作区的 shell 工具永久不可用。数据未损坏。 现象与日志原文（desktop-shell\logs\service.log）： WARN desktop: session history load failed err="workspace mutation conflicts with persisted state" WARN session: refusing unsafe event-log replay path=…\20260820-114923….events.jsonl resource=encoded_bytes value=194878707 limit=134217728 UI 侧：顶部「启动错误：session history could not be loaded safely; the session files were left unchanged」；主面板「暂时无法加载会话 / 本次历史加载未完成，请重试后继续」；「重试加载」永久失败；输入框禁用「恢复后可发送」。点「新
Upgrading v1.38.7 → v1.38.10 (Windows) replaces the sidebar's topic names with the first user-role record of each migrated session's transcript — which in practice is an injected host block — and multiplies rows by importing the same legacy session several times. The user's own topic titles are still on disk and are simply not used. Environment Windows 10 IoT Enterprise LTSC (19044), upgraded over an existing v1.38.7 install with existing history installed Reasonix-windows-amd64-installer.exe, sha256 c46cb375fae24becd0ac76306c664014dc50c37286789f11b70feba6848b32bf (release desktop-v1.38.10) What the sidebar shows 24 rows, labelled with injected block text rather than anything the user wrote — for example: <session-context version="1"> This host-generated snapshot supersedes every earlier session-context snapshot. Section lengths: Environment=410; Worksp… <capability-route version="1"> Relevant capabilities for this turn: - mcp-tool:ha-mcp/ha_search prefer: … <memory-upda
Version line v2 — Go rewrite (1.x), main-v2 (active development) Exact version 1.38.7 (build 036c7c50c5c1), Windows 10 IoT Enterprise LTSC 10.0.19044 What happened? A conversation can no longer be opened at all in the desktop app. It reports Failed to load conversation history. Previous content was kept when available — retry to try again. Failed to load conversation history. Previous content was kept when available — retry to try again. Cannot open session and — unlike the transient variant reported in #10162 — this does not recover by switching conversations, and does not recover by restarting the app. The session is a long-lived one (topic AI Arr** Doctor, 50 turns, 8.4 MB transcript). The data is intact. The canonical transcript parses completely: jsonl: 1423 lines, 8.4 MB, 0 unparseable roles: system 1 | user 77 | assistant 580 | tool 765 So this is a projection/load failure, not data loss — but the practical effect for the user is that a 50-turn conversation is unre
Version line v2 — Go rewrite (1.x), main-v2 (active development) Exact version 1.29.0 What happened? 自定义供应商会覆盖官网的key Steps to reproduce 当自定义供应商里面仅存在deepseek时，api_key_env会识别成：DEEPSEEK_API_KEY，这样就会把录入的DeepSeek官方的key给覆盖，而且没有任何提示。 OS / platform win10 Relevant logs or output
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to esengine/DeepSeek-Reasonix, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of esengine/DeepSeek-Reasonix acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.9% were successfully merged into the primary branch.
esengine/DeepSeek-Reasonix has a recorded first-timer success rate of 40.1%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 73.0 places esengine/DeepSeek-Reasonix in the Elite tier.
The external pull request merge rate is 69.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, esengine/DeepSeek-Reasonix currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for esengine/DeepSeek-Reasonix are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.