<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer-Security on krash.dev</title><link>https://krash.dev/tags/developer-security/</link><description>Recent content in Developer-Security on krash.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 08:29:09 +0530</lastBuildDate><atom:link href="https://krash.dev/tags/developer-security/rss.xml" rel="self" type="application/rss+xml"/><item><title>VS Code Security: Looking at the IDE from Security Lens</title><link>https://krash.dev/posts/attacking-vs-code/</link><pubDate>Thu, 14 Sep 2023 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/attacking-vs-code/</guid><description>&lt;p&gt;While perusing &lt;a href="https://survey.stackoverflow.co/2023/#section-most-popular-technologies-integrated-development-environment" target="_blank" rel="noopener noreferrer"&gt;StackOverflow&amp;#39;s 2023 Developer Survey&lt;/a&gt; (yes, we developers have our own version of celebrity gossip), I couldn&amp;rsquo;t help but notice that our trusty VSCode is still riding high as the undisputed IDE champ. With a whopping 73% of the developer vote, it&amp;rsquo;s safe to say that VSCode has firmly planted its flag. But, like any superstar, it&amp;rsquo;s not immune to the spotlight&amp;rsquo;s glare, especially when it comes to security. And in this blog, we&amp;rsquo;ll explore the security aspects that every VSCode user should consider.&lt;/p&gt;</description></item></channel></rss>