Matterbridge plugin manager for Matter
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 53%
Response Time: -
First Timer Success: 33%
Luligu/matterbridge has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Luligu/matterbridge 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 56.6 places Luligu/matterbridge in the A tier.
The external contributor pull request merge rate for Luligu/matterbridge is 52.5%, based on public PR activity from non-core contributors.
Luligu/matterbridge does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Growing TypeScript project in Luligu/matterbridge 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/Luligu/matterbridge?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 10:00 UTC (10: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 ~16 hours (66% approval). Large PRs (>500 lines) take ~115 hours (24% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. When you configure matterbridge to use tls, you need to change the command line to matterbridge --ssl --frontend 443. If you do this, the docker container becomes unhealthy, as the health probe seem to try port 8283. Describe the solution you'd like Ideally mb_health should be able to figure out what port the frontend runs on. Describe alternatives you've considered I am able to work around the issue by changing my docker compose: healthcheck: test: ["CMD-SHELL", "mb_health https://localhost:443/health"] interval: 60s timeout: 10s retries: 5 start_period: 60s
Describe the bug Alexa cannot commission Matterbridge. The Alexa app first reports that Matterbridge cannot be detected and asks me to confirm that the device is in pairing mode. At the end of the flow it displays: Something went wrong. Error: GS014 in japanese. Matterbridge is actually discovered successfully, but Alexa stops sending commissioning commands immediately after Matterbridge responds to attestationRequest. The failsafe expires after the 80 seconds. I initially had Matterbridge commissioned to Google Home. I removed the Google Home fabric and retried with no registered fabrics, so Alexa was the first and only commissioner. The result was unchanged. To Reproduce Start Matterbridge with matterbridge --mdnsinterface eth0. Ensure that no existing fabrics are registered. Open a new commissioning window from the Matterbridge frontend. Scan the newly generated QR code with the Alexa app. Wait for commissioning to complete. Expected behavior Alexa pairing, and adds its fabric to
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 Luligu/matterbridge, 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 Luligu/matterbridge acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.5% were successfully merged into the primary branch.
Luligu/matterbridge has a recorded first-timer success rate of 33.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 56.6 places Luligu/matterbridge in the Welcoming tier.
The external pull request merge rate is 52.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Luligu/matterbridge 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 Luligu/matterbridge 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.