GitHub Security
Trusted by millions
of developers
We protect and defend the most trustworthy platform for developers everywhere to create and build software.
| Dec | JAN | Feb |
| 20 | ||
| 2021 | 2022 | 2023 |
COLLECTED BY
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).
To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.
There is a dashboard running for the archivebot process at http://www.archivebot.com.
ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.
{{ message }}
We protect and defend the most trustworthy platform for developers everywhere to create and build software.
We’re constantly improving our security, audit, and compliance solutions with you in mind.
We keep GitHub safe, secure, and free of spam and abuse so that this can be the platform where developers come together to create. We do this through significant investments in platform security, incident response, and anti-abuse.
Our GitHub Security Lab is a world-class security R&D; team. We inspire and enable the community to secure open source at scale, so the world’s software we all depend on sits on foundations you can trust. Our ambition is to be the home where security researchers and developers can collaborate to make security easy for everyone willing to secure open source.
We help our customers' security and risk teams feel confident in their decisions to encourage developer collaboration on GitHub. We recognize that security is a shared responsibility with our customers. We are proud to partner with your security, risk, and procurement teams to provide the information needed for risk assessments and true understanding of our security and compliance posture.
Ship secure applications within the GitHub flow: Stay ahead of security issues, leverage the security community’s expertise, and use open source securely.
Explore GitHub Advanced SecurityWe embody the shift toward investments in safe and secure software design practices with our world-class security engineering program. We embed security expertise and capabilities into every phase of our Software Development Lifecycle.
Our Product Security Engineering team empowers developers to create a secure platform and products. Through developer training, the creation of components that form a secure foundation to build on, automated code analysis, in-depth threat modeling, and security code review and testing, we prevent vulnerabilities as early as possible in the development lifecycle.
Once our product is out the door, our security testing doesn’t stop. In addition to our internal Red Team, we leverage the collective expertise of the security research community through our Bug Bounty program to provide ongoing and broadly-scoped review.
Help us keep the world’s software safeWe aim to exceed industry standards for security.
GitHub is committed to developer privacy and provides a high standard of privacy protection to all our developers and customers. We apply stringent individual privacy protections to all GitHub users worldwide, regardless of their country of origin or location. Read more about our Global Privacy Practices.
GitHub is GDPR compliant. GDPR compliance is shown through actions, not through certifications. GitHub provides our users with the ability to access and control the information GitHub collects and processes about them. For more information, please see “How you can access and control the information we collect” in the GitHub Privacy Statement. Post Shrems II (Privacy Shield invalidation) GitHub relies on Standard Contractual Clauses (SCCs) and extends them to all of our customers.
Learn more about trans-Atlantic complianceGitHub offers AICPA System and Organization Controls (SOC) 1 Type 2 and SOC 2 Type 2 reports with IAASB International Standards on Assurance Engagements, ISAE 2000, and ISAE 3402 for GitHub Enterprise Cloud. View the SOC 3 report for GitHub Enterprise Cloud.
Learn more about our SOC reportsGovernment users can host projects on GitHub Enterprise Cloud with the confidence that our platform meets the low impact software-as-a-service (SaaS) baseline of security standards set by our U.S. federal government partners.
GitHub is a Trusted Cloud Provider(™) with the Cloud Security Alliance (CSA). GitHub registers our Consensus Assessment Initiative Questionnaire (CAIQ) on the CSA STAR Registry.
Learn more about GitHub and CSASecurity is at the core of everything we do. When you're busy building the Next Great Thing, you don't want to worry about the security of your data, much less your development platform. That’s our job.
Meet Jacob DePriest, GitHub’s new VP of security, who will be helping further our mission to secure open source software.
Learn more about JacobGitHub’s Bug Bounty turned seven this year, adding more private bounties and paying out over half a million dollars to security researchers.
Learn more about what’s to come for GitHub’s Bug BountyCodeQL security alerts now include security severity levels to help you understand the risks posed by the issue alerted and enable you to set policies by severity level.
Learn more about this new featureRead the GitHub Blog
Follow us on Twitter
GitHub Security Lab’s mission is to inspire and enable the community to secure the open source software we all depend on.
Explore GitHub Security LabGet rewarded for CodeQL queries that find and prevent vulnerabilities at scale in open source projects through our bounty program.
Interested in joining the Security team here at GitHub? All open roles are listed under the Security section via our careers page.
See open roles
Become part of our security story