Open-source project
OhMyGuus/I-Still-Dont-Care-About-Cookies avatar
OhMyGuus/I-Still-Dont-Care-About-Cookies

This cookie banner fork's package.json points at a different repository

Debloated fork of the extension "I don't care about cookies"

4,283 stars138 forksJavaScriptGPL-3.0

At a glance

What is it?
I still don't care about cookies is a debloated fork of a browser extension that was acquired by Avast and then by Gen Digital. The interesting part is the shape of the fork itself: site rules are generated from scripts, the website coverage backlog is the issue tracker, and package.json still points at a repository named I-Dont-Care-About-Cookies rather than this one.
Who is it for?
This extension fits someone who wants cookie banners suppressed without handing their browsing to a vendor-owned build, and who is willing to check per-site coverage rather than assume it. It does not fit someone who needs a settled data policy, because the extension calls an API hosted elsewhere and the page says nothing about what a request contains.
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 received new commits within the last day.
What is it written in?
Mainly JavaScript, 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.

From daily snapshots

Star history

  • OhMyGuus/I-Still-Dont-Care-About-Cookies4,283 ★ · +34
Star history
Repository2026-09-232026-11-15
OhMyGuus/I-Still-Dont-Care-About-Cookies4.2k4.3k

34 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The fork exists because of an acquisition chain

The stated reason is ownership, not features. The original extension was acquired by Avast, which was itself acquired by Gen Digital, and the maintainer says plainly that they do not trust Avast with their data.

A second reason is structural. Keeping the extension on GitHub is described as the way to improve the code and add support for websites faster, which is a claim about who decides what lands and when.

The fork pins its base explicitly: it is based on v3.4.3 of the original, distributed under GPLv3. That version number carries more weight than it looks, because the fork keeps a line of its own. The package name is `isdcac` and the version in the manifest is 1.1.9. Two version lines in one project means a 1.1.x release of the fork says nothing on its own about which upstream release it tracks.

Three manifest fields still point at the upstream repository

Three fields inside `package.json` name a repository that is not this one. The repository URL ends in `I-Dont-Care-About-Cookies.git`, the homepage ends in `I-Dont-Care-About-Cookies#readme`, and the issues URL ends in `I-Dont-Care-About-Cookies/issues`. All three name a repository called `I-Dont-Care-About-Cookies` under the same OhMyGuus account, while the fork is published as `I-Still-Dont-Care-About-Cookies`.

That matters for anything reading the manifest instead of the page: a link printed by a package tool, a clone suggestion, an issue link attached to a bug report.

The declared entry point has a related problem. `main` is set to `index.js`, while the tree shows the source under `src/` next to a `tools/` directory, with no `index.js` at the top level. The declared entry is either inside `src/` or absent, and nothing in the scripts resolves which.

Site rules are generated by tools, not edited by hand

Coverage of individual websites is the substance of this project, and it is generated rather than hand-maintained.

bash
node tools/add-rule.js
node tools/generate-block-rules.js > src/rules.json && prettier --write src/rules.json

The first script adds a rule. The second rebuilds `src/rules.json` by redirecting the tool's output into it and then formatting the result, which is why the formatter is wired into the generation step rather than left to a separate pass.

So the pipeline reads clearly: a report arrives, a rule is added, the JSON is rebuilt, and formatting runs. Every website added to the extension goes through those two commands, and nothing in the tree suggests a route that edits the JSON directly.

15,027 open issues is the website reporting channel

The issue count is the striking number: 15,027 open issues against 4,254 stars and 133 forks.

That is not backlog in the usual sense. The credits name everyone who reported a website among the contributors, which tells you what an issue in this tracker is for. A site whose banner is not being suppressed produces one report, and the fix is a rule produced by the script above.

The consequence for anyone reading the project is that the open issue count will never fall to a tidy number, and it should not be read as neglect. The commit history agrees: the last push on the default branch is dated 2026-11-02. That branch is named `master` rather than `main`, which is the older convention and matches a project that grew up on GitHub rather than being created from a current template.

The API is a separate C# repository the extension calls

The extension is not self-contained at run time. It sends requests to an API hosted at `api.istilldontcareaboutcookies.com`, and that backend lives in its own repository rather than here, written with the C# ASP.NET library in an MVC structure.

