0
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
A diagnostic wind model developed for use in wildland fire modeling.
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 C (77).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 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
67
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 Other.
Engineering
23
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
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/testing.yml).
Linter or formatter configured (data/leaflet/draw/.editorconfig).
Project health
68
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.
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)
- 55Forks
- 34Releaseslatest 8y ago
Community
- -Community health
- -authors own >50% of commits
- 168Watchers
Responsiveness
- 6d 10hMedian issue response
- 1d 8hMedian PR merge time
- 106Open issues
Repository files31 root entries
- .builds
- .githubGood: CI is configured (.github/workflows/testing.yml).
- autotest
- cmake
- dataGood: Linter or formatter configured (data/leaflet/draw/.editorconfig).
- doc
- images
- scripts
- src
- tools
- .clang-format
- .gitignoreGood: .gitignore present.
- .travis.yml
- AUTHORS
- CITATION
- CMakeLists.txt
- CONTRIBUTORS
- CREDITS.md
- DockerfileGood: Environment pinned via Dockerfile.
- Doxyfile
- HOWTORELEASE
- LICENSEGood: Licensed under Other.
- LICENSE-3RD-PARTY
- NEWS.md
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.
- Singularity
- vcpkg.json
- VERSION
- vg.sup
- wn-ms-resource.rc
- wn-resources.qrc
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/firelab/windninja)