blog / · open source
1.4 Billion Downloads, $129 a Month
Starlette and Uvicorn were downloaded 1.4 billion times last month. The sponsorships that pay for maintaining them add up to $129 a month.
That is not anyone’s fault but mine. My sponsors page was a tip jar. I never asked companies for anything, and I never offered them anything in return.
For 2027, I’m changing that.
What changed this year
This year I got 718% more security reports than last year: 180 so far, against 22 in 2025.
I close a lot of them without an advisory. Most reports I get are not valid. But every one has to be read, reproduced and answered before I know that.
This work doesn’t ship a feature. It is also the part of maintenance that matters most to a company running these projects in production.
The 2027 fund
The target is $60,000 for 2027, raised through GitHub Sponsors.
There are two tiers for companies.
| Supporter | Partner | |
|---|---|---|
| Price | $500 a month | $1,000 a month |
| Logo on the README and docs of the projects I maintain | Yes | Yes, with top placement and the docs sidebar |
| Credit in the release notes | Yes | Yes |
| A social post when you join | Yes | Yes |
| A mention in the yearly report | Yes | Yes |
| Your company description on the sponsors page | No | Yes |
| A week’s notice of security releases | No | Yes |
| Priority triage on your issues | No | Yes |
Your company can pay by card, or GitHub can invoice it, so the payment goes through normal procurement.
What the security notice is
Partners get a week’s notice before a security release. It is a heads-up to be ready, not a disclosure.
The notice names the project, the severity, the affected versions and the date of the fix. That is all. It does not say what the vulnerability is or how to trigger it, and it does not include the patch.
The point is to let your team plan the upgrade for the day the fix ships. Nobody gets a head start on the details, and a Partner signs a confidentiality term before the first notice.
If a vulnerability is already being exploited, I ship the fix without waiting.
I hope this doesn’t get misinterpreted. Security is not a business, and I’m not selling it. Every user gets the same fix on the same day, sponsor or not.
But I can’t work for free. The sponsorship I get today wouldn’t even pay for my Claude subscription.
How you can help
If your company runs these projects, the tiers are on the sponsors page.
If you’re an engineer, the same page has a short message you can copy and forward to whoever holds the budget.
To everyone who already sponsors me: thank you.
Was this useful? Consider sponsoring my open source work. ❤️