bigstack-oss/cubecos
Grade a repo

0

/ 100

GradeC

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

Top 33% of 5,156 graded repos

Open-source cloud native platform that automates and simplifies the deployment of virtualization, Kubernetes, and OpenStack infrastructure.

Documentation86
Engineering66
Health100
Python157Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

86

README12pt75

README is present.

Contributing guide5pt89

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

66

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt57

CI is configured (.github/workflows/dependency-review.yml).

Reproducibility6pt70

Lockfile present (core/cubectl/app/go.sum). Installs are reproducible.

Tests18pt80

Test files detected (core/cube_sdk_library/src/config_file/tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (core/cubectl/app/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)
  • 18
    Forks
  • 2
    Releaseslatest 5mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 157
    Watchers

Responsiveness

  • 2d 23h
    Median issue response
  • 1d 6h
    Median PR merge time
  • 299
    Open issues
Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/dependency-review.yml).
    Good: Issue or PR templates present.
  • core
    Good: Test files detected (core/cube_sdk_library/src/config_file/tests).
    Good: Lockfile present (core/cubectl/app/go.sum). Installs are reproducible.
    Good: Dependency manifest found (core/cubectl/app/go.mod).
  • doc
  • jail
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct 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.
    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.
  • git-conventional-commits.yaml
  • hex
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTAINERS.md
  • Makefile
  • project.mk
  • 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/bigstack-oss/cubecos)](https://www.repo-grade.com/report/bigstack-oss/cubecos)

More graded Python repos