PVS-Studio

by PVS-Studio • • Static Code Analysis Tools

No reviews yet
Free plan available View plans

PVS-Studio is a static code analyzer and SAST tool for C, C++, C#, Java, Go, JavaScript and TypeScript teams, installed on-premise and able to run offline.

PVS-Studio finds bugs and security weaknesses in source code by reading the code without running it. It is developed by PVS-Studio LLC, an independent company in Astana, Kazakhstan. Developers run it on their own machines, build servers run it on every change, and pipelines use its results to decide whether a build passes. Its diagnostics catch logic errors and suspicious constructs as well as security flaws such as SQL injection, XXE and XSS. Mapping tables tie the warnings to CWE, OWASP ASVS and SEI CERT, and an OWASP diagnostic group for C++, C# and Java includes a check for credentials stored in code. Software composition analysis looks for vulnerable components inside the application. Baselining hides the warnings already present in old code, so a team sees only what each change introduces. Project-level .pvsconfig files switch diagnostics off or change their certainty level, and the PVS-Studio server applies quality gates with thresholds per severity. The analyzer is made for development teams writing C, C++ and C#, with Java, Go, JavaScript and TypeScript covered as well. Game studios use it on Unreal Engine projects. Organisations that answer to MISRA, AUTOSAR, CWE or OWASP requirements use its standard mappings when they need to show how their code measures up. Security teams add it to an existing build to bring code and component checks into one step. Developers start an analysis from plugins for Visual Studio, JetBrains Rider, CLion, IntelliJ IDEA and VS Code, or let incremental analysis check the files touched by each build. On the server side, commit and merge request mode analyses only modified files in Jenkins, GitHub Actions, GitLab CI/CD, Azure DevOps or TeamCity. Results can go to GitHub code scanning, where a pull request check holds the merge until the warnings are dealt with. Teams that already track findings in SonarQube or DefectDojo export the reports there, and personalised email notifications send each developer the warnings found in their own code. For a team that wants every merge request read for defects before review, PVS-Studio becomes a standing step of the pipeline rather than an occasional audit.

Pricing

View plans
  • Team

    Custom pricing

    • Price on request; 1 or 2 year license, renewed at 80% of the base price within one month of expiry
    • Fewer than 10 developers
    • One platform (Windows)
    • Code base up to 1 million lines
    • Analyzer updates throughout the license period
    • Basic email support, requests handled one at a time
    • Trial key on request
  • Enterprise 30

    Custom pricing

    • Price on request; 1 or 2 year license, renewed at 80% of the base price within one month of expiry
    • 10 to 30 developers
    • Everything in Team
    • Cross-platform use on Windows, Linux and macOS
    • Priority support with several requests investigated at once
    • Personalised email notifications for developers
    • Analysis of merge and pull requests
    • Incremental analysis on the server from the command line
  • Enterprise 50+

    Custom pricing

    • Price on request; 1, 2 or 3 year license, renewed at 80% of the base price within one month of expiry
    • More than 30 developers
    • Discount offered for teams of 70 or more developers
    • Everything in Enterprise 30
    • Premium support with web-meeting consultations
    • Extended infrastructure features and diagnostic rules
  • Open source license

    Free

    • One-year license for qualifying personal open-source projects, renewable each year
    • Exclusions apply to some project types
    • Separate license programs for students and Microsoft MVPs

Features

  • Included: Quality gate that fails the build
  • Included: Pull request decoration with findings
  • Included: New-code-only analysis against a baseline
  • Not included: Custom rule authoring
  • Included: Rule set configuration per project
  • Included: SAST security vulnerability rules
  • Included: Hardcoded secrets detection
  • Included: Software composition analysis of dependencies
  • Not included: Code duplication detection
  • Not included: Complexity and maintainability metrics
  • Not included: Test coverage import and tracking
  • Not included: IDE plugin with live findings
  • Not included: Analysis for 20 or more languages
  • Not included: Infrastructure-as-code scanning
  • Not included: Automated fix suggestions for findings
  • Not included: Portfolio-level quality dashboards
  • Not included: Self-hosted analysis server
  • Included: Free analysis for open source projects

Additional Features

  • Analysis of C, C++, C#, Java, Go, JavaScript and TypeScript
  • SQL injection, XXE and XSS detection
  • CWE, OWASP ASVS and SEI CERT mapping tables
  • OWASP diagnostic group for C++, C# and Java
  • Credentials in source code check
  • Hardcoded IP address diagnostic
  • Vulnerable component search
  • Baselining of existing warnings
  • Commit and merge request analysis mode
  • Incremental analysis after build
  • Project-level .pvsconfig files
  • Certainty level per diagnostic rule
  • Quality gates with per-severity thresholds
  • Non-zero exit code on warnings for CI
  • GitHub code scanning report upload
  • Personalised email notifications for developers
  • Export to SonarQube, DefectDojo, GitLab Code Quality and CodeChecker
  • Unreal Engine integration
  • Jira integration

Best for

  • C, C++ and C# teams adding bug finding and SAST to CI
  • Game studios building on Unreal Engine
  • Teams working to MISRA, AUTOSAR, CWE or OWASP requirements
  • Security teams that want component checks beside code analysis
  • Teams that must run analysis offline on their own machines
  • Open-source maintainers who qualify for the free license

Use cases

  • finding bugs and vulnerabilities in C and C++ code
  • checking pull and merge requests before merge
  • failing a CI build on new analyzer warnings
  • suppressing legacy warnings with a baseline
  • auditing code against CWE and OWASP ASVS
  • checking code against MISRA and AUTOSAR rules
  • finding vulnerable third-party components
  • flagging credentials stored in source code
  • analysing Unreal Engine game projects
  • sending each developer the warnings in their own code

Screenshots & Videos

Explore PVS-Studio in action

Pvs Studio Homepage With Analyzer Headline
View full size
Pvs Studio Homepage With Analyzer Headline

User Reviews

Write a Review

No reviews yet

Be the first to share your experience with this software.

Compare with Similar Software

Click to compare side by side with PVS-Studio

Want to claim this brand?

To claim this brand, please contact support.