0
/ 100
Solid engineering. The biggest lever is CI.
AELVO is an autonomous AI software engineering agent that plans, codes, executes, verifies, and recovers from complex development tasks.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
77
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
60
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/publish.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Test files detected (auth/tests).
Linter or formatter configured (ruff.toml).
Project health
100
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 66Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 5Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files34 root entries
- .githooks
- .githubGood: CI is configured (.github/workflows/publish.yml).
- authGood: Test files detected (auth/tests).
- bin
- cli
- cognition
- config
- core
- learning
- mcp
- memory
- planning
- repo_intelligence
- runtime_next
- sandbox_core
- shared_task_board
- specialists
- tests
- tools
- web
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmignore
- .npmrc
- aelvo.bat
- LICENSEGood: Licensed under MIT.
- main.py
- package.jsonGood: Dependency manifest found (package.json).
- pytest.ini
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- requirements-cli.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- ruff.tomlGood: Linter or formatter configured (ruff.toml).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/jaswanth7722/aelvo)