Popular for its size, but the engineering basics lag behind the interest.
https://subscription.mmvpn.ggff.net
Documentation
73
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
20
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
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 is configured (.github/workflows/main.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Project health
91
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Dependency manifest found (requirements.txt).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 10Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 181Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files22 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).
- assets
- Base64
- configs
- Files
- Licence
- plus
- Splitted-By-Protocol
- src
- All_Configs_Sub.txt
- CNAME
- crawler.php
- index.html
- install.bat
- install.sh
- LICENSEGood: Licensed under MIT.
- README.mdGood: 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.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.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- Sub1.txt
- Sub2.txt
- Sub3.txt
- Warp_sub.txt