Findings
The findings map, the organization and repository inboxes, their views and filters, and what a finding page shows.
Every finding lands in an inbox, where you read it, work on it and close it out.
Map and list
Findings opens on the list. Map shows where the open findings are instead: a card per repository, sized by its open findings and marked with the highest severity among them, holding a box for its default branch and for each branch or pull request a run reviewed that holds findings the default branch doesn't have. In a repository, the map has a card per branch and pull request. The map looks at the 25 branches reviewed most recently in each repository; an older branches entry at the end of the repository's map lists the rest, and opening one shows its findings.
Click a card to see its details beside the map; click it again, double-click, or press Enter to open it. When the window is too narrow for the details, a card opens on the first click, and an N more entry opens its list in place. Arrow keys move between cards, J and K step through them, and Esc closes the details or goes back up.
Map and List above the page switch between the map and the inbox, and V12 remembers your choice: once you pick Map, Findings opens on it wherever it has more than one card.
Organization and repository inboxes
List is your organization's inbox: the findings of every repository in the workspace, each read at its default branch head.
Each repository workspace (/<organization>/) has its own Findings list, at the branch, pull request or commit you pick; see Positions.
A finding's key, such as F-42, is numbered within its organization. Its page is /<organization>/. Each row shows the finding's severity, status, key, title, repository, Steer, assignee and age.
Views, filters and groups
The tabs above the list are views, each with its count.
| View | Shows |
|---|---|
| Open | Findings that are Open or Investigating. The inbox opens on this view. |
| Mine | Open findings assigned to you |
| Unassigned | Open findings with no assignee |
| Last 7 days | Open findings first seen in the last seven days. On a narrow screen the tab reads New. |
| All | Every finding |
On a branch, the findings the branch introduced come first and the rest are under Also found on main (the default branch).
Filter narrows the view by Status, Severity, Steer, Repository, Assignee or Source (Agent or Human). With filters on, the button shows their number, as in Filter (2).
- A view doesn't offer a filter it already applies. Status appears only under All, and Mine and Unassigned leave out Assignee.
- A finding from a run that carried several Steers matches the Steer filter for each of them.
Group by, the icon beside Filter, bands the rows by Status, Severity, Steer, Repository, Assignee or Age. Its tooltip names the current grouping, such as Group by Severity. The menu offers only groupings that split the current rows into more than one band.
- Age bands are This week, This month, This quarter and Older.
- Status bands are Open, Fixed and Closed. Closed holds findings that are Won't fix, Duplicate or False positive.
Your browser remembers your filters and grouping. The inbox has no search box.
To change a finding's status, severity or assignee from the list, see Triage findings. To export the list, use the download icon beside Group by; see Export findings.
The finding page
Click a row to open the finding. From top to bottom, the page shows:
- The title and description.
- The code: a card for each file the finding points to, with its repository, path and commit. If V12 cannot read a file, its card shows only the lines the finding cites and counts the lines it cannot show. A location with no lines to show is listed under Evidence instead.
- PoC and Fix, when the run produced them: the proof-of-concept test and the patch, as cards led by V12's note on what each shows or changes. The test starts folded; Show n lines opens it in place. The fix shows each change with a few lines around it; Show unchanged lines opens the rest of the file in place. A PoC or fix that did not complete says so on its card.
- Activity: the finding's history and comments. The history names the runs, commits, findings and Steers involved: hover one to preview it and open it from there, or choose Reference in a comment in the preview to add it to your comment. Each stretch of repeat detections reads as one line saying how many times V12 found the finding again and in which run last. Write in Leave a comment, and type
@to reference a line, a commit, a run or a finding. Reply answers a comment in its thread.
In a wide window, a rail on the right holds the rest:
- Copy link copies the finding's address.
- Properties shows the status, severity and assignee. Click one to change it; see Triage findings.
- Contents lists the description, each code location, the PoC and fix files, and the activity. Click a row to jump there. The row you're reading is highlighted, and a row whose card you marked Read shows a tick. A finding without a PoC or fix says so. Click Contents to fold the list; your browser keeps it folded on every finding until you open it again.
- Origin lists the repositories, Steers and runs (Run #12) the finding came from, with a commit for each repository. Click a repository or a run to open it.
- Related lists findings linked to this one as duplicates, when there are any.
In a narrower window the rail is hidden. The status, severity and assignee appear as buttons under the title, with chips for the repositories and runs, and Contents opens the same list as a menu.