0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
A blazingly-fast, offline-first format and toolchain for lexical data 📖
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Expand with a description, install steps, usage, and examples.
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
41
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 GPL-3.0.
Engineering
81
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 (Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/build-docs.yml).
Test files detected (crates/odict/tests).
Rust linting configured (node/.editorconfig).
Project health
100
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)
- 13Forks
- 152Releaseslatest 5y ago
Community
- -Community health
- -authors own >50% of commits
- 158Watchers
Responsiveness
- 3d 24hMedian issue response
- 15hMedian PR merge time
- 15Open issues
Repository files31 root entries
- .cargo
- .githubGood: CI is configured (.github/workflows/build-docs.yml).
- .yarn
- cli
- cratesGood: Test files detected (crates/odict/tests).
- docs
- examples
- nodeGood: Rust linting configured (node/.editorconfig).
- python
- scripts
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .oxfmtrc.json
- .release-please-manifest.json
- .rumdl.toml
- .taplo.toml
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- dist-workspace.toml
- DockerfileGood: Environment pinned via Dockerfile.
- hk.pkl
- LICENSEGood: Licensed under GPL-3.0.
- logo.jpg
- mise.toml
- odict.tex
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.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.
- release-please-config.json
- terminal.png
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/theopendictionary/odict)