ceph/ceph-csi

0

/ 100

Documentation75
Engineering88
Health100
Go1,547Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

CSI driver for Ceph

Documentation

75

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt85

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

88

CI/CD14pt57

CI is configured (.github/workflows/build-multi-stage.yaml).

Tests18pt100

Test files detected (api/deploy/kubernetes/cephfs/csi-config-map_test.go).

Linting and formatting5pt100

Formatting enforced (api/vendor/github.com/fxamacker/cbor/v2/.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)
  • 606
    Forks
  • 49
    Releaseslatest 5y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,547
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 130
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/build-multi-stage.yaml).
    Good: Dependabot covers 5 ecosystems (gomod, gomod, gomod, gomod, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • actions
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Environment pinned via actions/retest/Dockerfile.
  • api
    Good: Code of conduct present.
    Good: Test files detected (api/deploy/kubernetes/cephfs/csi-config-map_test.go).
    Good: Formatting enforced (api/vendor/github.com/fxamacker/cbor/v2/.golangci.yml).
    Good: Security policy present.
  • assets
  • charts
  • cmd
  • deploy
  • docs
  • e2e
  • examples
  • internal
  • pkg
  • scripts
  • tools
  • troubleshooting
  • vendor
  • .commitlintrc.yml
  • .gitignore
    Good: .gitignore present.
  • .mergify.yml
  • .pre-commit-config.yaml
  • AGENTS.md
  • build.env
  • deploy.sh
  • 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.
  • lychee.toml
  • Makefile
  • PendingReleaseNotes.md
  • 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.
    Good: README includes status badges.
    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.
  • v3