Fixes and verification
Review a change before approval and verify afterward.
Review the proposed change
Eligible repository findings can have a prepared fix. Review the files, reason, validation and known limitations before approving. A website-only scan does not grant access to change its source code.
Follow the real status
Requested, preparing, ready for review, applied and verified are different states. An applied fix still needs verification. Filter fixes by platform and status; batch application targets only visible ready fixes. Undo is available for supported delivered GitHub changes.
Review before granting approval
A prepared fix is a proposed change, not an assurance that every consequence is understood. Inspect the diff, changed files, rationale and validation results. Automated or AI-generated changes require the same review standards as human changes. An external-only finding may need a hosting or application change outside Hackaiz.
- Check the finding and the intended protection.
- Review changed files and potential effects on legitimate users.
- Use the project’s tests and approve only the change you understand.
Delivery, deployment and verification are separate
A GitHub pull request establishes that a change was delivered for review. Merging changes the repository; deployment updates the running application. Verified means a relevant check was performed in its stated context, not that the entire platform passed a full audit. A failed preparation is different from a delivered pull request with later verification trouble.
Individual approval and rollback
Correction filters define the visible platform and status scope. Publication is approved individually after reviewing the exact preview. Check pending and failed items separately. Hackaiz does not merge or undo changes. Review an exact preview, approve publication individually, then handle any merge or rollback in GitHub. External settings and databases are never directly modified.
- Filter to the intended platform and ready status.
- Review each eligible preview separately.
- After deployment, rerun the relevant check and normal user workflow.
Sources and further reading
These publications describe related practices and standards. They do not certify your platform or imply that Hackaiz executes every documented method.