OpenClaw Maintainers Rethink Trust and Security After 388,000 GitHub Stars
Updated
Updated · github.blog · Aug 27
OpenClaw Maintainers Rethink Trust and Security After 388,000 GitHub Stars
3 articles · Updated · github.blog · Aug 27
Summary
OpenClaw’s maintainers said the project’s explosive rise to about 388,000 GitHub stars and 81,000 forks forced them to redesign how they review contributions, trust contributors and secure the codebase.
Thousands of pull requests and issues — including automated bursts of hundreds at a time — shifted the challenge from attracting help to filtering useful work without overwhelming human reviewers.
Maintainers now look beyond raw merge counts, which they said were gamed through duplicate pull requests, and instead favor evidence such as agent transcripts, screenshots, testing and clear reasoning.
Security concerns widened from code review to product defaults and dependencies, prompting tighter scrutiny of agent permissions, fewer core dependencies and closer ties with upstream maintainers after recent supply-chain attacks.
The team said GitHub’s Secure Open Source Fund helped them sharpen security practices and connect with peers, underscoring how AI-era open source growth is outpacing traditional maintainer systems.