An app for your desktop and your phone that tells you who has been visiting your GitHub
repositories.
Put your code out, and watch who turns up.
Somebody starring your project is one of the nicer things that happens on GitHub, and GitHub never mentions it. Issues and mentions get an email. A star, a fork, a new follower, or forty people downloading last night's release all happen in silence, and you find out days later when a number looks different. Download counts are tucked inside each release, and traffic figures are thrown away after two weeks.
Birdfeeder sits on your desktop or your phone and keeps an eye out. When something lands it tells you what it was and who it came from, keeps a list you can scroll back through, and hangs on to the history GitHub lets go of.
Notices the quiet things. Stars, forks and followers arrive with a name and a face. Lost stars and unfollows are written down too, without a notification, because nobody needs that before coffee.
Tells you who they are. Anyone with a following of their own arrives with it: how many people follow them, and where they work. Someone followed by a thousand people or more is a rare bird, and gets called one.
Shows what is nearly yours. Up next lists the milestones you will reach soonest, how far off each one is, and roughly when you will get there at the pace of the last month. One star to go is a good reason to keep an eye on things.
Counts your downloads. Every release and every file in it, with a tally of what was fetched each day. Signature files, checksums and updater manifests are left out by default, since machines fetch those and they flatter the total. The list of what to leave out is yours to edit.
Keeps a life list. Birders keep a list of every species they have seen. Yours has twenty entries, from the first fork to fifty stars in a day, ticked off as they happen. The open ones show how close you are.
Remembers your best days. Your best day and best week for stars, how many days running someone has starred something, and your own contribution streak, with a small celebration when it reaches a round number.
Reads your inbox. Mentions, replies, review requests and security alerts from any repository appear in the same list as everything else, with the comment that set them off. A new issue on your own repository shows up once, not twice.
Shows a season at a glance. The overview has a row for each kind of visitor and a square for each day, like a contribution graph turned to face the other way. Your own contributions run along the top, so you can see what you put out and who came for it. Click a square and the list beside it narrows to that day.
Keeps the traffic GitHub forgets. Views and clones are read every few hours and kept for good, so six months from now you can still find the week a link reached the front page. A sudden crowd gets its own notification, along with where it came from, and so does a repository whose stars run well ahead of its usual week.
Catches you up. Come back to the window after a while and the first thing you read is what happened while you were away, in one sentence. Milestones, records and new entries on the life list get a moment of their own, with the bird and a scatter of seed.
Draws your star history. For each repository and for the whole account, back to the first star rather than the day you installed the app.
Marks the milestones. The first star, the hundredth, the ten-thousandth download.
Watches Hacker News, if you ask. Off by default. Switch it on and Birdfeeder finds stories that link to your repositories, follows their score, and tells you when one passes a hundred points. It is the only time the app talks to anything other than GitHub, and all it sends is your username.
Knows when to be quiet. The first check records recent history without a single notification, and so does anything older that turns up afterwards, such as a repository you start including. After that you only hear about what is new. Your own activity never notifies, and neither do issues, pull requests or releases opened by bots. Each kind of notification has its own switch.
Keeps watching. Close the window and Birdfeeder carries on in the background. Its tray icon turns gold when something is waiting. It can start when you log in, and it checks as often as every minute or as rarely as once a day. On a phone it checks when you open it, unless it looked a moment ago, and about every fifteen minutes while it is closed, as often as Android allows.
Fits in your hand. On a phone the tabs sit along the bottom, within reach of a thumb. Pull a list down to check now. Tap a square on the overview to see what it holds, and slide a finger along a chart to read it. The back gesture steps out of a repository, then back to the overview, and only then leaves the app.
Keeps itself up to date. Birdfeeder looks for a newer release when it starts and every few hours after, and tells you when there is one. Installing it takes one click, or none if you switch on automatic installs. On Android it links to the new APK instead. The check reads one file from this project's releases and sends nothing about you.
Only reads. Birdfeeder cannot star, comment, close or mark anything as read. What it learns stays in a SQLite file on your computer or phone. There is no server, no account to create and no telemetry.
birdfeeder --demoThis opens the app on sample data and never contacts GitHub. Every visitor in the sample is a bird, which seemed only fair.
Grab the package for your system from the Releases page.
# Fedora, RHEL, openSUSE
sudo dnf install ./Birdfeeder-*.x86_64.rpm
# Debian, Ubuntu, Mint
sudo apt install ./Birdfeeder_*_amd64.deb
# Anything else
chmod +x Birdfeeder_*.AppImage && ./Birdfeeder_*.AppImageOn Android, download Birdfeeder_*_android.apk from the same page on your phone and open
it. Android asks once whether your browser may install apps. Birdfeeder needs Android 7 or
later, and asks whether it may send notifications once an account is connected.
Birdfeeder is built and tested on Linux and Android. It is a Tauri app, so Windows and macOS builds should work, but nobody has tried them yet.
On GNOME the tray icon needs the AppIndicator extension. Without it everything else still works: Ctrl+Q quits, and opening Birdfeeder again brings the window back.
After that Birdfeeder updates itself, whichever Linux package you chose. Every package is
signed and the signature is checked before anything is installed. On Android a new release
is announced in the app, and its APK installs over the old one. A .deb or .rpm update asks
for your password, since it goes through the package manager. Version 0.1.0 came before
the updater, so it has to be replaced by hand once.
Choose Sign in with GitHub. Birdfeeder shows a short code and opens GitHub in your
browser, where you enter the code and approve. GitHub asks for the repo scope, which
covers private repositories, traffic and the inbox. It describes that as full control, but
Birdfeeder only reads. An organisation that limits third-party apps needs an owner to
approve Birdfeeder before its private repositories show up.
If you use the GitHub CLI on a computer and have run
gh auth login, there is nothing to do. Birdfeeder borrows that login.
You can also paste a personal access token. A classic token with the repo scope covers
private repositories, traffic and the inbox. GitHub does not let fine-grained tokens read
notifications, so use a classic one if you want the inbox.
However it arrives, the token is kept in your system keyring, not in a file. On a phone it stays in the app's private storage, which other apps cannot read, and it is left out of Android's backups. Signing out in Settings forgets it, and GitHub lists Birdfeeder in your settings under Applications, where its access can be revoked.
Birdfeeder watches one account. If the login changes to a different one, it stops and asks before clearing what it has collected, so two accounts never end up mixed together.
The list on the left is everything that has happened, newest first. A filled square means you have not seen it yet. Click a row to open it on GitHub and mark it read, or clear a whole day with the button beside its date.
The chips above the list filter by kind. The grid on the overview filters by kind and day. A repository's page has a button that narrows the list to that repository. The life list has its own tab, along with the best-followed people who have come by.
Ctrl+R checks now. Ctrl+1 to Ctrl+5 switch tabs. Esc clears the filters. Ctrl+Q quits.
On a phone the activity list has a tab of its own, and Settings is the button at the top right.
Settings holds the rest: how often to check, whether to include forks, archived repositories and organisation repositories, which events notify, which release files to leave out of the download count, and whether updates install by themselves.
A Rust core does the watching and a Svelte 5 interface runs in a Tauri window, so the app uses your system's web view rather than shipping a browser. The Linux package is about 7 MB.
Each check lists your repositories in one request and compares the counts with what it saw last time. Only repositories that changed are read in detail. On a small account a check where nothing happened costs five requests against GitHub's allowance of five thousand an hour, and one more for every ten repositories that publish releases. Traffic costs three requests per repository and is read at most every three hours, and a visitor's profile is read once, the first time they turn up.
Signing in uses GitHub's device flow, which needs no server and no secret in the app: it asks GitHub for a code, then asks every few seconds whether the code has been approved.
Everything GitHub returns goes through one module with no network code in it, which turns it into events. Its rules are tested against an in-memory database: what counts as new, what stays quiet, when a star was lost, when a busy day is worth mentioning.
Your data lives in ~/.local/share/io.github.gingerbreadfork.birdfeeder/birdfeeder.db, or
in the app's private storage on Android.
On Android the app checks only while it is on screen. Once it is out of sight, a job that Android's scheduler runs about every fifteen minutes, with a connection, makes the same check and sends the notifications. Both take the same lock, so they never write the same findings twice. GitHub's certificates are checked against Mozilla's list of root certificates, which the app carries.
- Writing to GitHub. No replying, starring or marking as read. A tool that only reads can be trusted with a token.
- More than one account at a time.
- A hosted version. It runs on your computer and talks to GitHub directly.
- Reminders to keep a streak going. The streak is there to enjoy, not to nag.
You need Rust, Node 24, pnpm and Tauri's system packages.
pnpm install
pnpm tauri dev # run it
pnpm tauri dev -- -- --demo # run it on sample data
pnpm app:build # build packages into src-tauri/target/release/bundleapp:build is tauri build with two variables set that the AppImage step needs on a
current Linux distribution.
For Android you also need JDK 21, the Android SDK, and NDK 27, with ANDROID_HOME and
NDK_HOME pointing at them.
rustup target add aarch64-linux-android armv7-linux-androideabi x86_64-linux-android
pnpm tauri android dev # run it on a phone or emulator
BIRDFEEDER_DEMO=1 pnpm tauri android dev # run it on sample data
pnpm tauri android build --apk # build a universal APKA phone has no command line, so BIRDFEEDER_DEMO=1 at build time stands in for --demo.
A release APK is signed when src-tauri/gen/android/keystore.properties names a key:
storeFile=/path/to/birdfeeder.jks
password=...
keyAlias=birdfeederA debug build started with
adb shell am start -n io.github.gingerbreadfork.birdfeeder/.MainActivity --ez check-now true
runs the background check ten seconds later, which leaves time to switch away from the app.
Packaging signs each file for the updater, so it needs the private key in
TAURI_SIGNING_PRIVATE_KEY (the key itself or a path to it) and its password in
TAURI_SIGNING_PRIVATE_KEY_PASSWORD. To build without a key, leave the updater files out:
pnpm app:build --config '{"bundle":{"createUpdaterArtifacts":false}}'Publishing a release on GitHub runs a workflow that builds the packages and the APK,
attaches them to the release, and adds the latest.json the updater reads. It takes the
updater key, and the Android keystore as ANDROID_KEYSTORE (base64) with its password as
ANDROID_KEYSTORE_PASSWORD, from repository secrets.
Checks:
pnpm check # Svelte and TypeScript
cd src-tauri
cargo test # the event rules, against an in-memory database
cargo test -- --ignored live_sync # one real check, using the GitHub CLI's loginThe interface is in src/. In src-tauri/src/, github.rs talks to the API, sync.rs
decides what to fetch, apply.rs turns what came back into events, and watch.rs runs the
background loop and the notifications. background.rs is the check Android's scheduler
runs, called from CheckJob.kt in src-tauri/gen/android.
MIT. See LICENSE.