DEV Community: livrasand

The Best Open Source WakaTime Alternatives in 2026 🚀

livrasand — Tue, 07 Jul 2026 19:12:26 +0000

As developers, we love to measure everything. How much time did we spend on that CSS bug? Which language dominated our week? WakaTime has been the standard for years, but in 2026, the conversation has shifted. Privacy and data sovereignty are no longer optional.

If you're looking for an alternative that gives you complete control over your coding metrics, here are the best open-source options available today.

Why look for a WakaTime alternative?

WakaTime is excellent, but it's a proprietary and centralized platform. Your work habits, schedules, and projects live on its servers. For many, this represents a privacy risk or simply a lack of control over their own data.

Here we compare the four tools that are leading the shift toward more open developer analytics.

1. WakaTime (The current standard)

It's the "paid" and closed option.

Pros: Works out of the box, has extensions for almost everything.
Cons: Closed source, your data is on their servers, limitations in the free plan.

2. ActivityWatch (Local-first)

If you're looking for absolute privacy, this is the tool for you.

How it works: It logs your activity 100% locally on your machine.
Key difference: You don't need a server. It's ideal if you don't mind not having a global leaderboard or easy remote access.

3. Wakapi (The minimalist Go clone)

Wakapi is an open-source implementation compatible with the WakaTime API, written in Go.

Key difference: It's perfect for self-hosting. You can use the same WakaTime extensions but point them to your own server.
Best: Very lightweight and resource-efficient.

4. CodeTrackr (The next generation in Rust)

CodeTrackr is the newest and most ambitious alternative on this list. Designed from the ground up with a focus on community and extensibility.

What makes CodeTrackr different?

Unlike others, CodeTrackr doesn't just track time; it's an infrastructure you own and can extend.

Modern Stack: Written in Rust (Axum) for extreme speed and memory safety.
Privacy in Sweden: The official service is hosted in Sweden, under strict data protection laws.
Plugin System: Allows you to add panels and widgets to the dashboard using pure JavaScript (running in a secure QuickJS sandbox).
Anonymous Accounts: You can track your time without even giving your real name.

Technical Comparison at a Glance

Feature	WakaTime	ActivityWatch	Wakapi	CodeTrackr
Open Source	No	Yes	Yes	Yes (AGPL-3.0)
Self-Hosted	No	Yes (Local)	Yes	Yes (Docker/Rust)
Language	-	Python/Rust	Go	Rust
Plugins/Extensibility	Limited	No	No	Yes (QuickJS)
Free Cloud	Limited	N/A	Yes	Yes (Always)

How to Get Started with CodeTrackr (Quick Start)

If you want to try the latest option, setting up CodeTrackr is ridiculously easy. Its official extensions support VS Code, Cursor, Windsurf, Neovim, and many more.

Create an account (you can use an anonymous account).
Install the extension in your favorite IDE.
Configure your API key and you're all set.

What I like most about this project is its transparency: 77% of the code was AI-assisted (Claude) under human supervision, demonstrating that by 2026, the best tools will be built by humans with AI superpowers.

Conclusion: Which one to choose?

Choose ActivityWatch if you want 100% local.
Choose Wakapi if you want something very lightweight in Go.
Choose CodeTrackr if you're looking for a modern, extensible platform written in Rust that prioritizes your privacy above all else.

Frequently Asked Questions (FAQ)

Is CodeTrackr really free forever?
Yes, the core is open source and the official cloud plan remains free.

Can I migrate my WakaTime data?
Most of these tools allow data export, and CodeTrackr is working on a native import integration.

What if my company prohibits tracking?
That's where CodeTrackr or Wakapi's self-hosting shines; you own the database, and no one else has access.

