TimeScribe ships with auto-update disabled and a Windows build the recipe calls coming soon
Modern & private time tracking for macOS & Windows. No cloud, no registration, no paywall. Just download and track your work hours 100% offline.
At a glance
- What is it?
- TimeScribe is a desktop time tracker for macOS and Windows, built on Laravel, Vue, and NativePHP, that keeps its records on the machine it runs on. Its configuration tells a more candid story than its feature list: the updater is off by default, the PDF exporter cannot lay out right-to-left text, and the source recipe marks its own Windows target unfinished.
- Who is it for?
- TimeScribe suits a freelancer or a remote worker who wants billable hours on their own machine and is willing to read the source. It does not suit a team that needs shared accounts, server-side records, or invoices in right-to-left scripts.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 12 days ago.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- WINBIGFOX/TimeScribe936 ★ · +40
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| WINBIGFOX/TimeScribe | 896 | 936 |
40 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The source recipe calls its own Windows target coming soon
Building from source is the only place the whole toolchain appears, and it is worth reading as written:
# Clone the repo
git clone https://github.com/WINBIGFOX/timescribe.git
cd timescribe
# Install dependencies
composer install
npm install
# Copy the example environment file
cp .env.example .env
# Generate an application key
php artisan key:generate
# Build for macOS
npm run build
php artisan native:build mac
# Build for Windows (coming soon or adjust accordingly)
php artisan native:build winTwo things stand out. This path needs Node, Composer, and a PHP CLI on the machine, which is a different commitment from downloading an installer. And the comment on the final step calls the Windows target coming soon, or something to adjust, even though the project publishes TimeScribe-setup.exe and a WinGet package:
winget install WINBIGFOX.TimeScribeSo the Windows binaries handed to users come from a path the recipe itself does not vouch for. For anyone reproducing the project from a clean checkout, the documented build is macOS in practice.
Channel identifiers drift apart across those same options. The Homebrew cask is `timescribe`, the WinGet package is `WINBIGFOX.TimeScribe`, the release asset is `TimeScribe-setup.exe`, and the clone URL is spelled `timescribe.git` in lowercase. Anyone scripting an install across both platforms needs all four spellings rather than one name.
Auto updates ship disabled in the example environment
The feature list closes on a promise that the app is always up to date. The example environment is less enthusiastic. NATIVEPHP_UPDATER_ENABLED is set to false and NATIVEPHP_UPDATER_PROVIDER is left empty, sitting beside a row of blank packager fields: NATIVEPHP_APP_VERSION, NATIVEPHP_APP_ID, NATIVEPHP_APP_AUTHOR, NATIVEPHP_APP_DESCRIPTION, and NATIVEPHP_APP_WEBSITE. Blank identity values make sense for a project that serves its artifacts from its own site rather than an app store, and the site does split downloads per platform, a Windows installer plus separate Apple Silicon and Intel disk images. The result is that a build produced from the documented recipe starts with the updater off, and a provider has to be supplied before any user receives a patch. Release cadence is fast regardless: v1.16.0 on 2026-09-15, then v1.17.0 and v1.17.1 on the same day, 2026-09-21.
Right-to-left layout stops at the window, not at the PDF
Ten languages ship alongside the code, from Arabic and Danish through Hebrew, Italian, Polish, Brazilian Portuguese, and Chinese, with English and French each carrying region variants. Arabic and Hebrew are singled out as receiving right-to-left application layouts. The next sentence gives the claim back for exports: PDF output still goes through Dompdf, whose complex text layout support is incomplete, so right-to-left text in a PDF needs a separate rendering solution. The example environment pins that same library through LARAVEL_PDF_DRIVER='dompdf', quotes included, so the driver is configurable in principle and shipped pointed at the renderer with the known gap. Export is offered as PDF, Excel, and CSV. The practical split for an Arabic or Hebrew user is that the day view and project screens mirror correctly while the file sent to a client does not, and that file is the one that matters for billing.
Analytics and crash reporting are compiled in but keyed off
The no-tracking claim rests on configuration rather than on absence of code. GOOGLE_ANALYTICS_ID and NIGHTWATCH_TOKEN are both blank in the example environment, and the Nightwatch block sets NIGHTWATCH_IGNORE_QUERIES, NIGHTWATCH_IGNORE_OUTGOING_REQUESTS, and a NIGHTWATCH_REQUEST_SAMPLE_RATE of 0.05. Telemetry is therefore a supported path held switched off by leaving keys empty. Two reporting clients are still in the dependency list: @sentry/vite-plugin in the build and @sentry/vue in the browser bundle, and the example environment carries no Sentry key at all. Mail is redirected to the log with MAIL_MAILER=log, consistent with sending nothing. Two further defaults are worth reading before trusting a shipped build on a shared machine: APP_DEBUG is true and LOG_LEVEL is debug.
The deep-link surface is three verbs with nowhere to put a project
Control from outside the app is a documented and deliberately small API. Three links are given, and the scheme itself is configurable through NATIVEPHP_DEEPLINK_SCHEME=timescribe:
timescribe://start/work
timescribe://start/break
timescribe://stopThey work on macOS and Windows once the app is installed, and the named callers are Shortcuts, Alfred, Raycast, AutoHotkey, or a custom script. What the list does not include is any way to name a project, attach a note, or pass a rate. For a tool that tracks projects with descriptions, hourly rates, and billing calculations, that gap lands somewhere specific: a shortcut can stop the timer on a client but cannot start one against the right project, so the person still has to reach for the window at the moment work begins. Automatic start and pause, driven by screen and idle status, cover part of that gap but not the project assignment. The app also reads screen time to split observed application use into work and distraction, which is a second, passive source of the same classification and cannot be corrected from a link either.
Two ESLint configs share a root and the lint script reads one folder
The repository carries both .eslintrc.cjs and eslint.config.js, which is the legacy and the flat configuration format living side by side. The npm scripts resolve the ambiguity by narrowing scope: lint runs eslint over resources/js only, while style and style:fix run prettier across the whole tree. Four more tool configs sit next to them, pint.json for PHP style, rector.php for automated refactoring, phpunit.xml for tests, and patches.lock.json recording patched dependencies. Two agent-oriented directories, .agents and .junie, sit beside AGENTS.md at the top level, and .nvmrc pins the Node version for the build. Note that the published inventory of dependencies is incomplete in both places it appears: the dependencies object in package.json ends partway through a laravel-prefixed entry, and the stack list ends at the desktop runtime line naming NativePHP.
Every storage default points at the local machine
The offline claim is backed by concrete choices in the example environment. DB_CONNECTION is sqlite, with the MySQL host, port, database, username, and password lines still present but commented out. SESSION_DRIVER and QUEUE_CONNECTION are both database, so those land in the same file, CACHE_STORE is file, and FILESYSTEM_DISK is local. There is no service to sign up for and no key to obtain before tracking begins, and the project is GPL-3.0, so an auditor can read what touches the data.
The stack behind those choices is a Laravel application with a NativePHP desktop runtime and a Vue frontend, since the build script is vue-tsc followed by vite build and the client side is served through Inertia. A few environment values are desktop-specific rather than server-shaped: PHP_CLI_SERVER_WORKERS is set to 4, APP_MAINTENANCE_DRIVER is file rather than database, and session lifetime is 120. Two defaults suit a local install but would be wrong to copy into anything reachable from a network: SESSION_ENCRYPT is false, and APP_DEBUG is true with LOG_LEVEL set to debug.
Editorial conclusion
TimeScribe suits a freelancer or a remote worker who wants billable hours on their own machine and is willing to read the source. It does not suit a team that needs shared accounts, server-side records, or invoices in right-to-left scripts. Three things to confirm before relying on it: whether the build you install has the updater switched on, since the example environment disables it; whether your export path avoids PDF for Arabic or Hebrew text, since Dompdf is the shipped renderer; and whether the Windows binary you get matches what the source recipe produces, since that recipe marks its own Windows target as unfinished. The code is GPL-3.0 and releases move quickly, with v1.17.1 published on 2026-09-21, so both reading and re-checking are cheap.
Frequently asked questions
Does TimeScribe need an account, and does anything leave my machine?
No account and no cloud service; the data stays on the device. Analytics and usage reporting are configured but switched off by leaving GOOGLE_ANALYTICS_ID and NIGHTWATCH_TOKEN empty, mail goes to the log, and the updater is disabled by default in the example environment.
How do I install TimeScribe on macOS or Windows?
From the latest release as TimeScribe.dmg on macOS, with separate Apple Silicon and Intel downloads, or TimeScribe-setup.exe on Windows. The package managers are `brew install timescribe` on macOS and `winget install WINBIGFOX.TimeScribe` on Windows.
Can TimeScribe export timesheets in Arabic or Hebrew?
The application layout is right-to-left for Arabic and Hebrew, but PDF export still uses Dompdf, whose complex text layout support is incomplete, so right-to-left text in a PDF requires a separate rendering solution. Excel and CSV export are offered alongside PDF.
Can I start and stop TimeScribe timers from another app?
Yes, through a deep-link API with three actions: timescribe://start/work, timescribe://start/break, and timescribe://stop. The scheme is configurable and works on both platforms once the app is installed, but no documented link form carries a project, note, or rate.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/winbigfox-timescribe)Star history chart for your README
[](https://hysenlabs.com/projects/winbigfox-timescribe)Was this useful?