What problem does it solve? Teams often adopt open-source dependencies based on star counts, only to discover later that a project is maintained by one burned-out contributor or carries unpatched security advisories. This Skill reads a repository's actual maintenance vitality — contributor concentration, commit and release cadence, issue responsiveness, and open advisories — and returns a defensible healthy / at-risk / abandoned verdict. ## Core Features & Use Cases - Bus factor analysis: Computes the CHAOSS Contributor Absence Factor (bots excluded) and the Elephant Factor over organisations to expose single-maintainer or single-company dependence. - Cadence and responsiveness scoring: Rates days since last commit, release frequency, median issue first-response time, PR merge time, and issue backlog ratio against documented green/amber/red thresholds. - Security and hygiene checks: Flags advisories unpatched beyond a 90-day fix window, missing licences, and absent SECURITY.md, CI, or code of conduct. - Deterministic companion tool: scripts/osshealth.py (stdlib only) computes the full scorecard, prints the report template, and can fetch metrics from the GitHub REST API. - Use Case: Before betting production infrastructure on a vector database, run the vitality read on both candidate repositories and compare their verdicts and biggest risks side by side. ## Quick Start Ask the assistant to run an OSS project health check on a specific owner/repo slug, covering bus factor, commit and release cadence, issue response time, and open security advisories, and to return a healthy, at-risk, or abandoned verdict.
