Why does Lines of code show a dash on my scan?

Why this happens

The Lines of code figure counts the code that a scan analysed. A black-box scan never reads code. It tests the running app at its URL only, so there are no lines to count, and the Results card shows — where the number would be.

A white-box scan clones the repository and reads it. Its card shows a figure instead, such as 57,467 LOC in a scan we captured.

How to fix it

A dash is not an error. You only need to act if you wanted a white-box result, and in that case the fix takes a few minutes.

1. Look at the scan header first. A white-box scan shows Commit in the subtitle and in the Run details card. A black-box scan does not.
2. Go to Targets, click the target and check whether it has a repository URL.
3. If you want code analysed, create a new white-box target with the repository URL and branch. Targets cannot be edited, so you add a new one.
4. Create a scan profile for the new target and press Scan.
5. When the scan finishes, Lines of code shows a number in place of the dash.

Cost and tokens still show on black-box scans. Only the code count stays empty.

Still not working?

If a white-box scan still shows a dash, check that the target really has a repository URL and that the profile belongs to that target. For anything else, send the scan ID to /contact.

To see how the two scan types differ, read white-box and black-box scans.

Related questions

• Where do I see how many lines of code a scan analysed?
• Why is there no commit shown on my scan?
• What's the difference between a white-box and a black-box target?
• How do I see which commit a white-box scan tested?
• What does "No repository configured — add a Git repository URL to run a scan." mean?

Full tutorial

White-box vs black-box scans: how to choose a scan type in Cyberlop

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre