The open-source IT platform that comes with the workers. RMM + PSA in one system, with a governed AI operator built in.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 78%
Response Time: 1d
First Timer Success: 33%
LanternOps/breeze has a recorded first-timer success rate of 33.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LanternOps/breeze respond to incoming external pull requests in approximately 26.8 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 70.7 places LanternOps/breeze in the S tier.
The external contributor pull request merge rate for LanternOps/breeze is 78.0%, based on public PR activity from non-core contributors.
LanternOps/breeze currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The open-source IT platform that comes with the workers. RMM + PSA in one system, with a governed AI operator built in.
Collaborative maintainer environment in LanternOps/breeze. Reviews community pull requests with focus on project quality.
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/LanternOps/breeze?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (96% approval). Large PRs (>500 lines) take ~129 hours (35% approval). Keep your diff compact for rapid review.
Request From external tester (Wazo, 2026-04-11): Request for custom front-end plugin hooks on dashboard (widgets/extensions). Goal Allow partners / end-users to extend the Breeze dashboard with custom widgets or small front-end extensions without forking the web app. Think Grafana panel plugins or VS Code extensions — a constrained API surface where a third party can register a widget that shows up on the dashboard or a device page. Open questions Scope: dashboard widgets only? or also device-page tabs, settings sections, action menus? Isolation: iframe sandbox (safer, simpler) vs JS module loaded into the main bundle (richer, riskier) Distribution: uploaded per-partner in the UI, or config-file referenced URLs, or a registry? Data access: read-only via existing API with a scoped token, or a dedicated plugin API? Auth: plugins run as the logged-in user; need CSP / permission model This is a substantial design effort — not a quick add. Capturing here so it's tracked.
Request From external tester (Wazo, 2026-04-11): Add IT-admin "black screen" / privacy screen option during RDP sessions (similar to ScreenConnect behavior). Goal When an admin is remotely connected to a device, optionally blank the physical display so that a bystander at the device cannot see what the admin is doing. ScreenConnect and TeamViewer both offer this as a toggleable privacy option. Notes / open questions Windows: usually implemented via a driver-level blank display or by switching to a virtual display adapter; needs to survive UAC prompts and lock screen macOS: much harder — no supported API to blank a physical display while mirroring. Worth scoping separately Linux: probably skip for first pass Should be a per-session toggle surfaced in the viewer toolbar, not a global setting Should also optionally block local input (keyboard/mouse) on the target machine
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 LanternOps/breeze, 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 LanternOps/breeze acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.0% were successfully merged into the primary branch.
LanternOps/breeze has a recorded first-timer success rate of 33.3%. Repositories ranked Elite 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 70.7 places LanternOps/breeze in the Elite tier.
The external pull request merge rate is 78.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LanternOps/breeze 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 LanternOps/breeze 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.