Live now. Sign up free, paste your app’s address, and this works from your dashboard. What is live today lists what is still to come.
The rule
Bad news is believed. Good news is corroborated. A failure from any signal opens a finding at once. A pass closes it only when it comes from a source VibeLock can trust, or is backed up by a second one. This is what stops a badge being earned by reporting good news.
Opening
- A check fails on any signal: the outside scan, the repository host, your coding tool or the cross-check.
- A finding opens with the check’s severity and a confidence tag: Confirmed if it was reproduced, Likely if the signs are strong but it was not.
- The deadline clock starts the first time the failure is seen, and keeps running across rescans while it stays open.
Closing
- Fixed
- A rescan confirms the check now passes. For a coding tool result, that means a second matching scan at the same commit, at least an hour later, or a repository check.
- Likely cleared
- A Likely critical blocks Verified until a confirming rescan or VibeLock review clears it. A critical reported only by your coding tool is treated the same way.
You cannot dismiss, downgrade or mark a finding as accepted. Neither can anyone else on your team. The only way out is evidence.
Reopening
If a fixed check fails again later, a new finding opens and its clock starts from the new failure. Fixed findings stay in your history.
What it means for the badge
An open critical, including a Likely one, means the badge shows your last verified date. So does a high finding past its 30 day deadline. Medium and low findings never move the badge on their own.