Lots of room to improve. Start with a README and CI.
rhthsa / openshift-demo
Documentation
41
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
README documents how to install the project.
README is present.
Engineering
25
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/node.js.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Project health
23
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.
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 0Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files53 root entries
- .githubGood: CI is configured (.github/workflows/node.js.yml).
- bin
- ci-cd
- compliance-operator-reports
- images
- manifests
- .gitattributes
- acm-application-management.md
- acm-hibernate.md
- acm-observability.md
- acs.md
- application-metrics.md
- assign-pod-to-node.md
- book.json
- build-with-dev-console.md
- build-with-oc.md
- build-with-odo.md
- ci-cd-with-jenkins.md
- ci-cd.md
- clair4-on-ocp.md
- compliance-operator.md
- cost-management.md
- cost-mgmt-new-njiratti.md
- custom-alert.md
- custom-roles.md
- eap-on-ocp.md
- gitops.md
- grpc.md
- health.md
- helm.md
- hpa.md
- imagestreams.md
- infrastructure-authentication-providers.md
- infrastructure-backup-etcd.md
- infrastructure-cluster-cost-management.md
- infrastructure-cluster-logging.md
- infrastructure-cluster-registry.md
- infrastructure-cluster-upgrade.md
- infrastructure-csi-storage.md
- infrastructure-infra-nodes.md
- infrastructure-monitoring-alerts.md
- infrastructure-networking.md
- infrastructure-taint-and-toleration.md
- kustomize.md
- openshift-route.md
- openshift-service-mesh.md
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- puppeteer-config.json
- README.mdGood: 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- SUMMARY.md
- template-page.md
- thanos-object-storage.yaml
- thanos-receive.md