Feedback
We value your feedback during the public test period.
What to report
| Type | Description |
|---|---|
| False positive | A finding that is not actually an issue |
| Missed issue | A real issue CODYGIENE did not detect |
| Crash | The CLI crashed or produced an error |
| Installation problem | Could not install or run the CLI |
| Performance problem | Scan was too slow or used too much memory |
| Documentation problem | Documentation was unclear or incorrect |
| Feature request | A new rule, framework, or feature you'd like |
Minimal information to include
- CODYGIENE version ·
codygiene --version - Node.js version ·
node --version - Operating system · Windows, macOS, or Linux (and version)
- Stack/framework · Next.js, Supabase, Prisma, etc.
- Rule ID · if the feedback is about a specific finding (e.g., CAND-025)
- Short description · what happened, what you expected
What NOT to include
You do not need to share:
- Source code or snippets
- Private repository access
- Repository URLs
- Personal information
If a false positive report requires context, describe the pattern generically (e.g., "redirect target is validated against an allow-list defined in a separate module").
How to submit
During the public test period, submit feedback through:
- GitHub Issues (if the repository is public)
- Email (if provided with your test invitation)
- The feedback channel specified in your test invitation
What happens to feedback
- False positives are reviewed and may result in rule refinement
- Missed issues are evaluated for future rule candidates
- Crashes and installation problems are treated as priority fixes
- Feature requests are added to the backlog
Thank you for helping improve CODYGIENE.
Spotted something wrong or missing? Send feedback