Bitwarden

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Do not build this. And note what makes it unusual: it is already the cheap answer, it is open source, and you can self-host the server without writing a line.

The cryptography has been independently audited. Writing your own is not a project, it is a decision to put every account you own behind code nobody has reviewed. There is no version of this where that is sensible.

WHAT TO DO INSTEAD
- Keep it. If you want the data on your own machines, run the official server or the lighter compatible one — that is self-hosting, not building
- Either way the clients stay the official ones, because the browser extensions and mobile applications are most of the ongoing work and all of the attack surface

WHAT YOU CAN BUILD, AND SHOULD

An auditor over your own vault, using the official command-line tool. A local script, no server, nothing kept:
- Reused passwords, ranked by how much the account matters
- Weak passwords by entropy, and any appearing in a breach corpus, checked with k-anonymity so nothing leaves your machine
- Accounts with no second factor where the service supports one
- Entries whose domain no longer resolves or now redirects elsewhere — a login for a company that was acquired is a login on somebody else's system
- Credentials not rotated in years on accounts that matter
- A short report you act on once a quarter

Unlock the vault, read, report, and clear it. Write the cleanup into the script rather than trusting yourself.

THE THING NOBODY CHECKS
Rehearse recovery. If your phone and laptop both vanished today, could you get back in? Most people have never tested it, and that answer decides whether the manager is protecting you or holding your life hostage. Test it once, write down what you did, and keep it somewhere physical.

THE ONE-LINE VERSION
Self-host the server if you like. Never write the crypto, and go and test your recovery.