Ext Ops Panel
Open dashboard
Permissions and history

Is Website Framework Detector safe to install?

Website Framework Detector asks for 3 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.

Website Framework Detector

Chrome extension by Anupam Mondal · 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
1 kind of data declared
Audience
245 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

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.

Worth knowing

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

245 users

Users
+81 since 01.09
164-248 · 28 readings
  1. 2026-09-01164
  2. 2026-09-02167
  3. 2026-09-06164
  4. 2026-09-09165
  5. 2026-09-13170
  6. 2026-09-15177
  7. 2026-09-17180
  8. 2026-09-20181
  9. 2026-09-25183
  10. 2026-09-26184
  11. 2026-10-04200
  12. 2026-10-08201
  13. 2026-10-09204
  14. 2026-10-10206
  15. 2026-10-13207
  16. 2026-10-16216
  17. 2026-10-17218
  18. 2026-10-18214
  19. 2026-10-20215
  20. 2026-10-22221
  21. 2026-10-23230
  22. 2026-10-24232
  23. 2026-10-25235
  24. 2026-10-26236
  25. 2026-10-28244
  26. 2026-10-29248
  27. 2026-10-30245
  28. 2026-10-31245

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

Anupam Mondal, who publishes 3 listings we track. This listing has been in the store since 2025-08-05 and was last updated on 2026-08-11.

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. Tech Stack Checker No site access · 1 permission 18 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 Website Framework Detector access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 3 browser permissions.
What data does Website Framework Detector collect?
The developer declares that it collects these kinds of data: Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Website Framework Detector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Website Framework Detector 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 Website Framework Detector · Alternatives to Website Framework Detector

Where the data comes from: how the catalog is built