- A speaker at GitHub's session said security is the cost of consuming open source, not a tax maintainers owe. GitHub's grant gave each project $10,000.
- The speakers admitted $10,000 is not a salary and not a structural fix. They said funding one project can still reach millions of users.
A speaker at a GitHub Universe 2026 session argued that companies using open source should treat its security as a cost of use, not as free labour from volunteers. The point came in "How GitHub secures open source," an episode of the GitHub show. The guests were Bas Alberts and Xavier René-Corail of GitHub's security research teams.
What was said
GitHub Security Lab described its Secure Open Source Fund. Each project received $10,000, a three-week security programme from GitHub experts and partners such as the Open Source Security Foundation, and an AI security audit of its code. The excerpts do not say what the audit checked.
More than 200 projects and over 300 maintainers took part, and a speaker said thousands of vulnerabilities were fixed. A speaker tied the projects to 20 billion monthly downloads, though that figure comes from a machine transcript and may be misheard.
The speakers argued that fixing one project can protect millions of consumers. Some general background shows why. Modern products are built from packages, and those packages rely on other packages. A flaw in one small package sits inside every product that includes it, even indirectly. A fix helps only after the maintainer ships a patched release and downstream teams update to it.
A speaker was frank about scale. They said $10,000 is not a salary and called the fund a start, not a structural fix to the funding problem. Addressing companies, a speaker said: "Don't just treat maintainer labor as something you are owed."
Why it matters
Our reading: a volunteer-run package deep in your stack is a concrete risk. If its one maintainer has no time, a flaw may wait for a fix, and your product keeps carrying it. Your release then depends on their free time.
The grant works as a yardstick. A manager can ask which dependencies are run by a few unpaid people, and what the company has given them.
The other side
The speakers said the programme does not solve the funding problem. What happens to a project once the course ends is the article's own question. The excerpts do not answer it.
The results are GitHub's account of its own programme. The excerpts give no independent check of the claimed reach, and they do not show whether companies will pay.
The session also warned maintainers not to trust AI verdicts about their code blindly. An AI audit still needs a person to judge its findings.
Written by the WebPulse Newsroom with AI assistance, and checked by our editorial review: every quotation was verified against the recording's transcript. How we use AI.
The conversation this talking point comes from
- GitHub: How GitHub secures open source (2026-11-16)





