Getting some notice. Tests and CI would be the fastest wins.
Decent Open Scale
Documentation
78
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 GPL-3.0.
Engineering
41
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
CI is configured (.github/workflows/nightly.yml).
Test files detected (tools/test_calibration_validation.py).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 18Forks
- 24Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 83Watchers
Responsiveness
- 16hMedian issue response
- <1hMedian PR merge time
- 4Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/nightly.yml).
- assets
- Hardware
- include
- Scale Case
- src
- toolsGood: Test files detected (tools/test_calibration_validation.py).
- web_apps
- .gitattributes
- .gitignoreGood: .gitignore present.
- check_platform_freshness.py
- CLAUDE.md
- git_rev_macro.py
- LICENSEGood: Licensed under GPL-3.0.
- platformio.ini
- 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.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.