Ext Ops Panel
Open dashboard
Permissions and history

Is GitHub PR Review Checker safe to install?

GitHub PR Review Checker asks for 3 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 PR Review Checker

Chrome extension by Ryosuke Hoda · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 5 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
1 kind of data declared
Publisher
No store badges
Audience
124 users · 5.0/5

What data it declares

The developer declares that it collects these kinds of 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

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 3 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

124 users

Users
+21 since 01.09
99-124 · 32 readings
  1. 2026-09-01103
  2. 2026-09-05105
  3. 2026-09-07104
  4. 2026-09-08103
  5. 2026-09-09104
  6. 2026-09-10105
  7. 2026-09-13103
  8. 2026-09-15104
  9. 2026-09-1799
  10. 2026-09-21105
  11. 2026-09-22106
  12. 2026-09-25108
  13. 2026-09-26106
  14. 2026-09-28103
  15. 2026-10-04120
  16. 2026-10-08119
  17. 2026-10-09118
  18. 2026-10-10122
  19. 2026-10-13123
  20. 2026-10-16117
  21. 2026-10-18119
  22. 2026-10-19117
  23. 2026-10-20116
  24. 2026-10-21123
  25. 2026-10-22122
  26. 2026-10-24124
  27. 2026-10-25120
  28. 2026-10-26121
  29. 2026-10-28123
  30. 2026-10-29122
  31. 2026-10-30124
  32. 2026-10-31124

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

Ryosuke Hoda. This listing has been in the store since 2025-04-29 and was last updated on 2026-08-21.

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 Comment Tracker No permissions at all · No permissions declared 15 users
  2. GitHub PR Filter No site access · 1 permission 3 users
  3. GitOwl Access to specific sites only · 1 permission, 1 site pattern 3 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 PR Review Checker access?
Specific sites only: 1 match pattern. It declares 3 browser permissions.
What data does GitHub PR Review Checker collect?
The developer declares that it collects these kinds of data: Authentication information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has GitHub PR Review Checker asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does GitHub PR Review Checker 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-10-31.

Back to GitHub PR Review Checker · Alternatives to GitHub PR Review Checker

Where the data comes from: how the catalog is built