Ext Ops Panel
Open dashboard
Permissions and history

Is Cocos Creator Inspector safe to install?

Cocos Creator Inspector asks for no browser permissions and 1 site pattern. 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.

Cocos Creator Inspector

Chrome extension · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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 every site
Data collection
1 kind of data declared
Publisher
No store badges
Audience
42 users · 4.5/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

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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

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.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to every site.

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

42 users

Users
+42 since 01.09
0-42 · 27 readings
2026-09-04: released 0.2.02026-09-11: released 0.3.02026-09-19: released 0.4.52026-09-22: released 0.5.02026-09-22: released 0.5.52026-10-01: released 0.6.02026-10-31: released 0.6.6
  1. 2026-09-010
  2. 2026-09-022
  3. 2026-09-044released 0.2.0
  4. 2026-09-076
  5. 2026-09-097
  6. 2026-09-1012
  7. 2026-09-1325
  8. 2026-09-1520
  9. 2026-09-1724
  10. 2026-09-2025
  11. 2026-09-2533
  12. 2026-09-2634
  13. 2026-09-2835
  14. 2026-10-0438
  15. 2026-10-0835
  16. 2026-10-1036
  17. 2026-10-1137
  18. 2026-10-1638
  19. 2026-10-1839
  20. 2026-10-1940
  21. 2026-10-2138
  22. 2026-10-2235
  23. 2026-10-2333
  24. 2026-10-2434
  25. 2026-10-2939
  26. 2026-10-3142released 0.6.6
  27. 2026-11-0142

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.

  1. Asked for fewer permissions (1, was 3) (changed: browser permissions)
  2. Asked for more permissions (3, was 0)

Versions we have seen

  1. Version 0.6.6 · Asked for fewer permissions (1, was 3) (changed: browser permissions)
  2. Version 0.6.0 · Asked for more permissions (3, was 0)
  3. Version 0.5.5
  4. Version 0.5.0
  5. Version 0.4.5
  6. Version 0.3.0

Who publishes it

The store lists no publisher name. This listing has been in the store since 2026-08-28 and was last updated on 2026-10-31.

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. Scene Inspector for PixiJS Runs its code on every site · No permissions declared 36 users
  2. Phaser Debugger Runs its code on every site · No permissions declared 1k users ★ 5.0
  3. Coconutool Runs its code on every site · 1 permission 1k users ★ 4.9

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 Cocos Creator Inspector access?
Every site you visit. This extension can read and change the content of any page you open. It declares no browser permissions.
What data does Cocos Creator Inspector 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 Cocos Creator Inspector asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-10-31.
Does Cocos Creator Inspector 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-11-01.

Back to Cocos Creator Inspector · Alternatives to Cocos Creator Inspector

Where the data comes from: how the catalog is built