Skip to content

Development: Scope codacy security scanners to production code #13202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
krusche merged 2 commits into from
Jul 12, 2026
+18 −0
Merged

Development: Scope codacy security scanners to production code #13202

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aed4fc2
chore: scope Codacy security scanners to production code
krusche Jul 12, 2026
66aecdf
Merge remote-tracking branch 'origin/develop' into chore/codacy-scope…
krusche Jul 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .codacy.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
# Codacy configuration — read by Codacy Cloud from the default branch (develop).
# Scopes security scanners to production code: hardcoded test credentials, non-literal
# fs/regexp in test helpers, and similar security findings in test code are intentional
# fixtures, not vulnerabilities. Other tools (ESLint, Stylelint, PMD) still analyze tests.
engines:
opengrep: # Semgrep — SAST security scanning
exclude_paths:
- "src/test/**"
- "src/test/**/*"
- "**/*.spec.ts"
bandit: # Python security scanning
exclude_paths:
- "src/test/**"
- "src/test/**/*"
- "**/test_*.py"
- "**/*_test.py"
- "**/tests/**"
Loading