Ext Ops Panel
Open dashboard
Permissions and history

Is GitHub Discussion Reverser safe to install?

GitHub Discussion Reverser asks for 1 browser permission 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 Discussion Reverser

Chrome extension by Brenton · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 2 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

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
Upkeep
Updated 153 days ago
Publisher
No store badges
Audience
49 users · 1.0/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 links 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

When you add it, Chrome asks you to allow it to:

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.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Productivity · Developer, 30% 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 1 browser permission.

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

49 users

Users
-19 since 01.09
48-93 · 35 readings
  1. 2026-09-0168
  2. 2026-09-0263
  3. 2026-09-0574
  4. 2026-09-0784
  5. 2026-09-0886
  6. 2026-09-0985
  7. 2026-09-1381
  8. 2026-09-1563
  9. 2026-09-1767
  10. 2026-09-2083
  11. 2026-09-2188
  12. 2026-09-2578
  13. 2026-09-2677
  14. 2026-09-2870
  15. 2026-10-0483
  16. 2026-10-0893
  17. 2026-10-0991
  18. 2026-10-1090
  19. 2026-10-1187
  20. 2026-10-1376
  21. 2026-10-1676
  22. 2026-10-1777
  23. 2026-10-1878
  24. 2026-10-1977
  25. 2026-10-2179
  26. 2026-10-2276
  27. 2026-10-2379
  28. 2026-10-2478
  29. 2026-10-2574
  30. 2026-10-2769
  31. 2026-10-2960
  32. 2026-10-3151
  33. 2026-11-0148
  34. 2026-11-0349
  35. 2026-11-0449

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

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

Brenton. This listing has been in the store since 2025-09-18 and was last updated on 2026-06-04.

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 Commit Sorter No permissions at all · No permissions declared 19 users ★ 5.0
  2. GitHub PR Auto-Expand No permissions at all · No permissions declared 36 users ★ 5.0
  3. GitHub Conventional Comments No site access · 1 permission 8 users

How to check or remove it in Chrome

  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.

Questions people ask

What can GitHub Discussion Reverser access?
Specific sites only: 1 match pattern. It declares 1 browser permission.
What data does GitHub Discussion Reverser 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 Discussion Reverser asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does GitHub Discussion Reverser publish a privacy policy?
Yes, the store listing links 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-11-04.

Back to GitHub Discussion Reverser · Alternatives to GitHub Discussion Reverser

Where the data comes from: how the catalog is built