Is CSSViewer safe to install?
CSSViewer 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.
The facts we can check
No score. A single number would compress incomparable things and imply we had weighed them: an ad blocker needs every page and a theme needs nothing, and one figure would be wrong about both.
- Site access
- No site access is declared in the manifest, so it cannot read the pages you open on its own.
- Browser permissions
- 2 permissions
- Privacy policy
- Published in the store listing
- Manifest version
- V3, the current extension platform
- Publisher record
- The store shows this publisher its good record badge
- Rated by
- 11 people, average 4.2
What it can reach
No site access is declared in the manifest, so it cannot read the pages you open on its own.
-
Run its own code on the pages it can access
scripting -
Act on the current tab, but only after you click it
activeTab
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
SelectorsHub, who publishes 13 listings we track. This listing has been in the store since 2024-05-14 and was last updated on 2026-05-20.
We read the public store listing once 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-09-09.