Good shape overall. A few tweaks would push it into the top tier.
Interactive map showing premises eligible for the NBN FTTP upgrade program.
Documentation
82
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
66
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.
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.
Test files detected (tests).
CI is configured (.github/workflows/main.yml).
Lockfile present (code/requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (code/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)
- 26Forks
- 47Releaseslatest 8mo ago
Community
- —Community health
- —authors own >50% of commits
- 216Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 47Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.
- codeGood: Lockfile present (code/requirements.txt). Installs are reproducible.Good: Dependency manifest found (code/requirements.txt).
- extraGood: Environment pinned via extra/db/Dockerfile.
- resources
- results
- site
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .htmlhintrc
- .mega-linter.yml
- CNAME
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.