Files
aitbc/.gitea
aitbc1 8467748791
Some checks failed
audit / audit (push) Successful in 9s
ci-cd / build (push) Successful in 9s
ci / build (push) Successful in 7s
autofix / fix (push) Successful in 5s
ci-cd / deploy (push) Has been cancelled
ci / deploy (push) Has been cancelled
test / test (push) Has been cancelled
security-scanning / audit (push) Has been cancelled
fix: correct bandit command syntax for proper argument handling
BANDIT SYNTAX FIX: Use correct --confidence-level argument

Issue: bandit error 'unrecognized arguments: high'
Root cause: Incorrect argument syntax --confidence high
Correct syntax: --confidence-level high

Changes:
- Update all bandit commands to use --confidence-level high
- Maintain quiet mode (-q) and JSON output (-f json)
- Keep recursive scanning (-r .) for comprehensive coverage
- Ensure proper argument order for bandit CLI

Updated workflows:
- security-scanning.yml: Correct bandit syntax
- All workflows with bandit: Updated to proper syntax

Expected results:
- Bandit scans run without argument errors
- High confidence security issues detected
- Clean JSON output for potential integration
- No more 'unrecognized arguments' errors

This ensures bandit security scanning works correctly
with proper CLI argument syntax.
2026-03-27 14:59:30 +01:00
..