tldr-pages/tldr

Collaborative cheatsheets for console commands 📚.

View on GitHub ↗Jump to charts ↓Open shareable report →

tldr-pages/tldr has 63k+ stars and 5k+ forks on GitHub, is written in Markdown, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 49 minutes ago
Type:Curated List / Learning ResourceCategory(s):Cheatsheets, Checklists & Best PracticesLearning & Resources
Added to GitGenius on August 30th, 2026
Created on December 8th, 2013
Open Issues & Pull Requests: 275 (+0)
GitHub issues: Enabled
Number of forks: 5,473
Total Stargazers: 63,978 (+0)
Total Subscribers: 414 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.8 hours
Mean response time: 51.3 days
90th percentile: 104.0 days
Tracked items: 599

Maintainer activity

12 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 13% of issues opened in the past year have never received a reply. Only 22% of open issues come from outside the core team — the tracker reads mainly as internal planning. Work labelled "archive" is answered fastest, typically in under an hour, while "new command" waits about 7 days. 59% of tracked open issues have had no activity in three months. 69% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 195
New in 7 days: 5
Closed in 7 days: 0
Avg open age: 687 days
Stale 30+ days: 169
Stale 90+ days: 147

Recent activity

Opened in 7 days: 5
Closed in 7 days: 0
Comments in 7 days: 3
Events in 7 days: 15

Top labels

  • help wanted (457)
  • new command (336)
  • let's document (137)
  • page edit (73)
  • community (61)
  • good first issue (49)
  • translation (32)
  • decision (27)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

tldr-pages is a collaborative cheatsheet collection that provides simplified, example-focused help pages for command-line tools across multiple operating systems.

The project addresses the gap between the complexity of traditional man pages and the practical needs of command-line users. Rather than exhaustive technical documentation, tldr-pages focuses on real-world usage examples for common commands. Each page presents straightforward examples with clear explanations, making it easier for both newcomers and experienced users to quickly find how to accomplish specific tasks with tools like tar, lsof, and countless others. The collection covers command-line tools across UNIX, Linux, macOS, FreeBSD, NetBSD, OpenBSD, SunOS, Android, Windows, Cisco IOS, and DOS.

Developers should adopt this tool if they frequently work with command-line interfaces and want faster access to practical examples than man pages typically provide. It suits anyone from beginners learning the command-line to experienced users who need quick reference material. The project offers multiple ways to access the content: official clients in Python, Rust, and Node.js; a web-based client with offline support; and PDF versions for offline reading. The README does not compare the tool to alternatives, so no comparative assessment is warranted.

The project maintains an active community contribution model with regular updates to its command documentation. Development activity shows consistent engagement with the repository, indicating ongoing maintenance and expansion of the cheatsheet collection. The project welcomes contributions from the community, suggesting a collaborative approach to keeping the documentation current and comprehensive.