Popular for its size, but the engineering basics lag behind the interest.
Client database definitions for World of Warcraft
Documentation
45
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Licensed under Other.
Engineering
43
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
Lockfile present (code/Python/requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/dump_and_merge.yml).
.NET formatting configured (code/C#/.editorconfig).
Project health
100
Dependency manifest found (code/C#/DBDefsConverter/DBDefsConverter.csproj).
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)
- 120Forks
- 574Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 316Watchers
Responsiveness
- 7hMedian issue response
- 18hMedian PR merge time
- 9Open issues
Repository files14 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/dump_and_merge.yml).
- analytics
- codeGood: .NET formatting configured (code/C#/.editorconfig).Good: Lockfile present (code/Python/requirements.txt). Installs are reproducible.Good: Dependency manifest found (code/C#/DBDefsConverter/DBDefsConverter.csproj).
- definitions
- exedumper
- meta
- schlumpf
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- LICENSE.mdGood: Licensed under Other.
- manifest.json
- README.mdGood: 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.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.
- UPDATING.md