macOS menu bar app that proxies Claude/Codex/Grok + More subscriptions for use with Factory Droid CLI. Actively maintained and updated with new model releases!
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 56%
Response Time: -
First Timer Success: 83%
nikships/droidproxy has a recorded first-timer success rate of 83.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nikships/droidproxy 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 64.1 places nikships/droidproxy in the A tier.
The external contributor pull request merge rate for nikships/droidproxy is 56.0%, based on public PR activity from non-core contributors.
nikships/droidproxy currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in nikships/droidproxy. 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/nikships/droidproxy?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (70% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
Help wanted: add support for OpenAI's new "Ultrafast" speed tier on GPT models I don't have access to this (it's gated behind the new Pro 500 subscription / API access), so I can't test it myself. Looking for a contributor who has Ultrafast access to add support to DroidProxy. Background At DevDay (Sept 29, 2026), OpenAI announced a new Ultrafast premium speed tier — up to 300 tokens/sec in Codex and Work, also available to API users. Announcement coverage: https://www.engadget.com/2272106/openai-adds-dollar500-pro-subscription-nerfs-its-existing-dollar200-tier/ DroidProxy already supports the existing fast mode (Codex priority tier) on Responses API requests for gpt-6-astra, gpt-6.1-sol, and gpt-6-luna by injecting "service_tier":"priority" into the request body. What's needed Per-model "Ultrafast" toggles (alongside the existing fast-mode toggles) in SettingsView, backed by new AppPreferences keys Injection of the Ultrafast service_tier value on Responses API requests (/v1/respons
Parent: #146 The current Windows portable build can produce a single-file .exe, but it is unsigned and likely to trigger Windows SmartScreen warnings. We do not want an official release path that requires users to bypass security prompts. Potential scope: Research practical distribution options that avoid security override instructions. Document whether Windows code signing is required and what it would cost/entail. Investigate whether a source-only, winget, Microsoft Store, or other path is viable for this project. Propose a release workflow only if it avoids asking users to bypass security warnings. Do not attach unsigned Windows binaries to official releases as part of this issue.
Parent: #146 The Windows WIP app needs basic validation so contributors can safely make changes. Potential scope: Expand the existing npm run check coverage. Add lightweight tests for settings sanitization, config generation, and Factory settings updates. Add a simple manual smoke-test checklist for starting/stopping the proxy and applying Factory models. Consider CI coverage for the Windows WIP package if it can run without signing or privileged setup. The goal is to make provider ports and UI cleanup safer for contributors.
Parent: #146 The Windows WIP app was added as an early working implementation and needs cleanup for maintainability. Potential scope: Split large Electron main/renderer files into smaller modules. Reduce duplicated config/model/provider logic where possible. Add clearer boundaries for auth, settings, process management, and Factory settings writes. Improve error handling and logging consistency. Keep behavior aligned with the macOS app where practical. Please avoid large rewrites unless they preserve the current GPT/Codex functionality.
Parent: #146 The Windows WIP app needs general UI and Windows UX polish before it is ready for broader use. Potential scope: Improve layout, spacing, states, and visual hierarchy. Make provider/account status easier to understand. Improve empty, loading, error, and success states. Review copy for clarity and Windows-specific expectations. Ensure the app remains usable at smaller window sizes and common display scaling settings. This issue is a good fit for contributors who want to help without needing to implement a provider integration first.
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 nikships/droidproxy, 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 nikships/droidproxy acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.0% were successfully merged into the primary branch.
nikships/droidproxy has a recorded first-timer success rate of 83.3%. Repositories ranked Welcoming 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 64.1 places nikships/droidproxy in the Welcoming tier.
The external pull request merge rate is 56.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nikships/droidproxy 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 nikships/droidproxy 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.