<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dependabot on Romano Roth</title><link>https://romanoroth.com/en/tags/dependabot/</link><description>Recent content in Dependabot on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Thu, 19 Jan 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/dependabot/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub DevSecOps Part 3: Software Composition Analysis with Dependabot and CRDA</title><link>https://romanoroth.com/en/blogs/github-devsecops-sca/</link><pubDate>Thu, 19 Jan 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-sca/</guid><description>&lt;p>GitHub does not ship a default SCA tool the way GitLab does. You have to combine two things: a platform feature called Dependabot and an SCA action from the Marketplace. In Part 3 of the GitHub DevSecOps series, Patrick Steger and I wire both into our pipeline — and find out the hard way that the Marketplace path is not as smooth as the slides suggest.&lt;/p></description></item></channel></rss>