Software Alternatives, Accelerators & Startups

PVS-Studio

PVS-Studio is a useful piece of software for detecting problems in source code. The software examines program codes written in C, C++, and C# for any problems that might prohibit the code from functioning properly.

PVS-Studio Reviews and details

Screenshots and images

  • PVS-Studio Landing page
    Landing page //
    2023-08-02

Badges

Promote PVS-Studio. You can add any of these badges on your website.

SaaSHub badge
Show embed code

Videos

Generic Talks - PVS-Studio

CppCast Episode 238: PVS-Studio Static Analysis with Yuri Minaev

Social recommendations and mentions

We have tracked the following product recommendations or mentions on various public social media platforms and blogs. They can help you see what people think about PVS-Studio and what they use it for.
  • What errors are lurking in LLVM code?
    These checks are always very special for us because static analyzers operate almost the same way as compilers do when they analyze code. Compilers also leverage static analysis to issue warnings. They're almost cousins, though. However, each of them is good at their own thing. This article is proof of that. The Clang compiler, a part of LLVM, compiled our analyzer and got it working. We even have an article about... - Source: dev.to / about 2 months ago
  • Let's check the qdEngine game engine, part three: 10 more bugs
    This is where static code analysis tools such as PVS-Studio come in. Analyzers check code regardless of how often (with what probability) it's executed while the application is running. That's why analyzers can find errors in rarely used code. Let's look at such a case:. - Source: dev.to / 2 months ago
  • Let's check the qdEngine game engine, part one: top 10 warnings issued by PVS-Studio
    The analyzer has found various types of errors in the project. So, we'd like to look at them from different angles. That's why I'll publish several articles on different topics. The first one is dedicated to the Best button in the PVS-Studio plugins. - Source: dev.to / 3 months ago
  • Bugs that buzzed a lot
    One of the ways to create better and more secure code is to use static analyzers such as PVS-Studio. The tool provides code analysis for the C, C++, C#, and Java programming languages. - Source: dev.to / 3 months ago
  • Examining suspicious code fragments in AWS SDK for .NET
    I checked the code with the PVS-Studio analyzer using the plugin for Visual Studio. - Source: dev.to / about 1 year ago
  • Do developers care about code security?
    I'm working on PVS-Studio. It's a code analysis tool detects both coding errors and security flaws (SAST). So, I'd like to know more about what teams expect from SAST solutions. Source: about 1 year ago
  • SAST in Secure SDLC: 3 reasons to integrate it in a DevSecOps pipeline
    And yet SAST is another essential step-up that can help reduce reputational and financial risks. If you are building SSDLC, SAST tools should be a mandatory part of the DevSecOps pipeline. - Source: dev.to / over 2 years ago
  • Vulnerabilities due to XML files processing: XXE in C# applications in theory and in practice
    Since the project is open-source, we'll take advantage of this. To search for vulnerabilities, in addition to our own knowledge, we use PVS-Studio — a solution that searches for errors and security weaknesses. We need a group of security-related diagnostics — OWASP. You can read about turning on the corresponding warnings here. - Source: dev.to / over 2 years ago
  • Errors and suspicious code fragments in .NET 6 sources
    I checked the code with the PVS-Studio static analyzer. As you probably guessed from this article, PVS-Studio 7.16 supports the analysis of projects on .NET 6. You can read more about new enhancements of the current release here. The PVS-Studio C# analyzer for Linux and macOS now works on .NET 6 as well. - Source: dev.to / over 2 years ago
  • A variety of errors in C# code by the example of CMS DotNetNuke: 40 questions about the quality
    I use PVS-Studio 7.15 to perform the analysis. Want to try the analyzer on your project? Click here to open the page with all the necessary steps. Have any questions? Don't understand something? Feel free to contact us. - Source: dev.to / over 2 years ago
  • All hail bug reports: how we reduced the analysis time of the user’s project from 80 to 4 hours
    Before we proceed to the story, here's a little introduction. We are the PVS-Studio team. We develop the analyzer that searches for errors and potential vulnerabilities in C, C++, C#, and Java code. Yours truly is the team lead of the C# analyzer development team, the author of articles and posts. - Source: dev.to / over 2 years ago
  • Optimization of .NET applications: a big result of small edits
    Beware that we are not going to delve into any abstract theoretical reasoning. In this context, the "change the code to avoid the creation of one iterator" type of tips would look bizarre. All the problems listed in this article were identified after I profiled the PVS-Studio static analyzer for C#. The main purpose of profiling was to reduce the analysis time. - Source: dev.to / almost 3 years ago

External sources with reviews and comparisons of PVS-Studio

TOP 40 Static Code Analysis Tools (Best Source Code Analysis Tools)
PVS-Studio is a tool for detecting bugs and security weaknesses in the source code of programs, written in C, C++, C#, and Java. It works in Windows, Linux, and macOS environment.

Do you know an article comparing PVS-Studio to other products?
Suggest a link to a post with product alternatives.

Suggest an article

PVS-Studio discussion

Log in or Post with

This is an informative page about PVS-Studio. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.