This directory contains the configuration files for the automated validation system.
Defines best practices and coding standards validation rules.
Categories:
- Code Quality
- Security
- Documentation
- File Management
- Testing
- Git Hygiene
- Performance
- Dependencies
Defines security vulnerability detection patterns.
Categories:
- Authentication
- Injection (SQL, XSS, Command)
- Data Exposure
- Cryptography
- File System
- Network
- RegEx (ReDoS)
- Dependencies
Related (Node backend): best_practices.json includes BP-SEC-011 — do not import axios directly under backend/; use backend/utils/safeAxios.js (CWE-113 / CodeQL-aligned outbound header hardening).
Tracks project-specific security learnings and patterns discovered over time.
Contains:
- npm audit history
- Security incidents
- Best practice updates
- Project-specific notes
./test_cases/scripts/validate_best_practices.sh./test_cases/scripts/update_best_practices.sh- Edit
best_practices.jsonorsecurity_rules.json - Add rule to appropriate category
- Test:
./test_cases/scripts/validate_best_practices.sh - Commit changes
{
"id": "CATEGORY-TYPE-###",
"name": "Rule name",
"severity": "critical|error|warning|info",
"pattern": "regex pattern",
"exclude": ["patterns to exclude"],
"message": "User-friendly message",
"autoFix": false
}- Critical: Blocks commit, immediate security risk
- Error: Blocks commit, must be fixed
- Warning: Doesn't block, should be fixed
- Info: Informational only
See docs/QUALITY_ASSURANCE.md — Part 4: Validation System — for complete documentation.
- Review rules: Quarterly
- Update patterns: After security incidents
- Check npm audit: Weekly
- Refine exclusions: As needed
Last Updated: April 2026
Version: 1.9.0