Ext Ops Panel
Open dashboard
Permissions and history

Is VaptFinder: Vulnerability & Library Detector safe to install?

VaptFinder: Vulnerability & Library Detector asks for 2 browser permissions and 2 site patterns. 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.

VaptFinder: Vulnerability & Library Detector

Chrome extension by Adarsh Siddharthshankar Mishra · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 4 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 313 days ago
Audience
122 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 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

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

122 users

Users
+20 since 01.09
94-147 · 35 readings
  1. 2026-09-01102
  2. 2026-09-03100
  3. 2026-09-04102
  4. 2026-09-05108
  5. 2026-09-06104
  6. 2026-09-07103
  7. 2026-09-08105
  8. 2026-09-1394
  9. 2026-09-15109
  10. 2026-09-17116
  11. 2026-09-20140
  12. 2026-09-21147
  13. 2026-09-25143
  14. 2026-09-26136
  15. 2026-09-28127
  16. 2026-10-05110
  17. 2026-10-08106
  18. 2026-10-09108
  19. 2026-10-10106
  20. 2026-10-11104
  21. 2026-10-13108
  22. 2026-10-16118
  23. 2026-10-18129
  24. 2026-10-19126
  25. 2026-10-20127
  26. 2026-10-21128
  27. 2026-10-22123
  28. 2026-10-23124
  29. 2026-10-24120
  30. 2026-10-25116
  31. 2026-10-26118
  32. 2026-10-28119
  33. 2026-10-29120
  34. 2026-10-30126
  35. 2026-11-01122

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

Adarsh Siddharthshankar Mishra, who publishes 3 listings we track. This listing has been in the store since 2025-12-23 and was last updated on 2025-12-23.

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. Smelly Access to specific sites only · 1 permission, 6 site patterns 5 users (last published figure) ★ 5.0
  2. Xposer Access to specific sites only · 2 permissions, 1 site pattern 25 users
  3. Library Detector (Academic Tool) Access to every site · 1 permission, 1 site pattern 398 users ★ 4.6

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 VaptFinder: Vulnerability & Library Detector 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 VaptFinder: Vulnerability & Library Detector 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 VaptFinder: Vulnerability & Library Detector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does VaptFinder: Vulnerability & Library Detector 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 VaptFinder: Vulnerability & Library Detector · Alternatives to VaptFinder: Vulnerability & Library Detector

Where the data comes from: how the catalog is built