Popular for its size, but the engineering basics lag behind the interest.
Open source icons for custom Godot nodes
Documentation
70
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
21
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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 linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
Lockfile present (site_src/Gemfile.lock). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (site_src/Gemfile).
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)
- 3Forks
- 4Releaseslatest 1d ago
Community
- —Community health
- —authors own >50% of commits
- 280Watchers
Responsiveness
- 2d 1hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files9 root entries
- .githubGood: Issue or PR templates present.
- addons
- docs
- site_srcGood: Lockfile present (site_src/Gemfile.lock). Installs are reproducible.Good: Dependency manifest found (site_src/Gemfile).
- .gitattributes
- .gitignoreGood: .gitignore present.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- LICENSEGood: Licensed under MIT.
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.