Solid engineering. The main gap is visibility.

AI coding runtime for the business production environment

Documentation

84

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

Add setup instructions, code style notes, and how to run tests.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

74

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt57

CI is configured (.github/workflows/ax-code-ci.yml).

Reproducibility6pt92

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (crates/ax-code-tui/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

92

Dependency manifest6pt75

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 0
    Forks
  • 278
    Releaseslatest 2mo ago

Community

  • Community health
  • authors own >50% of commits
  • 8
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 1h
    Median PR merge time
  • 0
    Open issues
Repository files32 root entries
  • .github
    Good: CI is configured (.github/workflows/ax-code-ci.yml).
    Good: Dependabot configured for github-actions.
  • .husky
  • .vscode
  • crates
    Good: Test files detected (crates/ax-code-tui/tests).
  • desktop
  • docs
  • packages
    Good: Environment pinned via packages/ax-code/Dockerfile.
  • patches
  • script
  • tools
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .markdownlint.json
  • .node-version
  • .npmrc
  • .prettierignore
  • AGENTS.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • GEMINI.md
  • install
  • install.ps1
  • LICENSE
    Good: Licensed under MIT.
  • NOTICE
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • rust-toolchain.toml
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.json
  • turbo.json
  • vitest.config.ts