StackyOps Vault icon

StackyOps Vault

by devops · Privacy & Security
Manifest V3 Free
View in Chrome Web Store Data as of 15 Oct 2026

Fill logins from your StackyOps organization vault on matching sites — securely, over your org's own audit trail.

Users
3
store count
Rating
5.0 / 5
unchanged in 30 days
Ratings
1
total ratings
Store rank
#290K
#239K among extensions
Version
0.4.1
updated 14 Oct 2026

Users

monthly, 1 months
023Sep 2026Oct 2026Oct 2026
Latest, 15 Oct 2026: 3 usersMove the mouse over the chart for any month

Ratings count

monthly, 1 months
001Sep 2026Oct 2026Oct 2026
Latest, 15 Oct 2026: 1 ratingsMove the mouse over the chart for any month

The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.

About StackyOps Vault

Single purpose description ▎ StackyOps Vault lets a user sign in to websites using the logins stored in their own ▎ StackyOps account. It matches the site the user is on against their saved logins, and on the ▎ user's action fills the username and password and shows that site's 2FA code; it can also ▎ offer to save a newly entered login back to the vault. It talks only to the self-hosted ▎ StackyOps server the user pairs it with — no third parties. activeTab justification ▎ activeTab is used only when the user clicks the toolbar icon or a Fill/Save action in the ▎ popup. It lets the extension read the current tab's URL to find the matching saved login and ▎ fill it into that page's sign-in form. Tabs are never read in the background. Host permission justification (https://*/*, http://localhost/*) ▎ Host access is optional and granted by the user. It is needed to (1) detect the current ▎ site's domain so the right saved login can be matched and filled, and (2) reach the user's ▎ own StackyOps server. StackyOps is self-hosted, so each user runs it on a different address ▎ (including localhost for local self-hosting); the extension cannot hard-code one host, so ▎ the user grants access to the site(s) they actually use. No data is ever sent to any third ▎ party. scripting justification ▎ scripting is used to fill the user's saved username and password into the sign-in form of ▎ the page they are currently viewing, only when they explicitly click Fill in the popup, and ▎ to read a login form's fields to offer to save a newly typed login. Injection happens only ▎ on user action and only on the active tab. storage justification ▎ chrome.storage.local stores only the extension's own settings: the StackyOps server URL the ▎ user paired with, the device pairing token used to authenticate to that server, the ▎ auto-capture on/off preference, and a short-lived "pending capture" record while a ▎ Save-login prompt is open. It stores no website content and no passwords; vault secrets are ▎ fetched on demand and (for the personal vault) decrypted in memory only. Nothing is synced ▎ anywhere.

Growth

WindowUsersChangeRatingsRating
7 days+1+50.0%00.00

Version history

5 versions recorded
0.4.114 Oct 2026
0.3.1014 Oct 2026
0.3.724 Sep 2026
0.3.017 Sep 2026
0.2.016 Sep 2026

Details

Category
Privacy & Security
First seen
16 Sep 2026
Size
134 KB
Languages
en-GB
Pricing
Free
Privacy policy
stackyops.com
Support
stackyops.com
Extension ID
dcldfcflacgnfkbdhcmaijfhchcgklio

Permissions and risk

Moderate riskimpact 2, likelihood 3
Permissions
storageactiveTabscriptingtabswebAuthenticationProxysidePanel

Alternatives to StackyOps Vault

Extensions that rank for the same store searches or share the Privacy & Security category, ordered by users