Page types

Only /trending routes: repository lists and /trending/developers lists, including available language filters and daily, weekly or monthly periods.

What can be retained

Repository full names, URLs, descriptions, languages, rank, visible stars/forks, stars for the period and contributor links. Developer lists can retain username, display name, profile link and featured trending repository.

All fields depend on what is present in the current page markup. Media is represented by source URLs, not downloaded image or video files.

A practical capture workflow

  1. Choose the Trending language and period in GitHub yourself.
  2. Open a second Trending view if you need another language or period as a comparison.
  3. Select those tabs and export JSON for structured repository fields or CSV for a spreadsheet comparison.

Read the limits with the file

README pages, issues, repository detail pages and all other non-Trending GitHub routes are outside this adapter. It never opens repositories or calls the GitHub API. A Trending snapshot does not establish adoption or code quality.

Exports reflect loaded page content. The ordinary exporter does not scroll, paginate, expand replies, crawl links or fetch hidden data. Check the preview and extraction warnings before relying on a file.

Site redesigns can change extraction quality. Preview output and extraction warnings are more useful than assuming every live route has passed current manual QA.