Getting noticed, but rough fundamentals could turn visitors away.
Deltarune fangame engine for Love2D
Documentation
72
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 BSD-3-Clause.
Engineering
26
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.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)
- 125Forks
- 17Releaseslatest 4y ago
Community
- —Community health
- —authors own >50% of commits
- 263Watchers
Responsiveness
- <1hMedian issue response
- 13hMedian PR merge time
- 18Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- assets
- configs
- data
- data_templates
- docs
- lib
- luadoc_meta
- mod_template
- mods
- src
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .luarc.json
- build.py
- conf.lua
- gamecontrollerdb.txt
- icon.ico
- icon.png
- icon.rc
- icon.res
- LICENSEGood: Licensed under BSD-3-Clause.
- main.lua
- 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.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.
- VERSION