Ext Ops Panel
Open dashboard
Permissions and history

Is Source Patch safe to install?

Source Patch asks for 2 browser permissions and declares no blanket site access. 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.

Source Patch

Chrome extension by Robin Philip Thomas · 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
No site access
Data collection
2 kinds of data declared
Publisher
No store badges
Audience
65 users

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

From the permissions it declares, Chrome shows no permission warning when you add it.

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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

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: No site access.

The typical extension there declares 3 browser permissions; this one declares 2 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

65 users

Users
+19 since 01.09
46-68 · 28 readings
  1. 2026-09-0146
  2. 2026-09-0248
  3. 2026-09-0647
  4. 2026-09-0747
  5. 2026-09-0848
  6. 2026-09-1047
  7. 2026-09-1352
  8. 2026-09-1554
  9. 2026-09-1756
  10. 2026-09-2259
  11. 2026-09-2561
  12. 2026-09-2662
  13. 2026-09-2860
  14. 2026-10-0554
  15. 2026-10-0856
  16. 2026-10-0955
  17. 2026-10-1053
  18. 2026-10-1352
  19. 2026-10-1662
  20. 2026-10-1864
  21. 2026-10-2166
  22. 2026-10-2267
  23. 2026-10-2365
  24. 2026-10-2462
  25. 2026-10-2563
  26. 2026-10-2762
  27. 2026-10-2968
  28. 2026-11-0165

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

Robin Philip Thomas. This listing has been in the store since 2023-01-01 and was last updated on 2023-01-08.

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. VSCify No permissions at all · No permissions declared 3 users (last published figure)
  2. Commit Buddy No permissions at all · No permissions declared 2 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 Source Patch access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 2 browser permissions.
What data does Source Patch collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Source Patch asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Source Patch 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 Source Patch · Alternatives to Source Patch

Where the data comes from: how the catalog is built