So a suppression decision can involve a network round trip to a service somebody else operates, and sending a request is not the same as sending the contents of the page. The maintainer's reason for forking was not trusting a vendor with data, so the call is the place where a reviewer has to decide what leaves the browser.

The page says nothing about caching, timeouts or what happens when the request fails. What exists on disk is the generated rule file. The source of the backend being public is stated plainly, and that is what makes the arrangement reviewable at all.

Three store listings and two manual guides

There are three store links at the top of the page: Firefox add-ons, the Chrome Web Store, and Microsoft Edge add-ons. Alongside them sit two manual installation guides in the wiki, one for Firefox and one for Chrome.

Those two are the only browsers given a manual path, and the split shows where the effort went. Store distribution covers the browsers where a store listing is the normal route, and the manual guides exist for the cases where it is not sufficient.

The releases page is linked twice from the header, once straight to the latest release and once to the full list, so the current build and the history are both one click away. The full list matters more than it would elsewhere, for the reason in the release section below: the newest entry in it is not the current state of the branch.

Translations run through Crowdin, not through pull requests

Localisation is coordinated on a hosted platform rather than in the repository. `crowdin.yml` sits at the top of the tree, the project has a Crowdin page, and translators are credited as a group with their own link.

The practical effect is that adding or correcting a language means working inside that platform, while everything else about the extension is an ordinary Git repository. Contributors split into named groups in the credits: the current maintainer, one person credited with setting up and maintaining the project, translators, and everyone else who sent a patch.

The remaining credit goes to Daniel Kladnik, named as the developer of the original extension, who is also the reason a fork is possible: the upstream is distributed under GPLv3 and this fork states it is based on that release.

The newest tag is 1.1.9 and the branch moved on

Three recent tags are v1.1.7 on 2025-10-27, v1.1.8 on 2025-11-06 and v1.1.9 on 2025-12-07, and that last version matches the one in the package manifest.

After 2025-12-07 the commits continue without a new tag. The default branch has therefore moved on by about eleven months of work past every published release, and no nightly or edge channel is named on the page.

The dependency list is short enough to state exactly: `acorn`, `commander`, and a package named `packages` pinned at 0.0.8. The third is named so generically that its purpose cannot be told from the manifest, which is the kind of detail you only learn by reading the source.

Editorial conclusion

This extension fits someone who wants cookie banners suppressed without handing their browsing to a vendor-owned build, and who is willing to check per-site coverage rather than assume it. It does not fit someone who needs a settled data policy, because the extension calls an API hosted elsewhere and the page says nothing about what a request contains. Before you install it, check four things. Which store you take it from, since Firefox, Chrome and Edge have listings while only Firefox and Chrome have a manual guide. Whether the build you get is current, since the newest tag is v1.1.9 from 2025-12-07 while the branch has moved on since. Which upstream release it tracks, since the fork states it is based on v3.4.3 and keeps a separate 1.1.x line of its own. And whether you read PRIVACY_POLICY.md, which sits at the top of the tree and is not discussed on the page.

Frequently asked questions

What does "I still don't care about cookies" do?

It removes cookie warning banners from almost all websites, which is the stated purpose of the extension and of this debloated fork. The fork was made after the original was acquired by Avast and exists on GitHub so the code can be improved and new sites supported faster. It is based on v3.4.3 of the original, which is distributed under GPLv3.

How do I install I still don't care about cookies?

Store listings exist for Firefox, Chrome and Microsoft Edge, and manual installation guides are published in the project wiki for Firefox and Chrome. For contributors, the package scripts add a site rule with node tools/add-rule.js and rebuild the rule data with node tools/generate-block-rules.js.

How does I still don't care about cookies cover new websites?

Site coverage is contributed one website at a time as a GitHub issue, and everyone who reported a website is credited as a contributor. A rule is then added with a script under tools/, and src/rules.json is regenerated from it, which is why the open issue count sits in the tens of thousands rather than tracking defects.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. OhMyGuus/I-Still-Dont-Care-About-Cookies on GitHub
  4. README
  5. Releases
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/ohmyguus-i-still-dont-care-about-cookies.svg)](https://hysenlabs.com/projects/ohmyguus-i-still-dont-care-about-cookies)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/ohmyguus-i-still-dont-care-about-cookies.svg)](https://hysenlabs.com/projects/ohmyguus-i-still-dont-care-about-cookies)

Was this useful?