Popular for its size, but the engineering basics lag behind the interest.
Documentation
62
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
67
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.
Lockfile present (libs/ai-endpoints/poetry.lock). Installs are reproducible.
Test files detected (libs/ai-endpoints/tests).
CI is configured (.github/workflows/check_diffs.yml).
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (libs/ai-endpoints/pyproject.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 10 / 50Commits (30d / 90d)
- 97Forks
- 64Releaseslatest 2y ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 206Watchers
Responsiveness
- 14hMedian issue response
- 1d 2hMedian PR merge time
- 17Open issues
Repository files7 root entries
- .githubGood: CI is configured (.github/workflows/check_diffs.yml).
- cookbook
- libsGood: Test files detected (libs/ai-endpoints/tests).Good: Lockfile present (libs/ai-endpoints/poetry.lock). Installs are reproducible.Good: Dependency manifest found (libs/ai-endpoints/pyproject.toml).
- studio
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- 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.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.Good: README documents how to run the project.