Getting some notice. Tests and CI would be the fastest wins.
NCBI C++ Toolkit package sources
Documentation
32
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 Other.
Engineering
58
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.
Test files detected (include/test).
CI is configured (.gitlab-ci.yml).
Project health
100
Dependency manifest found (compilers/vs2019/dll/build/gbench/ncbi_gbench.sln).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 117 / 507Commits (30d / 90d)
- 45Forks
- 34Releaseslatest 1y ago
Community
- 37% - WeakCommunity health
- 5 bus factorauthors own >50% of commits
- 98Watchers
Responsiveness
- 3hMedian issue response
- —Median PR merge time
- 1Open issues
Repository files11 root entries
- compilersGood: Dependency manifest found (compilers/vs2019/dll/build/gbench/ncbi_gbench.sln).Good: .gitignore present.
- doc
- includeGood: Test files detected (include/test).
- scripts
- src
- .gitlab-ci.ymlGood: CI is configured (.gitlab-ci.yml).
- cmake-configure
- cmake-configure.bat
- configure
- LICENSEGood: Licensed under Other.
- README.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.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.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.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.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.