Self-hosted gateway for Claude Code, Codex, Antigravity, Grok Build, OpenCode. Run AI coding agents on your own infra with a shared local-first memory layer. Drive from web, mobile, Telegram / Slack / Discord / Feishu / DingTalk / WeCom. Open REST + WebSocket API. Apache 2.0.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 89%
Response Time: 2d
First Timer Success: 50%
Opendray/opendray has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Opendray/opendray respond to incoming external pull requests in approximately 40.4 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 62.0 places Opendray/opendray in the A tier.
The external contributor pull request merge rate for Opendray/opendray is 88.9%, based on public PR activity from non-core contributors.
Opendray/opendray currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Self-hosted gateway for Claude Code, Codex, Antigravity, Grok Build, OpenCode. Run AI coding agents on your own infra with a shared local-first memory layer. Drive from web, mobile, Telegram / Slack / Discord / Feishu / DingTalk / WeCom. Open REST + WebSocket API. Apache 2.0.
Growing Dart project in Opendray/opendray welcoming community pull requests and bug fixes.
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/Opendray/opendray?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~26 hours (96% approval). Large PRs (>500 lines) take ~194 hours (40% approval). Keep your diff compact for rapid review.
What opendray providers list and opendray status currently emit human-readable text. Add a --json flag to both that emits machine-readable JSON so operators can script against them (monitoring, dashboards, dotfiles, cron jobs). Acceptance criteria opendray providers list --json emits an array of provider objects with keys: id, name, installed_version, latest_version, update_available (bool), manifest_path, plus any other fields already in the human output. opendray status --json emits a single object with the daemon's current state: service_state (running / stopped / errored), pid, listen_address, binary_version, last_restart_ts, db_reachable (bool), active_session_count. Existing human-readable output unchanged when --json is absent. Output is parseable by jq (opendray providers list --json | jq '.[].id' works). Help text shows the flag: opendray providers list --help and opendray status --help. Tests in the CLI test suite cover both flag paths. Where to start CLI subcommands
What The Providers page (/admin/providers) currently renders empty / blank during the first API roundtrip and then snaps into the full list. Add skeleton placeholders so the layout is stable from first paint and the page doesn't appear to "jump" when data arrives. Acceptance criteria Each provider row (Claude / Codex / Gemini) shows a skeleton placeholder for: provider name, installed version chip, latest-version chip, Update button, and the account-status chips (subscription tier, rate-limit tier, active sessions, last-used, email). Skeletons match the final element heights and widths within ~5px so the layout doesn't shift when real data lands. Skeletons animate (pulse / shimmer) to signal "loading", not "stuck". If the API errors, the skeletons are replaced with an inline error state (not just a console error). No regressions on the other admin pages. Where to start Page component: app/web/src/pages/Providers.tsx (or similar) Existing skeleton primitive: check app/web/src/co
What scripts/install-linux.sh currently supports Debian / Ubuntu paths only (apt for package install, systemctl for service registration). Extend it to also work on Fedora, RHEL, Rocky Linux, and AlmaLinux (dnf / yum for packages, same systemd story for the service). Acceptance criteria install-linux.sh detects the distro via /etc/os-release (ID and ID_LIKE). For fedora, rhel, rocky, almalinux (or any distro where ID_LIKE contains rhel / fedora), use dnf install (preferred) or yum install (fallback) for package install. PostgreSQL + pgvector install on these distros uses the right package names. Note: Fedora and RHEL ship pgvector under different package names than Debian; the script should handle this. Document in a comment if any distro needs a third-party repo (e.g. postgresql.org rpm repo for PG17 on RHEL). Service registration (systemd unit drop-in, daemon-reload, enable, start) is unchanged. SELinux: warn the operator if getenforce returns Enforcing, with a one-liner suggest
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 Opendray/opendray, 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 Opendray/opendray acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.9% were successfully merged into the primary branch.
Opendray/opendray has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 62.0 places Opendray/opendray in the Welcoming tier.
The external pull request merge rate is 88.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Opendray/opendray currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Opendray/opendray 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.