Getting some notice. Tests and CI would be the fastest wins.
auto-updating terraform providers for nix [maintainer=@zimbatm]
Documentation
69
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
47
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/cron.yml).
Test files detected (test).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 32Forks
- 0Releases
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 59Watchers
Responsiveness
- 57d 20hMedian issue response
- 11hMedian PR merge time
- 3Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/cron.yml).Good: Dependabot configured for github-actions.
- example
- providers
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- ci.sh
- default.nix
- flake.lock
- flake.lock.nix
- flake.nix
- LICENSEGood: Licensed under MIT.
- overlay.nix
- 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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- release.nix
- shell.nix
- update.rb