Why an analysis is partial
The real reasons a report does not cover everything, and what to do.
Common causes
Credits ran out during the analysis (the most frequent cause): work already done is kept and the report shows what was not examined. Access is missing: without a connected repository, code checks cannot run; without a database connection, database checks stay marked as not run. Some checks were unticked: they are neither run nor billed.
What to do
Buy credits from the pause banner: resuming continues from the last saved point when it is still valid; otherwise a new analysis is needed. Connect the missing access (GitHub, database) for more coverage. A partial report is still useful: its findings are real, but it does not prove the rest is secure.
Is your AI app protected?
Create your account with free credits, prove your domain, then get a report with evidence and priorities.
Read the coverage section
Each report separates what was examined, what was not run and why. A check marked not run is neither a pass nor a failure.
Nothing is lost
Findings already produced stay in your report and history. Credits are only used for work actually done.
Ask the Pilot
The Pilot can explain why your analysis stopped and what the next step is; launching or resuming still requires your click.
Is your AI app protected?
Create your account with free credits, prove your domain, then get a report with evidence and priorities.
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.