Popular for its size, but the engineering basics lag behind the interest.
reverse engineering the best-selling drones on Amazon to control programmatically
Documentation
82
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
48
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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 (backend/requirements.txt). Installs are reproducible.
Test files detected (backend/plugins/follow/test_yolo.py).
Linter or formatter configured (frontend/eslint.config.js).
Project health
100
Dependency manifest found (backend/requirements.txt).
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)
- 70Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 516Watchers
Responsiveness
- 1d 16hMedian issue response
- 1hMedian PR merge time
- 5Open issues
Repository files8 root entries
- backendGood: Test files detected (backend/plugins/follow/test_yolo.py).Good: Lockfile present (backend/requirements.txt). Installs are reproducible.Good: Dependency manifest found (backend/requirements.txt).
- docs
- experimental
- frontendGood: Linter or formatter configured (frontend/eslint.config.js).
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under Apache-2.0.
- NOTICE
- 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.