Ext Ops Panel
Open dashboard
Permissions and history

Is JWT Inspector safe to install?

JWT Inspector asks for 3 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.

JWT Inspector

Chrome extension by cboy343dev · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 3 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
Upkeep
Updated 212 days ago
Publisher
No store badges
Audience
33 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

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

Reaches your browsing data or every site

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: Access to every site.

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

33 users

Users
-24 since 01.09
27-62 · 40 readings
  1. 2026-09-0157
  2. 2026-09-0262
  3. 2026-09-0451
  4. 2026-09-0546
  5. 2026-09-0641
  6. 2026-09-0739
  7. 2026-09-0836
  8. 2026-09-0930
  9. 2026-09-1327
  10. 2026-09-1529
  11. 2026-09-1730
  12. 2026-09-2032
  13. 2026-09-2130
  14. 2026-09-2529
  15. 2026-09-2630
  16. 2026-09-2829
  17. 2026-10-0430
  18. 2026-10-0831
  19. 2026-10-1333
  20. 2026-10-1634
  21. 2026-10-1833
  22. 2026-10-1931
  23. 2026-10-2132
  24. 2026-10-2231
  25. 2026-10-2330
  26. 2026-10-2431
  27. 2026-10-2529
  28. 2026-10-2828
  29. 2026-10-2929
  30. 2026-10-3031
  31. 2026-11-0130
  32. 2026-11-0234
  33. 2026-11-0433
  34. 2026-11-0632
  35. 2026-11-0733
  36. 2026-11-0834
  37. 2026-11-0933
  38. 2026-11-1032
  39. 2026-11-1133
  40. 2026-11-1233

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

cboy343dev. This listing has been in the store since 2023-10-22 and was last updated on 2026-04-14.

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. JWT Inspector No permissions at all · No permissions declared 12 users ★ 5.0
  2. JWT Decoder No site access · 1 permission 606 users ★ 5.0
  3. JWT.io Viewer Access to specific sites only · 1 permission, 1 site pattern 392 users ★ 3.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 JWT Inspector access?
Every site you visit. This extension can read and change the content of any page you open. It declares 3 browser permissions.
What data does JWT 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 JWT Inspector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does JWT 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-12.

Back to JWT Inspector · Alternatives to JWT Inspector

Where the data comes from: how the catalog is built