97/ 100 · A
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
Python132 starsApache-2.0updated today
Outstanding work. A score of 97/100 puts this repo in a very small tier of truly well-engineered open source projects.
DocumentationREADME, setup, examples, license
EngineeringTests, CI, linting, lockfiles
Project healthDescription, activity, stars, deps
What to fix first
The highest-impact improvements for this repo.
- 1TestsEngineeringIssue
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CDEngineeringInfo
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CDEngineeringInfo
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
Detailed breakdown
Documentation
97- README100
- README is present.
- README is well structured with multiple sections.
- README includes screenshots or visuals. Great for first impressions.
- README has code examples.
- README links to a live demo or deployed app.
- README includes status badges.
- Install and run instructions90
- README documents how to install the project.
- README documents how to run the project.
- No .env.example found (−10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
- License100
- Licensed under Apache-2.0.
- Contributing guide100
- Contributing guide is detailed and thorough.
- Contributing guide includes setup/install instructions.
- Contributing guide describes code style expectations.
- Contributing guide explains how to run tests.
- Contributing guide describes the PR/review workflow.
- Contributing guide includes code examples.
- Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.
Engineering
96- Tests95
- Test files detected (tests).
- Pytest referenced in pyproject.toml and test files present.
- Coverage reporting is configured in pyproject.toml.
- Test files detected (95/100) but no test runner configured (−5 pts). Without a documented test command the suite cannot be verified by contributors.Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- CI/CD100
Not applicable?
- CI is configured (.github/workflows/lint.yml).
- CI workflow runs tests.
- CI runs on pull requests, not just on pushes to main.
- CI workflow runs a lint or format check.
- Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- CI tests across multiple environments or versions.
- Linting and formatting100
- Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
- Reproducibility80
- Lockfile present (uv.lock). Installs are reproducible.
- Environment pinned via environment.yml.
- No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- Issue and PR templates100
- Issue or PR templates present.
- Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
Project health
100- Dependency manifest100
- Dependency manifest found (pyproject.toml).
- pyproject.toml has a [project] table with package metadata.
- pyproject.toml includes a description.
- pyproject.toml specifies requires-python, preventing installs on incompatible versions.
- pyproject.toml has a [build-system] table. The package can be built and published.
- Repository metadata100
- Repository has a description.
- Primary language detected: Python.
- pyproject.toml [project] metadata is complete (description, authors, urls).
- Activity100
- Actively maintained (pushed within the last month).
- 132 stars.
- Housekeeping100
- .gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 15Forks
- 3Releaseslatest 2mo ago
Community
- —Community health
- —authors own >50% of commits
- 132Watchers
Responsiveness
- 14hMedian issue response
- 2hMedian PR merge time
- 10Open 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.