Strong community interest, but tests, CI, or docs need work.
Firmware Launcher for ESP32 boards like: M5Stack, Lilygo, Marauder and CYD devices.
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 MIT.
Engineering
16
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/main.yml).
Project health
100
Dependency manifest found (webUi/backend/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)
- 202Forks
- 52Releaseslatest 2y ago
Community
- —Community health
- —authors own >50% of commits
- 1,739Watchers
Responsiveness
- 6hMedian issue response
- <1hMedian PR merge time
- 24Open issues
Repository files19 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/main.yml).
- .vscode
- boards
- include
- lib
- lib_modules
- src
- support_files
- webUiGood: Dependency manifest found (webUi/backend/package.json).
- .clang-format
- .gitignoreGood: .gitignore present.
- .gitmodules
- Launcher_anim.webp
- LICENSEGood: Licensed under MIT.
- M5Launcher.png
- New Launcher.jpg
- 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.