Getting noticed, but rough fundamentals could turn visitors away.
科学上网: 免费!✈️✈️✈️自动抓取Alvin9999的节点🪜🪜🪜,已适配账号迁移🪜🪜🪜,多格式支持。✈️✈️✈️,,,,chatgpt,gemini,claude,grok,x,twitter,youtube,油管,discord,google,yandex,tor,github,代理,节点,梯子,fanqiang
Documentation
30
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
45
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.
A test framework is installed but no test script or test files were found.
→ Add a scripts.test entry and create your first test file.
CI is configured (.github/workflows/hourly-write.yml).
Lockfile present (bun.lock). Installs are reproducible.
Linter or formatter configured (devDependency in package.json).
Project health
86
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 22Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 184Watchers
Responsiveness
- 10d 7hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/hourly-write.yml).
- data
- src
- .gitignoreGood: .gitignore present.
- .oxfmtrc.json
- .oxlintrc.json
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- clash_template.yaml
- package.jsonGood: Dependency manifest found (package.json).
- 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.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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.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.
- tsconfig.json