What shipped across your GitHub repos this week?

Connect the repos you choose and ask. Papercrane's AI agent reads commits, branches, and files across every repo you install it on and builds a live dashboard, by repo and by week, never ranked by developer name.

See a week with no leaderboard

Install on the repos you choose in about a minute. Free to connect and ask. Paid plans start when you publish a dashboard. See pricing

You already hit one of these walls

The 10,000 commit ceiling

GitHub's own contributor and commit graphs stop working past 10,000 commits in a repo, and every graph is scoped to one repo at a time.

The per seat DORA tax

Engineering metrics platforms start around $29 a seat a month with a 50 seat minimum. That is a real budget line before anyone has asked a single question.

The leaderboard nobody asked for

Individual commit and PR counts turn into a ranking the moment they exist, and the teams that get ranked notice. The vendors selling this category warn about it in their own research.

Every repo. No leaderboard.

The agent reads commits across the repos you install it on and builds this by default: a grid of repos by week, never sorted by author. Ask a follow up question if you want a breakdown by person. The default view stays at the repo level.

Commits by repo, last 8 weeks

Example week

Repo	Jul 6	Jul 13	Jul 20	Jul 27	Aug 3	Aug 10	Aug 17	Aug 24
web-app	18	22	15	27	19	24	20	26
api-gateway	9	14	11	8	13	10	15	12
payments-service	12	8	15	10	6	9	0	0
mobile-ios	5	7	4	9	6	8	5	7
infra-terraform	3	2	5	1	4	2	3	1
Quiet 14+ days payments-service, no commits in the last two weeks shown.

Example week. Built from your repos the first time you ask what shipped.

Ask what actually shipped

What shipped across all our repos last week?

Which repos have gone quiet, no commits in 14 days?

How many files changed in [repo] this month, and in how many commits?

Which branches are furthest behind main and for how long?

Which Jira sprints closed the most issues, and what landed in the repos during that window?

joins Jira and GitHub

Did last week's spike in Zendesk tickets line up with commits to a specific repo?

joins Zendesk and GitHub

Every answer comes back as a chart on a live dashboard, not a paragraph you have to trust.

1. Install the app on the repos you choose

2. Ask a question

3. The agent reads commits, branches, and files across those repos and builds a hosted dashboard

4. It stays live, and errors route back to the agent

Access is scoped to exactly the repos you select during install, on GitHub's own installation screen, not every repo your account can see. Nothing is copied into a separate store; dashboards query GitHub again each time they refresh.

Three ways to see what shipped

The job	GitHub's own graphs	LinearB or Swarmia	GitHub + Papercrane
See activity across every repo, not one	Each graph scoped to one repo	Yes, that's the product	Yes, across every repo you install it on
Cost for a 50 person team	Free, but capped at 10,000 commits per repo	$1,450 to $2,950 a month at published rates	Free to connect and ask; paid at publish
Time to first dashboard	Instant, but capped at 10,000 commits per repo	Typically a rollout measured in weeks	One conversation, right after you install
PR cycle time, review turnaround, deploy frequency	No	Yes, this is their core data	No, see the honest section below
Ranks developers by output	No	Often the default view	Never the default; askable, not headline
Share with a non technical exec	Screenshot the graph	Their dashboard, another login	Send a link to a live dashboard

The Monday update

An engineering director used to write a manual summary for the founder every Monday. Now it's a dashboard link: commits by repo, quiet repos flagged, sent before the standup starts.

The quiet repo catch

A team lead noticed a payments repo had gone three weeks with no commits, two weeks before anyone would have asked about it in a meeting.

The incident correlation

A support lead cross checked a spike in Zendesk tickets against commit activity in the repo that shipped the week before, without filing a ticket to the data team.

joins Zendesk and GitHub

When you don't need us

If pull request cycle time, code review turnaround, or deployment frequency by engineer is the actual job, LinearB and Swarmia read your pull request and CI data directly today and we do not, we read commits, repos, branches, and files. If your team is small enough that a five minute glance at GitHub's own graphs answers your Monday question, keep doing that. Papercrane is worth paying for once the question spans more than one repo, or needs to sit somewhere your non technical stakeholders can open without a GitHub login.