79
/ 100
Solid foundation. Invest in docs and CI to grow from here.
A fast canonical-correlation-based search algorithm for feature selection, system identification, data pruning, etc.
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.
- 3README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
- 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
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 MIT.
Engineering
85
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
CI is configured (.github/workflows/ci.yml).
Test files detected (fastcan/narx/tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Issue or PR templates present.
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
- 8 / 15Commits (30d / 90d)
- 5Forks
- 53Releaseslatest 2y ago
Community
- 50% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 24Watchers
Responsiveness
- 6hMedian issue response
- <1hMedian PR merge time
- 8Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- asv_benchmarks
- docGood: Environment pinned via doc/environment.yml.
- examples
- fastcanGood: Test files detected (fastcan/narx/tests).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .readthedocs.yml
- LICENSEGood: Licensed under MIT.
- meson.build
- pixi.lock
- pixi.toml
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/scikit-learn-contrib/fastcan)