A maintained, feature-rich and performance oriented, neofetch like system information tool.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 46%
Response Time: 4h
First Timer Success: 100%
fastfetch-cli/fastfetch has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in fastfetch-cli/fastfetch respond to incoming external pull requests in approximately 4.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 61.3 places fastfetch-cli/fastfetch in the A tier.
The external contributor pull request merge rate for fastfetch-cli/fastfetch is 45.7%, based on public PR activity from non-core contributors.
fastfetch-cli/fastfetch currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in fastfetch-cli/fastfetch. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in fastfetch-cli/fastfetch focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/fastfetch-cli/fastfetch?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 Tuesday - Thursday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (57% approval). Large PRs (>500 lines) take ~20 hours (21% approval). Keep your diff compact for rapid review.
Hi everyone! Per #2503, module name localization is coming to fastfetch in the next release! Module display names (e.g., Memory, Disk, Terminal, etc.) will now be translated into multiple languages. Before this feature is shipped, I'd like the community's help to review and verify the translations, especially from native speakers. If you spot any awkward phrasing, incorrect terminology, or missing nuances, please let me know. You can preview the localized module names right now with: $ fastfetch -c all --key-language --show-errors This will render all available modules with their translated display names. $ fastfetch --help key-language This will print all languages supported currently. If you'd prefer to review the raw translation entries directly, all localized displayName fields can be extracted from the source tree with: $ rg -U --multiline-dotall '\.displayName = .*?\},' src/modules/*/*.c Thank you so much for helping make fastfetch more accessible to users around the world! Eve
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 fastfetch-cli/fastfetch, 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 fastfetch-cli/fastfetch acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 45.7% were successfully merged into the primary branch.
fastfetch-cli/fastfetch has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 61.3 places fastfetch-cli/fastfetch in the Welcoming tier.
The external pull request merge rate is 45.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, fastfetch-cli/fastfetch 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 fastfetch-cli/fastfetch 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.