GitHub API skill

Read public GitHub data as clean JSON. This GitHub API skill covers repositories and their commits, contributors, issues, releases and language breakdown, plus user and organisation profiles, repo search and the trending list. Every endpoint costs 1 credit, making this the cheapest platform in the repo and a good one to test your key against.

This skill wraps 11 live GitHub endpoints from the ScraperSocial API. Public data only, returned as clean JSON.

When to use this skill

• You are evaluating a dependency or a project and want its activity, contributors or release history.
• You need issue lists for triage, changelog generation or research.
• You are tracking what is trending, or searching repos by keyword.
• A user pastes a GitHub URL and asks what the project is or how active it is.

Do not use this skill when

• You are authenticated and near no rate limit. GitHub's own REST and GraphQL APIs are free, richer and support writes. Use this when you want one uniform client across many platforms, or want to avoid managing another token.
• You need private repositories. Public data only.
• You need to open issues, push code or comment. Read-only.

Setup

export SCRAPERSOCIAL_KEY=sk_live_...   # https://scrapersocial.com/app/keys

Signing up at scrapersocial.com/signup includes 100 free credits, no card required.

Permissions and scope

These scripts do exactly three things and nothing else: read one environment variable (SCRAPERSOCIAL_KEY), send HTTPS requests to https://api.scrapersocial.com (the host is a constant in the code, not configurable), and print JSON. They run as node scripts/<name>.js with no other shell use, no file writes and no persistence. call_endpoint.js accepts only the 11 documented /v1/github/ paths in the table below and refuses anything else before a request is made.

Scripts

Every script also accepts --limit, --cursor, --fields, --format and --fresh. --limit is clamped to 50: above that the API returns an async job instead of data.

Example

node skills/github-api/scripts/get_profile.js torvalds

Every response uses the same envelope:

{ "data": {}, "meta": { "count": 20, "next_cursor": "..." }, "request_id": "a18e4ef88ad4b00b" }

meta appears on paginated endpoints only. Keep request_id — support traces calls with it.

Endpoints

Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.

FAQ

How do I get a repo's commits as JSON?

get_repo.js --section=commits with the owner/name handle. Commits, contributors, issues, languages and releases are all sections of the same script.

How do I list a user's or an organisation's repositories?

get_repos.js --section=user-repos or get_repos.js --section=org-repos, passing the handle.

Why use this instead of GitHub's own API?

Mostly consistency: same envelope, same auth and same client as the other 32 platforms here. If GitHub is the only source you need, their official API is free and a better fit.

Is this an official GitHub API?

No. ScraperSocial is independent and not affiliated with GitHub. It returns publicly available data only.

Links

• GitHub data on ScraperSocial
• All 33 platform skills
• OpenAPI spec · llms.txt

Disclaimer

ScraperSocial is an independent product and is not affiliated with, endorsed by, or sponsored by any platform named in this repository. All product names, logos and brands are property of their respective owners. These skills return only publicly available data.