Bitfocus Companion enables the Elgato Stream Deck and other controllers to be a professional shotbox surface for an increasing amount of different presentation switchers, video playback software and broadcast equipment.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 83%
Response Time: 2d
First Timer Success: 86%
bitfocus/companion has a recorded first-timer success rate of 85.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bitfocus/companion respond to incoming external pull requests in approximately 44.3 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 66.2 places bitfocus/companion in the A tier.
The external contributor pull request merge rate for bitfocus/companion is 83.0%, based on public PR activity from non-core contributors.
bitfocus/companion currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Bitfocus Companion enables the Elgato Stream Deck and other controllers to be a professional shotbox surface for an increasing amount of different presentation switchers, video playback software and broadcast equipment.
Highly welcoming maintainers in bitfocus/companion. 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/bitfocus/companion?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~29 hours (96% approval). Large PRs (>500 lines) take ~213 hours (37% approval). Keep your diff compact for rapid review.
Make sure you're on the latest stable or beta build I have tested this on the latest stable or beta release Is this a bug in companion itself or a module? I believe this to be a bug in companion and not a specific module Is there an existing issue for this? I have searched the existing issues Describe the bug using the blink function with the same arguments across multiple buttons creates buttons blinking asynchronously. Steps To Reproduce In a fresh config Create a simple button with a boolean based feedback 0 == 0 && blink (1000) copy and paste the button one or more times buttons will not blink synchronously Expected Behavior Expected synchronous blinking using same arguments Environment (please complete the following information) - Companion Version: 4.3.4 - OS: Windows 11 - Browser: Edge Version 149.0.4022.98 (Official build) (64-bit) Additional context No response
Is this a feature relevant to companion itself, and not a specific module? I believe this to be a feature for companion, and is not specific to a module Is there an existing issue for this? I have searched for similiar existing issues Describe the feature Its common for me to be working with or setting up a reasonable number of companion connections to devices of the same type, where most of the config is identical between units (ie only the IP and Label differ). It would speed things up if an existing connection could be duplicated, and it would appear as a new connection instance with the same config and a new label - similar to the duplicate action button. I would expect the newly created connection would not inherit any actions or feedbacks from the reference connection, as that would complicate things greatly. A duplicate connection would appear immediately beneath the reference connection in the connection list (ie in the same collection if in one). Perhaps the same icon fr
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 bitfocus/companion, 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 bitfocus/companion acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.0% were successfully merged into the primary branch.
bitfocus/companion has a recorded first-timer success rate of 85.7%. 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 66.2 places bitfocus/companion in the Welcoming tier.
The external pull request merge rate is 83.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bitfocus/companion currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bitfocus/companion 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.