Collaborative cheatsheets for console commands 📚.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 64%
Response Time: 5h
First Timer Success: 45%
tldr-pages/tldr has a recorded first-timer success rate of 45.0%. Repositories ranked S 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 4.5 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 71.4 places tldr-pages/tldr in the S tier.
The external contributor pull request merge rate for tldr-pages/tldr is 64.1%, based on public PR activity from non-core contributors.
tldr-pages/tldr currently has 44 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative cheatsheets for console commands 📚.
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)
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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (80% approval). Large PRs (>500 lines) take ~22 hours (29% approval). Keep your diff compact for rapid review.
Command description fsck has filesystem specific commands like fsck.ext4. I would assume these don't have uniform syntax similar to how mkfs doesn't have. If they do have a uniform syntax, the other commands should be made into aliases Documentation No response Platform Common VCS repository link (e.g. GitHub, GitLab) No response Additional information No response Commands fsck.btrfs fsck.ext2 fsck.ext4 fsck.fat fsck.fuseblk.bcachefs fsck.msdos fsck.bcachefs fsck.cramfs fsck.ext3 fsck.f2fs fsck.fuse.bcachefs fsck.minix fsck.vfat
Command description Disable a PPA and reverts to official packages Command details No response Documentation https://manned.org/ppa-purge Platform Common VCS repository link (e.g. GitHub, GitLab) No response Additional information No response
Command description Manage systemd boot passwords Command details No response Documentation https://github.com/kitsunyan/systemd-boot-password Platform Linux VCS repository link (e.g. GitHub, GitLab) No response Additional information https://wiki.archlinux.org/title/Systemd-boot#Kernel_parameters_editor_with_password_protection
Command description Tree-sitter is a parser generator tool and an incremental parsing library. It can build a concrete syntax tree for a source file and efficiently update the syntax tree as the source file is edited. Documentation https://tree-sitter.github.io/tree-sitter/ Platform Common VCS repository link (e.g. GitHub, GitLab) https://github.com/tree-sitter/tree-sitter Additional information No response Commands tree-sitter build (b as alias) tree-sitter complete (comp as alias) tree-sitter dump-languages (langs as alias) tree-sitter fuzz (f as alias) tree-sitter generate (gen and g as aliases) tree-sitter highlight (hi as alias) tree-sitter init (i as alias) tree-sitter init-config tree-sitter parse (p as alias) tree-sitter playground (play, pg, web-ui as aliases) tree-sitter query (q as alias) tree-sitter tags tree-sitter test (t as alias) tree-sitter version (publish as alias)
Command description Platform to track ML experiments Documentation https://mlflow.org/docs/latest/api_reference/cli.html Platform Common VCS repository link (e.g. GitHub, GitLab) https://github.com/mlflow/mlflow Additional information No response Commands main mlflow main commands mlflow server mlflow ui mlflow db mlflow run mlflow artifact mlflow model
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 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.1% were successfully merged into the primary branch.
tldr-pages/tldr has a recorded first-timer success rate of 45.0%. Repositories ranked Elite 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 71.4 places tldr-pages/tldr in the Elite tier.
The external pull request merge rate is 64.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tldr-pages/tldr currently has 44 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.