Summary
The component is intentionally small and that should stay true, but it may be worth expanding the fixed rule set with a very small number of additional probe patterns that are both common and low-risk in normal Symfony applications.
Candidate patterns
/.env
/xmlrpc.php
/wp-login.php
/vendor/phpunit
/phpunit
/.git/
/.svn/
Constraints
- Keep the package easy to audit.
- Prefer exact prefixes or very narrow markers.
- Avoid broad heuristics for SQL injection, XSS, traversal, or generic payload detection.
- Add a dedicated PHPUnit test for each new rule.
- Document each rule briefly in
FEATURES.md and armonic-docs if it is accepted.
Notes
The value of this package is simplicity. New rules should only be added when they are clearly recurring attack probes and have a very low false-positive risk.
Summary
The component is intentionally small and that should stay true, but it may be worth expanding the fixed rule set with a very small number of additional probe patterns that are both common and low-risk in normal Symfony applications.
Candidate patterns
/.env/xmlrpc.php/wp-login.php/vendor/phpunit/phpunit/.git//.svn/Constraints
FEATURES.mdandarmonic-docsif it is accepted.Notes
The value of this package is simplicity. New rules should only be added when they are clearly recurring attack probes and have a very low false-positive risk.