Popular for its size, but the engineering basics lag behind the interest.
Documentation
74
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.
README documents how to install the project.
Licensed under Other.
Engineering
46
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/build.yml).
Test files detected (test).
Project health
53
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.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 108Forks
- 9Releaseslatest 1mo ago
Community
- —Community health
- —authors own >50% of commits
- 243Watchers
Responsiveness
- 1hMedian issue response
- <1hMedian PR merge time
- 7Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).
- audit-report
- bench
- cmake
- docs
- emp-tool
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CMakeLists.txt
- LICENSEGood: Licensed under Other.
- 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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- run
- verdicts.txt