0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Python Backtesting library for trading research
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
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
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
81
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.
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Test files detected (api/scripts/test_sse.py).
Linter or formatter configured (web-ui/.eslintrc.cjs).
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
- -Commits (30d / 90d)
- 7Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 14Watchers
Responsiveness
- 2d 11hMedian issue response
- <1hMedian PR merge time
- 896Open issues
Repository files46 root entries
- .claude
- .conf
- .githubGood: CI is configured (.github/workflows/ci.yml).
- .specify
- apiGood: Test files detected (api/scripts/test_sse.py).
- docs
- examples
- features
- mcp_server
- migrations
- research
- scripts
- specs
- src
- tests
- web-uiGood: Linter or formatter configured (web-ui/.eslintrc.cjs).
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- AGENTS.md
- backup.sh
- CHANGELOG.md
- CLAUDE.md
- CONTEXT.md
- coverage.json
- deploy-test.cjs
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- install.py
- LICENSEGood: Licensed under MIT.
- main.py
- node
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yaml
- pyproject.toml
- pytest.e2e.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.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.
- restore.sh
- setup_install.py
- setup.py
- show-logs.sh
- test_memory_profile.md
- test_report.md
- uninstall.sh
- uv.lock
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/kaoruha/ginkgo)