0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
💬 The social web translator
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 a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
82
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 documents how to install the project.
README is present.
Licensed under CC0-1.0.
Engineering
57
No linter or formatter configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
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/auto-merge-dependabot.yaml).
Test files detected (granary/tests).
Lockfile present (requirements.txt). Installs are reproducible.
Project health
100
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)
- 62Forks
- 35Releaseslatest 9y ago
Community
- -Community health
- -authors own >50% of commits
- 516Watchers
Responsiveness
- <1hMedian issue response
- 20hMedian PR merge time
- 42Open issues
Repository files22 root entries
- .circleci
- .githubGood: CI is configured (.github/workflows/auto-merge-dependabot.yaml).Good: Dependabot covers 3 ecosystems (pip, pip, github-actions). Dependencies stay current.
- docs
- granaryGood: Test files detected (granary/tests).
- static
- .gcloudignore
- .gitignoreGood: .gitignore present.
- .readthedocs.yml
- api.py
- app.py
- app.yaml
- config.py
- index.yaml
- instagram_live_test.py
- LICENSEGood: Licensed under CC0-1.0.
- MANIFEST.in
- 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.
- requirements.pinned.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- test_api.py
- test_app.py
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/snarfed/granary)