Pocketwatch
Pocketwatch is a minimal, self-hosted time tracker for freelancers and the self-employed that records timed entries, supports editing and filtering, exports…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
44/100 Fair
- Maintained
- 68last commit 95 days ago
- Popular
- 3029 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 201 serious finding, 1 minor, tests
Based on 4 of 5 factors.
Security check: 1 serious finding
- Uses dompurify 3.4.13, which has a known critical vulnerability (npm)
Automated checks on commit 3b68a3d, 15 Nov 2026. Not an audit.
Availability: platform listings confirmed today, links checked 19 days ago
- GitHub stars
- 29
- Open issues
- 0
- Last commit
- 2026-08-18
- Latest release
- v1.1.0
- License
- MIT
- Activity
- stale
Checked 6 days ago - source: GitHub (winnicodes/pocketwatch)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Pick a Windows event source to watch Run PockETWatcher.exe from its folder with -provider set to a source like Microsoft-Windows-TCPIP, or with its GUID (a long unique ID that identifies the source). Without choosing a provider, the tool has no event stream to monitor. source
- Save captured events to a file Add -output tcpip_events.json to write captured events to a file on disk. This keeps the data available after the terminal session ends instead of losing it when the screen scrolls. source
- Filter by Event IDs to reduce noise Add -eventIds 1033 or a comma-separated list like -eventIds 1033,1034 to capture only the event types you need. Without filtering, a provider can produce too many events and make the useful data hard to spot. source
- Security The API has no built-in authentication, so keep Pocketwatch on a trusted LAN or behind a reverse proxy that handles authentication. source
- Installation Runs as a single Docker container. Start it with docker compose up -d. Works on a NAS or laptop, with no database required. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does Pocketwatch need a database to store time entries?
No. It stores all data in two local JSON files.
Can I export time tracking reports from Pocketwatch?
Yes. It supports exporting PDF or CSV reports.
Do I need to create an account to use Pocketwatch?
No. It is a self-hosted app that stores data locally without an account.
Can I edit or filter tracked entries in Pocketwatch?
Yes. It records timed entries and supports editing and filtering.
Answers sourced from github.com
Community
- Reddit (reddit)
Collected 49 days ago - public community threads