xovee/uestc-course

0

/ 100

Documentation75
Engineering58
Health68
HTML3,899Other1d ago
Grade a repo

Strong community interest, but tests, CI, or docs need work.

๐ŸŽ“็”ตๅญ็ง‘ๆŠ€ๅคงๅญฆ ๐Ÿ“”่ฏพ็จ‹่ต„ๆ–™

Documentation

75

Install and run instructions9pt45

No install instructions found in the README (โˆ’45 pts).

โ†’ Add a section showing how to install dependencies.

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt85

README is present.

License6pt100

Licensed under Other.

Engineering

58

Linting and formatting5pt0

No linter or formatter config found.

โ†’ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt0

No dependency lockfile found (โˆ’70 pts).

โ†’ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/jekyll-gh-pages.yml).

Tests18pt80

Test files detected (tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

โ†’ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 456
    Forks
  • 0
    Releases

Community

  • โ€”
    Community health
  • โ€”
    authors own >50% of commits
  • 3,899
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 3h
    Median PR merge time
  • 2
    Open issues
Repository files10 root entries
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (โˆ’28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/jekyll-gh-pages.yml).
    Good: Issue or PR templates present.
  • assets
  • tests
    Good: Test files detected (tests).
  • tools
  • ่€ƒ็ ”็›ฎๅฝ•
  • ่ฏพ็จ‹็›ฎๅฝ•
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • LICENSE
    Good: Licensed under Other.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (โˆ’15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Issue: No install instructions found in the README (โˆ’45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.