No vulnerable libraries
User guide
- Getting Started
Api
Concepts
Configurations
Configuring webhint
Connectors
Development flow integration
Extensions
Formatters
Hints
- Avoid CSS limits
- Avoid HTTP redirects
- axe accessibility check
- Babel configuration hint set
- Compatibility of CSS, HTML and JavaScript features
- Correct `Content-Type` header
- Correct manifest extension
- Correct viewport
- Detect CSS Reflows
- Disallowed HTTP headers
- External links disown opener
- Has web app manifest
- Highest document mode
- HTTP cache
- Leading '.' in `classList.add` or `classList.remove`
- Manifest has name
- Minify JavaScript
- Modern DOCTYPE
- No `createElement` with SVG
- No `P3P` headers
- No broken links
- No byte-order mark
- No Inline CSS Styles
- No protocol-relative URLs
- No small error pages
- No vulnerable libraries
- Nu HTML test
- Optimal compression
- Optimize images
- Performance budget
- Prefixed CSS first
- scoped-svg-styles
- Specify button type
- SSL server test
- TypeScript configuration hints set
- Unneeded HTTP headers
- Use `Strict-Transport-Security` header
- Use `X-Content-Type-Options` header
- Use Apple touch icon
- Use charset `utf-8`
- Use HTTPS
- Use subresource integrity
- Valid `Set-Cookie` header
- Valid `theme-color`
- Valid manifest
- webpack configuration hints set
Parsers
Server configurations
Troubleshoot
- Api
- Concepts
- Configurations
- Configuring webhint
- Connectors
- Development flow integration
- Extensions
- Formatters
- Hints
- Parsers
- Server configurations
- Troubleshoot
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.