Ext Ops Panel
Open dashboard
Permissions and history

Is GitHub Hide Whitespace safe to install?

GitHub Hide Whitespace 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 Hide Whitespace

Chrome extension by mild7caloriemategreentea · 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
Publisher
Featured
Audience
40 users · 5.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 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

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

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

40 users

Users
-3 since 31.08
36-46 · 27 readings
  1. 2026-08-3143
  2. 2026-09-0244
  3. 2026-09-0646
  4. 2026-09-0744
  5. 2026-09-0845
  6. 2026-09-0944
  7. 2026-09-1343
  8. 2026-09-1544
  9. 2026-09-2040
  10. 2026-09-2139
  11. 2026-09-2641
  12. 2026-09-2840
  13. 2026-10-0443
  14. 2026-10-0844
  15. 2026-10-1038
  16. 2026-10-1337
  17. 2026-10-1636
  18. 2026-10-1838
  19. 2026-10-1939
  20. 2026-10-2140
  21. 2026-10-2239
  22. 2026-10-2340
  23. 2026-10-2438
  24. 2026-10-2537
  25. 2026-10-2738
  26. 2026-10-2937
  27. 2026-11-0140

What the store shows

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

mild7caloriemategreentea. This listing has been in the store since 2023-03-13 and was last updated on 2024-08-19.

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 PR Review Enhancement No permissions at all · No permissions declared 3 users (last published figure)
  2. GitHub Helper No site access · 1 permission 9 users
  3. GitHub Diff No site access · 3 permissions 31 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 Hide Whitespace access?
Specific sites only: 1 match pattern. It declares 1 browser permission.
What data does GitHub Hide Whitespace 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 Hide Whitespace asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does GitHub Hide Whitespace 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-11-01.

Back to GitHub Hide Whitespace · Alternatives to GitHub Hide Whitespace

Where the data comes from: how the catalog is built