A GNOME Shell extension that lets you set any video as your lock screen background
C-Rank Grade: B (Solid) - 44/100
External PR Merge Rate: 25%
Response Time: 2d
First Timer Success: -
nick-redwill/LiveLockScreen 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 nick-redwill/LiveLockScreen respond to incoming external pull requests in approximately 42.2 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 44.2 places nick-redwill/LiveLockScreen in the B tier.
The external contributor pull request merge rate for nick-redwill/LiveLockScreen is 25.0%, based on public PR activity from non-core contributors.
nick-redwill/LiveLockScreen currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A GNOME Shell extension that lets you set any video as your lock screen background
Active maintainer team in nick-redwill/LiveLockScreen 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/nick-redwill/LiveLockScreen?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~27 hours (31% approval). Large PRs (>500 lines) take ~203 hours (15% approval). Keep your diff compact for rapid review.
Up front I do not think this is your bug, and I want to be clear about that before describing it. The extension's own memory behaviour is fine and its cleanup is correct — I checked. But it appears to be the trigger for a kernel-level leak in the NVIDIA driver, and you may want to know, and may be able to mitigate. Environment Live Lock Screen 3.2.0 (version 8) GNOME Shell 50.3, Wayland Fedora 44, kernel 7.1.4-200.fc44.x86_64 NVIDIA RTX 3090, driver 610.43.03 (open kernel module) GStreamer 1.28.5, gstreamer1-plugin-gtk4-0.15.2 32 GB RAM Also enabled: [email protected]@gmail.com (prevents screen blanking — likely relevant, see below) What happened Two system-wide OOM events, 19 processes killed by the kernel, including the audio server, input method, file manager, and terminal. The memory was not held by the extension or its player process. At the moment of the second OOM, the player process (gjs, PID 15373) held 374 kB of anonymous memory. Every process on the system combined held
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 nick-redwill/LiveLockScreen, 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 nick-redwill/LiveLockScreen acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.0% were successfully merged into the primary branch.
nick-redwill/LiveLockScreen 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 44.2 places nick-redwill/LiveLockScreen in the Solid tier.
The external pull request merge rate is 25.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nick-redwill/LiveLockScreen 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 nick-redwill/LiveLockScreen 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.