A high-momentum project with solid docs and deployment paths, but local dev setup needs clarity and testing guidance is sparse for contributors.

29 of 35 checks passed across 6 categories.

• Machine Orientation

  ✓7 checks passed⚠1 problem found

  • lowllms.txt present

    An llms.txt is the emerging machine-orientation standard — a curated map for LLMs.

    Fix: Add an llms.txt pointing at the key docs and entry points.

  • ✓README present — An agent reconstructs what the repo is and how to work in it from the README first.
  • ✓Agent instructions file — AGENTS.md / CLAUDE.md is the direct, machine-read channel for entry points and conventions.
  • ✓Agent instructions stay lean — A bloated instructions file burns context and measurably hurts more than it helps.
  • ✓Repository description set — The one-line description is the fastest orientation signal an agent reads.
  • ✓Topics set — GitHub topics situate the repo's domain and stack for an agent at a glance.
  • ✓Architecture doc — An ARCHITECTURE doc hands an agent the module map instead of making it infer one.
  • ✓Contribution conventions are written down — A contributor guide is where an agent learns the branch, commit, and review conventions it must follow.

• Reproducible Setup

  ✓5 checks passed⚠1 problem found

  • highLockfile committed

    Without a lockfile two clones can resolve different dependency trees — the build isn't reproducible.

    Fix: Commit your lockfile (package-lock.json / pnpm-lock.yaml / Cargo.lock / …).

  • ✓Runtime / toolchain pinned — An unpinned runtime makes an agent guess the version a clean environment needs.
  • ✓Version pins are exact — A floating pin (a bare major, or a range) still drifts between installs.
  • ✓Env template present — A .env.example tells an agent which configuration keys it must supply to run.
  • ✓Container or dev-container — A Dockerfile / compose / devcontainer removes 'works on my machine' from setup.
  • ✓Dev container — A .devcontainer gives an agent a one-command, fully-declared environment.

• Code Navigability

  ✓2 checks passed⚠0 problems found

  • ✓Conventional source layout — A recognised src/ · lib/ · app/ layout lets an agent localise code without spelunking.
  • ✓TypeScript strict mode on — Strict typing gives an agent typed signatures to anchor an edit on, not guesses.

• Verification Surface

  ✓6 checks passed⚠1 problem found

  • lowTask runner present

    A Makefile / Taskfile / justfile gives an agent a single index of the project's commands.

    Fix: Add a Makefile / Taskfile / justfile collecting the common commands.

  • ✓Tests present — Runnable tests are the ground truth an agent checks its own edits against.
  • ✓Test command defined — A `test` script is the documented, discoverable way to run the suite.
  • ✓Lint command defined — A linter an agent can run catches a class of mistakes before they ship.
  • ✓CI configured — Readable CI is the feedback loop an agent reads to know what 'green' means here.
  • ✓Typecheck command — A typecheck script lets an agent catch type errors before they ship.
  • ✓Build command — A documented build command is the discoverable way for an agent to produce artifacts.

• Agent Safety

  ✓7 checks passed⚠1 problem found

  • highNo committed .env

    A tracked real .env hands secrets to anything — including an agent — that reads the repo.

    Fix: Remove the .env from history, gitignore it, and ship a .env.example instead.

  • ✓No exposed secrets — Secret-shaped literals in tracked files are a live credential leak.
  • ✓.gitignore covers env files — An ignore rule for .env is what keeps the next careless commit from leaking secrets.
  • ✓CODEOWNERS present — CODEOWNERS marks the 'don't touch without review' zones an agent should respect.
  • ✓Automated dependency updates — Dependabot / Renovate keeps dependencies patched without a human in the loop.
  • ✓.gitignore present — A .gitignore is the first guard against an agent committing secrets or build junk.
  • ✓Security policy — A SECURITY.md is where an autonomous security agent reads this repo's rules before acting on it.
  • ✓License makes the code reusable — Without a license an agent cannot safely copy, redistribute, or vendor any of this code.

• Context Economy

  ✓2 checks passed⚠2 problems found

  • lowGenerated / vendored files marked

    A .gitattributes linguist marker tells tools (and agents) what to skip.

    Fix: Mark generated/vendored paths in .gitattributes (linguist-generated / linguist-vendored).

  • lowNo oversized source file

    A single file in the hundreds of KB blows past an agent's effective context window.

    Fix: Split the largest files along their natural seams.

  • ✓Dependencies not vendored in — A committed node_modules / vendor tree drowns the real signal an agent needs.
  • ✓Build output not committed — Generated dist/ · build/ output is noise an agent has to read past.

21 of 25 checks passed across 6 categories.

• First Impression

  ✓3 checks passed⚠0 problems found

  • ✓README present — The README is the first screen — with none, a newcomer has nothing to land on.
  • ✓Repository description set — The one-line description sets expectations before a newcomer even opens the README.
  • ✓Topics set — Topics situate the project's domain at a glance and help a newcomer find it.

• Getting Running

  ✓5 checks passed⚠1 problem found

  • highLockfile committed

    Without a lockfile a newcomer's install resolves differently and hits errors the docs don't mention.

    Fix: Commit your lockfile so a fresh clone installs the same dependency tree.

  • ✓Prerequisite versions pinned — Unpinned prerequisites are the classic 'works on my machine' first-run failure.
  • ✓Env template present — A .env.example shows a newcomer exactly which settings they must fill in to run it.
  • ✓One-command environment — A Dockerfile / compose / devcontainer turns a fiddly setup into one command.
  • ✓One-click dev container — A .devcontainer lets a newcomer start in a cloud IDE with zero local setup.
  • ✓Versions pinned exactly — A floating version still drifts — a newcomer can hit a break the maintainer never saw.

• Finding Your Way

  ✓2 checks passed⚠1 problem found

  • lowNo oversized source file

    A single thousand-line file is a wall a newcomer bounces off.

    Fix: Split the largest files along their natural seams.

  • ✓Conventional source layout — A familiar src/ · lib/ · app/ layout lets a newcomer guess where things live.
  • ✓Architecture / overview doc — An overview hands a newcomer the map instead of making them reconstruct it.

• Path to Contribute

  ✓5 checks passed⚠1 problem found

  • lowTask runner

    A Makefile / Taskfile gives a contributor a single index of the project's commands.

    Fix: Add a Makefile / Taskfile collecting the common dev commands.

  • ✓CONTRIBUTING guide — A CONTRIBUTING guide is the difference between a guessed and a guided first PR.
  • ✓Issue templates — Issue templates show a newcomer how to file something useful — and that contributions are welcome.
  • ✓Pull-request template — A PR template tells a first-time contributor what a good change includes.
  • ✓Test command defined — A documented test command lets a contributor check their change before opening a PR.
  • ✓Lint command — A linter lets a first-time contributor catch style issues before review.

• Signs of Life

  ✓3 checks passed⚠0 problems found

  • ✓Tests present — A test suite signals a project that's cared for, not abandoned.
  • ✓CI configured — Green CI on every change tells a newcomer the project is actively kept working.
  • ✓Automated dependency updates — Dependabot / Renovate activity is a visible heartbeat of ongoing maintenance.

• Open Door

  ✓3 checks passed⚠1 problem found

  • lowLicense is a standard one

    A non-standard or custom license is a legal question mark a newcomer won't resolve.

    Fix: Use a recognised OSI license so reuse terms are unambiguous.

  • ✓License present — With no license the project isn't legally reusable — the door is shut however friendly the README.
  • ✓Code of conduct — A code of conduct states the social ground rules that make it safe to step in.
  • ✓Security policy — A SECURITY.md tells a newcomer how to report a problem responsibly.