A closer look at GitHub’s new transparency reporting hub
GitHub has published transparency reports every six months since 2014, detailing how the company handles content moderation and user information disclosures. Today, the platform is changing how that data is presented. Instead of periodic blog posts, GitHub is introducing a dedicated transparency center—an interactive space designed for researchers, journalists, and developers who want to dig into the raw numbers.
The new transparencycenter.github.com site lets visitors explore reporting data through interactive charts, compare statistics across different reporting periods, and download CSV files from the associated github/transparency data repository. This move is meant to make long-standing reporting practices more accessible and straightforward.
From blog posts to interactive data
Over the past decade, the biannual transparency report has grown longer as GitHub expanded its reporting categories and added more detail. The company says the shift to a centralized platform is an effort to streamline the report while preserving its commitment to transparency. Going forward, GitHub will use its blog and social channels to announce updates, new reporting categories, and notable trends found in the data—rather than publishing the full report in a single post.
Evolving practices and principles
The reporting framework has evolved alongside GitHub’s growth past 100 million developers. The company has added more granular categories and updated its content moderation and disclosure practices in alignment with the Santa Clara Principles on Transparency and Accountability in Content Moderation and the United Nations report on content moderation. A developer-first moderation approach remains central—one that seeks to minimize disruption to software projects, protect developer privacy, and keep developers informed about moderation actions and information requests.
GitHub is inviting feedback on the new transparency center via the github/transparency repository, where users can open issues with questions or suggestions. The company’s site-policy repository remains the home for details on how GitHub’s policies and procedures are developed.
