GitHub

Know whether your org is shipping, where reviews are stuck, and how your repos are trending, all from your iPhone home screen.

Is your team shipping or stuck?

Org Pulse gives you seven metrics across your entire GitHub org: open PRs, PRs awaiting review, stale PRs older than seven days, merged PRs in the last 24 hours and seven days, new PRs opened today, and open issues. A glance at Merged PRs (24h) versus PRs Awaiting Review tells you immediately whether the team is flowing or backed up. If Stale PRs are climbing while merges stay flat, something is blocking review, not just writing.

Per-repo engineering health

Repo Pulse tracks queue depth, CI status, and commit activity for any repo in your account. Workflow Success Rate (24h) shows the percentage of completed CI runs that passed, and Failed Workflow Runs (24h) surfaces the raw failure count alongside it. Commits (24h) confirms whether the default branch is actively moving. These three signals answer the question engineers want answered before starting their day: is main green and is anyone working here?

Community momentum for open-source repos

Repo Stats pulls stars, forks, true watchers (GitHub's subscribers_count, not the legacy alias), and open issues from a single API call. Stars signal adoption; forks signal real use; watchers reflect notification-level engagement from subscribers. If you maintain or sponsor open-source work, these four numbers on your lock screen tell you at a glance whether momentum is building or plateauing.

How to get your GitHub API key

Generate a Classic Personal Access Token at github.com/settings/tokens/new with these scopes:

repo to read PRs, issues, commits, and Actions runs in private repos. Use public_repo instead if you only track public repos.
read:org to list orgs you belong to and run org-wide PR searches.
read:user to read your own profile, used for the Personal scope in Org Pulse.

Then:

Visit github.com/settings/tokens/new.
Set the note to PulseKit.
Set the expiration to 90 days or longer.
Select the scopes above.
Click Generate token and copy the value, which is shown once.
Paste it here.

These are read scopes only. PulseKit cannot write, push, or modify your repos.

Security

How we protect your credentials

Your GitHub API key is sealed on this device with AES-256-GCM before it ever leaves your iPhone. Only your device holds the unwrap secret, stored in the iOS Keychain. The PulseKit backend wraps that already-encrypted payload again with its STORAGE_SECRET and writes the double-envelope blob to Postgres, so the server never sees your plaintext key at rest. Each fetch request includes a one-time unwrap secret that decrypts the inner envelope only long enough to call GitHub. The key is scoped to this device, can be revoked from PulseKit at any time, and is never written to logs.

What you can track

Pick the metrics you care about and pin them as widgets.

Org Pulse

Org-wide PR throughput, review queue depth, and shipping velocity

42
Open PRs
8
PRs Awaiting Review
3
Stale PRs
17
Merged PRs (24h)
124
Merged PRs (7d)
21
New PRs (24h)
56
Open Issues

Repo Pulse

Per-repo PR queue, CI health, and commit activity

42
Open PRs
8
PRs Awaiting Review
38
Commits (24h)
94%
Workflow Success Rate (24h)
1
Failed Workflow Runs (24h)
56
Open Issues

Repo Stats

Stars, forks, watchers, and open issues for a repo

12.4k
Stars
1.8k
Forks
340
Watchers
56
Open Issues

Numbers shown are illustrative — your widgets show your live data.

Who uses this

Engineering leads
You need to know if the team is shipping without opening 10 GitHub tabs every morning. Org Pulse puts merged PR count, review queue depth, and stale PR count on your home screen so you catch the org's velocity signal the moment you pick up your phone.
Staff engineers
When you own a critical repo, knowing whether CI is red and commits are flowing before you open your laptop changes your whole morning. Repo Pulse surfaces Workflow Success Rate, Failed Workflow Runs, and Commits (24h) at a glance so you act on the right thing first.
Open-source maintainers
Stars and forks on your lock screen tell you whether a project is gaining traction or stalling. Repo Stats tracks stargazers, forks, true watchers, and open issues for any public or private repo, giving you a community momentum read without logging into GitHub.
CTOs
Shipping health should take one glance, not a meeting. Org Pulse gives you the org-wide merge rate, review bottleneck count, and open issue queue so you can judge whether engineering is unblocked or needs your attention before any standup or status call.

FAQs

What GitHub metrics does PulseKit show on my home screen?

PulseKit offers three GitHub modules. Org Pulse tracks seven org-wide metrics including open PRs, PRs awaiting review, stale PRs, and daily and weekly merge counts. Repo Pulse shows per-repo PR queue depth, commit activity, and CI workflow success rate. Repo Stats surfaces stars, forks, watchers, and open issues for any repo.

Does PulseKit need write access to my GitHub repos?

No. PulseKit uses read-only scopes on your Personal Access Token: repo (or public_repo for public-only repos), read:org, and read:user. These allow PulseKit to query PRs, issues, commits, and workflow runs. It cannot write, push, or modify anything in your repos.

How do I connect GitHub to PulseKit?

Generate a Classic Personal Access Token at github.com/settings/tokens/new with the repo, read:org, and read:user scopes, then paste it into PulseKit's GitHub connection screen. PulseKit validates the token immediately by calling the GitHub /user endpoint and populates your org and repo pickers right away.

Can I track multiple repos and orgs at the same time?

Yes. Each PulseKit widget is configured independently. You can add an Org Pulse widget for your main org, a Repo Pulse widget for your most active repo, and a Repo Stats widget for an open-source project, each showing live data side by side on the same home screen.

Does PulseKit work with private GitHub repos?

Yes. With the repo scope on your Personal Access Token, PulseKit can read PRs, issues, commits, and Actions runs from private repos. If you only need to monitor public repos, use the narrower public_repo scope instead to limit the token's reach.

What is the difference between Org Pulse and Repo Pulse?

Org Pulse gives a broad view across your entire GitHub org: total open PRs, org-wide review queue, stale PR count, and daily and weekly merge throughput. Repo Pulse focuses on a single repo and adds CI-specific metrics including Workflow Success Rate and Failed Workflow Runs alongside that repo's own PR queue and commit activity.

How often does PulseKit refresh my GitHub data?

PulseKit fetches data on demand when you view or manually refresh a widget. A single Org Pulse refresh uses 7 search API calls. GitHub's authenticated limits are 5,000 requests per hour and 30 search requests per minute per account, so typical usage stays well within those thresholds.

Add GitHub widgets to your iPhone

Install PulseKit, paste your credentials, pick a widget.

Download