Some interest. A stronger README and CI would help.
Documentation
21
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
README is present.
Engineering
11
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 dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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/clear.yml).
Project health
43
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.
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 11Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 1Open issues
Repository files39 root entries
- .githubGood: CI is configured (.github/workflows/clear.yml).
- .timestamp
- 443trojanwscdn.yaml
- Airuopcdn.yaml
- Airuopservername.yaml
- Airuopsni.yaml
- anaercdn.yaml
- anaerservername.yaml
- anaersni.yaml
- busymilkcdn.yaml
- chengaopancdn.yaml
- chengaopanservername.yaml
- chengaopansni.yaml
- DheMasker-Surfing-Fake-IP-Anti-DNSleak.yaml
- happysurfingcdn.yaml
- happysurfingsni.yaml
- mahdiblandcdn.yaml
- mahdiblandservername.yaml
- mahdiblandsni.yaml
- MrMohebicdn.yaml
- MrMohebiservername.yaml
- MrMohebisni.yaml
- peasoftcdn.yaml
- peasoftservername.yaml
- peasoftsni.yaml
- PuddinCatcdn.yaml
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tbbatbbcdn.yaml
- tbbatbbservername.yaml
- tbbatbbsni.yaml
- WilliamStar007cdn.yaml
- WilliamStar007servername.yaml
- WilliamStar007sni.yaml
- zzz000allcdn.sh
- zzz000allsni.sh
- zzz000newcdn.sh
- zzz000newservername.sh
- zzz000newsni.sh
- zzz000trojanvmesswscdn.sh