Ext Ops Panel
Open dashboard
Permissions and history

Is GitHub Pull Request Mark All Files as safe to install?

GitHub Pull Request Mark All Files as 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 Pull Request Mark All Files as

Chrome extension by Dunky13 · 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
No store badges
Audience
141 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 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

141 users

Users
+134 since 01.09
7-141 · 29 readings
2026-10-08: released 1.0.52026-10-09: released 1.1.02026-10-09: released 1.1.12026-10-20: released 1.1.22026-10-20: released 1.1.32026-10-21: released 1.1.42026-10-22: released 1.2.12026-10-24: released 1.3.1
  1. 2026-09-017
  2. 2026-09-038
  3. 2026-09-047
  4. 2026-09-067
  5. 2026-09-078
  6. 2026-09-0910
  7. 2026-09-109
  8. 2026-09-168
  9. 2026-09-219
  10. 2026-09-258
  11. 2026-09-287
  12. 2026-10-048
  13. 2026-10-099released 1.1.0released 1.1.1
  14. 2026-10-108
  15. 2026-10-16126
  16. 2026-10-17127
  17. 2026-10-18128
  18. 2026-10-19127
  19. 2026-10-20125released 1.1.2released 1.1.3
  20. 2026-10-21131released 1.1.4
  21. 2026-10-22129released 1.2.1
  22. 2026-10-23128
  23. 2026-10-24131released 1.3.1
  24. 2026-10-25129
  25. 2026-10-26130
  26. 2026-10-28131
  27. 2026-10-29132
  28. 2026-10-30136
  29. 2026-11-01141

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.

  1. Changed where it works (changed: pages it runs its code on)
  2. Asked for more permissions (2, was 1)
  3. Privacy policy link added to the listing

Versions we have seen

  1. Version 1.3.1
  2. Version 1.2.1
  3. Version 1.1.4
  4. Version 1.1.3 · Changed where it works (changed: pages it runs its code on)
  5. Version 1.1.2 · Changed where it works (changed: pages it runs its code on)
  6. Version 1.1.1 · Asked for more permissions (2, was 1)
  7. Version 1.1.0 · Asked for more permissions (2, was 1)
  8. Version 1.0.5

Who publishes it

Dunky13, who publishes 3 listings we track. This listing has been in the store since 2024-12-17 and was last updated on 2026-10-23.

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 File Hider Button No permissions at all · No permissions declared 5 users
  2. Better GitHub File Filter No permissions at all · No permissions declared 3 users
  3. GitHub Helper 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 Pull Request Mark All Files as access?
Specific sites only: 1 match pattern. It declares 1 browser permission.
What data does GitHub Pull Request Mark All Files as 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 Pull Request Mark All Files as asked for more permissions over time?
Its permissions changed 3 times while we watched, most recently on 2026-10-20.
Does GitHub Pull Request Mark All Files as 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-01.

Back to GitHub Pull Request Mark All Files as · Alternatives to GitHub Pull Request Mark All Files as

Where the data comes from: how the catalog is built