pnpm audit
Added in: v4.3.0
Checks for known security issues with the installed packages.
If security issues are found, try to update your dependencies via pnpm update
.
If a simple update does not fix all the issues, use overrides to force
versions that are not vulnerable. For instance, if lodash@<2.1.0
is vulnerable,
use this overrides to force lodash@^2.1.0
:
{ "pnpm": { "overrides": { "lodash@<2.1.0": "^2.1.0" } }}
Or alternatively, run pnpm audit --fix
.
#
Options#
--audit-level <severity>- Type: low, moderate, high, critical
- Default: low
Only print advisories with severity greater than or equal to <severity>
.
#
--fixAdded in: v6.11.0
Add overrides to the package.json
file in order to force non-vulnerable versions of the dependencies.
#
--jsonOutput audit report in JSON format.
#
--dev, -DOnly audit dev dependencies.
#
--prod, -POnly audit production dependencies.
#
--no-optionalDon't audit optionalDependencies
.
#
--ignore-registry-errorsAdded in: v6.7.1
If the registry responds with a non-200 status code, the process should exit with 0. So the process will fail only if the registry actually successfully responds with found vulnerabilities.