Measured entry
shadcn-block-login-03
A shadcn registry block for a centered sign-in page with Apple and Google choices, email and password fields, recovery and registration links, and legal copy. It ships as React page and form source, built from shadcn card, field, input, and button components with Tailwind utilities, a cn helper, and a Lucide brand icon. Authentication behavior is not included.



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 | 1 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 32.1 KB (97.5 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | none |
What the harness recorded
BARE BUILD
✗ Build failed in 30.89s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/blocks/login-03/components/login-form.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A sensible starting shell for a standard login route, with solid responsive behavior and familiar form structure. It needs a shadcn-style setup, and teams should fix the contrast issue and wire every action before treating it as production-ready.
Use it if
- You need a conventional account login screen that supports both social and password entry.
- Your app already uses shadcn components, Tailwind utilities, path aliases, and the shared cn helper.
- You want a compact form that stays centered and avoids horizontal overflow across common layouts.
Skip it if
- You need working authentication, validation, password recovery, or provider callbacks without adding application logic.
- Your design system does not use shadcn and adopting its field, card, input, and button primitives would add unwanted coupling.
- You cannot revise the muted supporting text and link colors to resolve the detected contrast problem.
- Your product does not offer both Apple and Google sign-in and you want a component that matches the enabled providers as shipped.
Install
| Declared dependencies | radix-ui |
|---|---|
| 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 Tailwind theme tokens and utilities, the shadcn card, field, input, button, and label-related primitives, the shared cn utility and path alias, Lucide React for the mark, and the registry's Radix dependency. Then connect submit, provider, recovery, registration, terms, and privacy actions to real routes and services.
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/shadcn-ui/uiAlternatives
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