ghs-repo-scan

Auditing a GitHub repository involves scanning for missing files like README, LICENSE, CODEOWNERS, and CI/CD configurations, along with checking branch protection rules and security policies to generate a scored health report.

A GitHub repository health score evaluates adherence to best practices by identifying missing files, CI/CD setup, branch protection, and security policies, calculating a quantitative score based on predefined logic to represent overall repository quality.

To organize open GitHub issues into a structured backlog, fetch and triage open issues from the repository, presenting them in a structured format and saving the findings as structured markdown backlog items.

Yes, you need the gh CLI, git, and python3 installed to scan your repository for best practices, as these dependencies are required to execute the health check, fetch issues, and generate the SUMMARY.md report.

Yes, a repository health check scans for missing CI/CD configurations and CODEOWNERS files, alongside README, LICENSE, branch protection rules, and security policies to evaluate overall repository quality and setup.

The best way to assess an existing GitHub repository's quality is to run an automated scan that checks best practice adherence, identifies missing files, fetches open issues, and produces a comprehensive health score with actionable backlog items.