Repository discovery
GitHubエンドポイントを使えば、「Repository discovery」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Search public GitHub repositories and users, track trending projects, and fetch repo, org, contributor, fork, language, and release data as JSON.
エンドポイントファミリー
5
ドキュメント化されたパラメータ
72
サンプル数
17
ライブカタログスナップショット
稼働エンドポイント
17
メソッド
GET
必須パラメータ
37
スキーマ参照
17
{
"platform": "GitHub",
"endpoint": "github-search-repositories",
"method": "GET",
"path": "/github/search/repositories",
"auth": "apiKey"
}ユースケース
Search public GitHub repositories and users, track trending projects, and fetch repo, org, contributor, fork, language, and release data as JSON.
GitHubエンドポイントを使えば、「Repository discovery」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
GitHubエンドポイントを使えば、「Open-source trend monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
GitHubエンドポイントを使えば、「Developer and organization research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のGitHubエンドポイントカタログから取得しています（エンドポイント17件、ドキュメント化されたリクエストパラメータ72個、公開レスポンススキーマ17件）。DocsとPlaygroundが参照しているカタログと同じものです。
GitHubのエンドポイントは17件、5つのリクエストファミリーに分類されています（User、Repo、Orgほか2件）。
これらのGitHubエンドポイントには72個のリクエストパラメータがドキュメント化されており、うち37個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
17件のGitHubエンドポイントのうち17件が実際のサンプルレスポンスを、17件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
GitHubのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
GitHubのエンドポイントは17個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/github/user/{username}
/github/repo/{owner}/{repo}
/github/org/{org}
/github/search/repositories
/github/trending
主要エンドポイント
/github/search/repositoriesSearches public GitHub repositories with the required GitHub search query `q`. Order with `sort` (`stars`, `forks`, `help-wanted-issues` or `updated`) and `order`, and page with `page` and `per_page` (max 100). The response has `total_count` and items with full name, owner, description, language, stars, forks, topics and license.
MCPツール github_search_repositories
/github/search/usersSearches public GitHub user accounts with the required GitHub search query `q`. Order with `sort` (`followers`, `repositories` or `joined`) and `order`, and page with `page` and `per_page` (max 100). The response has `total_count` and items with login, id, profile URL, account type and match score.
MCPツール github_search_users
/github/trendingLists the repositories currently trending on GitHub. Filter by programming `language` (such as `go` or `python`) and choose the window with `since` (`daily`, `weekly` or `monthly`). Each repository has its owner, name, URL, description, language, stars, forks and stars gained today.
MCPツール github_trending
/github/trending/developersLists the developers currently trending on GitHub. Filter by programming `language` (such as `go` or `python`) and choose the window with `since` (`daily`, `weekly` or `monthly`). Each developer has a username, display name, profile URL and their popular repository.
MCPツール github_trending_developers
/github/user/{username}Returns a public GitHub user's profile plus user-published social links. Email is included only when the user has made it public on their profile.
MCPツール github_user
/github/user/{username}/reposLists the public repositories of a GitHub user, identified by the required `username`. Filter with `type` (`all`, `owner` or `member`), order with `sort` (`created`, `updated`, `pushed` or `full_name`) and `direction`, and page with `page` and `per_page` (max 100). Each repository has its name, description, language, stars, forks, topics, fork flag and last push time.
MCPツール github_user_repos
関連API
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
Business & Market Intelligence
Use a Brand Data API to turn any domain into a normalized brand profile — title, description, slogan, brand colors, logos and icons, social profiles, footer links, and schema.org organization data — as structured JSON for enrichment, branding, and research workflows.
関連データセット
データセット · クエリ可能なJSON
Skip per-profile lookups: query ~973K enriched developer profiles in bulk — followers, company, interests, activity and clean geo — by country, stack, follower band or reachability over one REST call.
データセットを見る →GitHubのスクレイピング方法
GitHub's REST API is well documented but rate-limits unauthenticated search to roughly 10 requests per minute, and it has no trending endpoint at all. Crawlora's 17 GitHub endpoints cover search, trending repositories and developers, and user, organization, and repository detail behind one key.
Search repositories or users by query with sort by stars, forks, or recency, or pull trending repositories and developers by language over a daily, weekly, or monthly window.
User and activity endpoints take a username, organization endpoints take an org, and repository endpoints take owner plus repo.
List endpoints take page and per_page, so contributors, forks, releases, followers, and following all iterate the same way.
Combine repository, language-breakdown, and contributor calls to build developer-market or open-source-intelligence tables, or start from the stored GitHub Users dataset for bulk profiles.
On 2026-10-30 org repos for github, contributors for cli/cli and forks of cli/cli each returned exactly 20 rows at per_page=20, so keep paging until a short page arrives. Repo rows carry stars, forks and open_issues; contributor rows carry contributions.
エージェントスキル
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で GitHub のデータを JSON として取得できます。GitHub に対応するスキル:
Researches GitHub repos/users/orgs and Chrome Web Store extensions via the Crawlora API — search, profiles, contributors, releases, trending, and…
npx skills add github.com/Crawlora-org/crawlora-skills --skill developer-oss-researchFind developers through Crawlora public GitHub user datasets and verify relevant repository and contribution evidence. Use for role-specific…
npx skills add github.com/Crawlora-org/crawlora-skills --skill developer-talent-discoveryBuild requirements-based open-source project shortlists using Crawlora GitHub metadata, releases, contributors, and public project documentation.…
npx skills add github.com/Crawlora-org/crawlora-skills --skill open-source-project-shortlistingFAQ
GitHub's REST API is good and you should use it directly for authenticated work on your own repositories. These endpoints exist for the gaps: unauthenticated search is rate-limited to roughly 10 requests per minute, trending repositories and developers are a web page with no API behind them, and you would otherwise manage tokens and pagination per surface. Crawlora returns all of it as normalized JSON behind a single key.
Yes. Separate endpoints return trending repositories and trending developers, filtered by language and by a daily, weekly, or monthly window — data GitHub publishes as a web page but does not expose through its REST API.
For a repository: metadata, contributors, public forks, the language breakdown, and releases. For an account: profile, public repositories, pinned repositories, recent public activity, followers, and following.
Collecting publicly accessible repository and profile data is generally treated differently from accessing private repositories or logged-in account data, but it is not unconditional. Collect only public data, respect GitHub's terms and rate limits, and remember usernames and profile fields are personal data under GDPR and CCPA. This is not legal advice; review your local law before commercial use.