vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-auth-two-factor-verify

auth-formminimal-flat

A client-side React verification card for authenticator codes, resend handling, inline errors, and an optional recovery-code path. It ships as a HextaUI shadcn registry block and depends on local button, card, field, input-group, OTP, and separator primitives, plus React, Lucide icons, input-otp, Radix-based UI packages, Tailwind theme tokens, and a local cn utility.

Specimen
Harness screenshot of hextaui-auth-two-factor-verify at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-auth-two-factor-verify at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-auth-two-factor-verify at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for hextaui-auth-two-factor-verify
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal42.2 KB (107.6 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 2m 9s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/auth/auth-two-factor-verify.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A credible, accessible starting point for a conventional second-factor screen, with useful recovery and resend states already modeled. It needs a shadcn-style setup and is not a drop-in component for a bare React project, so its value is highest when those conventions already exist.

Use it if

  • You need a focused second-factor step with authenticator and recovery-code flows in the same card.
  • Your app already uses shadcn-style aliases, primitives, Tailwind theme tokens, and a cn utility.
  • You want submission, resend, loading, and server-error behavior exposed through callbacks and props.

Skip it if

  • You need a complete authentication backend, challenge issuance, or recovery-code validation rather than presentation and client state.
  • Your design system cannot absorb HextaUI's local primitives, aliases, and theme-token conventions.
  • Your verification flow requires a different code format or more control over OTP composition than this fixed authenticator layout provides.

Install

Installation record for hextaui-auth-two-factor-verify
Declared dependencies@radix-ui/react-slot, @radix-ui/react-label, @radix-ui/react-separator, input-otp
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add the referenced React, Lucide, input-otp, and Radix packages; recreate or replace the local UI primitives; provide the cn helper and import aliases; and map the Tailwind color, spacing, focus, and animation classes to your design system. Wire the callbacks to real verification and resend endpoints.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Author repository

github.com/preetsuthar17/HextaUI
License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the auth-form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.