0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Open Agentic AI Platform - The home your agents deserve
Documentation
81
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 AGPL-3.0.
Engineering
63
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.
Test files detected (backend/agent_runtime/test_continuation_nudge.py).
Lockfile present (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/test.yml).
Project health
100
Dependency manifest found (requirements.txt).
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)
- 65Forks
- 12Releaseslatest 22d ago
Community
- -Community health
- -authors own >50% of commits
- 281Watchers
Responsiveness
- 5hMedian issue response
- 17hMedian PR merge time
- 23Open issues
Repository files34 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).
- backendGood: Test files detected (backend/agent_runtime/test_continuation_nudge.py).
- cli
- defaults
- dockerGood: Environment pinned via docker/tools/Dockerfile.
- docs
- evaluator
- evonet
- improver
- lib
- models
- plugins
- routes
- scripts
- seed
- skills
- skillsets
- static
- templates
- tools
- unit_tests
- .env.example
- .gitignoreGood: .gitignore present.
- app.py
- CHANGELOG.md
- COMMERCIAL.md
- config.py
- evonic
- install.sh
- LICENSEGood: Licensed under AGPL-3.0.
- NOTICE
- 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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- VERSION