0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Free tools for building robust, clustered server infrastructure — WolfStack, WolfScale, WolfDisk, WolfNet
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (78).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add integration tests in a tests/ directory or unit tests via #[cfg(test)] blocks.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
61
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
47
No Rust linting or formatting enforced.
→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.
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.
Cargo.toml has dev-dependencies (may include test tooling).
CI is configured (.github/workflows/close-external-prs.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Project health
98
Dependency manifest found (Cargo.toml).
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)
- 24Forks
- 16Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 280Watchers
Responsiveness
- 17hMedian issue response
- <1hMedian PR merge time
- 2Open issues
Repository files24 root entries
- .codewolf
- .githubGood: CI is configured (.github/workflows/close-external-prs.yml).
- docs
- examples
- scripts
- src
- web
- wolfdiskGood: Environment pinned via wolfdisk/docker/Dockerfile.
- wolfnet
- .gitignoreGood: .gitignore present.
- build_out.txt
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- check_out.txt
- install_service.sh
- LICENSEGood: Licensed under MIT.
- 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.Good: README includes status badges.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- run.sh
- setup_lb.sh
- setup.sh
- wolfscale.logrotate
- wolfscale.png
- wolfscale.toml.example
- wolfstack
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/wolfsoftwaresystemsltd/wolfscale)