Ext Ops Panel
Open dashboard
Permissions and history

Is Kode Injector safe to install?

Kode Injector 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.

Kode Injector

Chrome extension by maximtop · 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
Featured
Audience
402 users

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

Worth knowing

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.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse.

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

402 users

Users
+23 since 01.09
359-408 · 39 readings
2026-09-07: released 0.9.2
  1. 2026-09-01379
  2. 2026-09-03383
  3. 2026-09-05395
  4. 2026-09-06388
  5. 2026-09-07397released 0.9.2
  6. 2026-09-08390
  7. 2026-09-10386
  8. 2026-09-13376
  9. 2026-09-15378
  10. 2026-09-17370
  11. 2026-09-21391
  12. 2026-09-25390
  13. 2026-09-27387
  14. 2026-09-28380
  15. 2026-10-04371
  16. 2026-10-08364
  17. 2026-10-09361
  18. 2026-10-10366
  19. 2026-10-13362
  20. 2026-10-16361
  21. 2026-10-18359
  22. 2026-10-19369
  23. 2026-10-20367
  24. 2026-10-21368
  25. 2026-10-22374
  26. 2026-10-23370
  27. 2026-10-25366
  28. 2026-10-28369
  29. 2026-10-29375
  30. 2026-10-30378
  31. 2026-11-01391
  32. 2026-11-04396
  33. 2026-11-06401
  34. 2026-11-07398
  35. 2026-11-08399
  36. 2026-11-09407
  37. 2026-11-10408
  38. 2026-11-11402
  39. 2026-11-13402

What the store shows

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.

Versions we have seen

  1. Version 0.9.2

Who publishes it

maximtop, who publishes 7 listings we track. This listing has been in the store since 2018-02-18 and was last updated on 2026-09-06.

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. CSS Injector Runs its code on every site · 3 permissions 28 users ★ 5.0
  2. Blank Extension Access to every site · 2 permissions, 1 site pattern 4 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 Kode Injector 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 Kode Injector 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 Kode Injector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Kode Injector 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-13.

Back to Kode Injector · Alternatives to Kode Injector

Where the data comes from: how the catalog is built