github-api/repos

GitHub repos API — stars, forks, issues, license, topics

Public repositories of one user, via the official API. Fields keep the source's own names.

Parameters

Name	What it is
`handle`	The GitHub login.

Handle format and anchor

Handle: login
Anchor: login + id

Fields returned

stargazers_count
forks_count
open_issues_count
watchers_count
language
topics
license (SPDX)
archived
fork
created_at
updated_at
pushed_at

What this endpoint does not return.

metricsA repository is not a post, so nothing here is folded into the metrics object. A star is not a like.

A field we cannot read comes back null, never 0. A zero would be a claim about the account; null is a fact about our collection.

Where this goes wrong.

Field names are the source's, not ours. stargazers_count stays stargazers_count. Renaming it to likes would be a claim about what a star means.

Cost

1 credit per call. A call that finds nothing is charged all the same.

Why are the field names not normalised like the other routes?

Because there is nothing to normalise them to. A star is not a like and a fork is not a repost.

Am I charged for an account with no repositories?

Yes. An account with no repositories returns an empty items list and is charged — the lookup happened. An account that does not exist is not charged.

Other routes for this platform

github-api/profile