Reports

FlowMind includes a complete reporting system that exports test results as structured reports for recording, sharing, and archiving.

Reports Page

The reports page is organized into 5 tabs:

Tab	Function
Overview	Dashboard with finding stats, material count, memo count, exported reports
Findings	Full findings browser with filtering, batch operations, per-occurrence management
Materials	Clipping management, supports free-form notes and flow/finding references
Memos	Rich text memo editor
Generate	Select format and export, manage exported files

Report Formats

Format	Description	Use Case
HTML	Self-contained directory (index.html + assets/)	Recommended — open directly in browser with interactive navigation and styling
PDF	Printable document format	Formal delivery, print archiving
JSON	Structured data format	Programmatic processing, secondary analysis

HTML Report Demo

Exporting Reports

Steps

1. Go to Reports → Generate tab
2. Select export format (HTML recommended)
3. Choose save location:
   • Default report directory: saves to workspace reports/{project-id}/
   • Choose other directory: system dialog to pick any directory
4. Wait for completion; the report directory opens automatically

Report Structure

Section	Content
Cover	Project name, description, target URL, generation time, tool version
Executive Summary	Overview stats (requests, domains, findings, severity distribution, status distribution)
Assessment	Target URL, scope, accounts, period, assessors
Traffic Profile	Protocol composition, method distribution, status code distribution, Top 10 hosts, Top 10 paths
Findings	Findings grouped by source (Scan/AI/Manual) and severity
Domains	All involved domain names
Attachments	Tool version, plugin list, project notes, clippings, memos, note attachments

Finding Management

Findings Browser

In Reports → Findings tab:

• Search: keyword search
• Severity filter: High / Medium / Low / Info
• Status filter: Open / Confirmed / Fixed / Ignored
• Batch operations: batch delete, delete all
• Expand details: description, recommendation, affected URL list

Per-Occurrence Management

Each occurrence of a finding can be managed individually:

• Status: confirmed, fixed, ignored
• Notes: add custom remarks
• Add to materials: add finding to report materials
• View related Flow: navigate to the associated request

Finding Sources

Each finding is labeled with its source:

Source	Description
Scan	Auto-detection from built-in rules or plugins
AI	Findings generated by AI security analysis
Manual	Manually created findings

Clippings

Clipping Types

Type	Description
Flow	Request captured from the forwarder
Finding	Security finding record
Note	User-created free-form note

Adding Clippings

1. From Forwarder: right-click request → Add to Materials
2. From Findings: in finding details, click Add to Materials
3. Manually: in the Materials tab, fill in title and content

Managing Clippings

In Reports → Materials tab:

• View all clippings (card-style layout)
• Reorder with move up/down
• Edit title and content
• Delete clippings

Memos

Using Memos

In Reports → Memos tab:

1. Sidebar lists all memos
2. Click a memo to view or edit
3. New memo: fill in title and rich text content
4. Delete unwanted memos

Use Cases

• Record testing ideas and findings
• Hypotheses to verify
• Test plans
• Report-related notes

HTML Report Details

An HTML report is a self-contained directory:

report-{project-name}-{timestamp}/
├── index.html          # Main page
└── assets/
    ├── report.css      # Stylesheet
    ├── report.js       # Interactive script
    └── notes/          # Project note attachments

HTML Report Features

• Sidebar navigation: quick jump to sections
• Scroll spy: auto-highlights current reading position
• Filtering: filter findings by severity and status
• Print optimized: supports print-to-PDF
• Responsive design: readable on desktop and mobile
• Self-contained attachments: project note files embedded

Best Practices

Report Content

1. Include key findings: ensure important findings are in the report
2. Add context: use clippings and memos for supplementary information
3. Project notes: write test instructions and conclusions in the project

Format Selection

1. Formal delivery: use HTML (recommended) or PDF
2. Technical exchange: use JSON format
3. Internal records: HTML is the most intuitive

Workflow Suggestions

1. Add clippings via right-click during testing
2. Record test ideas in memos as you go
3. Generate the final report after testing is complete
4. Use the default report directory for easy management