0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
jinja2 template renderer for aiohttp.web
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.
- 2README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
- 3README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
59
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 Apache-2.0.
Engineering
79
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 (pytest.ini).
Lockfile present (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.flake8).
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)
- 61Forks
- 27Releaseslatest 10y ago
Community
- -Community health
- -authors own >50% of commits
- 239Watchers
Responsiveness
- 2hMedian issue response
- 13hMedian PR merge time
- 5Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.
- aiohttp_jinja2
- docs
- tests
- .codecov.yml
- .coveragerc
- .flake8Good: Linter or formatter configured (.flake8).
- .gitignoreGood: .gitignore present.
- .mypy.ini
- .pre-commit-config.yaml
- .readthedocs.yml
- CHANGES.rst
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- MANIFEST.in
- pytest.iniGood: Test files detected (pytest.ini).
- README.rstGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements-dev.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- setup.cfg
- setup.py
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/aio-libs/aiohttp-jinja2)