Modern weather widget for KDE Plasma 6 with multi-provider support and rich customization options.
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 85%
Response Time: 2h
First Timer Success: 86%
pnedyalkov91/advanced-weather-widget has a recorded first-timer success rate of 85.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pnedyalkov91/advanced-weather-widget respond to incoming external pull requests in approximately 2.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 70.3 places pnedyalkov91/advanced-weather-widget in the S tier.
The external contributor pull request merge rate for pnedyalkov91/advanced-weather-widget is 84.8%, based on public PR activity from non-core contributors.
pnedyalkov91/advanced-weather-widget currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in pnedyalkov91/advanced-weather-widget 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/pnedyalkov91/advanced-weather-widget?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~10 hours (38% approval). Keep your diff compact for rapid review.
Updating the plasmoid from 1.7.3 to 1.8.0 causes plasmashell to crash on my system. Manually downgrading back to 1.7.3 immediately allows plasmashell to start again. Attempting to start plasmashell via the terminal with 1.8.0 installed mentions an "address boundary error": KCrash: Attempting to start /usr/bin/plasmashell KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2 fish: Job 1, 'plasmashell' terminated by signal SIGSEGV (Address boundary error) I have updated through both Adaptifier (which prompts the user for a plasmashell restart after updating) and manually by removing the widget from my panel, re-downloading through the "Download new widgets" dialog, then re-adding the widget. The former allows the widget to be opened and location set, but appears to begin crashing plasmashell when I attempt to access notification settings.
Hello translators! (@TomfromBerlin , @PauloAlbqrq , @Vistaus , @PhvntxmX , @Katze-942, @rcspam, @herzane52 , @BroxiCoros , @Yo-oo , @Guokangz , @Zero-MF , @aldolat , @summoner001 , @l3monik , @Uni-Dev-Hub , @presire, @tonikarppi, @vitneum) 😊 I am planning to release Advanced Weather Widget v1.8.0 on October 6. The translation files have been updated with the new strings from the upcoming release. If you have time, please help update your language translation before the release date. There are two ways to contribute: Option 1: Create a PR Update your language .po file. Commit your changes. Open a PR to the main branch. Option 2: Attach the updated .po file here If you are not comfortable with Git/GitHub, you can simply send me the updated .po file here (archived as a .zip file), and I will integrate it into the project. You can see the files here: translations.zip Both methods are absolutely fine. Use whichever is easier for you 😊 Translation status for 1.8.0 (Updated: 02.10.202
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 pnedyalkov91/advanced-weather-widget, 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 pnedyalkov91/advanced-weather-widget acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 84.8% were successfully merged into the primary branch.
pnedyalkov91/advanced-weather-widget has a recorded first-timer success rate of 85.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. 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.3 places pnedyalkov91/advanced-weather-widget in the Elite tier.
The external pull request merge rate is 84.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pnedyalkov91/advanced-weather-widget 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 pnedyalkov91/advanced-weather-widget 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.