<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gemnasium on Romano Roth</title><link>https://romanoroth.com/en/tags/gemnasium/</link><description>Recent content in Gemnasium on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Wed, 17 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/gemnasium/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab DevSecOps Part 3: Software Composition Analysis with Gemnasium</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-sca/</link><pubDate>Wed, 17 Aug 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-sca/</guid><description>&lt;p>Your code is the small part. The libraries you pull in are the big part — and that is where most of your CVEs live. In Part 3 of the GitLab DevSecOps series, Patrick Steger and I bring up a tiny Spring Boot demo, wire it into a GitLab pipeline, and then add Software Composition Analysis with a single include line.&lt;/p></description></item></channel></rss>