97
/ 100
Polished and well engineered. Punching above its star count.
One line code to get any remote sensing foundation model embeddings for any place and any time
Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.
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.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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
97
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Contributing guide is detailed and thorough.
Engineering
96
Lockfile present (uv.lock). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/lint.yml).
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
- -Commits (30d / 90d)
- 15Forks
- 3Releaseslatest 3mo ago
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 138Watchers
Responsiveness
- 14hMedian issue response
- 2hMedian PR merge time
- 11Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/lint.yml).Good: Issue or PR templates present.
- docsGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- examples
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .prettierignore
- CHANGELOG.md
- environment.ymlGood: Environment pinned via environment.yml.
- LICENSEGood: Licensed under Apache-2.0.
- mkdocs.yml
- 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.
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/cybergis/rs-embed)