Hi,I built ShareClean after noticing how often debugging output gets shared before anyone checks it for secrets. A common example is a database URL like this: DATABASE_URL=postgresql://app_user:super-secret-pass@db.internal:5432/orders Deleting the full line removes useful debugging context. ShareClean instead produces: DATABASE_URL=postgresql://app_user:[REDACTED]@db.internal:5432/orders The host, port, database name, and surrounding error remain available for troubleshooting while the password is removed. It works on logs, terminal output, stack traces, curl output, config snippets, URLs, and headers. It can also be used through shell pipelines: cat app.log | shareclean --report This is not meant to replace GitHub Secret Scanning, Gitleaks, or TruffleHog. Those scan repositories and history. ShareClean is for the earlier moment: the text you are about to paste somewhere else. Everything runs locally. No account, API key, telemetry, or network calls. I would love practical feedback on fake examples where ShareClean either misses a risky value or redacts too much useful debugging context.

GitHub

Clean sensitive logs before you share them

Clean sensitive logs before you share them