Momentum
12% of overallIs this an active program right now, or a museum?
What it measures
Two signals over a 90-day window: how many non-archived repos saw real activity (commits, releases, merged PRs) and how recently you published on the blog or YouTube channel. The repo denominator is capped at 50 so big orgs aren't punished for historical breadth.
Why it matters
Momentum is what evaluators check after they like the docs. A flagship repo that hasn't shipped in 18 months is a stronger signal than any landing page.
Sub-metrics
| Metric | What we read | Weight | Source |
|---|---|---|---|
| Active repos (90d) | active_count / min(50, non_archived). ≥20 active = floor of 80. | 60% | GitHub REST |
| Blog recency | Posts in last 90d (preferred), or days since last post | 40% | Blog crawl |
How it's weighted
Recent repo activity matters more than content cadence, but both count. Orgs that hit a healthy floor of consistently active repos stop being penalized for their long tail of older work.
Best practices
- Set a cadence on flagship repos — even a weekly dependency bump keeps the activity signal alive.
- Archive repos you're not maintaining. Honest is better than dormant.
- Aim for a blog post every 2–4 weeks. Engineering deep-dives count; status updates count.
- Publish a 'what shipped this month' digest — it produces a steady stream of dated, dev-focused content.
- Cross-post launches to the blog (not just X / LinkedIn) so they're crawlable.