Ext Ops Panel
Open dashboard
Permissions and history

Is Toolship: Browser Toolkit for DEV & QA safe to install?

Toolship: Browser Toolkit for DEV & QA asks for 11 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.

Toolship: Browser Toolkit for DEV & QA

Chrome extension by Shridhar TL · 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
Upkeep
Updated 209 days ago
Audience
199 users · 4.2/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 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

Reaches your browsing data or every site

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.

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 11 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

199 users

Users
-1 since 01.09
196-208 · 32 readings
  1. 2026-09-01200
  2. 2026-09-03199
  3. 2026-09-04203
  4. 2026-09-05202
  5. 2026-09-06203
  6. 2026-09-07202
  7. 2026-09-08203
  8. 2026-09-10207
  9. 2026-09-13208
  10. 2026-09-15204
  11. 2026-09-17202
  12. 2026-09-21203
  13. 2026-09-22204
  14. 2026-09-25201
  15. 2026-09-26200
  16. 2026-09-28202
  17. 2026-10-05196
  18. 2026-10-08202
  19. 2026-10-09201
  20. 2026-10-10203
  21. 2026-10-11200
  22. 2026-10-16197
  23. 2026-10-17198
  24. 2026-10-19197
  25. 2026-10-21201
  26. 2026-10-22202
  27. 2026-10-23203
  28. 2026-10-24199
  29. 2026-10-25201
  30. 2026-10-27199
  31. 2026-10-29202
  32. 2026-11-01199

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.

Who publishes it

Shridhar TL, who publishes 4 listings we track. This listing has been in the store since 2018-05-20 and was last updated on 2026-04-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. Develobar No site access · 4 permissions 8 users ★ 5.0
  2. Web Tools No site access · 5 permissions 30 users
  3. Ikharo Inspector No site access · 5 permissions 1 users (last published figure)

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 Toolship: Browser Toolkit for DEV & QA access?
Every site you visit. This extension can read and change the content of any page you open. It declares 11 browser permissions.
What data does Toolship: Browser Toolkit for DEV & QA 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 Toolship: Browser Toolkit for DEV & QA asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Toolship: Browser Toolkit for DEV & QA 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 Toolship: Browser Toolkit for DEV & QA · Alternatives to Toolship: Browser Toolkit for DEV & QA

Where the data comes from: how the catalog is built