As per legal filing obtained by The New York Times on Friday, Twitter has removed a GitHub repository containing a considerable portion of its leaked source code.

According to the filing, “The leaked code seemed to have been accessible on GitHub for several months prior to Twitter issuing a copyright infringement takedown on Friday.

It consisted of ‘proprietary source code for Twitter’s platform and internal tools.'”

The filing further stated that the code had been removed from GitHub since then

As reported by the Times, the individual who leaked Twitter’s source code identified themselves as “FreeSpeechEnthusiast” on GitHub.

According to the Daily Wire, after Twitter filed the copyright infringement claim, GitHub requested a description of the allegedly infringed copyrighted code.

In response, Twitter stated that the material consisted of “proprietary source code for Twitter’s platform and internal tools.” Twitter further admitted that it did not have any measures in place to regulate access to the content.

In an effort to pursue legal action, Twitter is seeking to obtain identifying information about the user “FreeSpeechEnthusiast,” as well as any individuals who may have accessed and disseminated the leaked Twitter source code.

To do so, they are employing a subpoena to compel GitHub to provide this information.

In response to a query from BleepingComputer, GitHub indicated that they had no further comments to offer on the matter.

This is because it is the general policy of the platform to refrain from commenting on decisions related to the removal of content.

While the number of people who accessed or downloaded Twitter’s leaked source code is unknown, it has been noted that the leaker had a small number of followers.

However, the leak could have serious implications for Twitter, as the code may be analyzed to identify any potential vulnerabilities that could be exploited.

Apart from seeking information about the leaker, the court order also requires GitHub to identify any users who may have posted, uploaded, downloaded, or altered the leaked data.

GitHub has been given a deadline of April 3 to provide the requested information.