Skip to content
← All apps

A developer tool by Flavio

Repo Foyer

Find the GitHub repository you need with ranked lists, pinned favorites and keyboard search. A Chrome extension.

Buy Repo Foyer · $20

One-time purchase. Tax included. Source code included.

Chrome extension

Latest version 1.4.0, released November 18, 2026

Repo Foyer, a Chrome extension that shows your repositories on the GitHub home page

$20 including tax, one-time purchase.

You open github.com to get to a repo. You get a feed.

Most of the time I open github.com, it’s to get to one of the repos I’ve been working on. The home page shows me a feed instead. So I click my avatar, then Repositories, then scroll or type in the filter. That’s a detour I take many times a day.

I wanted the home page to do one thing: get me to my repo in a couple of seconds. So I made my own.

Repo Foyer is a Chrome extension that replaces the GitHub home page with your repositories. Three short lists show the repos you work on most, the ones you created last, and the ones getting stars this week. A search box covers every repo, and it has the focus before you reach for the mouse.

Here it is in a minute and a quarter, recorded on a made-up GitHub account:

The account, the repositories and the numbers in the video and the screenshots are made up.

Who it’s for

  • Developers with dozens of repos, mostly private. You have 140 repositories and work on six of them this month. GitHub’s feed shows other people’s activity. Repo Foyer shows those six at the top.
  • Indie hackers who ship a new project every few weeks. Your newest repos sit in Recently created, so the thing you started on Tuesday is one click away, not buried under older names.
  • People who release open source. Getting traction counts the stars each repo got in the last 7 days. You see which launch is getting attention, separate from your oldest, most starred projects.
  • Keyboard people. Open github.com, type weekend, press Enter. Cmd+Enter opens it in a new tab and Escape clears the search.
  • Members of several organizations. Search covers repos you own, your organizations’ repos and the ones where you collaborate, in one box.

What it does

When you open github.com, the feed is gone. In its place there are three short lists of your repositories:

  • Most used: the 10 repos you work on the most right now
  • Recently created: your 10 newest repos, without forks
  • Getting traction: the repos that got the most stars in the last 7 days

The GitHub home page with Repo Foyer on a sample account: three short lists of repos, most used, recently created and getting traction

Each repo takes one line: its name, a Private label if it’s private, and when it was pushed or created, or how many stars it got. The description shows up when you hover over it.

To keep a repo at the top of Most used, hover over it and click the ☆. Click the ★ to remove it. These stars live in the extension, not on GitHub, so they don’t change the repo’s star count.

GitHub’s header stays where it is. The list uses GitHub’s own colors, so it follows the light or dark theme. When you’re logged out, you see the normal page. The lists stay side by side down to about 600 pixels wide.

Ten seconds from new tab to repo

  1. Open a new tab and go to github.com. The lists show up right away, drawn from a cache.
  2. The repo you want is usually in Most used. Click it.
  3. If it isn’t, start typing. The search box already has the focus, and it matches names and descriptions across every repo you can reach.
  4. Use the arrow keys to move the selection and press Enter. Cmd+Enter opens it in a new tab (Ctrl+Enter on Windows or Linux).
  5. Press Back. The search box still has what you typed, selected, so you can type a new search right away.

How it knows what I work on

Each repo gets a score from three things: my commits in the last 90 days, how often I opened it in this browser, and how recently it got a push.

Visits and pushes count less as they get older. Visits to the same repo less than 30 minutes apart count once, so an hour spent browsing a repo is one visit.

My first version counted commits with GitHub’s contribution data, the one behind the green squares on your profile. For my account it counted 260 commits in public repos, and reduced 2,436 contributions in private repos to a single number, with no repo names. That happens even when you ask about your own account, with a token that can read those repos.

Most of my work happens in private repos, so the ranking was wrong. Now the extension counts commits in each repo’s own history, for every repo pushed in the last 90 days.

What contributes to Most usedRepo Foyer combines recent commits, browser visits, and push recency. Older visits and pushes count less, and visits within thirty minutes count once.90-day commitsMost used scoreVisits30-min groupingVisits lose weightPushesPushes lose weightRank repos

Which repos are getting traction

I also wanted to see which of the repos I released lately are getting traction. The total star count doesn’t tell me that, because my oldest repos have the most stars.

