@hint/hint-no-vulnerable-javascript-libraries

hint that that checks using Snyk for vulnerable JavaScript libraries

Stats

StarsIssuesVersionUpdatedCreatedSize
@hint/hint-no-vulnerable-javascript-libraries
3,2063072.12.44 months ago3 years agoMinified + gzip package size for @hint/hint-no-vulnerable-javascript-libraries in KB

Readme

No vulnerable libraries (no-vulnerable-javascript-libraries)

no-vulnerable-javascript-libraries checks for known vulnerabilities within client-side JavaScript libraries and frameworks detected on a web site.

webhint uses Snyk’s Vulnerability DB to lookup known vulnerabilities.

Why is this important?

Making sure your website dependencies are free of known vulnerabilities is important in preventing malicious attacks such as cross-site scripting attacks that can be used to compromise web site information.

What does the hint check?

This hint uses Snyk’s Vulnerability DB and js-library-detector to check if the website is running a vulnerable version of a client-side JavaScript library or framework.

The vulnerability database is updated automatically from Snyk if the cached content is older than 24h.

Can the hint be configured?

You can configure the minimum severity to report in the .hintrc file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        "no-vulnerable-javascript-libraries": ["error", {
            "severity": "low|medium|high"
        }],
        ...
    },
    ...
}

The severity possible values are: low (default), medium, and high.

If you configure this hint to high, and webhint only finds low or medium vulnerabilities, no issues will be raised.

How to use this hint?

This package is installed automatically by webhint:

npm install hint --save-dev

To use it, activate it via the .hintrc configuration file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        "no-vulnerable-javascript-libraries": "error",
        ...
    },
    "parsers": [...],
    ...
}

Note: The recommended way of running webhint is as a devDependency of your project.

Further Reading

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.