Ext Ops Panel
Open dashboard
Permissions and history

Is Forks Diff Counter for GitHub safe to install?

Forks Diff Counter for GitHub declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

Forks Diff Counter for GitHub

Chrome extension by Giacomo Ferretti · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 3 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 permissions at all
Data collection
Declares it collects none
Audience
68 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

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

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 · Developer, 30% of extensions ask for access to every site. This one: No permissions at all.

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

68 users

Users
-6 since 01.09
65-143 · 38 readings
  1. 2026-09-0174
  2. 2026-09-0275
  3. 2026-09-0372
  4. 2026-09-0466
  5. 2026-09-0765
  6. 2026-09-0866
  7. 2026-09-1070
  8. 2026-09-1572
  9. 2026-09-1774
  10. 2026-09-2070
  11. 2026-09-2171
  12. 2026-09-2567
  13. 2026-09-2868
  14. 2026-10-04108
  15. 2026-10-08110
  16. 2026-10-09109
  17. 2026-10-10116
  18. 2026-10-11117
  19. 2026-10-16122
  20. 2026-10-17123
  21. 2026-10-18127
  22. 2026-10-19138
  23. 2026-10-20141
  24. 2026-10-21135
  25. 2026-10-22138
  26. 2026-10-23139
  27. 2026-10-24143
  28. 2026-10-25142
  29. 2026-10-26127
  30. 2026-10-28116
  31. 2026-10-29106
  32. 2026-10-3094
  33. 2026-11-0176
  34. 2026-11-0271
  35. 2026-11-0470
  36. 2026-11-0669
  37. 2026-11-0867
  38. 2026-11-1068

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

Giacomo Ferretti. This listing has been in the store since 2020-04-30 and was last updated on 2024-10-24.

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 Forks Diff Counter for GitHub access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
What data does Forks Diff Counter for GitHub 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 Forks Diff Counter for GitHub asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Forks Diff Counter for GitHub 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 Forks Diff Counter for GitHub · Alternatives to Forks Diff Counter for GitHub

Where the data comes from: how the catalog is built