So the third list counts the stars each repo got in the last 7 days. The week I first built it, Work Tracebook got 57 new stars, Skill Cabinet 55 and Note Repo 45, all released a few days before. My Vue developer roadmap from 2018 has 527 stars and got none that week, so it stays out.

It only looks at public repos you or your organizations own, and leaves out forks. It’s a quick read on recent attention, not a full popularity report.

Why not use GitHub’s own pages

GitHub already gives you ways to get to a repo. The left sidebar on the home page lists some of your repositories. Your profile’s Repositories tab has a filter and can sort by last updated. The / key opens GitHub’s search. Each of those works.

What they don’t do is rank by how much you work on a repo, keep your favorites at the top, or count this week’s stars. And the home page still opens on the feed, so each visit starts with a detour.

GitHub’s pagesRepo Foyer
What the home page showsA feedYour repos, in three lists
OrderLast updated or nameYour commits, visits and pushes
Favorites at the topNot available☆ on any repo
This week’s starsTotal stars onlyStars in the last 7 days
KeyboardOpen search, type, pickType right away, Enter
Speed on loadLoads with the pageShown from a cache, refreshed in the background

The token stays in Chrome

Repo Foyer reads your repos with the GitHub API, so it needs a token. You paste it in the extension’s settings: a classic token with the repo scope, or the output of gh auth token if you use the GitHub CLI. If an organization uses SAML single sign-on, authorize the token for it too, or its repos may be missing.

The token stays in Chrome’s extension storage, and the extension only sends it to api.github.com. The visits stay in the browser too, and Clear visit history in Settings removes them. There are no accounts and no analytics.

The Repo Foyer settings page with a saved token, connected to a sample account

Under the hood

It’s plain JavaScript, with no build step.

The content script starts before GitHub draws the page. On the home page, a CSS rule hides GitHub’s content, and the script puts the list in its place, drawn from a cache. A service worker refreshes the cache in the background when it’s older than 5 minutes, so the list shows up right away. Refresh at the bottom fetches new data now.

Fig 1 · 1/4The repository list loads from a cache
Open github.com

GitHub changes pages without a full reload, so the script watches the address and puts the list back whenever you land on the home page.

The repo has a test that loads the extension into Chromium with Playwright, on a fake github.com with demo data, so it runs without a token.

What it doesn’t do

  • It isn’t on the Chrome Web Store. You load it into Chrome yourself, and it doesn’t update itself.
  • It only changes the home page. Repo pages, issues and pull requests look as they always do.
  • It doesn’t star repos on GitHub. The ☆ is a favorite inside the extension.
  • It only counts visits in this browser. Visits from another computer or browser don’t add to the ranking.
  • Getting traction is public repos only. Private repos and forks are left out of that list.

Questions

Does it work in other browsers?

It’s a Chrome extension, and the setup steps are for Chrome.

What does it store about my visits?

The repository name and visit time, up to the last 50 visits per repository. A repo’s visits are removed after 180 days without one.

Some of my organization’s repos are missing.

Check the token’s access, and authorize it for organizations that use SAML single sign-on.

Is the source code included?

Yes. The purchase page delivers a source ZIP along with the ready-to-load extension.

The documentation covers setup and troubleshooting.

Buy Repo Foyer and get started

Repo Foyer costs $20 including tax, paid once.

After purchase, download the ready-to-load Chrome extension ZIP from your purchase page.

Repo Foyer isn’t on the Chrome Web Store, so you load it into Chrome yourself:

  1. Unzip the extension zip from your purchase page.
  2. Move the unzipped folder somewhere it can stay, like your Documents folder. Chrome runs the extension from that folder.
  3. Open chrome://extensions and turn on Developer mode in the top right corner.
  4. Click Load unpacked and pick the folder.
  5. Click the Repo Foyer icon in the extensions menu, and paste your token in the settings.

An extension you load this way doesn’t update itself. When a new version comes out, download it again from your purchase page, then copy its files over the old ones in the same folder, then click the reload arrow on the Repo Foyer card in chrome://extensions. The included README has the details.

If you want to ship an extension through the store instead, I wrote how to publish a Chrome extension to the Chrome Web Store.

Repo Foyer screenshot at full size