Code hosting service GitHub now warns developers if certain software libraries used by their projects contain any known vulnerabilities and provides advice on how to address the issue.
The new security feature added by GitHub is designed to alert developers when one of their project’s dependencies has known flaws. The Dependency graph and the security alerts feature have been automatically enabled for public repositories, but they are opt-in for private repositories.
When a vulnerable library is detected, a “Known security vulnerability” alert will be displayed next to it in the Dependency graph. Administrators can also configure email alerts, web notifications, and warnings via the user interface, and they can add the teams or individuals who should see the alerts.
GitHub identifies vulnerable projects by tracking flaws in Ruby gems and NPM packages on MITRE’s Common Vulnerabilities and Exposures (CVE) list. When a new flaw is added, the company identifies all repositories that use the affected version and informs their owners.
The information provided to administrators includes the type of flaw, its severity, and affected versions. There is also a link that points to a page where additional details are available.
If a patch exists for the vulnerability, GitHub advises developers to update or uses machine learning to suggest a fix provided by the community.
GitHub currently tracks vulnerabilities that have been assigned a CVE identifier, but since many publicly disclosed flaws don’t have CVEs, the company will also try to warn users of issues that don’t have one. “We’ll continue to get better at identifying vulnerabilities as our security data grows,” GitHub said.
Related: GitHub Paid $100,000 Since Launch of Bug Bounty Program
Related: “Truffle Hog” Tool Detects Secret Key Leaks on GitHub
Related: Hackers Earn Big Bounties for GitHub Enterprise Flaws