Skip to main content

Audit View

The Audit View provides a comprehensive interface for reviewing, triaging, and managing security findings.

Three-Panel Layout

The audit view uses a three-panel design optimized for efficient review:

┌────────────────┬─────────────────────┬────────────────┐
│ │ │ │
│ Findings │ Code View │ Details │
│ List │ │ Panel │
│ │ │ │
│ • Filter │ • Syntax │ • Description │
│ • Sort │ highlighting │ • Severity │
│ • Select │ • Line numbers │ • Remediation │
│ │ • Annotations │ • References │
│ │ │ │
└────────────────┴─────────────────────┴────────────────┘

Left Panel: Findings List

All findings for the current project, filterable by:

  • Severity: Critical, High, Medium, Low
  • Status: Open, In Progress, Resolved, Ignored
  • File: Specific contract files
  • Pattern: Vulnerability type

Click a finding to view it in context.

Center Panel: Code View

Source code with:

  • Syntax highlighting for Solidity/Vyper
  • Line numbers linked to findings
  • Annotations showing affected lines
  • File navigation via breadcrumbs

The vulnerable code is highlighted with severity-colored markers.

Right Panel: Details

Selected finding details:

SectionContent
SummaryBrief description of the issue
SeverityRisk level and confidence score
LocationFile path, line number, function
ImpactWhat could go wrong
RemediationHow to fix it
ReferencesRelated vulnerabilities, CVEs
AI NotesLLM verification commentary

Working with Findings

Triage Workflow

  1. Review - Read the finding details
  2. Verify - Check the code in context
  3. Decide - True positive or false positive?
  4. Act - Fix, assign, or dismiss

Status Options

StatusMeaning
OpenNew finding, needs review
In ProgressBeing worked on
ResolvedFixed in code
IgnoredFalse positive or accepted risk

Bulk Actions

Select multiple findings to:

  • Change status
  • Assign to team member
  • Add tags
  • Export selection

Adding Comments

Document your analysis:

  1. Click Add Comment on a finding
  2. Write your notes (supports Markdown)
  3. Optionally mention team members with @username
  4. Comments are visible to all project members

Keyboard Shortcuts

ShortcutAction
j / kNavigate findings (down/up)
oOpen selected finding
sToggle status dropdown
aAssign finding
dDismiss as false positive
/Focus search
?Show all shortcuts

Code Navigation

Jump to Definition

Click function or contract names to jump to their definitions.

Cross-References

View where a function is called from or what it calls:

  1. Right-click on a function name
  2. Select Find References or Go to Definition

File Tree

Browse all analyzed files:

  1. Click the folder icon in the code panel
  2. Navigate the file tree
  3. Click a file to view its contents

Comparing Scans

Compare findings between two scans:

  1. Click Compare in the toolbar
  2. Select two scan dates
  3. View:
    • New findings (in latest only)
    • Resolved findings (in older only)
    • Unchanged findings

Exporting Findings

Export findings for external tools or reports:

Export Options

  • PDF Report - Formatted security report
  • CSV - Spreadsheet-compatible
  • JSON - Machine-readable
  • SARIF - GitHub Security compatible
  • Markdown - Documentation-friendly

Export Scope

  • All findings
  • Filtered findings (current view)
  • Selected findings only

Integration with IDEs

Open findings directly in your IDE:

VS Code

  1. Install the FirePan VS Code extension
  2. Click Open in VS Code on any finding
  3. File opens at the exact line

JetBrains IDEs

Similar integration available for IntelliJ/WebStorm.

Next Steps