Some interest. A stronger README and CI would help.
An open-source Grasshopper AI plugin
Documentation
69
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 AGPL-3.0.
Engineering
9
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 .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
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 (src/Physalia.UI/package-lock.json). Installs are reproducible.
Project health
100
Dependency manifest found (src/Physalia.Core/Physalia.Core.csproj).
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)
- 0Forks
- 2Releaseslatest 2mo ago
Community
- —Community health
- —authors own >50% of commits
- 18Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files7 root entries
- Files
- Images
- planning
- srcGood: Lockfile present (src/Physalia.UI/package-lock.json). Installs are reproducible.Good: Dependency manifest found (src/Physalia.Core/Physalia.Core.csproj).
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under AGPL-3.0.
- README.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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.