henrychiao/mihomo_yamls

0

/ 100

Documentation67
Engineering25
Health59
Shell2,134AGPL-3.01d ago
Grade a repo

Real traction, but rough engineering makes it hard for contributors to trust.

一个精心整理的 Mihomo (Clash Meta) 配置文件仓库，通过 GitHub Actions 每日自动同步上游优质规则，提供从入门到进阶的完整解决方案。

Documentation

67

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt65

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

License6pt100

Licensed under AGPL-3.0.

Engineering

25

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

Reproducibility6pt12

No dependency lockfile found (−70 pts).

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

CI/CD14pt40

CI is configured (.github/workflows/build-go-project.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

59

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.

Housekeeping3pt40

No .gitignore found (−60 pts).

→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 215
    Forks
  • 169
    Releaseslatest 6mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,134
    Watchers

Responsiveness

  • 22h
    Median issue response
  • 2h
    Median PR merge time
  • 0
    Open issues
Repository files8 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: CI is configured (.github/workflows/build-go-project.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • custom
  • Overwrite
  • scripts
  • THEDOC
  • THEYAMLS
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • 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.
    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.