Is t8y2/dbx welcoming to first-time open-source contributors?
t8y2/dbx has a recorded first-timer success rate of 78.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。
C-Rank Grade: S (Elite) - 69/100
External PR Merge Rate: 80%
Response Time: -
First Timer Success: 78%
t8y2/dbx has a recorded first-timer success rate of 78.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in t8y2/dbx respond to incoming external pull requests in approximately 0.0 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 69.3 places t8y2/dbx in the S tier.
The external contributor pull request merge rate for t8y2/dbx is 80.2%, based on public PR activity from non-core contributors.
t8y2/dbx does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。
Highly welcoming maintainers in t8y2/dbx. Prompt code reviews with positive guidance for new contributors.
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/t8y2/dbx?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (36% approval). Keep your diff compact for rapid review.
来源 QQ 群反馈 · 反馈人:🇨🇳Heavy Metal AI 摘要 建议允许用户随意调整 AI 对话界面的大小,支持最大化,并可向左拖动至最大宽度。 原始描述 优化 AI 对话界面,可以随意调整大小,可以最大化,可以往左拖到最大.
数据库类型和版本 DM8 问题描述 在查询窗口进行查询,查询结果标签页通过shift+鼠标以及水平滚动条滚动时,概率会将查询结果标签复制一份,多次滑动就会复制多个标签,影响操作 错误日志 DBX 版本 0.5.33 操作系统 Windows 优先级(是否紧急) 🟠 P1 重要 · 尽快处理 补充信息 No response
描述 ollama本地模型设置,测试无法通过,本地模型在其它软件(cherrystdio、python程序)使用正常 环境信息 DBX版本:0.5.32、0.5.34便携版 操作系统:WIN11
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 t8y2/dbx, 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 t8y2/dbx acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.2% were successfully merged into the primary branch.
t8y2/dbx has a recorded first-timer success rate of 78.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 69.3 places t8y2/dbx in the Elite tier.
The external pull request merge rate is 80.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
t8y2/dbx does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for t8y2/dbx 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.