Keep Symfony object authorization before the order write: Perch rule pack
1 saved requirement for Symfony. Inspect the selectors and adapt the example paths to your repository.
- name: order-voter-before-mutation
where: "src/Controller/CancelOrderController.php"
ensure: >-
CancelOrderController must call denyAccessUnlessGranted with ORDER_CANCEL and the loaded order before changing or flushing its status.
Download the rule pack ZIP · Download YAML · Agent repair task · Implementation, integration requirements and captured checks
Install the rule without replacing your configuration
npm install -g @lakeday/perch
perch login
curl -fL 'https://reporules.fyi/symfony/object-voter-before-write/rule-pack.zip' -o 'perch-guide-symfony-object-voter-before-write.zip'
unzip -n 'perch-guide-symfony-object-voter-before-write.zip'Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-symfony-object-voter-before-write.yaml. Review each where selector before running a check on your application.
Configure your coding agent
perch setup claude-code
perch setup codex
perch setup cursor
perch setup piChoose the setup command for the agent you use.
Check the edit, fix the finding, check again
perch check src/Controller/CancelOrderController.php --rules order-voter-before-mutation --jsonRun the check after an agent edit. Read the finding and affected code, repair the implementation, and repeat the identical command. Keep the application regression tests as separate gates.
Exit 3 means a finding. Exit 1 or 2 means the check did not complete. A pass does not prove application correctness. Fresh judgments can vary; unchanged requests reuse cached answers. Relevant source is sent to the configured model service.