0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Python library for ODE integration via Taylor's method and LLVM
Documentation
76
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 MPL-2.0.
Engineering
30
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/gh_actions_ci.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (pyproject.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)
- 14Forks
- 64Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 88Watchers
Responsiveness
- 14hMedian issue response
- <1hMedian PR merge time
- 3Open issues
Repository files16 root entries
- .circleci
- .githubGood: CI is configured (.github/workflows/gh_actions_ci.yml).Good: Issue or PR templates present.
- cmake
- doc
- heyoka
- tools
- .clang-format
- .clang-tidy
- .clangd
- .gitignoreGood: .gitignore present.
- .travis.yml
- CMakeLists.txt
- environment.ymlGood: Environment pinned via environment.yml.
- LICENSEGood: Licensed under MPL-2.0.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.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.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.