store-evaluation

# Store Evaluation Score a proposed source store against five dimensions. Stores below the threshold are rejected. Stores above are added to `sources/supported-stores.json` via [source-inventory](../source-inventory/SKILL.md). ## When to Use - A user invokes `/add-source` with a candidate store - Periodic re-evaluation of borderline entries (every 6 months) ## The Five Dimensions Score 0–2 per dimension. Maximum score is 10. **Threshold for inclusion: ≥ 7**. ### 1. Maintenance Health (0–2) | Score | Criterion | |---|---| | 0 | Repo archived, no commits in 12+ months, last release > 2 years old | | 1 | Active but low velocity — commits in last 6 months, no recent release | | 2 | Active maintenance — commits in last 90 days OR active issue triage OR recent release | ### 2. Adoption Signal (0–2) | Score | Criterion | |---|---| | 0 | Solo project, < 50 stars, no external contributors | | 1 | Some adoption — 50–500 stars, occasional external contributors | | 2 | Real adoption — > 500 stars OR multiple maintainers OR sustained external contribution | (Stars are noisy; weight them with maintenance + license signal.) ### 3. License Clarity (0–2) | Score | Criterion | |---|---| | 0 | No license, custom restrictive license, or unclear terms | | 1 | Permissive license but with vendor-specific restrictions | | 2 | Clean OSI-approved license (MIT, Apache 2.0, BSD, ISC, etc.) | ### 4. Catalog Fit (0–2) | Score | Criterion | |---|---| | 0 | Off-topic — no clear use case for an...