Incomplete coverage is not a clean bill of health
A scan can finish with zero findings and still have reviewed none of your delivery. Only a covered verdict may be shown as a real audit.
Published 2026-09-10 · Search job: supply audit coverage verdict incomplete
A Supply Audit scan can finish cleanly and still have reviewed none of your delivery. Calling that "succeeded, zero findings" is the most misleading thing the feature could do.
coverage_verdict is one of covered, no_account_rows, no_provider_rows, or no_campaigns. The API exposes the buyer boolean as audited. The CLI prints a warning when the run was not covered. The dashboard shows an amber Incomplete badge and the sentence "This scan did not review your delivery." The empty state becomes "Nothing checked yet" so the screen cannot warn and reassure at once.
Only covered may be presented as a real audit result.
Why a run can be empty on purpose
The scan reads the exchange with the product reporting user. If that user is wrong, the provider can return plenty of rows that do not belong to the account, or zero rows for campaigns you know are live. The reporting user is not the other Beeswax login is that incident.
The interval gate counts only covered runs. A coverage gap does not start the 24-hour skip clock. Today is always excluded from the scan window, because a partial day makes healthy placements look zero-click.
What we will not display as green
Zero findings on no_account_rows is not proof the remnant was clean. Zero findings on a laptop runner that got HTTP 401 is not proof either. Verify coverage against the deployed API.
Coverage verdict is the term. How to judge display traffic is still the score. A covered scan with findings is a recommendation list, not an IVT certificate.