Strong community interest, but tests, CI, or docs need work.
Bayesian inference with probabilistic programming.
Documentation
73
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.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
60
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/Tests.yml).
Test files detected (test).
Issue or PR templates present.
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)
- 239Forks
- 247Releaseslatest 7y ago
Community
- —Community health
- —authors own >50% of commits
- 2,240Watchers
Responsiveness
- 2d 23hMedian issue response
- 1hMedian PR merge time
- 26Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/Tests.yml).Good: Dependabot covers 2 ecosystems (github-actions, julia). Dependencies stay current.Good: Issue or PR templates present.
- docs
- ext
- src
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- .JuliaFormatter.toml
- CITATION.bib
- CLAUDE.md
- HISTORY.md
- LICENCEGood: Licensed under MIT.
- Project.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.