googlecloudplatform/gcs-fuse-csi-driver

0

/ 100

Documentation74
Engineering88
Health100
Go165Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

The Google Cloud Storage FUSE Container Storage Interface (CSI) Plugin.

Documentation

74

README12pt55

README is present.

Contributing guide5pt58

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

88

CI/CD14pt57

CI is configured (.github/workflows/ci.yml).

Tests18pt100

Test files detected (hack/boilerplate/test).

Linting and formatting5pt100

Formatting enforced (test/vendor/github.com/Masterminds/semver/v3/.golangci.yml).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (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

  • —
    Commits (30d / 90d)
  • 59
    Forks
  • 185
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 7d 11h
    Median issue response
  • 15h
    Median PR merge time
  • 62
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 5 ecosystems (docker, docker, docker, docker, gomod). Dependencies stay current.
    Good: Issue or PR templates present.
  • .prow
  • cmd
    Good: Environment pinned via cmd/csi_driver/Dockerfile.
  • deploy
  • docs
  • examples
  • hack
    Good: Test files detected (hack/boilerplate/test).
  • pkg
  • test
    Good: Code of conduct present.
    Good: Formatting enforced (test/vendor/github.com/Masterminds/semver/v3/.golangci.yml).
    Good: Security policy present.
  • vendor
  • .gitignore
    Good: .gitignore present.
  • cloudbuild-build-image.yaml
  • cloudbuild-install.yaml
  • cloudbuild-uninstall.yaml
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • README.md
    Good: 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.