#093Tutorial4 min
View analysis history
Find earlier runs, reopen their reports, and read dates, versions, status, and changes without confusing history with current security.
Hackaiz team · updated 21/11/2026

01Start with the right project
An analysis is a record of a particular run, not a permanent verdict about your application. To investigate an earlier release, identify the project first. The Monitored projects screen has a Search platforms field with the placeholder “Name, repository or address…”. Search using the repository or website address when several applications have similar names. The list shows the latest report status and when the project was scanned; that summary is not the complete history.
Opening a project card takes you to its latest available report when one exists, or to analysis setup otherwise. For the chronological list, use the project detail page, which has a Scan history section. Do not assume that the report opened by a card is the run you are looking for. Match the target and the release before drawing conclusions about an old incident.
02Read the information on each run
Each row in Scan history shows a status badge, the project version, the start date and time, and a finding count. Open a row to read that run’s report. A version and a timestamp together are a better reference than “the scan from last week”, especially when several checks were launched close together. Record both in your own release or incident notes so a colleague can identify the same evidence.
The list also compares each row’s finding count with the next older row. A positive or negative number is a difference in counts, not a list of newly introduced or repaired vulnerabilities. “Unchanged” means those counts match. One issue could disappear while another appears, leaving the total unchanged. Read the actual findings and the comparison on the project page rather than interpreting this small number as proof of remediation.
- 1Find the intended project and open its detail page.
- 2Locate Scan history and match the version, timestamp, and status.
- 3Select the matching row to reopen the report.
- 4Check the report’s findings and executed checks before using it as evidence.
03Keep incomplete runs in context
History includes runs with different statuses. A partial analysis is useful evidence of what was checked, but missing coverage must not become a clean bill of health. If a report has fewer findings, first ask whether the same target and checks were examined. An unavailable service, changed permissions, or a narrower selection can change what a run is able to observe. Use the report’s execution information rather than the count alone.
The project page also offers Compared with the previous scan. Read the dates shown there and distinguish that comparison from the count difference in the history list. The interface can label a missing finding Proven fixed; for a release decision, confirm that the relevant check ran under comparable conditions. For example, a previously exposed page that is no longer reachable needs context: it may have been removed intentionally, or the tested environment may simply be unavailable.
04Use history as a working record
For a handover, note the target, version, run time, reported problem, corrective action, and the later run used to check that action. This is a recommended record you keep with your team, not a claim that Hackaiz supplies a complete incident-management system. Reopening an old report helps explain what was observed then; it cannot establish the state of code deployed after that run.
Be careful with project deletion. The deletion dialog warns that scans, findings, fixes, proofs, and history entries for that project will be removed. Do not use Delete to hide an obsolete result that you still need for traceability. A fresh analysis is a separate credit-consuming action. For a website or API, domain ownership proof remains mandatory before analysis, including a later verification run; an old report is not a substitute for that authorization.
Frequently asked questions
Take the next step
Was this article helpful?