Where to find reports
- One scan. The Findings by OWASP and CWE category section of a completed scan, which you open from the Security page.
- Your workspace. The Compliance page, next to Security in the sidebar, brings together the latest scan of every repository in the workspace, and the findings fixed in the period you pick under Fixed in the period: 30 days, 90 days, or 12 months.
What each category shows
For every category of the standard, the report counts the following, and Findings in this category lists the findings behind the counts:- open findings;
- findings your team marked Not exploitable or False positive;
- accepted risks, each with the date it ends;
- on the workspace page, findings fixed in the period.
Fixed or no longer reported
A finding counts as fixed only when a later scan shows it went away: its file was deleted, or the analyzer that reported it ran on that file again, completed, and no longer reports it. A finding that went away for another reason, for example because an analyzer did not complete, a rule was removed, or Veridical’s analyzers changed, is recorded as no longer reported, with the reason, and reports leave it out. It is never counted as fixed.Categories with no open findings
Each category also shows how many rules in the scan’s rule set map to it, so an empty category never reads as a clean result:Counts can overlap
Weaknesses map to categories many to many, so one finding can count in two categories, and the category counts can add up to more than the number of findings.How findings map to categories
- A finding’s CWE ids come from the rule or the advisory that reported it. A more specific weakness counts under a mapped parent, following CWE’s own relations.
- OWASP Top 10 2021 uses MITRE’s CWE view of it (view 1344). OWASP Top 10 2025 uses OWASP’s own list of weaknesses for each category, pinned to a version that the report header names. CWE Top 25 2025 uses MITRE’s view 1435.
- Some findings have a fixed mapping. Exposed secrets map to CWE-798, use of hard-coded credentials. Vulnerable dependencies map to A06:2021 Vulnerable and Outdated Components and A03:2025 Software Supply Chain Failures, plus the CWE ids the advisory lists. Configuration checks map to Security Misconfiguration (A05:2021 and A02:2025).
- For scans from before analyzers recorded CWE ids, Veridical derives them from each rule’s title and from known rule ids, so reports work on existing scans too.
Coverage statement
Below the category table, each report says what was checked, under What was checked. The report of one scan lists the analyzers and languages that ran, data flow across files, any analyzer that ran only in part or did not run, and the kinds of weakness static analysis cannot see. The workspace report lists the analyzers behind its findings and the kinds of weakness static analysis cannot see; open a scan’s own report for what that scan ran in full. Read the counts with it.Mark findings
Workspace owners and admins, and members with permission to manage repositories, can mark a finding from its detail on the Security page: Mark not exploitable, Mark false positive, Accept risk until a date at most a year ahead, Confirm, or Reopen. A decision applies to that one finding at its place in the code, and reports count it at once. An accepted risk counts as open again after its date.Export a report
Only decisions your team made become SARIF suppressions. If you upload the SARIF
file to GitHub code scanning, a tool that acts on suppressions may dismiss those
alerts there.
Every report and export ends with its data sources and their licences, and says
that it is not an assessment or certification.
Data sources
- CWE. CWE ids, names, and relations, copyright The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10. A project of the OWASP Foundation, licensed under CC BY-SA 4.0. Reports use its category ids, names, and links only.
- Advisory CWE ids. The GitHub Advisory Database, licensed under CC BY 4.0, read from the public OSV data exports.

