zzispp/hook
Grade a repo

0

/ 100

GradeB

Strong early engineering with some momentum.

AI API gateway and operations platform for unified model routing, token/RBAC access control, billing, provider management, and monitoring.

Documentation70
Engineering85
Health86
Rust17MITtoday

Documentation

70

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

85

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.

Reproducibility6pt80

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

Tests18pt100

Test files detected (apps/hook_backend/src/llm_proxy/candidate/selection/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (apps/hook_frontend/.editorconfig).

Project health

86

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

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)
  • 2
    Forks
  • 3
    Releaseslatest 21d ago

Community

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

Responsiveness

  • 2d 15h
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files32 root entries
  • .codex-tasks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • apps
    Good: Test files detected (apps/hook_backend/src/llm_proxy/candidate/selection/tests).
    Good: Linter or formatter configured (apps/hook_frontend/.editorconfig).
  • config
  • crates
  • docs-site
  • packaging
  • scripts
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .release-please-manifest.json
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • deploy.sh
  • docker-compose.prebuilt.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • install.sh
  • justfile
  • LICENSE
    Good: Licensed under MIT.
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • README_CN.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.
  • README_RELEASE.md
  • README.md
  • release-please-config.json
  • rustfmt.toml
  • update.sh