<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Dragan Petrovic</title>
    <description>The latest articles on Forem by Dragan Petrovic (@dragan_petrovic_32bcfd458).</description>
    <link>https://forem.com/dragan_petrovic_32bcfd458</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3092005%2Fb68eaccd-7a8e-44ef-aa58-8516f2ace1d9.png</url>
      <title>Forem: Dragan Petrovic</title>
      <link>https://forem.com/dragan_petrovic_32bcfd458</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/dragan_petrovic_32bcfd458"/>
    <language>en</language>
    <item>
      <title>Analyze your dependencies</title>
      <dc:creator>Dragan Petrovic</dc:creator>
      <pubDate>Sat, 26 Apr 2025 04:29:49 +0000</pubDate>
      <link>https://forem.com/dragan_petrovic_32bcfd458/analyze-your-dependencies-m8o</link>
      <guid>https://forem.com/dragan_petrovic_32bcfd458/analyze-your-dependencies-m8o</guid>
      <description>&lt;p&gt;Sometimes we need to analyze npm packages, how often are they updated, if they have some security vulnerability (or had in some previous version) and a lot of different checks.&lt;/p&gt;

&lt;p&gt;A useful tool that can help with this is &lt;a href="https://www.npmcheck.com" rel="noopener noreferrer"&gt;www.npmcheck.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;You can access to a lot of informations about the package itself:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6bfl8vk0o7vyt4olp8h4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6bfl8vk0o7vyt4olp8h4.png" alt="Image description" width="800" height="1191"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can check the versions history of the package with informations about dimensions etc:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffpwgum4mku6tq4cvtn7o.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffpwgum4mku6tq4cvtn7o.png" alt="Image description" width="800" height="811"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Or maybe check for the security issues of the package itself or related to some transitive dependency of the package:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2bo7q3jv1kmbcxwblvnh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2bo7q3jv1kmbcxwblvnh.png" alt="Image description" width="800" height="808"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>npm</category>
    </item>
  </channel>
</rss>
