Ext Ops Panel
Open dashboard
Permissions and history

Is Akeyless Password Manager 2.0 safe to install?

Akeyless Password Manager 2.0 asks for 14 browser permissions and 23 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.

Akeyless Password Manager 2.0

Chrome extension by akeyless.io · Make Chrome Yours · Privacy

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
3 kinds of data declared
Publisher
No store badges
Audience
709 users · 5.0/5

What data it declares

The developer declares that it collects these kinds of 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.

Show the remaining 22
  • https://auth.dbk.akeyless.io/* only auth.dbk.akeyless.io
  • https://auth.wmt.akeyless.io/* only auth.wmt.akeyless.io
  • https://auth.cvs.akeyless.io/* only auth.cvs.akeyless.io
  • https://*.akeyless.dev/* akeyless.dev and all its subdomains
  • http://127.0.0.1:17891/* only 127.0.0.1
  • http://localhost:17891/* only localhost
  • <all_urls> every site
  • http://localhost/* only localhost
  • http://127.0.0.1/* only 127.0.0.1
  • https://*.run.app/* run.app and all its subdomains
  • https://console-pwm.akeyless.dev/* only console-pwm.akeyless.dev
  • https://console-pwm.dbk.akeyless.dev/* only console-pwm.dbk.akeyless.dev
  • https://console-pwm.us.akeyless.dev/* only console-pwm.us.akeyless.dev
  • https://console-pwm.eu.akeyless.dev/* only console-pwm.eu.akeyless.dev
  • https://console-pwm.cvs.akeyless.dev/* only console-pwm.cvs.akeyless.dev
  • https://console-pwm.wmt.akeyless.dev/* only console-pwm.wmt.akeyless.dev
  • https://console-pwm.akeyless.io/* only console-pwm.akeyless.io
  • https://console-pwm.dbk.akeyless.io/* only console-pwm.dbk.akeyless.io
  • https://console-pwm.us.akeyless.io/* only console-pwm.us.akeyless.io
  • https://console-pwm.eu.akeyless.io/* only console-pwm.eu.akeyless.io
  • https://console-pwm.cvs.akeyless.io/* only console-pwm.cvs.akeyless.io
  • https://console-pwm.wmt.akeyless.io/* only console-pwm.wmt.akeyless.io

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.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 14 site patterns.

Show the remaining 11
  • https://console-pwm.dbk.akeyless.dev/* only console-pwm.dbk.akeyless.dev
  • https://console-pwm.us.akeyless.dev/* only console-pwm.us.akeyless.dev
  • https://console-pwm.eu.akeyless.dev/* only console-pwm.eu.akeyless.dev
  • https://console-pwm.cvs.akeyless.dev/* only console-pwm.cvs.akeyless.dev
  • https://console-pwm.wmt.akeyless.dev/* only console-pwm.wmt.akeyless.dev
  • https://console-pwm.akeyless.io/* only console-pwm.akeyless.io
  • https://console-pwm.dbk.akeyless.io/* only console-pwm.dbk.akeyless.io
  • https://console-pwm.us.akeyless.io/* only console-pwm.us.akeyless.io
  • https://console-pwm.eu.akeyless.io/* only console-pwm.eu.akeyless.io
  • https://console-pwm.cvs.akeyless.io/* only console-pwm.cvs.akeyless.io
  • https://console-pwm.wmt.akeyless.io/* only console-pwm.wmt.akeyless.io

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Make Chrome Yours · Privacy, 42% 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 14 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

709 users

Users
+76 since 31.08
633-752 · 37 readings
2026-10-14: released 1.30.1312026-10-19: released 1.30.1332026-10-20: released 1.30.1342026-10-22: released 1.30.1352026-10-25: released 1.30.1362026-10-25: released 1.30.1372026-10-26: released 1.30.1382026-10-28: released 1.30.1392026-11-01: released 1.30.1412026-11-03: released 1.30.144
  1. 2026-08-31633
  2. 2026-09-02639
  3. 2026-09-04655
  4. 2026-09-06656
  5. 2026-09-07657
  6. 2026-09-09676
  7. 2026-09-13670
  8. 2026-09-15669
  9. 2026-09-17707
  10. 2026-09-20715
  11. 2026-09-22716
  12. 2026-09-25705
  13. 2026-09-26699
  14. 2026-09-28702
  15. 2026-10-04691
  16. 2026-10-08727
  17. 2026-10-09728
  18. 2026-10-10730
  19. 2026-10-11728
  20. 2026-10-13740
  21. 2026-10-16745
  22. 2026-10-17746
  23. 2026-10-18742
  24. 2026-10-19737released 1.30.133
  25. 2026-10-20744released 1.30.134
  26. 2026-10-21751
  27. 2026-10-22752released 1.30.135
  28. 2026-10-23739
  29. 2026-10-24733
  30. 2026-10-25721released 1.30.136released 1.30.137
  31. 2026-10-26720released 1.30.138
  32. 2026-10-28719released 1.30.139
  33. 2026-10-29715
  34. 2026-10-30722
  35. 2026-11-01706released 1.30.141
  36. 2026-11-02709
  37. 2026-11-03709released 1.30.144

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 more permissions (37, was 35) (changed: browser permissions)

Versions we have seen

  1. Version 1.30.144
  2. Version 1.30.141
  3. Version 1.30.139
  4. Version 1.30.138
  5. Version 1.30.137
  6. Version 1.30.136
  7. Version 1.30.135
  8. Version 1.30.134

Who publishes it

akeyless.io, who publishes 2 listings we track. This listing has been in the store since 2025-12-01 and was last updated on 2026-11-02.

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. ClawGuard Password Manager Runs its code on every site · 3 permissions, 1 site pattern 5 users
  2. Lemonade Password Manager Runs its code on every site · 3 permissions, 4 site patterns 4 users
  3. GestAuth - Password Manager Access to every site · 4 permissions, 1 site pattern 6 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 Akeyless Password Manager 2.0 access?
Every site you visit. This extension can read and change the content of any page you open. It declares 14 browser permissions.
What data does Akeyless Password Manager 2.0 collect?
The developer declares that it collects these kinds of data: Authentication information, Personal communications, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Akeyless Password Manager 2.0 asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-14.
Does Akeyless Password Manager 2.0 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-03.

Back to Akeyless Password Manager 2.0 · Alternatives to Akeyless Password Manager 2.0

Where the data comes from: how the catalog is built