Ext Ops Panel
Open dashboard
Permissions and history

Is Attribute Class Enhancer for Webflow safe to install?

Attribute Class Enhancer for Webflow asks for 1 browser permission and 2 site patterns. 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.

Attribute Class Enhancer for Webflow

Chrome extension by frontendcsssimplified · 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
Declares it collects none
Publisher
No store badges
Audience
50 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

Specific sites only: 2 match patterns.

Worth knowing

Pages it runs its code on

It runs its own code on specific pages only: 2 site patterns.

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

50 users

Users
+3 since 31.08
39-50 · 28 readings
  1. 2026-08-3147
  2. 2026-09-0248
  3. 2026-09-0445
  4. 2026-09-0642
  5. 2026-09-0744
  6. 2026-09-1040
  7. 2026-09-1342
  8. 2026-09-1543
  9. 2026-09-1741
  10. 2026-09-2139
  11. 2026-09-2240
  12. 2026-09-2541
  13. 2026-09-2643
  14. 2026-09-2842
  15. 2026-10-0441
  16. 2026-10-0842
  17. 2026-10-0943
  18. 2026-10-1040
  19. 2026-10-1341
  20. 2026-10-1645
  21. 2026-10-1944
  22. 2026-10-2146
  23. 2026-10-2243
  24. 2026-10-2344
  25. 2026-10-2545
  26. 2026-10-2949
  27. 2026-11-0150
  28. 2026-11-0250

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

frontendcsssimplified, who publishes 3 listings we track. This listing has been in the store since 2026-04-03 and was last updated on 2026-08-09.

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. RiseVerse Library: Prevent class duplication in Webflow No site access · 3 permissions 154 users ★ 5.0
  2. Webflow Attribute Editor Access to specific sites only · 1 site pattern 29 users ★ 5.0
  3. Attribute Pro for Webflow Access to specific sites only · 1 site pattern 38 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 Attribute Class Enhancer for Webflow access?
Specific sites only: 2 match patterns. It declares 1 browser permission.
What data does Attribute Class Enhancer for Webflow 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 Attribute Class Enhancer for Webflow asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Attribute Class Enhancer for Webflow 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-02.

Back to Attribute Class Enhancer for Webflow · Alternatives to Attribute Class Enhancer for Webflow

Where the data comes from: how the catalog is built