Ext Ops Panel
Open dashboard
Permissions and history

Is PostMessage Inspector safe to install?

PostMessage Inspector asks for 2 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.

PostMessage Inspector

Chrome extension by ncctcr · 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 every site
Data collection
Declares it collects none
Publisher
No store badges
Audience
397 users · 4.3/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

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

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

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 every site.

The typical extension there declares 3 browser permissions; this one declares 2 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

397 users

Users
+108 since 01.09
289-399 · 34 readings
2026-10-22: released 0.2.02026-10-23: released 0.4.02026-10-27: released 0.5.02026-10-28: released 0.6.02026-10-30: released 0.6.1
  1. 2026-09-01289
  2. 2026-09-02293
  3. 2026-09-05296
  4. 2026-09-06302
  5. 2026-09-07306
  6. 2026-09-08304
  7. 2026-09-10307
  8. 2026-09-13309
  9. 2026-09-15308
  10. 2026-09-17316
  11. 2026-09-21324
  12. 2026-09-25334
  13. 2026-09-27332
  14. 2026-09-28338
  15. 2026-10-05346
  16. 2026-10-08348
  17. 2026-10-09353
  18. 2026-10-10359
  19. 2026-10-13365
  20. 2026-10-16375
  21. 2026-10-17378
  22. 2026-10-18376
  23. 2026-10-19370
  24. 2026-10-20372
  25. 2026-10-22379released 0.2.0
  26. 2026-10-23378released 0.4.0
  27. 2026-10-24385
  28. 2026-10-25383
  29. 2026-10-26387
  30. 2026-10-28388released 0.6.0
  31. 2026-10-29399
  32. 2026-10-30398released 0.6.1
  33. 2026-11-01395
  34. 2026-11-02397

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 (3, was 4) (changed: browser permissions)

Versions we have seen

  1. Version 0.6.1 · Asked for fewer permissions (3, was 4) (changed: browser permissions)
  2. Version 0.6.0
  3. Version 0.5.0
  4. Version 0.4.0
  5. Version 0.2.0

Who publishes it

ncctcr, who publishes 2 listings we track. This listing has been in the store since 2026-04-01 and was last updated on 2026-10-30.

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. postMessage-catcher Runs its code on every site · 1 permission 2k users ★ 4.0
  2. Message Channel Tracker No site access · 3 permissions 18 users
  3. PostMessage Tracker Access to every site · 1 permission, 1 site pattern 188 users ★ 5.0

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 PostMessage Inspector access?
Every site you visit. This extension can read and change the content of any page you open. It declares 2 browser permissions.
What data does PostMessage Inspector 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 PostMessage Inspector asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-30.
Does PostMessage Inspector 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 PostMessage Inspector · Alternatives to PostMessage Inspector

Where the data comes from: how the catalog is built