Discover what the token can see.
Start with the supplied GitHub user's account and organizations available to that token. Coverage depends on permissions and a successful sync.
A repository inventory with a point of view
From source
to signal.
See the repositories a GitHub token can reach. Choose a source, find what needs attention, and look deeper only where it matters.
Source-run local app · restricted source access · no hosted account
GITDEX / WORKING MODEL01 — 03
01discovered sourcesuser / orgs
02selected sourcerepositories visible here
03 / SIGNALattention, with context.health · staleness · history on demand
WORKFLOW ILLUSTRATION · NO TOKEN OR LIVE REPOSITORY DATA
THE PRINCIPLE
An inventory is useful when you can see where a repository came from and why it deserves a closer look.
01 / THE METHOD
A path through
the noise.
Gitdex joins discovery, source-scoped browsing, and configurable signals into one local working view.
Narrow to one source.
Browse the synchronized inventory together or select a discovered source account. Search and filters help turn a long list into a working queue.
Read the signals, then decide.
Health weights and staleness thresholds are configurable. Run optional per-repository analysis for stack, commits, and releases when the metadata matters.
02 / THE SIGNALS
A score is a prompt
to inspect.
Recency, project metadata, activity and other weighted factors form a configurable health score. The result helps prioritize review; it is not a promise of repository quality.
HEALTH MODEL / ILLUSTRATIONCONFIGURABLE
Recency01
Documentation02
Activity03
Metadata04
Diagram values are illustrative, not a Gitdex calculation or live repository score.
03 / CURRENT BOUNDARY
Local by design.
Clear about the edges.
Gitdex is currently a restricted-source prototype run with an Encore API, PostgreSQL and a SolidJS frontend. This public page explains the product; it does not host the inventory.
Read setup and access notesToken
The local app validates a GitHub classic personal access token and stores it in that browser's local storage. Use a trusted machine.
Coverage
Only token-visible repositories from discovered and successfully synced sources appear. A source filter does not certify complete estate coverage.
Open work
Repository identity across renames or transfers and incomplete metadata after sync failures remain unresolved. There is no verified public app deployment.