0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Orly™ — An open-source graph database
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
62
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.
Lockfile present (examples/agent-swarm/go.sum). Installs are reproducible.
Test files detected (base/test).
CI is configured (.github/workflows/ci.yml).
Project health
100
Dependency manifest found (examples/agent-swarm/go.mod).
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)
- 1Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 21Watchers
Responsiveness
- 19hMedian issue response
- <1hMedian PR merge time
- 6Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- baseGood: Test files detected (base/test).
- docs
- examplesGood: Lockfile present (examples/agent-swarm/go.sum). Installs are reproducible.Good: Dependency manifest found (examples/agent-swarm/go.mod).
- jhm
- orly
- tests
- third_party
- tools
- .gitignoreGood: .gitignore present.
- AUTHORS
- bootstrap.jhm
- bootstrap.sh
- CHANGELOG.md
- debug.jhm
- LICENSEGood: Licensed under Other.
- Makefile
- 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.
- release.jhm
- root.jhm
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/orlyatomics/orly)