zm-bad/dag-chat
Grade a repo

0

/ 100

GradeB

Solid foundation. Invest in docs and CI to grow from here.

Chat applications that use DAG to build question-answer relationships.

Documentation84
Engineering70
Health100
TypeScript32MITtoday

Documentation

84

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

70

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.

CI/CD14pt72

CI is configured (.github/workflows/backend-test.yml).

Tests18pt80

Test files detected (backend/tests).

Reproducibility6pt80

Lockfile present (backend/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.pylintrc).

Project health

100

Dependency manifest6pt100

Dependency manifest found (backend/requirements.txt).

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)
  • 0
    Forks
  • 7
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files25 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/backend-test.yml).
  • .vscode
  • backend
    Good: Test files detected (backend/tests).
    Good: Lockfile present (backend/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (backend/requirements.txt).
  • docs
  • frontend
  • scripts
  • specs
  • sql
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .gitmessage
  • .markdownlint.json
  • .pre-commit-config.yaml
  • .pylintrc
    Good: Linter or formatter configured (.pylintrc).
  • .python-version
  • AGENTS.md
  • CLAUDE.md
  • docker-compose.yml
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • README_zh.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.
  • README.md
  • start.sh