kubevirt/kubevirt-velero-plugin

0

/ 100

Documentation85
Engineering95
Health100
Go46Apache-2.01d ago
Grade a repo

Well engineered for its size. A portfolio piece worth showing off.

Plugin to Velero which automates backing up and restoring KubeVirt/CDI objects

Documentation

85

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

95

CI/CD14pt85

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

Reproducibility6pt97

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

Tests18pt100

Test files detected (pkg/plugin/dv_backup_item_action_test.go).

Linting and formatting5pt100

Formatting enforced (vendor/github.com/fsnotify/fsnotify/.editorconfig).

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)
  • 46
    Forks
  • 13
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 90d
    Median issue response
  • 1d 3h
    Median PR merge time
  • 12
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/coverall.yml).
    Good: Dependabot configured for gomod.
    Good: Issue or PR templates present.
  • cluster-up
  • cmd
  • example
  • hack
  • pkg
    Good: Test files detected (pkg/plugin/dv_backup_item_action_test.go).
  • tests
  • vendor
    Good: Code of conduct present.
    Good: Formatting enforced (vendor/github.com/fsnotify/fsnotify/.editorconfig).
    Good: Security policy present.
  • .gitignore
    Good: .gitignore present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • 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.
  • main.go
  • Makefile
  • OWNERS
  • OWNERS_ALIASES
  • partner-compatibility-testing.md
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.