Getting some notice. Tests and CI would be the fastest wins.
A fast, customizable service detection tool powered by a flexible fingerprint system. It helps you identify services, APIs, and network configurations across your infrastructure.
Documentation
85
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 Other.
Engineering
41
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.
CI is configured (.github/workflows/lint.yml).
Lockfile present (go.sum). Installs are reproducible.
Linter or formatter configured (.golangci.yml).
Project health
100
Dependency manifest found (go.mod).
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
- 28Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 47Watchers
Responsiveness
- <1hMedian issue response
- 1hMedian PR merge time
- 300Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/lint.yml).
- .vscode
- cmd
- config
- data
- pkg
- templates
- tools
- .gitignoreGood: .gitignore present.
- .golangci.ymlGood: Linter or formatter configured (.golangci.yml).
- build.bat
- build.sh
- DockerfileGood: Environment pinned via Dockerfile.
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under Other.
- Makefile
- poc_stats.md
- 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.