Why does my black-box target say "No repository configured"?

Why this happens

The page header reads "No repository configured" for any target without a Git address. You chose Black-box in the New target dialog, where the repo fields turn grey with the help text "Not used for black-box scans." So the target has none, by design.

The longer line under Target details still tells you to add a Git repository URL to run a scan. That wording suits a white-box target, and on a black-box one you can ignore it.

How to fix it

There is nothing to fix. Check these instead.

1. Look at the Ownership verification card below Target details.
2. Make sure it shows Verified with the line "Black-box scans can run."
3. If it does not, follow how to prove ownership.
4. In the Scan profiles card, click ▷ Scan on a profile. Add one with + New profile if the list is empty.

Want Cyberlop to read your code as well? Create a new white-box target with a repository, since a target cannot gain a repository later.

Still not working?

• A scan that will not start on a black-box target usually points to missing ownership proof, not to the repository note.
• A target has no edit option, so adding a repository means creating a new target.
• Compare the two types in white-box versus black-box.

If the note puzzles you, write to /contact.

Related questions

• What does "No repository configured — add a Git repository URL to run a scan." mean?
• What's the difference between a white-box and a black-box target?
• Why are the repository fields greyed out in the New target dialog?
• Why can't I run a black-box scan on my new target?
• How do I verify that I own a black-box target?

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