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.
No score, just the facts
VibeLock does not boil your app down to one number. A number you cannot act on is a verdict, and "72" tells you nothing to do next. You see the facts instead: which badge criteria hold, how much of the app was tested, and what is open with its deadline.
Coverage
Coverage is how much of your app VibeLock actually tested, out of everything that applies. If a scan finds 40 pages and only reaches 10, coverage is 25 percent.
"Zero findings across four pages" is not a verified app; it is an app that was barely looked at. VibeLock does the counting, so hiding pages or skipping checks can only lower coverage, never raise it. A single coding tool report does not count toward coverage until it is corroborated. The badge needs at least 80 percent.
Checks that judge a document you write yourself, such as your incident runbook or your security design record, are listed separately and left out of coverage, because VibeLock does not gather that evidence itself. If one of them records a failure, it still opens a finding with its own deadline.
Nothing you do to narrow the scan can raise coverage or earn the badge.
How close you are
Your Overview shows the five badge criteria and how many hold today, for example 4 of 5, and names the one that does not with what fixes it.
- Coverage at least 80 percent.
- No open critical findings.
- No high findings past their 30 day deadline.
- A full scan in the last 30 days.
- Live URL and code connected: a proved address plus a repository host connection or corroborated coding tool results.
Nothing on the preview
The free public preview only sees what your app shows to anyone on the internet. It shows the findings it is sure of, tagged Confirmed or Likely, and no number or letter grade.
As evidence ages
Staying verified covers the 21 day reminder, the 30 day window, and what happens when a connection or ownership proof is lost.