0
/ 100
Polished and well engineered. Punching above its star count.
Support Let's Encrypt for a Go server application.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add more sections (Overview, Install, Usage, Contributing) using ## headings.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 4Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
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
79
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
87
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.
Lockfile present (go.sum). Installs are reproducible.
Test files detected (autotls_test.go).
CI is configured (.github/workflows/go.yml).
Formatting enforced (.editorconfig).
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)
- 43Forks
- 14Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 409Watchers
Responsiveness
- 31d 6hMedian issue response
- 7hMedian PR merge time
- 11Open issues
Repository files14 root entries
- _example
- .githubGood: CI is configured (.github/workflows/go.yml).Good: Dependabot covers 2 ecosystems (github-actions, gomod). Dependencies stay current.
- .editorconfigGood: Formatting enforced (.editorconfig).
- .gitignoreGood: .gitignore present.
- .golangci.yml
- .goreleaser.yaml
- autocertcache.go
- autotls_test.goGood: Test files detected (autotls_test.go).
- autotls.go
- doc.go
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/gin-gonic/autotls)