The open-source AI research workbench for scientific research and agent workflows. Local-first, model-agnostic desktop app with extensible skills, MCP tools and connectors, Python/R execution and traceable artifacts for reproducible research on macOS, Windows and Linux.
C-Rank Grade: S (Elite) - 69/100
External PR Merge Rate: 78%
Response Time: -
First Timer Success: 69%
aipoch/open-science has a recorded first-timer success rate of 69.2%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in aipoch/open-science 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.4 places aipoch/open-science in the S tier.
The external contributor pull request merge rate for aipoch/open-science is 77.6%, based on public PR activity from non-core contributors.
aipoch/open-science does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
The open-source AI research workbench for scientific research and agent workflows. Local-first, model-agnostic desktop app with extensible skills, MCP tools and connectors, Python/R execution and traceable artifacts for reproducible research on macOS, Windows and Linux.
Highly welcoming maintainers in aipoch/open-science. 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/aipoch/open-science?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10: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 (35% approval). Keep your diff compact for rapid review.
Preflight checklist I searched existing issues and this has not been reported yet. I'm running a recent version of Open-Science. What happened? An external folder was explicitly granted Read & write permission through the Open-Science GUI, but access to that folder is inconsistent across clean sessions and automatically selected Agent execution backends. The session cwd was intentionally left unchanged. The external folder is outside the managed session workspace. I expected that, once a folder had been explicitly granted Read & write permission, the Agent could access it consistently without requiring the user to specify implementation details such as Notebook, Shell, Python, pathlib, Node.js, or host.artifacts(). Instead, the same authorized folder and the same natural-language request produced different results. Controlled observations: Codex + Codex Subscription / gpt-5.6-sol: failed. Codex + Kimi / kimi-k2.6: failed. Claude Code + Kimi / kimi-k2.6: inconsistent across cl
Preflight checklist I searched existing issues and this has not been reported yet. I'm running a recent version of Open-Science. What happened? 首先感谢你们开发 Open-Science。这个工具整体体验很好，工作流和 UI 设计也很不错，尤其是在数据挖掘、探索和分析方面非常方便，对我的工作很有帮助。 在 macOS 上使用 Open-Science 时，只要发生页面或布局变化，整个 UI 就会明显卡顿，部分操作需要数秒才响应。 目前观察到以下操作都可以触发： 打开项目或进入新的页面 调整应用窗口大小 打开设置页面 关闭设置页面 其他会导致页面或布局发生变化的操作 问题发生时，Open-Science Helper (Renderer) 的 CPU 占用会迅速升高到约 95–100%，而主进程和 GPU Helper 的 CPU 占用都比较低。 例如一次实际观察到： Open-Science Helper (Renderer)：约 97% CPU Open-Science：约 3% CPU Open-Science Helper (GPU)：约 1% CPU 此时磁
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 aipoch/open-science, 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 aipoch/open-science acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.6% were successfully merged into the primary branch.
aipoch/open-science has a recorded first-timer success rate of 69.2%. 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.4 places aipoch/open-science in the Elite tier.
The external pull request merge rate is 77.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
aipoch/open-science 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 aipoch/open-science 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.