github-discovery-scoringlisted

# GitHub Discovery Scoring ## WHEN TO USE (Triggers) 1. When ranking discovered GitHub repos by relevance to a project 2. When generic repos (React boilerplates) rank too high in results 3. When building a recommendation engine for code repositories 4. When filtering discovery results by tech stack overlap 5. When scoring needs to distinguish domain-specific from generic matches ## FAILED ATTEMPTS | # | Attempt | Why Failed | Lesson | |---|---------|-----------|--------| | 1 | Scored by star count only | Popular generic repos (React templates) outranked niche relevant ones | Stars measure popularity, not relevance | | 2 | Equal weight for all dependency matches | React/Tailwind matches scored same as google-adk/pgvector | Domain-specific deps need 10x weight vs generic | | 3 | Keyword matching in description only | Missed repos with relevant dependencies but generic descriptions | Analyze actual dependencies (package.json, requirements.txt) | ## CORRECT PATTERN ### Weighted Scoring Formula ```javascript score = maxOverlap // Dependency/topic match weight + strategyWeight // Strategy bias (tech-stack: 3.0, curated: 2.5, rising-stars: 2.0) + Math.min(starVelocity, 10) * 2.0 // Star velocity capped at 20 pts + recencyScore * 10.0 // Last push recency x 10 + readmeQuality * 0.5; // README length normalized [0,1] // Weighted overlap: domain-specific >> generic weightedOverlap = specificDe