Popular for its size, but the engineering basics lag behind the interest.
Nimony is a new Nim implementation that is in heavy development.
Documentation
70
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 MIT.
Engineering
47
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/ci.yml).
Test files detected (src/njvl/tests).
Project health
68
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.
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)
- 32Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 405Watchers
Responsiveness
- 1d 9hMedian issue response
- <1hMedian PR merge time
- 40Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot configured for github-actions.
- doc
- examples
- icons
- lib
- srcGood: Test files detected (src/njvl/tests).
- tests
- tools
- vendor
- .gitignoreGood: .gitignore present.
- .gitmodules
- AGENTS.md
- clang.args
- CLAUDE.md
- license.txtGood: 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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.