A well-known project done right. Strong docs and solid engineering throughout.
A lightweight, cloud-native GIS platform for visualizing, exploring, and analyzing geospatial data. It runs in the web browser, on the desktop, on mobile, and inside Jupyter notebooks.
Documentation
93
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
85
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.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (backend/geolibre_server/tests).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (eslint.config.mjs).
Project health
92
Dependency manifest found (package.json).
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)
- 154Forks
- 16Releaseslatest 14d ago
Community
- —Community health
- —authors own >50% of commits
- 1,155Watchers
Responsiveness
- 1hMedian issue response
- <1hMedian PR merge time
- 5Open issues
Repository files29 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- apps
- backendGood: Test files detected (backend/geolibre_server/tests).
- docker
- docs
- e2e
- packages
- packaging
- python
- scripts
- tests
- workers
- .dockerignore
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- CITATION.cff
- CLAUDE.md
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- LICENSEGood: Licensed under MIT.
- mkdocs.yml
- netlify.toml
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- playwright.config.ts
- 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.
- requirements-docs.txt
- tsconfig.base.json