Impeccable vs UI Craft — head-to-head
Date: 2026-11-19 · Run in: FINDS - TESTS (at Ros's direction)
Target (identical for both): ~/workspace/ts-spaces/my-finds-library/client/src
— 5 files, App.tsx 4,430 lines / 235,337 bytes (post UI-Craft-fix-pass, post test-tracking build)
Raw outputs: ~/workspace/finds-tests/impeccable-vs-ui-craft-2026-11-19/
(ui-craft.json, impeccable.json/.sarif/.txt, impeccable-url.json, impeccable-rules.json)
Read-only throughout: no app code modified, no --fix, no skill installed, Impeccable telemetry off (DO_NOT_TRACK=1).
Tools
- UI Craft detector
ui-craft-detectv0.13.0 (same version as the Nov 19 baseline runs) - Impeccable v4.10.0 (
npx impeccable), detector catalog verified live: exactly 62 rules
Results
UI Craft — source scan (same-day re-run)
Exit 1 (gate fail). 8 findings: 6 critical + 2 warnings, all in App.tsx.
| Rule | Count | Lines |
|---|---|---|
| dark-pattern/destructive-no-confirm | 5 | 3915, 3919, 4202, 4206, 4388 |
| a11y/modal-without-dialog | 1 | 3675 |
| layout/eyebrow-flood | 1 | 475 |
| copy/em-dash-flood | 1 | 1862 |
Delta vs the Nov 19 post-fix baseline (7): +1 destructive. The new hit (4388, "Remove this test") came in with the test-tracking build shipped after the fix pass.
Spot-checks: - 3915/3919 (Delete pair) and 4202/4206 (Remove-cover pair): false positives — both buttons sit inside the existing two-step confirm gates, the detector's known blind spot. - 4388 "Remove this test": technically accurate — it deletes with no confirmation — but it only removes an unsaved form row (local state, nothing persisted). Trivial; standard form UX. - Modal: accepted remainder (custom div, now with ESC / focus trap / focus return). - Eyebrow + em-dash: deliberate, kept by Ros's earlier call.
Net: 0 new real issues, 1 trivial.
Impeccable — source scan (the scoped, like-for-like run)
Exit 0. 0 findings (JSON [], SARIF results empty).
But the tool itself disclaims this result, verbatim from its text output:
"5 files scanned with regex matching only (.css, .ts, .tsx). Rules that need a parsed page (tiny-text, low-contrast and other element rules) did not run on them; findings are an undercount, not a clean bill of health."
Catalog check (62 rules, dumped via detect --list-rules): Impeccable has no equivalent
for UI Craft's core source catches — no transition-all, no focus-visible/outline, no modal/dialog
semantics, no destructive-confirm rules. Its source-mode patterns (gradient text, side-tab
borders, bounce easing, overused fonts, cream palette…) are simply not present in this post-fix
codebase. Its em-dash rule is advisory-only and did not fire in source mode.
Impeccable — rendered scan (extra pass, to give it its full mode)
Served the current built client (client/dist, built Nov 19 16:53 from this same source)
locally and scanned the rendered page in headless Chromium
(IMPECCABLE_BROWSER wrapper, --no-sandbox). Exit 2. 2 findings, both on the footer <p>:
- low-contrast — REAL, verified. Footer is
text-xs text-[var(--dim)](App.tsx:3668); light theme--dim: #8a8378on--bg: #f5f3ef(theme.css:32/28) = 3.4:1, needs 4.5:1 for 12px text. A genuine WCAG AA fail — and a class of check UI Craft does not have at all. - line-length — real, cosmetic. The footer credits paragraph renders ~173 chars/line.
Limitation: the static dist has no server backend, so only the app shell/footer rendered — catalog tiles, detail modal, and forms never appeared, so rendered rules were exercised on the shell only. Full rendered coverage needs the live app with data. Both findings are a floor, not a ceiling.
Verdict
Complementary, not a replacement. UI Craft wins the job it was adopted for.
- As a source/CI gate on React code, UI Craft is the real detector: it parses TSX semantics and catches mechanical regressions (transitions, focus, modal, confirm patterns). Impeccable's source mode is regex-only by its own admission and would wave this code through.
- Impeccable's genuine edge is rendered-mode quality checks UI Craft lacks — contrast above all. Its one real catch here (footer contrast) is worth a fix.
- The missing 0–100 score turned out not to matter: neither tool's count is a quality verdict (UI Craft's 8 = 4 false positives + 1 trivial + 3 accepted; Impeccable's 0 = didn't run).
Recommendation
1. Keep UI Craft as the Finds Library post-build checklist (unchanged, as adopted Nov 19).
2. Do NOT adopt Impeccable as a skill/hook/live-mode install.
3. File Impeccable as Reuse later: an occasional rendered-mode pass against the live
app (contrast / tiny-text / heading order), not a source gate.
4. One actionable fix for the Finds Library app (Ros's go, via FINDS-LIBRARY): darken light-theme
--dim so footer/small dim text meets 4.5:1 on #f5f3ef.
Test record (for Finds Library)
- Subject: Impeccable (alternative to UI Craft, find #64 lineage)
- Date: 2026-11-19
- What:
impeccable detectv4.10.0 (62-rule catalog verified) on the Finds Library source, head-to-head against a same-dayui-craft-detectv0.13.0 re-run on the identical tree; plus a rendered-mode scan of the built client. - Outcome: Success-with-caveats — Impeccable source mode 0 findings (self-declared undercount, no overlap with UI Craft's rule core); rendered mode 2 findings incl. one verified real WCAG AA contrast fail UI Craft cannot catch. UI Craft re-run: 8 findings, 0 new real issues.
- Output: this report + raw outputs in
~/workspace/finds-tests/impeccable-vs-ui-craft-2026-11-19/ - Reuse status: Reuse later (rendered passes only) — UI Craft remains the adopted post-build checklist.