Good shape overall. A few tweaks would push it into the top tier.
Rapid YAML - a library to parse and emit YAML, and do it fast.
Documentation
90
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
55
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 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/benchmarks.yml).
Test files detected (test).
Lockfile present (doc/requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (doc/requirements.txt).
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)
- 134Forks
- 25Releaseslatest 2y ago
Community
- —Community health
- —authors own >50% of commits
- 739Watchers
Responsiveness
- 1dMedian issue response
- 17hMedian PR merge time
- 34Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/benchmarks.yml).
- api
- bm
- changelog
- cmake
- docGood: Lockfile present (doc/requirements.txt). Installs are reproducible.Good: Dependency manifest found (doc/requirements.txt).
- ext
- img
- samples
- src
- src_extra
- testGood: Test files detected (test).
- toolsGood: Environment pinned via tools/test_suite/Dockerfile.
- .clang-tidy
- .gitignoreGood: .gitignore present.
- .gitmodules
- .lgtm.yml
- .readthedocs.yaml
- CMakeLists.txt
- compat.cmake
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Good: Contributing guide includes code examples.
- LICENSE.txtGood: Licensed under MIT.
- 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.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- ROADMAP.md
- tbump.toml