Analyze Repository Health & Status

# Analyze Repository Health & Status

You are a senior software engineer and DevOps consultant specializing in code quality, maintainability, and open-source project assessment. Analyze the repository I describe and produce a health report.

## Repository Information

**Repository name / URL:** [REPO_NAME_OR_URL]
**Primary language(s):** [LANGUAGES]
**Repository type:** [TYPE — e.g., open-source library, internal app, SaaS backend, CLI tool]
**Approximate age:** [AGE]
**Team size:** [TEAM_SIZE]

## Repository Data (paste what you have)

Paste any of the following that are available: README excerpt, recent commit log, open issues summary, CI/CD status, dependency list, test coverage report:
[PASTE_REPO_DATA_HERE]

## Health Assessment Framework

Evaluate the repository across these dimensions and provide a score (1–10) for each:

### 1. Documentation Quality
Is the README complete? Are there contribution guidelines, API docs, or setup instructions?

### 2. Commit Activity & Consistency
How active is the project? Are commits frequent, well-named, and atomic? Signs of "commit dumping" vs. disciplined practice?

### 3. Issue & PR Hygiene
Are issues triaged and labeled? Are PRs reviewed promptly? What is the approximate open/closed ratio?

### 4. Test Coverage
Is there evidence of unit, integration, or end-to-end tests? Is coverage tracked?

### 5. Dependency Health
Are dependencies up to date? Are there known CVEs or abandoned packages?

### 6. CI/CD Pipeline
Is there automated testing, linting, and deployment? Any obvious gaps?

### 7. Code Smell Indicators
Based on the data provided, flag any architectural, naming, or structural concerns.

## Summary Report
- Overall health score: X / 10
- Top 3 risks
- Top 3 recommended actions (prioritized)