Example verification report

Run: npx https://alize.one/alize-verify.tgz https://github.com/login

Both runs below are real and recorded. There is no READY example: READY needs credentials for an account on the target, we hold none, and inventing a green run on a verification product's own example page is the one thing this page must never do.

Example: INCONCLUSIVE (a healthy target, no account)

Evidence: 2026-07-21T20-44-33-861Z__github.com__blocked.json · Timestamp: 2026-07-21T20:44:33.861Z

alize verify  https://github.com/login

  PASS     Site reachable
           HTTP 200 in 322ms.

  PASS     App renders
           Rendered 282 characters of visible text.

  PASS     Login form found
           Found at https://github.com/login

  PASS     Auth rejects a bad password
           App rejected a deliberately wrong password in 464ms.

  BLOCKED  Real sign-in works
           No credentials given, so signing in as a real user was not tested.
           This is not a verdict about your app — it is a gap in what we
           checked.

  INCONCLUSIVE — 4 passed, 1 could not be tested
  4.2s · https://github.com/login

  BLOCKED means we could not test it. It is not a pass.

  Exit code 2.

Example: NOT READY (an auth outage)

Evidence: 2026-07-21T20-44-14-185Z__localhost-4010__fail.json · Timestamp: 2026-07-21T20:44:14.185Z

alize verify  http://localhost:4010

  PASS     Site reachable
           HTTP 200 in 55ms.

  PASS     App renders
           Rendered 23 characters of visible text.

  PASS     Login form found
           Found at http://localhost:4010/

  FAIL     Auth rejects a bad password
           Auth request never came back — still hanging after 15080ms. This is
           the shape of an auth outage: the browser asked, nothing answered. A
           user sees a spinner that never stops.

  BLOCKED  Real sign-in works
           No credentials given, so signing in as a real user was not tested.

  NOT READY — 1 check failed
  17.0s · http://localhost:4010

  Exit code 1.

← Back