Ext Ops Panel
Open dashboard
Permissions and history

GitHub Dark Theme is no longer in the Chrome Web Store: what it can access

GitHub Dark Theme is no longer in the Chrome Web Store: the listing disappeared on 2026-09-09. When it left, it had 10k users. GitHub Dark Theme asks for 2 browser permissions and 1 site pattern. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

GitHub Dark Theme

Chrome extension by LP Luxtra · Productivity · Developer · no longer in the store

What to use instead

Listings still in the store that are closest to it in what they say they do. Comparable, not endorsed.

  1. GitHub Pitch Black Theme Describes nearly the same job, smaller audience 110 users ★ 5.0
  2. Github Native Theme Switcher Describes nearly the same job, smaller audience 9 users ★ 5.0
  3. AAD - Highly Customizable GitHub Describes nearly the same job, smaller audience 6 users ★ 4.8
  4. GitHub Enhancer Describes nearly the same job, smaller audience 10 users
  5. GitHub Contributions Shade Describes nearly the same job, smaller audience 4 users

All alternatives, with why each one is close

If you still have it installed

A listing leaving the store does not by itself remove the extension from browsers that already have it. If you still have it, you can see what it can reach and remove it in a minute:

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to specific sites only
Data collection
Declares it collects none
Publisher
No store badges
Audience
10k users · 4.7/5

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing does not link to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

It also declares site patterns we have not read by name, so the dialog will add a line about site access. Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Specific sites only: 1 match pattern.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

Where it runs its code

We have not read this listing's manifest since we started keeping where it embeds its code, what it may ask for later and which sites can connect to it. The next pass of the store fills this in.

How usual this is for its category

In Productivity · Developer, 31% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 2 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

10k users

Users
unchanged since 31.08
10k · 2 readings
2026-09-09: removed from the store
  1. 2026-08-3110k
  2. 2026-09-0910kremoved from the store

What the store shows

The listing is no longer in the store, so none of the store's badges apply to it now.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

LP Luxtra. This listing has been in the store since 2018-03-22 and was last updated on 2023-06-13.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. GitHub Pitch Black Theme No permissions at all · No permissions declared 110 users ★ 5.0
  2. GitHub Vercel Theme No permissions at all · No permissions declared 48 users
  3. GitHub Contributions Shade No site access · 1 permission 4 users

Questions people ask

What can GitHub Dark Theme access?
Specific sites only: 1 match pattern. It declares 2 browser permissions.
What data does GitHub Dark Theme collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has GitHub Dark Theme asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does GitHub Dark Theme publish a privacy policy?
No, the store listing does not link to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-09-09.

Back to GitHub Dark Theme · Alternatives to GitHub Dark Theme

Where the data comes from: how the catalog is built