erixwong/touwaka-ai-mate
Grade a repo

61

/ 100

GradeD

Getting some notice. Tests and CI would be the fastest wins.

Higher than 45% of 5,156 graded repos
Documentation100
Engineering33
Health69
JavaScript17Apache-2.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (93).

See your top fixes
Now
D
61
Potential
A
93

Top fixes

Highest-impact changes first, ranked by point weight

10 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

    If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  4. 4
    Issue and PR templates6pt

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

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

100

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

33

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

Tests18pt35

Test files detected (server/tests).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (frontend/.editorconfig).

Project health

69

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt73

Dependency manifest found (package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 3
    Forks
  • 11
    Releaseslatest 3mo ago

Community

  • 42% - Weak
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 17
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1h
    Median PR merge time
  • 19
    Open issues
Repository files31 root entries
  • apps
  • config
  • data
    Issue: Build artifacts or local files may be committed (data/skills/pypdf/__pycache__/index.cpython-313.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
    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.
  • frontend
    Good: Linter or formatter configured (frontend/.editorconfig).
  • lib
  • models
  • plans
  • scripts
  • server
    Good: Test files detected (server/tests).
  • tests
  • tools
  • .dockerignore
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CHANGELOG.md
  • check_invoice.py
  • check_skill.py
  • docker-compose.standalone.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • 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.
  • requirements.txt
  • test_fapiao_direct.mjs
  • test_fapiao.cjs
  • test_pdfjs.mjs
  • test_skill_env.mjs
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/erixwong/touwaka-ai-mate)](https://www.repo-grade.com/report/erixwong/touwaka-ai-mate)

More graded JavaScript repos