Gregg Cochran is a staff program manager at GitHub who writes about open-source maintainers and software security. His reporting explains how funding, security expertise and maintainer judgment combine as AI changes contribution volume.[1][2]
Start with OpenClaw went viral. Meet the maintainers building and securing it. →
Links
Gregg Cochran: GitHub Staff Program Manager · GitHub
Career
GitHub’s author card identifies Cochran as a staff program manager. His Secure Open Source Fund article describes a program that pairs maintainers with GitHub Security Lab experts, tools, funding and a peer community. The article treats security as ongoing maintenance: incident plans, vulnerability reporting, dependency updates and release practices remain necessary even when AI helps with triage or fixes.[2]
Ideas
Cochran’s OpenClaw article draws on a discussion with project maintainers about contribution growth and trust. They describe why a merge count is an unreliable reputation signal when contributions can be copied, and why transcripts, screenshots, tests and an explanation of the contributor’s thinking provide more useful evidence. The account also follows the pressure to review agent-generated work with agents. His role here is author and program communicator; the byline does not make him an OpenClaw creator or maintainer.[3]
Tools, writing & talks
Writing, research & talks
Start here
A maintainer conversation about contribution volume, evidence of understanding, secure defaults and dependency relationships.
Begin with the OpenClaw maintainer conversation if you review contributions. Its examples make the trust problem concrete before the fund article explains the program and security practices behind the response.
Author; not an OpenClaw authorship claim[3]Original sourceGitHub’s account of a Secure Open Source Fund cohort and the security practices supported by its funding and expert guidance.
Author[2]Original source