Skip to main content
Detail scans your codebase and produces a ranked list of reproducible bugs. Unlike shallow bug scanners, Detail sets up your dev environment in the cloud, runs code to confirm bugs are real, and uses historical data on what bugs get fixed to select the bugs you’re most likely to care about. Each scan generates a new set of findings.

​
How it works

1

Detail analyzes your codebase

When a scan runs, Detail dispatches sets up your dev environment in a container and runs whatever you run locally, e.g. a local Redis instance or a Next.js application. Detail finds thousands of candidate bugs and determines which ones are real.
2

Findings are ranked and deduplicated

Detail maintains a model of which bugs get fixed and which bugs get ignored, which we use to select a small subset of the bugs we can find that you are most likely to fix. Before results are surfaced, Detail also deduplicates findings across scans, so the same underlying issue never appears twice unless the code substantially changes.
3

Reports are delivered

Each bug is packaged as a structured bug report with all the context you need to fix it. Optionally, we will deliver your bugs to Linear, Jira, Asana, GitHub Issues, or Slack.

​
Scan modes

Full Repo Scans

Detail scans your whole repository for the bugs we think you are most likely to care about.

Recent Changes Scans

Detail focuses on changes introduced in the last week. Useful for reviewing a sprint’s worth of changes or improving quality before a release.

On-demand scans

Trigger a one-off scan at any time from the Detail dashboard.
If you’re interested in a custom scan, e.g. one that focuses on a particular portion of your repository or only on a certain kind of bug, contact Detail Support and we can help.

​
Bug report fields

Every bug Detail finds includes the following information:

​
Managing bugs

From the dashboard or CLI you can change the status of any bug:
  • Open — unresolved and awaiting action (the default state)
  • Resolved — fixed and closed
  • Dismissed — closed without a fix, with a reason: Not a Bug, Won’t Fix, Duplicate, or Other
You can always reopen later. This is useful when a fix is reverted or a “won’t fix” decision is overturned.