Skip to main content
Detail runs scans on a nightly schedule by default, so your bug findings stay fresh without any manual effort. You can also trigger on-demand scans at any time from the dashboard and configure exactly what each scan covers — whether that’s a full repository scan or a focused look at recent changes.

​
Scan types

Default

A full repository scan against the latest commit on your primary branch. This is the standard scan type used for nightly runs.

Recent Changes

Scans only code introduced since a specific date or by specific authors. Faster than a full scan and useful for reviewing work in progress before merging.

​
Scan schedule

Nightly scans run automatically — no configuration required. Detail picks up the latest commit on your primary branch each night and runs a full default scan. Results appear in the dashboard as soon as the scan completes.

​
Triggering an on-demand scan

You can kick off a scan at any time without waiting for the nightly schedule. From the dashboard:
  1. Go to Settings → Repositories and find the repository you want to scan.
  2. Click Scan Now on the repository card.
  3. The scan starts immediately. You’ll see it appear under the Scans tab with an in-progress status.

​
Inspecting scan history

From the dashboard: Click on a repository, then open the Scans tab. You’ll see a list of past scan runs with their status, scan type, commit SHA, and bug counts. From the CLI: Use detail scans list to view scan history for a repository. 
# List all scans for a repository
detail scans list owner/my-repo

# Filter by status and time range
detail scans list --status complete --since 7d

​
Scan statuses

StatusMeaning
in_progressThe scan is currently running. Results are not yet available.
completeThe scan finished successfully. Bug findings are available in the dashboard and API.
failedThe scan encountered an error and did not produce results.
dlqThe scan failed repeatedly and has been dequeued. Contact support if you see this status.
If a scan consistently shows a failed or dlq status, contact [email protected] with the repository name and the approximate time of the failed scan.
Scans run in isolated sandboxes and never modify your code. Detail only reads your repository content — it does not execute your code or install your dependencies.