Repository Health Score Generator

WHAT IT DOES

This tool generates a comprehensive health score for smart contract repositories by analyzing GitHub metadata and community activity indicators. It evaluates multiple dimensions of repository health—including community engagement (stars, forks), issue management (open vs. closed ratio), pull request efficiency, contributor activity, commit recency, license presence, CODEOWNERS configuration, and test coverage indicators. The tool aggregates these metrics into a single health score (0-100) with categorical ratings (excellent, good, fair, poor), providing a quick at-a-glance assessment of repository quality. It also generates detailed breakdowns of each health factor, enabling teams and auditors to identify specific areas needing improvement. This is essential for developers evaluating dependencies, auditors assessing codebase maturity, and teams tracking their own repository health over time.

HOW TO USE

Connect your wallet (read-only, no transaction required) and select the target network. Enter the GitHub repository (format: owner/repo) you want to evaluate. Provide a GitHub personal access token to increase API rate limits (optional). Click "generate health score" and the tool will fetch repository metadata via the GitHub API. Results display a prominent health score with categorical rating, a breakdown of health factors (community, issue resolution, PR management, activity, code quality), a metrics grid showing key repository stats, and a detailed table of individual metric scores. Use this data to assess dependency quality, track repository improvement, or identify areas requiring attention in your own projects.

TECHNICAL MECHANISM

The analyzer uses the GitHub REST API to fetch comprehensive repository metadata including stars count, forks count, open and closed issues, open and closed pull requests, contributor count, last commit date, license information, and file presence (CODEOWNERS, README, CONTRIBUTING, test directories). It then applies a weighted scoring algorithm that evaluates each metric and normalizes it to a 0-100 scale. Stars and forks are scaled logarithmically to account for the wide range of values across repositories. Issue and PR ratios are calculated as closed/(open+closed) to measure resolution efficiency. Recency is scored based on days since last commit, with recent activity receiving higher scores. Additional points are awarded for presence of license, CODEOWNERS, and test files. The final score is a weighted sum of all factors, with configurable weights emphasizing issue management (15%), PR management (15%), recency (15%), contributors (10%), license (10%), CODEOWNERS (10%), tests (10%), and community engagement (10%). Results are cached during the session to minimize API calls and respect rate limits.

WHAT IT CANNOT SEE

This tool cannot analyze private repositories that are not accessible via the GitHub API. It is limited by GitHub API rate limits, which may restrict the number of repositories that can be analyzed in a single session, especially without a GitHub token. It cannot measure code quality, security vulnerabilities, or code review depth beyond basic metadata metrics. It cannot account for repository-specific nuances such as community engagement quality, discussion activity, or documentation completeness. The tool relies on the accuracy and completeness of GitHub metadata; if metadata is incomplete (e.g., missing issue labels or PR reviews), the score may be inaccurate. It cannot detect off-platform development activity or contributions from forked repositories not reflected in the primary repository's metadata. It cannot measure actual code documentation quality or testing coverage beyond presence of test directories. The score is a heuristic and should not be used as the sole indicator of repository quality or security. It is limited to repositories that are accessible and have at least some public visibility.

PLEASE NOTE

This is a read‑only analytics tool—it never submits transactions or signs anything. It is designed for EVM‑compatible chains but can analyze GitHub data for any repository. For best results, provide a GitHub personal access token to increase API rate limits from 60 to 5,000 requests per hour. The scoring algorithm is a heuristic and should be considered one of many factors when evaluating repository quality. The tool respects GitHub's API terms of service and includes appropriate delays between requests to avoid rate limiting.