Concerto Digital Signage System
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 50%
Response Time: 2d
First Timer Success: -
concerto/concerto has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in concerto/concerto respond to incoming external pull requests in approximately 37.9 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 46.3 places concerto/concerto in the B tier.
The external contributor pull request merge rate for concerto/concerto is 50.0%, based on public PR activity from non-core contributors.
concerto/concerto currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in concerto/concerto 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/concerto/concerto?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (62% approval). Large PRs (>500 lines) take ~182 hours (22% approval). Keep your diff compact for rapid review.
There is a slider which allows screen admins to control the relative frequency of a subscription. The slider appears on the page without any context - we should add some labels / description / additional text to clarify what it does. (reported by @bigG114 in #1763)
Background Both `ConcertoGraphic` and the video components (`ConcertoYoutubeVideo`, `ConcertoTiktokVideo`, `ConcertoVimeoVideo`) apply `boxStyle` (border, padding, box-shadow, outline — see `splitFieldStyle.js`) to a wrapper element that fills the entire field rectangle. When the content's aspect ratio doesn't match the field's, the visible content is letterboxed/pillarboxed inside that border, so the border outlines the field rather than hugging the visible content. For example, a small white border around a flyer is meant to make the graphic stand out against the template background. Today, that border instead frames the whole field with empty space between the border and the visible image. Why this isn't fixed in #1780 #1780 ships the "smaller graphics scale up to fill their position" change requested in #1779 using `width: 100%; height: 100%; object-fit: contain`. We tried two patches that would also make the graphic border hug the rendered image: Pure CSS via `width: 100%; heig
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 concerto/concerto, 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 concerto/concerto acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
concerto/concerto has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 46.3 places concerto/concerto in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, concerto/concerto 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 concerto/concerto 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.