huangpustar/fenixagent
Grade a repo

64

/ 100

GradeD

A workable base with real gaps. Start with test coverage and the README.

Top 49% of 5,156 graded repos
Documentation75
Engineering61
Health70
TypeScript285Apache-2.011d 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 (91).

See your top fixes
Now
D
67
Potential
A
91

Top fixes

Highest-impact changes first, ranked by point weight

19 to address
  1. 1
    Tests18pt

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

  2. 2
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  3. 3
    README12pt

    Link to a deployed version, docs site, or demo video. Users want to see it running.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

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

75

README12pt50

README is present.

Contributing guide5pt58

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 instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

61

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 (packages/acp-link/src/__tests__).

Reproducibility6pt80

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

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Project health

70

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.

Dependency manifest6pt55

Dependency manifest found (package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 203 / 653
    Commits (30d / 90d)
  • 16
    Forks
  • 9
    Releaseslatest 28d ago

Community

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

Responsiveness

  • 1d 13h
    Median issue response
  • <1h
    Median PR merge time
  • 11
    Open issues
Repository files42 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .husky
  • docker
  • docs
  • drizzle
  • packages
    Good: Test files detected (packages/acp-link/src/__tests__).
  • scripts
  • side-project
  • spec
  • src
  • tools
  • ui-sandbox
  • web
  • workflow-examples
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .npmrc
  • AGENTS.md
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • build-image.sh
  • buildkitd.toml
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • CLAUDE.md
  • components.json
  • 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • create-user.sh
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • drizzle.config.ts
  • fenix-sandbox-ops.sh
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
  • restart-server.sh
  • TODO.md
  • tsconfig.base.json
  • 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/huangpustar/fenixagent)](https://www.repo-grade.com/report/huangpustar/fenixagent)

More graded TypeScript repos