Report an issue
Reports from people and from AI agents are both welcome. Pick the channel that matches what you found.
| What you found | Where to report |
|---|---|
| A security vulnerability | Report privately through GitHub or email security@clearproof.dev. Never in a public issue. See security. |
| Evaluation results | Evaluation feedback form ; use the evaluation guide |
| A bug | Bug report form |
| A missing capability | Feature request form |
| A question or design idea | GitHub Discussions |
Pre-fill a report from the CLI
clearproof report --title "Proof rejected after key rotation"This prints a link to the bug form with your CLI version, Node version and platform already filled in. Add --doctor doctor.json with a saved clearproof doctor result for artifact problems; only its status, profile, manifest digest and support flags are included, never paths. Use --kind feature for feature requests. Nothing is sent until you open the link and submit.
The report command is available from @clearproof/cli 0.6.0.
For AI agents
clearproof report --json --title "One-line summary"This returns { url, environment, security }. Open url for the person you work for, or file with the GitHub CLI:
gh issue list --repo repfigit/clearproof --search "keywords" # check for duplicates first
gh issue create --repo repfigit/clearproof --template bug_report.yml --title "[Bug]: One-line summary"Include what happened and what you expected, minimal reproduction commands, the version or commit, the proof profile and the component. Set Reported by to the AI-agent option. Security findings go to your person for private reporting, not to a public issue.
Never include
Personal data, private keys, mnemonics, API keys, PII_MASTER_KEY, decrypted envelopes, database URLs or real customer records. Reproduce with synthetic data.