DevSafe Backup AI Safety Lockbox
Free Tools Pricing
Blog Docs Architecture Changelog Trust Center Risk Check New
Log in Sign up →

Free Tool

One score for
everything

Cloud sync exposure. Git state. Backup coverage. AI secret leaks. One number tells you if your repos are protected -- or not.

$ npx devsafe health click to copy

See it in action

What a real health check looks like on a developer's machine.

42
Health score
Below 30 is red. Above 80 is green. Your average is 42.
2
Active risks
Cloud sync and AI exposure are happening right now.
2
Warnings
No encrypted backups and stale git state. One bad day away.
$0
Free forever
No account. Runs locally. Three seconds. You keep the results.

What this means

Most developers check one thing at a time. Is my repo backed up? Is my .env safe? Is my git clean? devsafe health checks all of them at once and gives you one number. Below 30 means something is actively wrong. Above 80 means you are protected. Each factor -- cloud sync, git state, backup coverage, AI secret exposure -- contributes to the score.

Fix it

Go from 42 to 95+ in under 5 minutes. devsafe setup walks through fixing each risk factor -- encrypt, back up, shield. One command to protect everything.

devsafe setup

Newsletter

Stay ahead of threats

Research, threat intel, and tutorials. We only publish when we have something worth your time.

No spam. Unsubscribe anytime.

What topics interest you?

Threats
Tutorials
Engineering
AI Security
Product
Everything

Skip this step

Other free tools

devsafe scan

Find repos in cloud sync danger zones. One command shows which repos are at risk.

devsafe diagnose

Find secrets your AI tools can read. Scans for exposed API keys, tokens, and credentials.

devsafe mcp-scan

Audit your MCP configs for secrets. Finds API keys in Claude, Cursor, and VS Code configs.

devsafe lockbox

Encrypted secret vault. Import .env files, inject at runtime, share with time-limited grants.