<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Static Analysis - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Static Analysis News feed</description>
    <item>
      <title>LinkedIn Leverages GitHub Actions, CodeQL, and Semgrep for Code Scanning</title>
      <link>https://www.infoq.com/news/2026/02/linkedin-redesigns-sast-pipeline/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Static+Analysis-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/02/linkedin-redesigns-sast-pipeline/en/headerimage/generatedHeaderImage-1769573261709.jpg"/&gt;&lt;p&gt;LinkedIn has rebuilt its static application security testing (SAST) pipeline using GitHub Actions and custom workflows, enabling consistent, enforceable code scanning across thousands of repositories. The redesign improves security coverage, developer workflow, and observability while supporting the company’s shift-left strategy.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Security</category>
      <category>GitHub Actions</category>
      <category>CodeQL</category>
      <category>Observability</category>
      <category>Metrics</category>
      <category>Static Analysis</category>
      <category>Security Code Reviews</category>
      <category>Workflow / BPM</category>
      <category>github</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 06 Feb 2026 15:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/02/linkedin-redesigns-sast-pipeline/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Static+Analysis-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-02-06T15:00:00Z</dc:date>
      <dc:identifier>/news/2026/02/linkedin-redesigns-sast-pipeline/en</dc:identifier>
    </item>
  </channel>
</rss>
