30-second self-assessment

Is your code at risk?

5 questions, answer them, and most fail at least 3.

Question 1 of 5

Are your git repos backed up somewhere other than GitHub?

GitHub is a hosting service, not a backup. If your account is suspended, compromised, or GitHub has an outage, can you recover your code from somewhere else?

DevSafe fixes this. Every repo on your machine, encrypted and backed up to storage you own. Not another copy on someone else's server. One command. devsafe backup --all

Question 2 of 5

Is your code encrypted before it leaves your machine?

GitHub "private" repos are not encrypted. Your hosting provider can read them. If you push to any remote, that provider has your source code in plaintext.

DevSafe fixes this. AES-256-GCM on your machine, before anything uploads. Your keys never leave. Your storage provider sees encrypted blobs, not your source code.

Question 3 of 5

Can you recover uncommitted work if your machine dies today?

Everything between commits lives only on your local disk. Staged changes, work in progress, stashed experiments. If your drive fails, that work is gone.

DevSafe fixes this. It captures everything you have not committed yet. Staged changes, untracked files, stashes, a half-finished rebase. No commit. No change to your repo.

Question 4 of 5

Are your AI tool configs free of hardcoded API keys?

Claude Desktop, Cursor, VS Code, and Cline store MCP credentials in plain JSON. No encryption, no keychain integration. 1 in 31 public MCP configs on GitHub leak real secrets.

DevSafe fixes this. devsafe mcp-scan finds every hardcoded secret in every MCP config on your machine. Then shows you how to fix each one. Free.

Question 5 of 5

Is your .git directory protected from cloud sync corruption?

iCloud, Dropbox, OneDrive, and Google Drive corrupt .git directories through documented mechanisms. Lockfile races, partial pack writes, ref pointer overwrites. Git's own FAQ warns against it.

DevSafe fixes this. It reads directly from git, not the filesystem. Cloud sync never touches the backup, so it cannot corrupt it. Your .git stays untouched.

0/5

Your protection score

Which sounds most like you?

Your fix plan adapts to your situation.

Your fix plan

Step 0: Install DevSafe

One command. No dependencies.

curl -fsSL https://devsafe.com/install | sh

You're in

Here's your fix plan. Run these in your terminal.

Sources

1,722 MCP configs scanned GitGuardian 2026 Git FAQ

Built by DevSafe. Your keys. Your bucket. Your proof chain.

Is your code at risk?

Which sounds most like you?

Your fix plan

Start fixing

You're in