kgerring/github-topics-trending

KGerring / github-topics-trending

Python★ 1

Use in your agent Ask this codebase

github.com/kgerring/github-topics-trendingIndexed at 225e7fe2mo agoUp to date with upstream

About this codebase

17 files and 139 symbols in 1 module, written in Python.

Built from the index

Start reading

Knowledge graph17 files and how they depend on each other.

Code health

9.2out of 10Excellent

Full health report

Use KGerring/github-topics-trending in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

1.In Claude, open Customize → Connectors, click +, then Add custom connector. On a Team or Enterprise plan an owner adds it first under Organization settings → Connectors.
2.Paste the server URL below as the Remote MCP server URL, then click Add.
3.Click Connect. A Repowise sign-in window opens. Approve access.
4.Repowise's tools are now available in your Claude chats.

Connect with one click. Sign in with Repowise (OAuth), no API key to copy. Works in Claude on the web, desktop, and mobile.

Docs

bash

https://api.repowise.dev/mcp/kgerring/github-topics-trending

Editors need an API key: sign in to create one.Sign in to connect

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

get_overview()
get_answer("how is github-topics-trending put together?")
get_why("why is github-topics-trending structured this way?")

Explore github-topics-trending

How KGerring/github-topics-trending works

The codebase has 17 files and 139 symbols in 1 module, led by Python. Code health is 9.2 out of 10, rated excellent.

About this page

Get a page like this for your own codebase

Repowise built this map of KGerring/github-topics-trending from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Index your repo free See how Repowise worksFree for 2 public repos, with a page like this one.

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.

Maintain KGerring/github-topics-trending?

Claim this page, add a badge to the README, or re-index it.

Claim this page

Sign in with GitHub and we check that you are an admin or maintainer of kgerring/github-topics-trending. Then add a badge to the README that links readers here.

Add a badge to your README

Every badge is public, cached, and updates on its own after every index. Nothing to install.

Repowise badge

Links to this page, with no score on it. Adding it also re-indexes the repo every week.

[![repowise.dev](https://api.repowise.dev/badge/wiki/kgerring/github-topics-trending.svg)](https://repowise.dev/repo/kgerring/github-topics-trending?src=badge_wiki)

Code health badge

The repo's health score out of 10, from the latest index.

[![repowise.dev code health](https://api.repowise.dev/badge/health/kgerring/github-topics-trending.svg)](https://repowise.dev/repo/kgerring/github-topics-trending?src=badge_health)

Code health card

A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.

[![repowise.dev code health](https://api.repowise.dev/badge/health/kgerring/github-topics-trending.svg?style=card)](https://repowise.dev/repo/kgerring/github-topics-trending?src=badge_card)