0
/ 100
Solid engineering. The main gap is visibility.
Official Terraform Provider for WarpStream
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
70
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 MPL-2.0.
Engineering
86
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 (internal/provider/agent_key_resource_test.go).
CI is configured (.github/workflows/test.yml).
Formatting enforced (.golangci.yml).
Project health
68
No pushes in over a year (−80 pts).
→ A recent commit signals the project is alive and worth contributing to.
Repository has a description.
Dependency manifest found (go.mod).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Dependabot configured for gomod.
- docs
- examples
- internalGood: Test files detected (internal/provider/agent_key_resource_test.go).
- templates
- tools
- .gitignoreGood: .gitignore present.
- .golangci.ymlGood: Formatting enforced (.golangci.yml).
- .goreleaser.yml
- GNUmakefile
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under MPL-2.0.
- main.go
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.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.
- terraform-registry-manifest.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/nkvoll/terraform-provider-warpstream)