Read the signals.

Four landscapes, one evidence standard

Few projects and fast search growth: early blue ocean. Many projects and fast growth: growth red ocean. Many projects without fast growth: established red ocean. Few projects without fast growth: quiet waters. Missing or weak evidence: uncharted.

Published method 1.0.2

Supply includes non-fork, non-archived repositories with at least 5 stars and a push in the last 180 days. 50 matching projects is the dense-supply threshold.

Demand compares the median of 8 complete weeks with the prior 8. Fast growth requires at least 25% growth, a positive lower resampling band, persistence and a seasonal check. At least 26 consecutive weeks are required; evidence older than 14 days is insufficient.

Weekly intervals must have ended when collected and when analyzed. Invalid rows cannot make old evidence fresh; conflicting values for a week prevent classification. These thresholds are heuristics, not calibrated business forecasts. How Google Trends measures search attention.

CLI and MCP

Requires Node.js 22.13 or newer. Start the local radar:

npx --yes --package=https://radar.ghtrends.dev/ghtrends.tgz ghtrends ui

Run ghtrends scan --topic mcp-servers --json to inspect a category, or ghtrends mcp to connect an MCP client over stdio.

Tools: ghtrends_scan, ghtrends_repo, ghtrends_compare, ghtrends_watch_list. Full installation and configuration instructions.