AuditScan — code audits with file-line evidence
By DestroCorp · Live at auditscan.sh. Static analysis over your code — findings cite the exact file and line.
How it works
- Point at code — a folder or a git URL.
Scans read code only; nothing is executed. - Review findings — each finding cites
file:linewith an explanation.
Covers dead handlers, untested risky functions, and user input reaching shell or SQL. - Recheck after fixes — rescan to confirm findings are resolved.
Includes a PR merge gate, a compliance overview and a triage board.
Scope: AuditScan is static analysis. It does not guarantee code is vulnerability-free and is not a compliance certification. It does not replace manual security review. Liability is capped to fees paid (see Terms).
Frequently asked questions
Is this pull request safe to merge?
The PR merge gate rescans the changed files. If the cited findings no longer appear, the gate passes; otherwise it lists the lines still to fix.
Does AuditScan certify compliance?
No. It shows which parts of common frameworks relate to your code and links each item to a file and line. It is not a certification or legal opinion.
What data do you retain from scans?
Repository file names and scan results, retained until you delete them. Request erasure anytime via grievance@destrocorp.com.