Collaborative cheatsheets for console commands 📚.
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 12%
Response Time: 5h
First Timer Success: 17%
tldr-pages/tldr has a recorded first-timer success rate of 16.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tldr-pages/tldr respond to incoming external pull requests in approximately 5.4 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 52.8 places tldr-pages/tldr in the B tier.
The external contributor pull request merge rate for tldr-pages/tldr is 12.0%, based on public PR activity from non-core contributors.
tldr-pages/tldr currently has 57 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in tldr-pages/tldr. Prompt code reviews with positive guidance for new contributors.
Discussions in tldr-pages/tldr 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/tldr-pages/tldr?utm_source=github&utm_medium=badge)
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 - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (15% approval). Large PRs (>500 lines) take ~26 hours (15% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Markdown.
7 community-maintained translations of MDN Web Docs in ES, FR, JA, KO, PT-BR, RU, and ZH, to learn and contribute in your native language.
The official source for MDN Web Docs content. Home to over 14,000 pages of documentation about HTML, CSS, JS, HTTP, Web APIs, and more.
⬆️ GitHub Actions uptime monitor & status page by @AnandChowdhary
Command description System control utility for Linux designed primarily for ASUS laptops Command details No response Documentation https://github.com/OpenGamingCollective/asusctl Platform Linux VCS repository link (e.g. GitHub, GitLab) No response Additional information No response
Command description Example: gtrash put file # equivalent of rm gtrash restore # open an interactive tui to restore files Command details No response Documentation No response Platform Common VCS repository link (e.g. GitHub, GitLab) https://github.com/umlx5h/gtrash Additional information
Command description show OpenCL platforms and devices Command details No response Documentation https://manned.org/clinfo Platform Common VCS repository link (e.g. GitHub, GitLab) No response Additional information No response
Command description tree-sitter Command details No response Documentation No response Platform Common VCS repository link (e.g. GitHub, GitLab) No response Additional information No response
Command description Different tools to manipulate the TTY Documentation No response Platform Common VCS repository link (e.g. GitHub, GitLab) No response Additional information No response Commands brltty colcrt #23606 deallocvt dumpkeys getkeycodes infocmp kbdinfo kbdrate kbd_mode loadunimap mapscrn nroff openvt psfaddtable psfgettable psfstriptable resizecons screendump setkeycodes setleds #23516 setlogcons setmetamode setvesablank setvtrgb setterm showconsolefont tset unicode_start unicode_stop
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 tldr-pages/tldr, 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 tldr-pages/tldr acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 12.0% were successfully merged into the primary branch.
tldr-pages/tldr has a recorded first-timer success rate of 16.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 52.8 places tldr-pages/tldr in the Solid tier.
The external pull request merge rate is 12.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tldr-pages/tldr currently has 57 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tldr-pages/tldr 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.