Where do I see how many lines of code a scan analysed?

Steps

Lines of code is a measure of how much of your repository the scan read.

1. Go to Recent Scans. Choose it in the sidebar.
2. Click the scan. The detail page opens on Overview.
3. Find the Results card. It holds the donut chart.
4. Read the footer. Lines of code sits beside Tokens consumed and Cost.
5. Check the scan type. A dash means black-box.

Good to know

The figure appears only when the scan has source to count. A white-box run reads your Git repository, so it has a number. A black-box run tests the live URL only, so the field shows a dash.

While a white-box scan is running, the live counter shows the lines of code so far. Press Refresh to update it.

A dash on a white-box scan deserves a look. Check that the target has a repository and that the scan ran past the first phase. Our page on why lines of code shows a dash goes through it.

What the number tells you

A large figure means the scan had a lot of code to read, which often means a longer run and a higher cost. A figure far below what you expect can mean the repository or branch on the target is not the one you meant. Targets cannot be edited, so delete and recreate one to fix that.

Use the figure to sanity check scope. If you scan a large repository and the count looks tiny, the branch field on the target may point at the wrong branch, or the repo may hold only part of the code. Check early.

Related questions

• Why does Lines of code show a dash on my scan?
• Where do I see how much a scan cost and how many tokens it used?
• How do I see which commit a white-box scan tested?
• How do I see the severity breakdown for one scan?
• How long does a scan take?

Full tutorial

The scan detail page: how to read a Cyberlop scan from Overview to Diff

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre