Skip to content

Since the last run

Overall +20 points

mckaywrigley/chatbot-ui (opens in a new tab)

A high-traffic AI chat project with good docs and tests, but contributors hit friction quickly: vague contributing guide, 240 open issues unreviewed, and stalled maintenance signals.

TypeScript33,268240 open issuesMIT License
Overall score: 62 out of 100
Holding

Readiness lenses

The same repo, two ways: how ready it is for an AI coding agent, and for a human newcomer. Switch lenses to see each one's score and checks.

How ready the repo is for an AI coding agent to read, build, and operate it.

62 / 100

8 of 17 checks passed across 6 categories.

  • First Impression

    82

    Clear purpose, active demo, and maintained by a known maintainer, but missing depth about the 2.0 rewrite and current capability scope.

    Reasoning available in the full report.
  • Getting Running

    68

    Step-by-step commands are present and copy-pasteable, but heavy dependencies (Docker, Supabase CLI), undocumented Node version gotcha, and SQL file editing requirements create friction.

    Reasoning available in the full report.
  • Finding Your Way

    55

    Codebase is well-structured by feature (app/, components/, db/, lib/) and uses TypeScript, but no architecture doc, no entity relationships explained, and deep nesting makes navigation opaque.

    Reasoning available in the full report.
  • Path to Contribute

    40

    CONTRIBUTING.md is a stub ('We are working on a guide'), no issue labels or templates, and issues policy discourages involvement—actively hostile to newcomers.

    Reasoning available in the full report.
  • Signs of Life

    48

    Recent commits (Aug 2024) and high star count suggest visibility, but 240 unreviewed issues, 'big update coming soon' message, and no visible PR velocity signal maintenance burden and stall.

    Reasoning available in the full report.
  • Open Door

    78

    MIT license is clear, but no code of conduct, and issue triage policy feels discouraging rather than welcoming—legal is safe, but social safety is questionable.

    Reasoning available in the full report.
  • Machine Orientation

    1 check passed2 problems found

    3 more checks in the full report.

  • Reproducible Setup

    0 checks passed3 problems found

    3 more checks in the full report.

  • Code Navigability

    2 checks passed0 problems found

  • Verification Surface

    2 checks passed1 problem found

    4 more checks in the full report.

  • Agent Safety

    1 check passed2 problems found

    4 more checks in the full report.

  • Context Economy

    2 checks passed1 problem found

    1 more check in the full report.

Where the grip slips

  1. 7 more issues found — each with a concrete fix.

Unlock the full report

See all 8 issues with concrete fixes and the reasoning behind every score. One-off, tied to your account so it works on every device — sign in with GitHub to buy. The score and badge stay free.

Show your score

Latch badge
[![Latch score](https://latch.fyi/api/badge/def4490d-2052-4b40-8cc4-ea9de1f3bad5)](https://latch.fyi/mckaywrigley/chatbot-ui)

Share this analysis

https://latch.fyi/mckaywrigley/chatbot-ui

Fixed some issues? Re-analyze to measure your progress →

Copy the whole report

Grab the entire verdict in one go — a Markdown block for a README or an issue, plain text, or a prompt you can paste straight into an LLM.

Was this verdict fair?

One tap helps — or tell us more.