68
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (82).
See your top fixesTop 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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues 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
88
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
A license file is present.
Engineering
63
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/issue.yml).
Test files detected (lib/IRremoteESP8266/test).
Linter or formatter configured (lib/lvgl/.editorconfig).
Issue or PR templates present.
Project health
46
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.
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
.gitignore present.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 5 / 14Commits (30d / 90d)
- 62Forks
- 0Releases
Community
- 25% - WeakCommunity health
- -authors own >50% of commits
- 450Watchers
Responsiveness
- 1d 5hMedian issue response
- 13d 16hMedian PR merge time
- 6Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/issue.yml).
- 3D_files
- boards
- docs
- examples
- firmware
- hardware
- libGood: A license file is present.Good: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: Test files detected (lib/IRremoteESP8266/test).Good: Linter or formatter configured (lib/lvgl/.editorconfig).Good: Issue or PR templates present.Good: Security policy present.Issue: Build artifacts or local files may be committed (lib/IRremoteESP8266/.idea/IRremoteESP8266.iml) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitignoreGood: .gitignore present.
- platformio.ini
- README_CN.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.
- README-bk1.md
- README.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/xinyuan-lilygo/t-embed-cc1101)