opentofu/registry

0

/ 100

Documentation58
Engineering81
Health100
Go408Apache-2.0today
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Metadata and tooling for the OpenTofu registry

Documentation

58

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt75

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

81

Reproducibility6pt70

Lockfile present (src/go.sum). Installs are reproducible.

CI/CD14pt72

CI is configured (.github/workflows/build.yaml).

Tests18pt80

Test files detected (modules/a/adamconway/test).

Linting and formatting5pt100

Linter or formatter configured (src/.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 67 / 235
    Commits (30d / 90d)
  • 68
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 408
    Watchers

Responsiveness

  • 5d 12h
    Median issue response
  • 18h
    Median PR merge time
  • 18
    Open issues
Repository files15 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yaml).
    Good: Issue or PR templates present.
  • keys
  • modules
    Good: Test files detected (modules/a/adamconway/test).
  • providers
  • src
    Good: Linter or formatter configured (src/.golangci.yml).
    Good: Lockfile present (src/go.sum). Installs are reproducible.
    Good: Dependency manifest found (src/go.mod).
  • .gitignore
    Good: .gitignore present.
  • .shellcheckrc
  • BLACKLIST_README.md
    Good: README is present.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • POLICY.md
  • PROCEDURES.md
  • README.md
  • SECURITY.md
    Good: Security policy present.
  • versions_blacklist.json