necmttn/ax
Grade a repo

76

/ 100

GradeC

Strong early engineering with some momentum.

Top 38% of 5,156 graded repos

the agent experience layer · observability + memory for AI coding agents (Claude Code + Codex) · local-first, typed, yours

Documentation94
Engineering58
Health92
TypeScript63AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

94

Contributing guide5pt85

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

58

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

Tests18pt35

Test files detected (apps/axctl/src/advice/model.test.ts).

Reproducibility6pt70

Lockfile present (bun.lock). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/ci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

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

  • 917 / 1505
    Commits (30d / 90d)
  • 6
    Forks
  • 44
    Releaseslatest 2mo ago

Community

  • 85% - Good
    Community health
  • -
    authors own >50% of commits
  • 63
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 26
    Open issues
Repository files44 root entries
  • .ax
  • .claude
  • .claude-plugin
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .vscode
  • agents
  • apps
    Good: Test files detected (apps/axctl/src/advice/model.test.ts).
  • bench-results
  • community
  • docs
  • functions
  • goals
  • integrations
  • packages
  • scripts
  • skills
  • tests
  • .env.example
  • .envrc
  • .gitignore
    Good: .gitignore present.
  • .release-please-manifest.json
  • AGENTS.md
  • alchemy.run.ts
  • ATTEMPTS.md
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bun.nix
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTEXT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • flake.lock
  • flake.nix
  • install.sh
  • interview.md
  • lefthook.yml
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • release-please-config.json
  • RELEASING.md
  • tsconfig.base.json
  • tsconfig.json
  • turbo.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/necmttn/ax)](https://www.repo-grade.com/report/necmttn/ax)

More graded TypeScript repos