barry-far/v2ray-config

0

/ 100

Documentation68
Engineering20
Health91
Python2,105MIT1d ago
Grade a repo

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

Free V2ray Configs, Updating Every 15 minutes. 🚀🌐

Documentation

68

Contributing guide5pt30

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

README12pt85

README is present.

License6pt100

Licensed under MIT.

Engineering

20

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.

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/CD14pt40

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

Reproducibility6pt70

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

Project health

91

Housekeeping3pt40

No .gitignore found (−60 pts).

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

Dependency manifest6pt100

Dependency manifest found (Files/requirements.txt).

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

Community

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

Responsiveness

  • 2d 16h
    Median issue response
  • —
    Median PR merge time
  • 44
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/main.yml).
  • Base64
  • Files
    Good: Lockfile present (Files/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (Files/requirements.txt).
  • Splitted-By-Protocol
  • .gitattributes
  • All_Configs_base64_Sub.txt
  • All_Configs_Sub.txt
  • Chinese-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.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • LICENSE
    Good: Licensed under MIT.
  • Persian-README.md
  • README.md
  • Russian-README.md
  • Sub1.txt
  • Sub10.txt
  • Sub11.txt
  • Sub12.txt
  • Sub13.txt
  • Sub14.txt
  • Sub2.txt
  • Sub3.txt
  • Sub4.txt
  • Sub5.txt
  • Sub6.txt
  • Sub7.txt
  • Sub8.txt
  • Sub9.txt
  • Turkish-README.md