cloud-barista/cb-tumblebug

0

/ 100

Documentation93
Engineering70
Health94
Go81Apache-2.01d ago
Grade a repo

Solid foundation. Invest in docs and CI to grow from here.

Cloud-Barista Multi-Cloud Infra Management Framework

Documentation

93

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

70

Tests18pt30

Go module found but no *_test.go files detected.

→ Add *_test.go files alongside your packages and run `go test ./...`.

CI/CD14pt85

CI is configured (.github/workflows/continuous-integration-mcp.yaml).

Reproducibility6pt97

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

Linting and formatting5pt100

Formatting enforced (src/.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 53
    Forks
  • 184
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 81
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 26
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/continuous-integration-mcp.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • assets
  • cmd
  • conf
  • docs
  • init
  • scripts
    Issue: Build artifacts or local files may be committed (scripts/etcd/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • src
    Good: Formatting enforced (src/.golangci.yml).
  • .all-contributorsrc
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • docker-compose.traefik.yaml
  • docker-compose.yaml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • go.work
  • go.work.sum
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • OWNERS
  • README.md
    Good: 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.