Measured entry

hextaui-settings-security

formminimal-flat

A client-side React security settings card covering password changes, two-factor authentication, backup codes, active sessions, and security history. It ships as a shadcn registry block and depends on HextaUI or shadcn primitives, Radix-backed dialogs and labels, lucide-react, Tailwind utility classes, and the @/lib/utils alias.

Specimen
Harness screenshot of hextaui-settings-security at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-security at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-security 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-settings-security
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical1
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal53.3 KB (118.7 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 1m 36s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-security.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A broad, practical account-security shell that built and mounted cleanly in its intended environment, but it needs a shadcn-style setup and is not drop-in for a bare React app. Fix the unsupported ARIA attributes before production and wire every security callback deliberately.

Use it if

  • You need one account-security surface that accepts your session and audit data through props.
  • Your app already uses shadcn-style primitives, Tailwind theme tokens, and path aliases.
  • You can connect the provided callbacks to real password, two-factor, backup-code, and session APIs.

Skip it if

  • Your accessibility gate cannot accept unsupported ARIA attributes until the component is corrected.
  • Your design system does not use shadcn-style primitives or Tailwind utility classes.
  • You need a complete security workflow rather than a UI shell whose action callbacks may otherwise do nothing.

Install

Installation record for hextaui-settings-security
Declared dependencies@radix-ui/react-alert-dialog, @radix-ui/react-slot, @radix-ui/react-dialog, @radix-ui/react-label, @radix-ui/react-separator
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

A non-shadcn project must add the required HextaUI or equivalent shadcn primitives, their Radix packages, lucide-react, Tailwind theme tokens, a cn utility, and an @ path alias. It also needs client-component support and application handlers for every security action.

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.

License
MIT
Record published
2026-08-14

Alternatives

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