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 / 10 days ago
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 / 25 days ago
I checked the code with the PVS-Studio analyzer using the plugin for Visual Studio. - Source: dev.to / 10 months ago
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
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 / about 2 years ago
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 / about 2 years ago
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
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
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
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 / over 2 years ago
Do you know an article comparing PVS-Studio to other products?
Suggest a link to a post with product alternatives.
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.