usenotra/notra
Grade a repo

0

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Top 38% of 5,156 graded repos

Turn Your Work Into Content

Documentation88
Engineering64
Health89
TypeScript130AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

88

README12pt70

README is present.

Contributing guide5pt97

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

64

Tests18pt35

Test files detected (packages/ai/src/integrations/mcp-tool-name.test.ts).

CI/CD14pt57

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

Linting and formatting5pt100

Linter or formatter configured (biome.jsonc).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

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)
  • 38
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 130
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1h
    Median PR merge time
  • 18
    Open issues
Repository files32 root entries
  • .agents
  • .claude
  • .codex
  • .cursor
  • .expect
  • .github
    Good: CI is configured (.github/workflows/code-quality.yml).
    Good: Dependabot covers 2 ecosystems (bun, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .husky
  • .opencode
  • .stagewise
  • .vscode
  • apps
    Good: Environment pinned via apps/api/Dockerfile.
  • packages
    Good: Test files detected (packages/ai/src/integrations/mcp-tool-name.test.ts).
  • scripts
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • AGENTS.md
  • biome.jsonc
    Good: Linter or formatter configured (biome.jsonc).
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • commitlint.config.ts
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • package.json
    Good: Dependency manifest found (package.json).
  • POST_GROUPS_PLAN.md
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
  • SECURITY.md
    Good: Security policy present.
  • skills-lock.json
  • sonnet-generation-story.md
  • 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/usenotra/notra)](https://www.repo-grade.com/report/usenotra/notra)

More graded TypeScript repos