To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

Handing out PVS-Studio Analyzer License…

Handing out PVS-Studio Analyzer Licenses to Security Experts

May 23 2017

We have suddenly realized that there are opportunities for mutually beneficial cooperation between us and information security experts. Those experts who specialize in search of vulnerabilities in software code can use the PVS-Studio analyzer for free in their research. This will, in its turn, make our tool more popular if it succeeds in finding vulnerabilities. PVS-Studio can check projects written in C and C++.


It all started with the open letter "PVS-Studio Team Willing to Work on Improving Tizen Project" with which we intended to attract Samsung Electronics' attention. Samsung cares about reliability and security of the Tizen OS and carries out various kinds of research in this area. For example, they invested over $10 million in Svace static analyzer developed in the Institute for System Programming of the Russian Academy of Science. So, we thought that the Tizen developers would probably find PVS-Studio analyzer useful as well since it managed to detect bugs in their project.

After that we were contacted by Amihai Neiderman (@AAAAAAmihai) who showed interest in PVS-Studio's capabilities. Coincidentally, he gave a conference talk about vulnerabilities in the Tizen OS (Breaking Tizen) just a month ago.

We exchanged a few emails, and then our company granted Amihai Neiderman a PVS-Studio license to use in his further research of vulnerability detection. It's unknown if he will be lucky to find any issues using our analyzer, but why not give it a try? If he is, then everyone will benefit from it. We gave Amihai Neiderman a new tool capable of detecting suspicious code where vulnerabilities may hide. If he succeeds and finds such issues, it will be a nice opportunity for him to mention PVS-Studio in his next conference talk. And for us it will be a nice opportunity to get additional promotion.

It was at this point that a good idea occurred to us. It's strange that it hadn't happen earlier, but that's just the way of many good ideas :). We realized that we should start cooperating with other experts studying vulnerabilities, too.

So, if you happen to be a public expert in security and specialize in vulnerability detection, you are welcome to email us to get your PVS-Studio license. We will help you with scanning various projects and provide user support. If you manage to find issues using our tool, we'll appreciate you mentioning it in your articles and talks.

Those willing to get the license and support will need to prove that they deal with software security and are engaged in public activity, for example, writing articles. Anyway, these points will be discussed during our communication. If you are interested, please email us at support [@]

Far not all PVS-Studio diagnostics detect security related errors. For example, the V665 warning is hardly going to be useful if you look for vulnerabilities. Luckily, such diagnostics can be turned off to leave only relevant warnings. As I already said, you can also count on our support if you have any questions.

Note. We haven't positioned our analyzer as a tool for detecting vulnerabilities before. We only discussed regular bugs in our articles. Now we want programmers to view PVS-Studio not only as a tool for detecting typos and other mistakes, but also as a tool that helps prevent multiple vulnerabilities. Many errors detected by PVS-Studio analyzer fall under CWE classification (example). In certain circumstances, CWE issues may turn to CVE ones, so using PVS-Studio allows you not only to eliminate bugs from your code, thus reducing the development cost, but also prevent lots of vulnerabilities.

Supported languages and compilers:

  • Windows. Visual Studio 2017 C, C++, C++/CLI, C++/CX (WinRT), C#
  • Windows. Visual Studio 2015 C, C++, C++/CLI, C++/CX (WinRT), C#
  • Windows. Visual Studio 2013 C, C++, C++/CLI, C++/CX (WinRT), C#
  • Windows. Visual Studio 2012 C, C++, C++/CLI, C++/CX (WinRT), C#
  • Windows. Visual Studio 2010 C, C++, C++/CLI, C#
  • Windows. MinGW C, C++
  • Windows/Linux. Clang C, C++
  • Linux. GCC C, C++


Popular related articles
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →