Good shape overall. A few tweaks would push it into the top tier.
An easy-to-use framework for modular RAG
Documentation
84
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 MIT.
Engineering
77
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/ci.yml).
Lockfile present (poetry.lock). Installs are reproducible.
Test files detected (integrations/pairag-file/tests).
Linter or formatter configured (frontend/.eslintrc.json).
Project health
96
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)
- 74Forks
- 12Releaseslatest 5mo ago
Community
- —Community health
- —authors own >50% of commits
- 470Watchers
Responsiveness
- 4d 17hMedian issue response
- 1hMedian PR merge time
- 0Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- alembic
- backend
- docker
- docs
- examples
- frontendGood: Linter or formatter configured (frontend/.eslintrc.json).
- integrationsGood: Test files detected (integrations/pairag-file/tests).
- resources
- scripts
- skills
- tests
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- alembic.ini
- DockerfileGood: Environment pinned via Dockerfile.
- Dockerfile.api
- Dockerfile.base
- LICENSEGood: Licensed under MIT.
- Makefile
- poetry.lockGood: Lockfile present (poetry.lock). Installs are reproducible.
- 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.