whatisgithub

What is trackerlab?

efforg/trackerlab — explained in plain English

Analysis updated 2026-07-16 · repo last pushed 2013-08-02

11DAudience · developerComplexity · 3/5DormantSetup · hard

In one sentence

An experimental browser extension by the Electronic Frontier Foundation that automatically detects and blocks invisible web trackers using heuristic methods instead of manually maintained blocklists.

Mindmap

mindmap
  root((repo))
    What it does
      Blocks web trackers
      Heuristic detection
      Browser extension
    Tech stack
      D language
      AdBlock Plus base
      Chrome extension
    Use cases
      Test tracker blocking
      Tinker with privacy tools
      Study heuristic methods
    Audience
      Privacy-conscious users
      Privacy tool developers
      Tinkerers and hackers
    Project status
      Experimental effort
      Sparse documentation
      Rough build process

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Install the extension in Chrome to experiment with automatic tracker blocking using heuristic detection.

USE CASE 2

Study the code to understand how heuristic tracker detection could work without relying on manual blocklists.

USE CASE 3

Use it as a starting point to build your own privacy-focused browser extension based on AdBlock Plus.

What is it built with?

DAdBlock PlusChrome Extension

How does it compare?

efforg/trackerlabgnunn1/tilixabraunegg/onedrive
Stars115,68312,424
LanguageDDD
Last pushed2013-08-02
MaintenanceDormant
Setup difficultyhardeasymoderate
Complexity3/52/53/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Build process involves a dummy package and Chrome's manual local extension loading procedure, described by the developers as a frustrating ritual.

No license information is provided in the documentation, so it is unclear what rights you have to use or modify this code.

So what is it?

The Electronic Frontier Foundation built this experimental tool, called Tracker Blocking Laboratory, to test new ways of stopping online trackers that follow you around the web without your consent. It is a browser extension that aims to block tracking automatically, using heuristic methods rather than relying on someone to manually maintain a list of known trackers. At a technical level, the project is based on AdBlock Plus, a popular open-source ad-blocking extension. Rather than simply blocking ads, the EFF's version focuses specifically on detecting and blocking the invisible trackers that companies use to build profiles of your browsing behavior. The code is primarily written in D, which is an unusual choice for a browser extension project. The README does not go into detail about how the heuristic detection actually works, so the specifics of its approach remain unclear from the documentation alone. The intended audience is likely privacy-conscious users who want a more proactive approach to tracker blocking, as well as developers interested in privacy tooling. The EFF is a well-known digital rights organization, so this project carries their credibility and mission of protecting user privacy online. However, with only a small number of stars and a sparse README, it appears to be a niche experimental effort rather than a polished product ready for everyday use. One notable tradeoff is that the build process described in the README involves creating a dummy package and navigating what the developers call Chrome's "stupid magic ritual" for installing local extensions. This suggests the project is still rough around the edges and aimed at tinkerers willing to work through friction to test experimental privacy tools.

Copy-paste prompts

Prompt 1
I want to build a browser extension that automatically detects and blocks web trackers using heuristic methods instead of a manual blocklist. How should I structure the detection logic based on what EFF's Tracker Blocking Laboratory does?
Prompt 2
Help me understand the build process for installing a local Chrome extension from source, including creating a dummy package and loading an unpacked extension in developer mode.
Prompt 3
I'm extending an AdBlock Plus-based project to focus on blocking invisible trackers instead of ads. What behavioral signals should my heuristic detection look for to identify tracking scripts?
Prompt 4
Help me set up a D-language build environment for a browser extension project and explain what toolchain I need to compile and package the extension for Chrome.

Frequently asked questions

What is trackerlab?

An experimental browser extension by the Electronic Frontier Foundation that automatically detects and blocks invisible web trackers using heuristic methods instead of manually maintained blocklists.

What language is trackerlab written in?

Mainly D. The stack also includes D, AdBlock Plus, Chrome Extension.

Is trackerlab actively maintained?

Dormant — no commits in 2+ years (last push 2013-08-02).

What license does trackerlab use?

No license information is provided in the documentation, so it is unclear what rights you have to use or modify this code.

How hard is trackerlab to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is trackerlab for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.