AI-native workspace for local shells and remote machines.Zero Webview, zero OpenSSL, zero telemetry, and no app subscription.
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 75%
Response Time: -
First Timer Success: 100%
AnalyseDeCircuit/oxideterm has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AnalyseDeCircuit/oxideterm 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 54.2 places AnalyseDeCircuit/oxideterm in the B tier.
The external contributor pull request merge rate for AnalyseDeCircuit/oxideterm is 75.0%, based on public PR activity from non-core contributors.
AnalyseDeCircuit/oxideterm currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in AnalyseDeCircuit/oxideterm. Ensure PR scope matches issue requirements closely before requesting review.
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/AnalyseDeCircuit/oxideterm?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (94% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
OxideTerm version / 版本 2.0.28 Platform / 平台 Windows (x86_64) Installation source / 安装来源 GitHub Release (.dmg / .exe / .AppImage / .deb / .rpm) Area / 问题领域 Terminal / local terminal / serial Summary / 简述 终端输入时内容同时包含英文和中文的话渲染有问题 用方向键把光标从右到左,再从左到右,这样几次就会出问题 打开"自由输入"模式时,不用方向键,直接用鼠标在这行来回点几下,特别是中文上,也会出现同样问题 Reproducibility / 可复现性 Always (100%) / 必现 Steps to reproduce / 复现步骤 随便登录一个ssh后输入一串英文与中文 方向键左右来回按到底,几次后就出现 或不用方向键,开启自由输入时,光标在这行来回点,多点几下中文也出现 Expected vs actual / 预期与实际 预期应与全英文一样无渲染问题 Logs or screenshots / 日志或截图 No response Additional environment details / 其他相关环境信息 No response Con
OxideTerm version / 版本 2.0.12 Problem or use case / 问题或使用场景 Currently, the CLI companion allows managing saved connections (oxideterm connections list/search/...) and launching a temporary SSH terminal in the GUI (oxideterm ssh <host>). However, there is no direct way to open/launch an already saved connection profile in the native GUI via the CLI by referencing its name or ID (e.g., oxideterm connections open <name_or_id>). In automated workflows, third-party launchers (like Raycast, Alfred, or custom terminal scripts), or window manager shortcuts, users often want to quickly trigger a pre-configured SSH connection (with all its saved credentials, identity files, and custom settings) in the OxideTerm GUI without re-entering temporary connection details or manually clicking through the app UI. Proposed solution / 期望方案 Introduce a subcommand under connections (or extend oxideterm ssh) to launch a saved connection directly in the GUI. For example: oxideterm con
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 AnalyseDeCircuit/oxideterm, 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 AnalyseDeCircuit/oxideterm acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
AnalyseDeCircuit/oxideterm has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 54.2 places AnalyseDeCircuit/oxideterm in the Solid tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AnalyseDeCircuit/oxideterm currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for AnalyseDeCircuit/oxideterm 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.