huangpustar/fenixagent

0

/ 100

Documentation64
Engineering61
Health70
TypeScript101d ago
Grade a repo

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

Documentation

64

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt64

Contributing guide is detailed and thorough.

README12pt70

README is present.

Install and run instructions9pt100

README documents how to install the project.

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

  • —
    Commits (30d / 90d)
  • 7
    Forks
  • 3
    Releaseslatest 2d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 10
    Watchers

Responsiveness

  • 2d 23h
    Median issue response
  • <1h
    Median PR merge time
  • 5
    Open issues
Repository files41 root entries
  • .agents
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .husky
  • docker
  • docs
  • drizzle
  • packages
    Good: Test files detected (packages/acp-link/src/__tests__).
  • prompts
  • reviews
  • scripts
  • spec
  • src
  • tools
  • web
  • workflow
  • workflow-examples
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .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
    Good: Contributing guide is detailed and thorough.
    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.
  • DESIGN.md
  • docker-compose.machines.yml
  • docker-compose.prod.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • drizzle.config.ts
  • infinity_conf.toml
  • 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.
    Good: README links to a live demo or deployed app.
    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
  • tsconfig.base.json
  • tsconfig.json