Ext Ops Panel
Open dashboard
Permissions and history

Is Table Formatter for GitLab™ safe to install?

Table Formatter for GitLab™ asks for no 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.

Table Formatter for GitLab™

Chrome extension by hidaka · Productivity · Tools

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
No store badges
Audience
57 users

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.

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.

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 · Tools, 20% 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 no 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

57 users

Users
+10 since 01.09
47-59 · 37 readings
  1. 2026-09-0147
  2. 2026-09-0349
  3. 2026-09-0552
  4. 2026-09-0751
  5. 2026-09-0953
  6. 2026-09-1356
  7. 2026-09-1555
  8. 2026-09-1757
  9. 2026-09-2051
  10. 2026-09-2149
  11. 2026-09-2652
  12. 2026-09-2853
  13. 2026-10-0452
  14. 2026-10-0850
  15. 2026-10-0954
  16. 2026-10-1053
  17. 2026-10-1155
  18. 2026-10-1353
  19. 2026-10-1649
  20. 2026-10-1752
  21. 2026-10-1853
  22. 2026-10-1952
  23. 2026-10-2054
  24. 2026-10-2157
  25. 2026-10-2258
  26. 2026-10-2356
  27. 2026-10-2554
  28. 2026-10-2853
  29. 2026-10-2954
  30. 2026-10-3056
  31. 2026-11-0158
  32. 2026-11-0259
  33. 2026-11-0658
  34. 2026-11-0756
  35. 2026-11-0858
  36. 2026-11-0957
  37. 2026-11-1057

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

hidaka, who publishes 3 listings we track. This listing has been in the store since 2024-04-05 and was last updated on 2024-04-25.

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 Tables No permissions at all · No permissions declared 10 users
  2. Waffle Lens Runs its code on every site · No permissions declared 9 users
  3. Table Enhancer for GitHub No site access · 1 permission 15 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 Table Formatter for GitLab™ access?
Specific sites only: 1 match pattern. It declares no browser permissions.
What data does Table Formatter for GitLab™ 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 Table Formatter for GitLab™ asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Table Formatter for GitLab™ 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-10.

Back to Table Formatter for GitLab™ · Alternatives to Table Formatter for GitLab™

Where the data comes from: how the catalog is built