Built from real tests
The report is only as good as the testing behind it. Every section comes from assessments that ran against your app: passive checks that need no permission, active scanning and pen testing on domains you have verified, and a threat model built from your own code. Nothing is filled in from a template.
For the people who fix it
Most VAPT reports end up in a compliance folder. This one is built so a developer can pick up any finding and act on it: the evidence, the affected page and the remediation are all there, and the same findings are waiting in CodeReviewer as issues that can become fix pull requests.