Transparency

See what ads have earned, what has been collected, and what has reached open-source maintainers.

Where the money goes

For every $10 in ad revenue

$7.00 · 70%Open source$3.00 · 30%Running Obrigado

Our share covers every cost: payment fees, infrastructure, salaries, and fiscal-host fees. Those costs never come out of the open-source share.

The money so far

All-time totals from our ledger. Updated about every minute. All amounts in USD.

Ad revenue recorded
$18.09
Revenue earned, including bills not yet paid.
Allocated to open source
The pool's share, including unpaid bills and write-offs.
Obrigado's share
$5.42
The business's share, before its costs and fees.
Pool collected
$12.66
Money received for the pool, including grants already paid.
Pool granted
Paid out to maintainers.
Unpaid bills written off
$0.00
Unpaid advertiser bills that will never be collected.
How does the pool reach maintainers?

The pool funds full-time maintenance teams when it can support them, fixed-term grants when it cannot, and one-off donations when it is smaller still. Only money we have collected can fund a payment.

Allocated → collected → granted. These are different stages of the same money. The collected total includes money already granted; it is not an available balance. Written-off bills stay in the recorded revenue and allocation totals, but will never fund grants.

Who do you sponsor?

We aim to support established maintainers of widely used or critical open-source projects whose work is underfunded.

We look for people with a sustained record of looking after the software others depend on. Our support should help them keep doing that work—or make more time for it.

For every grant, we’ll publish who received it, how much, for how long, and why we chose them. Maintainers keep control of their projects.

How do you choose maintainers?
A sustained track record
Ongoing maintenance: releases, contribution reviews, bug fixes, security work, documentation, and support.
Ecosystem importance
Software widely relied on, directly or through other dependencies, or critical to an important part of the ecosystem.
A real funding gap
Essential maintenance that lacks adequate, reliable financial support.
A clear benefit from sponsorship
Funding that helps someone sustain their current work or make more time for it. They do not need to be working full-time on open source already.

Nominated projects

Anyone can nominate a project and name the people who maintain it. We consider every nomination when choosing who receives a grant. A nomination count is a signal, not a vote. These are the projects at least 2 people have nominated.

No project has reached 2 nominations yet.

What advertisers are billed for

We’re still measuring attention. Advertisers currently pay for impressions classified as attended or unknown. That includes lines we cannot confirm a person saw. Impressions classified as unattended are never billed.

How is attention estimated?

An impression starts when the developer’s machine reports drawing the line. We then classify it using the activity signals its host can provide:

Attended
Evidence of activity, such as a prompt or click, or input in the last 5 minutes with the required focus and timing checks. An editor must be focused and recently used. This estimates presence, not attention to the ad.
Unknown
No clear answer either way. This includes lines before the first prompt or more than 5 minutes after the last, unless another signal decides the result.
Unattended
A disqualifying signal: an unfocused window or, where timing is reported, a session under 20 seconds or model requests taking over 50% of session time. Never billed.

Known automated environments—CI, containers, or a reported lack of a terminal—are blocked before an ad is served.

Activity across Obrigado

All-time totals. Impressions count reported displays, not unique people.

Impressions
29158
Ad displays reported by developer machines.
Dependency sets
99
Different dependency lists reported by projects.
Packages seen
1660
Distinct packages in those dependency lists.

What this audience depends on

The most common packages in public projects. We name a package only after at least 5 separate installations report it in public dependency lists.

No packages have cleared that privacy threshold yet. Recorded impressions still count toward the totals above.

What agents read

Dependencies show what a project installs. Optional read reporting shows which packages an agent opens while working. It’s off by default, and file paths stay on the developer’s machine.

· Month to date (UTC)

Reported package reads
0
Package reads reported alongside ad impressions.
Packages read
0
Distinct packages an agent actually opened.
Dependency sets reporting
0
Distinct dependency lists with reported reads.
What does read reporting send?

The client turns file paths into package names locally, then reports those names with an impression. Reads are kept separate from the project’s dependency-list fingerprint, so opening different files does not create a new project identity or bypass the privacy threshold above.

Check the numbers

The totals come directly from our ledger. View the live totals as JSON →

How are the totals calculated?

Recorded revenue is the full amount earned from ads, before costs or fees, whether or not the advertiser has paid. 70% is allocated to open source; the remaining 30% runs Obrigado and funds its growth.

Collected means the advertiser’s payment has arrived. Granted means the money has been paid to maintainers. Written off means an unpaid advertiser bill will not be collected; its allocated pool share cannot be granted.

We calculate in millionths of a dollar, using whole numbers throughout. Any fraction left over when splitting a payment goes to the open-source pool.