Did you find this comparison helpful? If you'd like to support the development of privacy tools, don't forget to visit the CodeTrackr repo (https://github.com/livrasand/CodeTrackr) and leave a star rating! ⭐️

Your Git Commit History Is More Public Than You Think 🕵️‍♂️

livrasand — Wed, 01 Jul 2026 15:52:13 +0000

In the open source world, we often say that "your code is your resume." However, what many developers forget is that every time they run a git push, they're handing over much more than just lines of code. They're delivering a permanent digital trail that can be tracked, analyzed, and used against them years later.

This article is an educational guide about privacy in Git and how the metadata you generate every second can compromise your security and your professional future.

The command that reveals your "naked identity"

If you want to see exactly what you're sharing with the world, open your terminal in any repository and run the following command:

git log --format=fuller

Unlike the standard log, the fuller format breaks down the complete anatomy of your contributions. This is where most developers are shocked to see what they're actually leaking:

1. Name and Email (Direct Exposure)

Git stores your user.name and user.email locally in every commit. This data:

Is harvested by spam bots for marketing databases.
Allows recruiters to map all your historical activity, even on projects you no longer represent.
Exposes you to doxxing attacks if you contribute to controversial projects.

2. Dates and Timestamps (Time Analysis)

Git not only saves the day, but also the exact second and time zone of the authorship and commit. This allows you to create an activity pattern:

What time do you usually code?
Are you working on personal projects during office hours?
What geographical area are you actually in?

3. File Patterns and Metadata

In addition to text, if you upload binaries (PDFs or images), these usually contain EXIF metadata (GPS coordinates, camera model, etc.) that Git doesn't clean up by default.

The Problem with "Permanent Logs"

GitHub is, by design, an accountability platform, not a privacy one. Once a commit enters the public history, deleting it is extremely difficult and often pointless if the repository has already been cloned or indexed by third-party services.

This creates a HR liability risk: a contribution made today could be judged in a completely different context five years from now.

The Solution: Enter GitGost 👻

For those times when you want your code to speak for itself, without any identifying tags, there's GitGost.

GitGost is an open-source proxy designed to offer strong anonymity for your contributions. It requires no accounts, tokens, or complex browser configurations.

How Does It Work?

Instead of uploading code directly to GitHub with your identity, you submit it through GitGost. The server:

Clean all your metadata (name, email, timestamps).
Replace the authorship with the neutral bot @gitgost-anonymous.
Automatically create a Pull Request in the target repository.

Quick Workflow:

1. Add the GitGost remote

git remote add gost https://gitgost.fly.dev/owner/repo

2. Push your branch (without logs or tokens)

git push gost main

Is this just for "hackers"?

Absolutely not. Anonymity in open source has legitimate and ethical use cases:

Employees who want to fix bugs in competing tools without violating exclusivity clauses.
Activists and journalists in censored regions who need to contribute to privacy tools without personal risk.
Developers who simply want to fix an annoying typo without it defining their public profile forever.

Conclusion: Be a ghost, fix the internet

Privacy isn't about hiding something bad; it's about having the power to choose what you share. If you believe developers deserve the right to contribute without being permanently profiled, it's time to start auditing your metadata.

Frequently Asked Questions (FAQ)

Can I contribute to GitHub anonymously?
Yes. Tools like gitGost allow you to create anonymous pull requests without exposing your GitHub account, name, or email address.

Does GitHub expose my email address?
Potentially, yes. Git commits contain author metadata (email) unless they are specifically anonymized before being published.

Is anonymous open source contribution legitimate?
Yes. Many developers use anonymity to avoid harassment, workplace conflicts, political risks, or unwanted profiling by recruiters.

If you're passionate about privacy, check out the gitGost repository and leave a star to support the right to anonymity in development.

How to Contribute to GitHub Anonymously in 2026

livrasand — Mon, 29 Jun 2026 17:23:00 +0000

In the world of open source, your code is your resume. But sometimes, you want the code to speak for itself without attaching your legal name, your company’s email, or a permanent timestamp to it. Whether it's to avoid HR liabilities, contribute to controversial projects, or simply stay private, contributing anonymously to GitHub is a skill every modern developer should have.

In this guide, we’ll explore why your current Git workflow is "leaking" data and how tools like gitGost are changing the game for privacy in 2026.

Why GitHub Contributions are Permanent

GitHub is designed for accountability, not anonymity. By default, every time you push code, you are creating a permanent public record. This "contribution graph" can become a liability over time:

HR and Recruiters: Your activity can be used to judge your "productivity" or interests during hiring processes.
Email Harvesting: Spammers and scrapers crawl commit histories to build databases of active developer emails.
Political Risks: In some jurisdictions, contributing to specific tools or repositories can lead to real-world consequences.

What Information Your Git Commits Actually Expose

If you run git log --format=fuller on any of your repositories, you’ll see the "naked" truth. A standard Git commit exposes:

Full Name and Email: Your local user.name and user.email settings.
Timestamps: When exactly you authored the code (often revealing your timezone and work habits).
Metadata: Hidden info in binary files (like images or PDFs) through EXIF data.
Identity Correlation: Passive metadata that links your personal GitHub account to every Pull Request you open.

Anonymous Accounts vs. True Anonymity

Many developers think creating a "burner" GitHub account is enough. It's not.
Secondary accounts still carry metadata in the commits. Furthermore, GitHub’s own platform telemetry can often link your accounts via IP addresses or browser fingerprints. True anonymity requires stripping all identifying metadata before the code even reaches a remote server.

The Solution: Using gitGost

gitGost is an open-source proxy designed for "strong anonymity" in Git contributions. It allows you to contribute to any public repository without an account, a token, or metadata.

How to use gitGost (The One-Command Setup)

The beauty of gitGost is that it requires no browser extensions or complex setups. Just add a remote and push:

Add the Gost remote:

git remote add gost https://gitgost.fly.dev/owner/repo

Push your changes:
```
git push gost your-branch
```

What happens next?
gitGost's neutral bot, @gitgost-anonymous, creates a Pull Request on your behalf. Your name, email, and timestamps are stripped and replaced with generic metadata. Your commit message automatically becomes the PR description, so make sure to provide context there.

Enhanced Privacy: Using Tor and Stripping Metadata

For developers who need a higher level of protection (protecting against IP identification), combining gitGost with Tor is the gold standard.

1. Hiding your IP with `torsocks`

gitGost strips your commit data, but the server still sees your IP. To mask it, use torsocks:

# Install on Linux
sudo apt install torsocks
# Push through Tor
torsocks git push gost main

Note: Tor is slower due to its three-layer encryption, so expect the push to take a few minutes.

2. Stripping Binary Metadata with `exiftool`

If your contribution includes images or PDFs, they might contain GPS coordinates or device info. Use exiftool before committing:

exiftool -all= -overwrite_original image.png

The gitGost Threat Model

Anonymity is never absolute. It’s important to understand what gitGost protects you against and what it doesn't:

It protects against: Public exposure of name/email, direct association with your personal account, and passive metadata collection by recruiters or scrapers.
It does NOT protect against: Stylometry (code style analysis), advanced temporal correlation, or nation-states with infrastructure-level access.

Explicit Assumption: You must use a trustworthy network (VPN/Tor) and avoid mixing anonymous and personal contributions in the same repository to stay safe.

Conclusion: Be a Ghost, Fix the Internet

Privacy is a right, even for developers. gitGost was built for responsible, good-faith contributions where identity is unnecessary. It's about giving you the choice to "disappear" after you've made the internet a little better.

Frequently Asked Questions (FAQ)

Can I contribute to GitHub anonymously?
Yes. Tools like gitGost allow you to create anonymous pull requests without exposing your account or metadata.

Does GitHub expose my email address?
Yes, unless you specifically use a proxy or anonymize your Git metadata.

Is anonymous contribution legitimate?
Absolutely. It is used by activists, journalists, and developers wanting to avoid profiling or employer conflicts.

If you believe developers deserve the right to privacy, consider starring the gitGost repository.

DEV Community: livrasand

The Best Open Source WakaTime Alternatives in 2026 🚀

Why look for a WakaTime alternative?

1. WakaTime (The current standard)

2. ActivityWatch (Local-first)

3. Wakapi (The minimalist Go clone)

4. CodeTrackr (The next generation in Rust)

What makes CodeTrackr different?

Technical Comparison at a Glance

How to Get Started with CodeTrackr (Quick Start)

Conclusion: Which one to choose?

Frequently Asked Questions (FAQ)

Your Git Commit History Is More Public Than You Think 🕵️‍♂️

The command that reveals your "naked identity"

1. Name and Email (Direct Exposure)

2. Dates and Timestamps (Time Analysis)

3. File Patterns and Metadata

The Problem with "Permanent Logs"

The Solution: Enter GitGost 👻

How Does It Work?

Quick Workflow:

1. Add the GitGost remote

2. Push your branch (without logs or tokens)

Is this just for "hackers"?

Conclusion: Be a ghost, fix the internet

Frequently Asked Questions (FAQ)

How to Contribute to GitHub Anonymously in 2026

Why GitHub Contributions are Permanent

What Information Your Git Commits Actually Expose

Anonymous Accounts vs. True Anonymity

The Solution: Using gitGost

How to use gitGost (The One-Command Setup)

Enhanced Privacy: Using Tor and Stripping Metadata

1. Hiding your IP with torsocks

2. Stripping Binary Metadata with exiftool

The gitGost Threat Model

Conclusion: Be a Ghost, Fix the Internet

Frequently Asked Questions (FAQ)

1. Hiding your IP with `torsocks`

2. Stripping Binary Metadata with `exiftool`