0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Depth-weighted De-Mixing
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 more sections (Overview, Install, Usage, Contributing) using ## headings.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
79
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 BSD-2-Clause.
Engineering
79
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
Lockfile present (docs/requirements.txt). Installs are reproducible.
Test files detected (freyja/tests).
CI is configured (.github/workflows/python-package-conda.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (setup.py).
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)
- 36Forks
- 34Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 134Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 2Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/python-package-conda.yml).Good: Issue or PR templates present.
- ci
- docsGood: Lockfile present (docs/requirements.txt). Installs are reproducible.
- freyjaGood: Test files detected (freyja/tests).
- freyja.egg-info
- .gitignoreGood: .gitignore present.
- CHANGELOG.rst
- LICENSEGood: Licensed under BSD-2-Clause.
- Makefile
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.
- setup.pyGood: Dependency manifest found (setup.py).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/andersen-lab/freyja)