Our website uses cookies to enhance your browsing experience.
Accept
to the top
Home
>
Documentation
>
Installing PVS-Studio JavaScript and...
menu mobile close menu
Introduction
How to enter the PVS-Studio license and what's the next move
PVS-Studio's trial mode
System requirements
Technologies used in PVS-Studio
Release history
Release history for previous versions (before 8.00)
Analyzing projects
On Windows
Getting acquainted with the PVS-Studio static code analyzer on Windows
Build-system independent analysis (C and C++)
Direct integration of the analyzer into build automation systems (C and C++)
On Linux and macOS
PVS-Studio C# installation on Linux and macOS
How to run PVS-Studio C# on Linux and macOS
Installing and updating PVS-Studio C++ on Linux
Installing and updating PVS-Studio C++ on macOS
How to run PVS-Studio C++ on Linux and macOS
Cross-platform
PVS-Studio Java quick start
Direct use of Java analyzer from command line
Cross-platform analysis of C and C++ projects in PVS-Studio
PVS-Studio for embedded development
Analysis of C and C++ projects based on JSON Compilation Database
How to use JavaScript and TypeScript analyzer from the command line
How to use Go analyzer from the command line
IDE
Get started with PVS-Studio in Visual Studio
Using PVS-Studio with JetBrains Rider and CLion
How to use the PVS-Studio extension for Qt Creator
How to integrate PVS-Studio in Qt Creator without the PVS-Studio plugin
Using the PVS-Studio extension for Visual Studio Code
Using PVS-Studio with IntelliJ IDEA and Android Studio
How to use PVS-Studio in JetBrains WebStorm and PhpStorm
How to use PVS-Studio in JetBrains GoLand
Build systems
Analyzing Visual Studio / MSBuild / .NET projects from the command line using PVS-Studio
Using PVS-Studio with the CMake module
Integrating PVS-Studio Java into the Gradle build system
Integrating PVS-Studio Java into the Maven build system
Game Engines
How to analyze Unity projects with PVS-Studio
Analysis of Unreal Engine projects
Continuous use of the analyzer in software development
Running PVS-Studio in Docker
Running PVS-Studio in Jenkins
Running PVS-Studio in TeamCity
How to upload analysis results to Jira
PVS-Studio and continuous integration
PVS-Studio's incremental analysis mode
Analyzing commits and pull requests
Unattended deployment of PVS-Studio
Speeding up the analysis of C and C++ code through distributed build systems (Incredibuild)
Integrating of PVS-Studio analysis results in code quality services (web dashboard)
Integration of PVS-Studio analysis results into DefectDojo
Integration of PVS-Studio analysis results into SonarQube
Integration of PVS-Studio analysis results into CodeChecker
Deploying the analyzer in cloud Continuous Integration services
Using with Travis CI
Using with CircleCI
Using with GitLab CI/CD
Using with GitHub Actions
Using with Azure DevOps
Using with AppVeyor
Using with Buddy
Managing analysis results
How to display the analyzer's most interesting warnings
How to use the OWASP diagnostic group in PVS-Studio
MISRA Coding Standards and Compliance
Baselining analysis results (suppressing warnings for existing code)
Handling the diagnostic messages list in Visual Studio
Suppression of false-positive warnings
How to view and convert analyzer's results
Relative paths in PVS-Studio log files
Viewing analysis results with C and C++ Compiler Monitoring UI
Notifying the developer teams (blame-notifier utility)
Filtering and handling the analyzer output through diagnostic configuration files (.pvsconfig)
Excluding files and directories from analysis
Additional configuration and resolving issues
Tips on speeding up PVS-Studio
PVS-Studio: troubleshooting
PVS-Studio analyzer diagnostic logging
Additional diagnostics configuration
User annotation mechanism in JSON format
Annotating C and C++ entities in JSON format
Annotating C# entities in JSON format
Annotating Java entities in JSON format
Configuration file: pvs-settings.toml
How to delete redundant false alarm markers
Predefined PVS_STUDIO macro
Analysis configuration file (Settings.xml)
Settings: general
Settings: Common Analyzer Settings
Settings: Detectable Errors
Settings: Don't Check Files
Settings: Keyword Message Filtering
Settings: Registration
Settings: Specific Analyzer Settings
Analyzer diagnostics
PVS-Studio Messages
General Analysis (C++)
General Analysis (C#)
General Analysis (Java)
Micro-Optimizations (C++)
Micro-Optimizations (C#)
Diagnosis of 64-bit errors (Viva64, C++)
Customer specific requests (C++)
MISRA errors
AUTOSAR errors
OWASP errors (C++)
OWASP errors (C#)
OWASP errors (Java)
Problems related to code analyzer
Additional information
Credits and acknowledgements
toggle menu Contents
Jul 22 2026

Installing PVS-Studio JavaScript and TypeScript analyzer (pvs-js)

Jul 22 2026

Direct links to download the distributions are available on the download page.

pvs-js dependencies

To run pvs-js, Node.js versions 18-24, npm, and PVS-Studio C++ analyzer are required.

To install pvs-js via a package manager, the dependencies are installed automatically. When installing from an archive, install the C++ analyzer and the other dependencies manually. See the relevant documentation sections for installation instructions on Linux and macOS.

Windows

To install pvs-js, select the JavaScript and TypeScript analysis engine option. pvs-js requires Node.js version 18-24. If Node.js is not installed on your system, the installer will offer to install it. On the installer page, you can also choose to install the WebStorm plugin.

Linux

Installation from repositories

For debian-based systems

Before Debian 11 and Ubuntu 22.04:

wget -q -O - https://wcdn.pvs-studio.com/etc/pubkey.txt | \
  sudo apt-key add -

sudo wget -O /etc/apt/sources.list.d/viva64.list \
  https://wcdn.pvs-studio.com/etc/viva64.list

sudo apt-get update
sudo apt-get install pvs-js

Debian 11 and Ubuntu 22.04 and newer: 

wget -qO- https://wcdn.pvs-studio.com/etc/pubkey.txt | \
  sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/viva64.gpg

sudo wget -O /etc/apt/sources.list.d/viva64.list \
  https://wcdn.pvs-studio.com/etc/viva64.list

sudo apt-get update
sudo apt-get install pvs-js

For yum-based systems:

wget -O /etc/yum.repos.d/viva64.repo \ 
  https://wcdn.pvs-studio.com/etc/viva64.repo
yum update
yum install pvs-js

For zypper-based systems:

wget -q -O /tmp/viva64.key \
  https://wcdn.pvs-studio.com/etc/pubkey.txt

sudo rpm --import /tmp/viva64.key
sudo zypper ar -f https://wcdn.pvs-studio.com/rpm viva64

sudo sed -i \
  's|enabled=1|enabled=1\ngpgkey=https://wcdn.pvs-studio.com/etc/pubkey.txt|' \
  /etc/zypp/repos.d/viva64.repo

sudo zypper refresh
sudo zypper install pvs-js

Manual installation

To install, use the following command:

Deb package

sudo gdebi pvs-js-VERSION.deb

or

sudo apt-get -f install pvs-js-VERSION.deb

Rpm package

sudo dnf install pvs-js-VERSION.rpm

or

sudo zypper install pvs-js-VERSION.rpm

or

sudo yum install pvs-js-VERSION.rpm

or

sudo rpm -i pvs-js-VERSION.rpm

Archive

tar -xzf pvs-js-VERSION.tar.gz
sudo ./install.sh

macOS

Installation from Homebrew

Installation commands:

brew install viva64/pvs-studio/pvs-js

Update commands:

brew upgrade pvs-studio-js

Installer

Run the .pkg file and follow the instructions. On the Installation Type page, click the Customize button and select the components you want to install.

Archive

To install from the archive, run:

unzip pvs-js-VERSION.zip
sudo ./install.sh

Was this page helpful?

< Previous
Next >