Findings and triage
Work across every repository at once, export to CSV, and dismiss false positives so your numbers mean something.
A report answers "what did this audit find?". The findings explorer answers the question you actually work from: "what is open across everything I own, worst first?"
Scope and filters
By default the explorer shows the newest audit of each repository, which is the current state of your code. Switch the scope to include every audit when you want history instead. On top of that you can filter by severity, by CWE, by repository, and by free text across titles, files and repository names.
CSV export
The export hands you exactly what the filters select, one row per finding, with a link back to the finding in the report. Values that start with a formula character are escaped, so opening the file in a spreadsheet cannot execute anything that came out of the model.
Dismissing a false positive
Not every finding is real, and a list you do not trust is a list you stop reading. Dismiss a finding and it leaves the explorer, the exposure counts on the dashboard and the per-repository severity strip. The count of dismissed findings stays visible, and one click brings them back.
A dismissal is attached to the weakness and the file, not to the wording of the title or a line number. When a later audit describes the same issue in different words, or the code moves down the file, the dismissal still applies. Change the file it lives in, or the weakness class, and it comes back as a new finding — which is what you want.
Dismissals are yours alone. They do not change what the audit found, and the report still shows the finding, marked as dismissed.