Popular for its size, but the engineering basics lag behind the interest.
Chrome Offline Updater and Making Chrome Portable.
Documentation
56
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 AGPL-3.0.
Engineering
42
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.
Go module found but no *_test.go files detected.
→ Add *_test.go files alongside your packages and run `go test ./...`.
CI is configured (.github/workflows/build.yml).
Lockfile present (go.sum). Installs are reproducible.
Formatting enforced (gofmt (built into Go toolchain)).
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)
- 17Forks
- 17Releaseslatest 1y ago
Community
- —Community health
- —authors own >50% of commits
- 288Watchers
Responsiveness
- 1d 20hMedian issue response
- 7hMedian PR merge time
- 1Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).
- assets
- doc
- lang
- .gitignoreGood: .gitignore present.
- base.go
- bean.go
- bundle.go
- chrome_auto_update.go
- chrome_info.go
- chrome_plus.go
- common.go
- custom_theme.go
- data.go
- download.go
- FyneApp.toml
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- layout.go
- LICENSEGood: Licensed under AGPL-3.0.
- locale_windows.go
- locale.go
- log.go
- main.go
- README_ZH.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.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- README.md
- setting.go