Add ClamAV-compatible exit codes for CI/CD integration #216
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Create constants.py with EXIT_CLEAN=0, EXIT_UNSAFE=1, EXIT_ERROR=2 - Update cli.py to use symbolic constants instead of literal values - Export constants from package for programmatic use This follows the ClamAV convention for scan results, making fickling easier to integrate with CI/CD pipelines and other security tools. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
constants.pywith ClamAV-compatible exit codes:EXIT_CLEAN = 0- No issues foundEXIT_UNSAFE = 1- Potentially malicious content detectedEXIT_ERROR = 2- Scan error (parse failure, file not found, etc.)cli.pyto use symbolic constants instead of magic numbersWhy ClamAV convention?
ClamAV is a widely-used antivirus tool with established exit code conventions.
Following this convention makes fickling easier to integrate with existing
CI/CD pipelines and security tooling that already understands these codes.
Test plan
🤖 Generated with Claude Code