49
/ 100
Some interest. A stronger README and CI would help.
Production catalog for Red Hat Certified Operator Bundles
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to D (62).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
45
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.
Licensed under Apache-2.0.
Engineering
47
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.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/pipeline-trigger.yml).
Test files detected (operators/abinitio-runtime-operator/v4.2.2-6/tests).
Project health
62
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
.gitignore present.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 241 / 762Commits (30d / 90d)
- 631Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 9 bus factorauthors own >50% of commits
- 78Watchers
Responsiveness
- 21d 24hMedian issue response
- 4hMedian PR merge time
- 18Open issues
Repository files7 root entries
- .githubGood: CI is configured (.github/workflows/pipeline-trigger.yml).
- catalogs
- operatorsGood: Test files detected (operators/abinitio-runtime-operator/v4.2.2-6/tests).Good: Environment pinned via operators/abinitio-runtime-operator/v4.2.2-6/Dockerfile.Issue: Build artifacts or local files may be committed (operators/pan-cn-series-operator/1.0.0/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitignoreGood: .gitignore present.
- config.yaml
- LICENSEGood: Licensed under Apache-2.0.
- README.mdGood: 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/redhat-openshift-ecosystem/certified-operators)