u/Environmental_Fan595

I built a Chrome extension called ShieldVault, and I’m looking for honest feedback.

The first version was mostly API key leak prevention. Reddit pretty much laughed it off.

Fair enough.

A lot of developers already have secret scanners, GitHub warnings, pre-commit hooks, password managers, and the belief that they won’t be the one to do such a thing.

But API keys were only part of the problem. The scope was solid but needed to be expanded.

I considered how much we all type and paste nowadays without thinking. messages that probably needed a second thought before being sent.

So I rebuilt ShieldVault around that broader idea: a browser seatbelt for split-second mistakes.

Right now, it can catch or warn on API keys, tokens, private keys, database URLs, webhook secrets, confidential-looking text, large code blocks going into AI chats, and messages that look like they may have been written too hot.

The extension uses 100% local storage for detection and proof history, ensuring that your secrets, messages, or typed text are never stored or transmitted.

The source is publicly inspectable on GitHub under the Business Source License 1.1.

GitHub: https://github.com/jeffsvendsonjr-jpg/shieldvault-code

The API/secret leak protection is free. The paid side is for people who want more behavioral/pre-send protection.

Since adding the broader online-hygiene layer, it has gotten around 250 installs. Not huge, but enough to suggest the first version was too narrow.

What I’m trying to figure out:

Would this fit into your workflow?

Would you prefer us to continue developing the broader' browser seatbelt' concept or focus mainly on API keys and secrets? Your opinion can shape the future of ShieldVault.

Chrome Store link/official URL: shieldvault.site

I’m grateful for your feedback on what feels useful, unclear, or unnecessary, as it directly influences the product's evolution.

Hey all — looking for some honest answers from folks who manage multiple client sites for a living.

I'm trying to understand a specific failure mode better: the one where the site is technically "up" — homepage loads, returns 200 — but something is actually broken. Contact form silently failing, checkout throwing an error after the button click, a plugin update killing the booking widget, etc. The kind of thing your monitoring doesn't catch because it's looking at the wrong thing.

What are you currently using for uptime monitoring across your client sites? (Doesn't matter if it's UptimeRobot free tier, BetterStack, a homegrown cron, or nothing — just curious what's actually working out there.)
What's the last silent failure that bit you? The one where the client called or emailed you about something broken before your monitoring did. What was it, and how did you eventually find out?
After that happened, did you actually change anything in your monitoring setup — or just kind of move on and hope it doesn't happen again?

Not pitching anything, not selling anything. I'm trying to figure out if a thing I'm thinking about building is solving a real problem, and I'd rather find that out from people doing the work than from my own head.

Happy to share back what I learn if there's interest.

Chrome extension to help combat digital regret