Loading page
Recommended Tab
Open source grant and fund application rounds with amounts and deadlines, GitHub Sponsors, Open Collective and Thanks.dev payout and fee changes, license changes at widely used projects, supply chain security incidents affecting popular packages, maintainer burnout and project archival announcements, corporate open source program launches, and government open source funding, with the fund or project first.
A $50,000 Sovereign Tech Fund grant, a GitHub Sponsors fee change, or a license change on a dependency that forces a migration each matters more than the fee.
The objective your Tab starts with. You can edit every line of it once the Tab is yours.
Open source grant and fund application rounds with amounts and deadlines, GitHub Sponsors, Open Collective and Thanks.dev payout and fee changes, license changes at widely used projects, supply chain security incidents affecting popular packages, maintainer burnout and project archival announcements, corporate open source program launches, and government open source funding, with the fund or project first.
Track open source sustainability for US maintainers and developers. Report only confirmed, source-backed items from the last 7 days: grant and fund application rounds from Sovereign Tech Fund, GitHub Secure Open Source Fund, Alpha-Omega, Mozilla, NLnet, Linux Foundation, Python Software Foundation, Rust Foundation and government programs with amounts and deadlines; GitHub Sponsors, Actions, Copilot and Open Collective fee, payout and terms changes; license changes at projects with over 10,000 GitHub stars or top-1,000 package downloads; supply chain compromises and critical vulnerabilities in packages with over 1 million weekly downloads; project archival, maintainer departure and fork announcements at widely used projects; corporate open source program and FOSS fund launches; and npm, PyPI, crates.io and Maven policy changes. Prefer foundation, fund, GitHub, registry, OpenSSF and CISA sources; ignore vendor blog promotion. Put the fund or project first in the title. Use high severity for a grant deadline within 21 days, a license change on a top-100 dependency, or a compromise in a package over 10 million weekly downloads. Return no more than 8 findings. Push each as a finding with a title, a two-sentence summary, sections for what it is, who qualifies or is affected, the deadline, what to do, and the source link. If nothing qualifies, push nothing and submit the run receipt.
Someone else wants the same subject? They start their own Tab from this idea. Ideas are shared; Tabs are not.
Start this Tab