# Frontend Vulnerable Dependency Analyzer
|Time To Fix
This analyzer triggers relies on your frontend package manager (NPM or Yarn) to scan for vulnerable dependencies.
The analyzer fails if there are any known vulnerabilities in your frontend depdendencies.
# How To Fix
To fix the issue, first you need to learn what packages have vulnerabilities. Run the
audit command on your frontend package manager:
Next, you would need to upgrade to a version that fixes the vulnerability. Most of the time, it should be a minor version patch release, but sometimes it can mean upgrading to a major version.
If you need to upgrade a major version, make sure to go through the upgrade guide for the package so that you ensure the upgrade doesn't break your frontend code.
NPM also offers a
npm audit fix command that installs any compatible updates to your vulnerable dependencies:
npm audit fix
Note that NPM will not upgrade to a semver major version by the command above. If you wish to do so, you can add the
npm audit fix --force
Yarn does not offer any command to automatically fix vulnerabilities. You would need to upgrade the vulnerable packages yourself.
Make sure to run the audit command again once you fix the vulnerabilities, to make sure all vulnerabilities are indeed fixed with the upgrades.
# Do Frontend Vulnerabilities Even Matter?
Yes, some of them can matter. First of all, you should check if it's a dev dependency or a production dependency. If it's a dev dependency, it probably won't matter but production dependencies can definitely matter.
The most critical production dependency vulnerabilities are malware. Sometimes package owners sneak malware into their packages (for instance, malware to steal or mine bitcoin).
In a nutshell, don't take frontend dependencies lightly. If any of your customers had their financial data stolen because of frontend vulnerabilities in your application, they can potentially hold you responsible!