0
/ 100
Solid engineering. The biggest lever is a license.
AI-native pipeline that turns data into backtested trading signals
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
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4License6pt
Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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
54
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
80
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/tests).
CI is configured (.github/workflows/backend.yml).
Linter or formatter configured (frontend/.eslintrc.cjs).
Lockfile present (backend/uv.lock). Installs are reproducible.
Project health
95
Actively maintained (pushed within 3 months).
Dependency manifest found (backend/pyproject.toml).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- 1hMedian PR merge time
- 7Open issues
Repository files11 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/backend.yml).Good: Dependabot covers 3 ecosystems (pip, npm, github-actions). Dependencies stay current.
- backendGood: Test files detected (backend/tests).Good: Lockfile present (backend/uv.lock). Installs are reproducible.Good: Environment pinned via backend/Dockerfile.Good: Dependency manifest found (backend/pyproject.toml).
- docs
- frontendGood: Linter or formatter configured (frontend/.eslintrc.cjs).
- .env.example
- .gitignoreGood: .gitignore present.
- .gitleaks.toml
- .pre-commit-config.yaml
- PLAN.md
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/albertoramirez77/tenk-signal)