Introducing the GitHub transparency center

By admin
As the home for all developers,

GitHub
ORG

is committed to providing a safe, open, and inclusive platform for code collaboration. We take a developer-

first
ORDINAL

approach to content moderation centered on minimizing the disruption of software projects, protecting developer privacy, and being transparent with developers about content moderation and disclosure of user information.

It’s time for our

biannual
DATE

transparency report, where we have been sharing how we approach content moderation and disclosure of user information since our

first
ORDINAL

report in

2014
DATE

. As GitHub has grown to be the home of

over 100 million
CARDINAL

developers, we’ve expanded our reporting categories and added more granularity to our stats. We’ve also updated our transparency reporting and content moderation practices to reflect the spirit of the Santa Clara Principles on Transparency and Accountability in Content Moderation and the

United Nations
ORG

report on content moderation.


This year
DATE

, we’re making changes to the format of the report itself.

We’re excited to introduce the transparency center, a new platform for our transparency reporting data. Using the GitHub transparency center, you can interact with the charts, compare data across

years
DATE

, and download the

CSVs
ORG

in the repository to delve into the aggregate reporting data yourself. The transparency center was designed to make our reporting as accessible, interactive, and straightforward as possible—with researchers, journalists, and developers in mind.

After over

almost a decade
DATE

of transparency reports, our blog posts became longer as we expanded our reporting. The transparency center is an effort to streamline and simplify the report while maintaining our commitment to transparency. Going forward, we will continue to use the

GitHub
ORG

blog and social media channels to share when we’ve updated our numbers, expanded and deepened reporting, and discovered interesting insights in our data.

We encourage you to check out the transparency center and open an issue with feedback and questions in our repository.