ShareClean: local-first CLI to clean logs before sharing

Hi, I’m the author of ShareClean.

It’s a small Python CLI for cleaning logs, stack traces, config snippets, and terminal output before pasting them into GitHub issues, support tickets, Slack, support threads, or AI chats.

Example:

cat app.log | shareclean --report

Input:

user=user@example.com
password=fake-secret-value
postgresql://app:fake-pass@db.example.com/app

Output:

user=[EMAIL REDACTED]
password=[REDACTED]
postgresql://app:[REDACTED]@db.example.com/app

Why I made it:

I kept seeing people paste debug output that accidentally included tokens, local paths, emails, or connection strings. ShareClean is meant to be a quick local safety pass before sharing text publicly.

A few details:

  • Local-first, no network calls
  • No telemetry
  • No runtime dependencies
  • Redacts passwords, API keys, bearer tokens, JWT-like values, emails, local user paths, and optionally private IPs
  • Has --check mode for scripts, hooks, and CI

This is not trying to replace full repo secret scanners like gitleaks or trufflehog. It’s for the smaller everyday moment where you’re about to paste logs somewhere and want to clean them first.

GitHub: https://github.com/OmarH-creator/ShareClean

Browser demo: https://omarh-creator.github.io/ShareClean/

I’d appreciate feedback from people who use CLI tools often: does the workflow make sense, and are there redaction rules you’d expect in a tool like this?

github.com
u/JewelerBeautiful1774 — 5 days ago
▲ 48 r/PythonProjects2+3 crossposts

ShareClean: a local-first CLI to redact sensitive info from logs before sharing

Hi r/commandline, I’m the creator of ShareClean.

It’s a small Python CLI for cleaning logs, stack traces, config snippets, and terminal output before pasting them into GitHub issues, support tickets, Slack, support threads, or other public places.

ShareClean is meant to be a quick local safety pass before sharing text publicly.

Example:

cat app.log | shareclean --report

Input:

user=user@example.com
password=fake-secret-value
postgresql://app:fake-pass@db.example.com/app

Output:

user=[EMAIL REDACTED]
password=[REDACTED]
postgresql://app:[REDACTED]@db.example.com/app

Why I made it:

I kept seeing people paste debug output that accidentally included tokens, local paths, emails, or connection strings. ShareClean is meant to be a quick local safety pass before sharing text publicly.

A few details:

  • Local-first, no network calls
  • No telemetry
  • No runtime dependencies
  • Redacts passwords, API keys, bearer tokens, JWT-like values, emails, local user paths, and optionally private IPs
  • Has --check mode for scripts, hooks, and CI

This is not trying to replace full repo secret scanners like gitleaks or trufflehog. It’s for the smaller everyday moment where you’re about to paste logs somewhere and want to clean them first.

GitHub: https://github.com/OmarH-creator/ShareClean

Browser demo: https://omarh-creator.github.io/ShareClean/
(Demo is just to show the redaction behavior. Real use is local CLI.)

I’d appreciate feedback from people who use CLI tools often: does the workflow make sense, and are there redaction rules you’d expect in a tool like this?

u/JewelerBeautiful1774 — 5 days ago

WHAT IS GOING ON?!

Can someone explain what’s happening here? The screen looks completely black in a dark room when it is sleeping, but when I shine a flashlight on it, I can still faintly see what was displayed before it turned off.

u/JewelerBeautiful1774 — 2 months ago