redhat-openshift-ecosystem/community-operators-prod

0

/ 100

Documentation47
Engineering42
Health68
Dockerfile135Apache-2.01d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

community-operators metadata backing OpenShift OperatorHub

Documentation

47

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt65

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.

License6pt100

Licensed under Apache-2.0.

Engineering

42

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.

Issue and PR templates6pt0

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt40

CI is configured (.github/workflows/pr-label-command.yml).

Tests18pt80

Test files detected (operators/3scale-community-operator/0.10.1/tests).

Project health

68

Dependency manifest6pt0

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.

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)
  • 639
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 21h
    Median issue response
  • 2h
    Median PR merge time
  • 31
    Open issues
Repository files9 root entries
  • .github
    Good: CI is configured (.github/workflows/pr-label-command.yml).
  • catalogs
  • docs
  • operators
    Good: Test files detected (operators/3scale-community-operator/0.10.1/tests).
    Good: Environment pinned via operators/apicurito/0.1.0/Dockerfile.
  • .gitignore
    Good: .gitignore present.
  • config.yaml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • mkdocs.yml
  • 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.
    Good: README includes status badges.
    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.