As described in EPI-712 frontrunning is possible against deployProxyAndDistributeBySignature, but your implementation looks solid and preventing any side effects for the smart contract itself (so the web3 part of your application), but is your UI/web2 back-end ready for such behavior?
This is just to highlight that you ensure the other part of your dApp will handle this case in a smooth manner, as your original transaction would revert in favor for the front-runner.
Original transaction calling deployProxyAndDistributeBySignature will revert if successfully front-run, please ensure that your dApp handle this case properly.
Code examination
Just be aware of this and prepare to handle it accordingly.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.