agentmark-ai/agentmark
Grade a repo

92

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 10% of 5,156 graded repos

Markdown for the AI era

Documentation92
Engineering93
Health89
TypeScript351AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

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

  4. 4
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

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

92

Contributing guide5pt66

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

93

Reproducibility6pt80

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

CI/CD14pt85

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

Tests18pt100

Test files detected (packages/api-schemas/src/__tests__).

Linting and formatting5pt100

Linter or formatter configured (packages/cli/cli-src/eslint.config.mjs).

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)
  • 24
    Forks
  • 628
    Releaseslatest 1y ago

Community

  • 87% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 351
    Watchers

Responsiveness

  • 1d
    Median issue response
  • <1h
    Median PR merge time
  • 5
    Open issues
Repository files24 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .nx
  • .yarn
  • assets
  • examples
  • packages
    Good: Test files detected (packages/api-schemas/src/__tests__).
    Good: Linter or formatter configured (packages/cli/cli-src/eslint.config.mjs).
  • scripts
  • skills
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .yarnrc.yml
  • audit-output.txt
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • LICENSE.md
    Good: Licensed under AGPL-3.0.
  • logo.svg
  • nx.json
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • turbo.json
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.
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/agentmark-ai/agentmark)](https://www.repo-grade.com/report/agentmark-ai/agentmark)

More graded TypeScript repos