Timewarrior - Commandline Time Tracking and Reporting
1.6k
Stars
115
Forks
125
Open issues
30
Contributors
AI Analysis
Timewarrior is a command-line time tracking utility that combines simple stopwatch functionality with calendar-based backfill and flexible reporting. It serves individual users and teams who need portable, scriptable time tracking without GUI dependencies. This tool is best suited for developers, technical professionals, and organizations comfortable with CLI workflows; it is not for users who require graphical interfaces or cloud-based time management platforms.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Lightweight CLI time tracker with calendar backfill, mature but modest adoption in niche community
Timewarrior is a command-line time tracking utility offering stopwatch features, calendar-based time entry, and reporting. Built by the Gothenburg Bit Factory (creators of Taskwarrior), it targets users who prefer terminal-based workflows and need flexible time logging without heavy web infrastructure. Real-world adoption appears concentrated in Taskwarrior-adjacent communities and power users; adoption numbers not publicly verified but distribution through major Linux package managers suggests modest but sustained user base.
Created in February 2018 by Gothenburg Bit Factory as a companion to Taskwarrior, positioned to fill the time tracking gap in their task management ecosystem. Evolved as a deliberate, focused project rather than a reaction to market dominance by other trackers.
Growth has been steady but slow: 1,630 GitHub stars across ~8 years suggests stable niche appeal rather than explosive adoption. Last 7 days show only 7 new stars, typical of mature project serving established audience. Packaged across Homebrew, Debian, Fedora, Ubuntu, and Arch Linux indicates institutional acceptance. Recent activity (push 2026-07-04) confirms ongoing maintenance rather than stagnation.
Adoption not verified through explicit case studies or production user announcements in README. However, presence in five major Linux distributions (Homebrew, Debian testing, Fedora, Ubuntu, Arch) and macOS Homebrew download metrics visible suggests real installations. Reddit/Discord community existence indicates active user base, but scale unknown. GitHub discussions badge shows engagement pathway but volume not quantified.
Written in C++ with C++17 standard, built on CMake. README indicates portable design with cross-platform packaging support. Likely uses event-driven time logging stored in local data files (typical for Gothenburg Bit Factory tools), though specific storage format not documented in README. Test harness present (Python-based test suite mentioned) suggesting structured validation approach.
Build process includes optional test suite execution via `cmake --build _build --target timew_test`, indicating test infrastructure exists, but coverage percentage and scope not documented in README.
Actively maintained as of July 2026 (last push 2026-07-04, 2 days ago from analysis date). Release badges and milestone tracking visible in README, suggesting planned feature work. Contributors badge indicates multi-person maintenance. No evidence of burnout or slow-response issues in provided metadata.
ADOPT IF: you use Taskwarrior, prefer terminal-only workflows, need offline-first time logging, and want a well-maintained project with institutional backing. AVOID IF: you need team collaboration, cloud sync, automatic activity detection, mobile access, or integration with mainstream accounting software. MONITOR IF: you're a solo freelancer evaluating lightweight CLI tools—adoption is real but concentrated in specific communities; test fit in your personal workflow before long-term commitment.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
4/10
- Adoption concentrated in Gothenburg Bit Factory ecosystem; limited evidence of independent uptake outside Taskwarrior users
- C++ codebase may limit contributor pool compared to Python/JavaScript alternatives; 115 forks vs 1,630 stars suggests low fork-to-star ratio indicating modest community code contribution
- Single-user, offline-only design prevents scaling to team workflows where competing projects have advantages
- Documentation and community channels shared with Taskwarrior; Timewarrior-specific issues may get less visibility
- No cloud sync, mobile client, or API documented; tight coupling to local machine limits modern workflow integration patterns
Likely to remain a stable, well-maintained but slow-growth project serving power users and Taskwarrior ecosystem members. May see modest growth as CLI tool renaissance continues, but unlikely to challenge web-based or automatic tracking tools. Maintenance will probably persist given Gothenburg Bit Factory's commitment to long-term open source stewardship.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://timewarrior.net
- Language
- C++
- License
- MIT
- Last updated
- 7d ago
- Created
- 103mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Similar repos
GothenburgBitFactory/taskwarrior
Taskwarrior is a command-line task management utility designed for...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
GothenburgBitFactory/timewarrior
this
|
1.6k | +5 | C++ | 8/10 | 7d ago |
|
GothenburgBitFactory/taskwarrior
|
5.9k | — | C++ | 8/10 | 2d ago |
 vladelaina/Catime
|
4.4k | — | C | 7/10 | 2w ago |
 ttscoff/doing
|
1.3k | — | Ruby | 7/10 | 1w ago |
 solidtime-io/solidtime
|
8.8k | — | PHP | 7/10 | 16h ago |
 ActivityWatch/activitywatch
|
18.2k | — | Python | 8/10 | 4d ago |
Parent ecosystem project for task management; Timewarrior complements rather than competes. Taskwarrior users form natural adoption funnel for Timewarrior.
Automatic activity tracking via desktop client; Timewarrior is manual time logging. Different use case: ActivityWatch for passive surveillance, Timewarrior for deliberate time allocation.
Web/cloud-based time tracking with team features; Timewarrior is CLI-only, local-first, single-user focused. Different deployment model.
Similar niche (CLI time tracking in Ruby); Timewarrior has higher stars, broader packaging support, stronger institutional backing via Gothenburg Bit Factory.
C-based time tracking; Timewarrior in C++. Feature parity not clear from metadata, but Timewarrior's broader distribution suggests more mature release cycle.
