Measured entry
hextaui-auth-recovery-codes
A client-side React and TypeScript card for generating, revealing, copying, downloading, and regenerating recovery codes. It ships as a shadcn registry block and depends on React state, Lucide icons, Radix-backed alert dialog behavior, local shadcn UI primitives, Tailwind theme classes, and the local cn utility.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 45.8 KB (111.2 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 2m 11s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/auth/auth-recovery-codes.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A capable account-security block with sensible concealment, export actions, and a confirmation step before regeneration. The empty state repeats the generate action and clipboard failures lack feedback, so expect minor product work. It needs a shadcn-style setup and is not a standalone drop-in.
Use it if
- You need a ready-made recovery-code step for an existing two-factor authentication flow.
- Your product should let users hide, copy, download, and regenerate codes from one compact card.
- Your app already uses shadcn conventions and can connect the supplied callbacks to real authentication APIs.
Skip it if
- You need the component to generate or validate recovery codes itself; it only presents codes and calls supplied handlers.
- Your security policy forbids browser clipboard or text-file download handling for recovery secrets.
- You need polished failure feedback for copy actions, since clipboard errors are silently ignored.
- You want a dependency-light drop-in without local shadcn primitives, aliases, or theme tokens.
Install
| Declared dependencies | @radix-ui/react-alert-dialog, @radix-ui/react-slot |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add the local cn helper, configure the path alias, bring in compatible alert, alert-dialog, button, and card primitives, install the Radix alert-dialog and slot packages plus Lucide React, and provide the Tailwind theme tokens used by the classes. Wire generation and regeneration callbacks to your authentication service.
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/HextaUIAlternatives
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.
- meraki-auth-sign-in-card-with-side-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.9KB
- Bare
- pass
- Prov
- NO
- shadcn-block-login-01minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 30.3KB
- Bare
- fail
- Prov
- NO
- shadcn-block-login-02minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.9KB
- Bare
- fail
- Prov
- NO
- shadcn-block-login-05minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.9KB
- Bare
- fail
- Prov
- NO
- 8bitcn-login-formskeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 33.2KB
- Bare
- fail
- Prov
- NO
- 8bitcn-advanced3skeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 33.3KB
- Bare
- fail
- Prov
- NO