nano-collective/nanocoder
Grade a repo

0

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

Top 28% of 5,156 graded repos

An open coding agent for your terminal, built by a community collective rather than a company. Bring your own model, keep your code on your machine, and owe nothing to anyone.

Documentation87
Engineering71
Health100
TypeScript2,148Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

5 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
    Install and run instructions9pt

    Add a section showing how to start or use the project.

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

87

Install and run instructions9pt55

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

71

Tests18pt35

Test files detected (source/acp/acp-agent.spec.ts).

CI/CD14pt85

CI is configured (.github/workflows/pr-checks.yml).

Reproducibility6pt92

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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)
  • 204
    Forks
  • 89
    Releaseslatest 11mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,148
    Watchers

Responsiveness

  • 8d 15h
    Median issue response
  • 20h
    Median PR merge time
  • 20
    Open issues
Repository files35 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/pr-checks.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • .husky
  • assets
  • badges
  • benchmarks
  • docs
  • Formula
  • patches
  • plugins
  • scripts
  • source
    Good: Test files detected (source/acp/acp-agent.spec.ts).
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .mcp.example.json
  • .npmignore
  • .semgrepignore
  • AGENTS.md
  • biome.json
  • CHANGELOG.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • flake.lock
  • flake.nix
  • knip.json
  • LICENSE.md
    Good: Licensed under Other.
  • 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.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tsconfig.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/nano-collective/nanocoder)](https://www.repo-grade.com/report/nano-collective/nanocoder)

More graded TypeScript repos