cliprooflisted

# Cliproof — prove your CLI actually runs Turn a **real** command and its **real** output into a styled terminal image (or animated GIF) and embed it into `README.md`, so GitHub visitors get instant confidence the project works. The whole value is honesty: cliproof captures genuine execution, never a mock-up. ## When to use - Capture a screenshot of a command + its output in a styled terminal (macOS/iOS traffic-light bar, Windows-style chrome, or a theme). - Record an animated terminal demo (typing + live output) as a GIF. - Add visual "proof it works" evidence to a `README.md`, docs page, or release notes. ## Core principles (do not violate) 1. **Never fabricate output.** Always run the real command and capture what actually happens. A faked screenshot is worse than none. 2. **Redact secrets before anything is written to disk or the README.** This is enforced by `scripts/redact.py`, not left to judgement. 3. **Guard the command before executing it.** Run it past `scripts/guard.py`; never capture a destructive or clearly unsafe command. 4. **Confirm before installing tools, before writing README.md, and before committing.** 5. **Stay local.** Cliproof never transmits captured output anywhere. It only reads/writes files in the user's repo. ## The two capture tools cliproof uses [Charm](https://charm.sh) CLIs that run a real command in a pseudo-terminal and capture genuine ANSI output. | Need | Tool | Output | Platforms | |---|---|---|---| | **Static screenshot** (default)