Some open-source software maintainers prefer GitHub's private vulnerability reporting because it centralizes submitted reports within the platform.
Researchers of a human-centered security paper published at PETS concluded that researchers should only use contact information that has been visibly made public by individuals with the intention of allowing the general public to contact them, noting that GitHub’s email address mechanics and users’ lack of knowledge about them had not been addressed by previous work.
“The biggest reason I never used them is they’ve never been pushed or the benefits of them sold to me […] If it’s really easy and simple to use, it’d be nice if that is kind of turned on by default on all projects.”
The 'State of the Octoverse' is an annual report published by GitHub regarding software development trends, with a 2023 edition available.
GitHub provides its terms of service at https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies.
Jenny T. Liang, Thomas Zimmermann, and Denae Ford authored 'Understanding skills for oss communities on github', published in the Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) in 2022.
Some Open Source Software (OSS) maintainers prefer using email for vulnerability reporting because they perceive it as having more inherent privacy compared to public GitHub issues.
The survey design was informed by the 'Getting started GitHub security features guide' and established initiatives like the OpenSSF guides on vulnerability management.
The GitHub Security Advisory Database, established in 2017, serves as a repository for security vulnerabilities in software projects hosted on GitHub.
GitHub disallows private forks from using CI features for security purposes, despite OSS maintainers desiring such features for fixing vulnerabilities.
The authors' study found little evidence from the perspective of Open Source Software (OSS) maintainers to support GitHub's recommendation to use private vulnerability reporting Private Security Features (PSFs) over public reporting.
GitHub provides documentation on collaborating in a temporary private fork to resolve a repository security vulnerability at https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.
Preventing the premature disclosure of potentially severe and easily exploitable vulnerabilities is a strong argument in favor of GitHub's recommendation to use private vulnerability reporting.
Jason Tsay, Laura Dabbish, and James Herbsleb analyzed the influence of social and technical factors on evaluating contributions in GitHub in their 2014 paper published in the Proceedings of the 36th International Conference on Software Engineering.
GitHub's private vulnerability reporting feature allows contributors to report vulnerabilities privately within the platform, enabling maintainers to review reports, update severity, invite others to develop fixes, and decide whether to request a CVE.
Dependabot is an automated dependency update tool built into the GitHub platform, introduced in 2019.
Sabato Nocera, Simone Romano, Massimiliano Di Penta, Rita Francese, and Giuseppe Scanniello performed a mining study on GitHub to analyze the adoption of Software Bill of Materials (SBOM), published in the 2023 IEEE International Conference on Software Maintenance and Evolution (ICSME).
Open-source software maintainers use various mediums to notify the community about the need to upgrade, including mailing lists, backchannels, GitHub security advisories, and requesting a CVE.
Molden et al. cautioned against the use of gamification features on GitHub, such as daily activity streaks, because they may elicit unwanted behaviors like making contributions solely to maintain an activity streak.
To comply with GitHub's terms of service, the researchers only contacted Open Source Software maintainers who had publicly available contact information advertised as reachable to the general public, such as in profile introduction markdown or on an external website.
Laura Dabbish, Colleen Stuart, Jason Tsay, and Jim Herbsleb published 'Social coding in github: transparency and collaboration in an open software repository' in the Proceedings of the ACM 2012 conference on computer supported cooperative work.
OSS maintainers face challenges with Private Security Fixes (PSFs) because the built-in private vulnerability reporting feature on GitHub lacks Continuous Integration (CI) processes for developing fixes on private forks.
“I haven’t really needed anything more involved than GitHub issues […] Security isn’t something that we worry too much about. We’re not ready to hear that message, even if GitHub does push me, I’ll probably just skim over them, because I’m not ready to actually to, you know, get that message […] We worry, we kind of have it in mind, but it’s not our main goal.”
The researchers excluded subjects residing in OFAC-sanctioned countries and regions from their study to comply with their institutional IRB-approved protocol, reducing the pool of potential GitHub projects to 1,920.
The researchers recruited participants for an interview study by directing interested respondents to a Calendly space where they could join a publicly available Zoom link and provide the GitHub project they oversee.
Hassan Onsori Delicheh, Alexandre Decan, and Tom Mens quantified security issues in reusable JavaScript actions within GitHub workflows in a 2024 study published in the Proceedings of the 21st International Conference on Mining Software Repositories.
Most open-source software project maintainers encourage using a private avenue for reporting vulnerabilities, while some are willing to use public channels like GitHub issues for security bugs.
To mitigate the lack of CI processes in private forks, OSS maintainers often host additional private repositories outside of GitHub that mimic their public presence or run potential fixes through build processes on personal machines.
Open-source software maintainers use private forks within GitHub's private vulnerability reporting feature to develop fixes quietly.
“The first one that I use quite often is Renovate, that is a tool in Github easily available where you can configure: I want this and this upgraded like that, and you can have all kinds of settings and then it automatically gives you a pull request […] with a dependency update and automatically, the test pipeline fires.”
Open-source software project maintainers use a variety of tooling both in and out of the GitHub platform for vulnerability management.
The researchers filtered GitHub Advisory Database entries to identify projects hosted on GitHub, resulting in just over 2,000 unique projects.
GitHub provides documentation on GitHub security features at https://docs.github.com/en/code-security/getting-started/github-security-features.
“We have a security policy in place where we say please do not report it publicly but try to contact me personally via email or send a mail to our security mailing list or create a security advisory on GitHub.”
Four interviewees reported that GitHub's private vulnerability reporting feature is easy to use and quick to set up.
GitHub provides documentation on the coordinated disclosure of security vulnerabilities at https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/about-coordinated-disclosure-of-security-vulnerabilities#standard-process.
The authors of the study 'A Mixed-Methods Study of Open-Source Software Maintainers' only reached out to maintainers who had publicly available contact information advertised as reachable to the general public, such as in profile introduction markdown or on a self-hosted website, to comply with GitHub’s terms of service and the ethical standards suggested by the PETS paper.
A human-centered security paper published at the Privacy Enhancing Technologies Symposium (PETS) mined commit information for maintainer emails from GitHub.
OSS platforms like GitHub provide security features such as dependency management, but these features are frequently underutilized by maintainers.
GitHub reported that 60% more vulnerability-related, automated pull requests were merged in 2023 compared to 2022.
Lukas Moldon, Markus Strohmaier, and Johannes Wachs conducted a natural experiment on GitHub to analyze how gamification affects software developers, published in the 2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE).
Some open-source software maintainers link to organization-specific security policies published outside of the GitHub platform.
Eric Tooley and Kate Catlin announced that private vulnerability reporting became generally available on GitHub in a 2023 blog post.
Ayala et al. found that many GitHub repositories lack a security policy.
Jessy Ayala, Yu-Jye Tung, and Joshua Garcia authored a poster titled 'A glimpse of vulnerability disclosure behaviors and practices using github projects', presented at the 45th IEEE Symposium on Security and Privacy in 2024.
Felix Fischer, Jonas Höbenreich, and Jens Grossklags authored 'The effectiveness of security interventions on github', published in the Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security, pages 2426–2440.
The researchers sampled 1,920 unique GitHub projects from the GitHub Advisory Database, with some projects having up to 185,000 stars and 400,000 listed dependent GitHub projects.
Jessy Ayala and Joshua Garcia conducted an empirical study on workflows and security policies in popular GitHub repositories, published in the 2023 IEEE/ACM 1st International Workshop on Software Vulnerability.