0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
A catalogue of available long read sequencing data analysis tools
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to D (67).
See your top fixesTop 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
67
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
41
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.
CI is configured (.github/workflows/automated_tool_search.yml).
Test files detected (docs/test_server.py).
Project health
62
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.
.gitignore present.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 19Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 89Watchers
Responsiveness
- 21d 16hMedian issue response
- 1hMedian PR merge time
- 1Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/automated_tool_search.yml).
- docsGood: Test files detected (docs/test_server.py).
- libraries
- R
- .DS_StoreIssue: Build artifacts or local files may be committed (.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitattributes
- .gitignoreGood: .gitignore present.
- append_script.py
- benchmark_studies.csv
- build_lrs_db.R
- generate_pr_message.py
- LICENSEGood: Licensed under MIT.
- long_read_tools_master.csv
- long_read_tools.Rproj
- lrdb_contribution
- lrdb_contribution.md
- new_submission_check.R
- new_submissions_conflicts.csv
- new_submissions_no_conflicts.csv
- new_submissions.csv
- new_tools.csv
- PULL_REQUEST_TEMPLATE.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.Good: README documents how to run the project.
- robots.txt
- search_tools.py
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mritchielab/long_read_tools)