Getting some notice. Tests and CI would be the fastest wins.
Tracing Compiler with CppAD and Pinocchio
Documentation
82
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
18
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 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/docker-build.yml).
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)
- 11Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 50Watchers
Responsiveness
- 2d 12hMedian issue response
- 4hMedian PR merge time
- 3Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/docker-build.yml).
- cmake
- include
- python
- resources
- src
- third_party
- .clang-format
- .dockerignore
- .gitignoreGood: .gitignore present.
- CMakeLists.txt
- CppADCodeGen.patch
- DockerfileGood: Environment pinned via Dockerfile.
- environment-runtime.yaml
- environment.yaml
- LICENSE.txtGood: Licensed under MIT.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.