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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.

>
>
Ways to Get a Free PVS-Studio License

Ways to Get a Free PVS-Studio License

March 11, 2019
Author:

There are several ways to get a free license of the PVS-Studio static code analyzer, which is meant for searching for errors and potential vulnerabilities. Open source projects, small closed projects, public security specialists and owners of the Microsoft MVP status can use the license for free. The article briefly describes each of these options.

Some potential users complain that options of free licensing described here aren't user-friendly or don't suit them in order to try PVS-Studio. So here's a very important note: what is written here is not the way to try PVS-Studio! To investigate the abilities of the tool, one has to use a temporary license key that you can request on the download page. And only if you decide to use PVS-Studio (in addition, for free), this article will give a clue how to do it.

0614_Free_PVS-Studio_variants/image1.png

PVS-Studio is a tool designed to detect errors and potential vulnerabilities in the source code of programs, written in C, C++, C# and Java. It works in Windows, Linux and macOS environments.

PVS-Studio is a paid B2B solution, it is used by many teams in various companies. List of clients.

So let's consider the cases, when the PVS-Studio analyzer can be used free of charge.

Open Source Projects

PVS-Studio can be used for free by the programmers, participating in development of open source projects, posted on GitHub, GitLab or Bitbucket. Everyone who wishes, can get a free license for 1 year. To get a license, you need to:

  • Go to the page: /en/open-source-license/
  • Enter your name and the e-mail, to which you'd like to receive a license key;
  • Enter the link to your GitHub/GitLab/Bitbucket profile;
  • Send a request for a free license.

Upon expiration of the license, you can get a new license key in the same way.

The key is individual and can only be used to check open source projects hosted on GitHub/GitLab/Bitbucket. Free license doesn't extend to projects' mirrors.

More details about this type of free licensing are given in the article "Free PVS-Studio for those who develops open source projects".

Closed Projects

There are many small private projects developed by enthusiasts. For example, games, created by indie developers or projects of academic focus.

The option of free licensing, based on adding comments of a special type in the code, will be right for these projects. The point is that such comments are unacceptable in large corporate projects, but developers may well add them in their individual projects.

Here are these comments:

Comments for students (academic license):

// This is a personal academic project. Dear PVS-Studio, please check it.

// PVS-Studio Static Code Analyzer for C, C++, C#, and Java: http://www.viva64.com

Comments for individual developers:

// This is an independent project of an individual developer. Dear PVS-Studio, please check it.

// PVS-Studio Static Code Analyzer for C, C++, C#, and Java: http://www.viva64.com

By the way, this type of free licenses can be actually used not only in closed, but in open projects as well.

Comments for free open source projects:

// This is an open source non-commercial project. Dear PVS-Studio, please check it.

// PVS-Studio Static Code Analyzer for C, C++, C#, and Java: http://www.viva64.com

You need to go through two steps to start using PVS-Studio code analyzer for free.

Step 1. If you are using PVS-Studio as a Visual Studio plugin or you are using the "C and C++ Compiler Monitoring UI" (Standalone.exe) utility, enter the following license key:

Name: PVS-Studio Free

Key: FREE-FREE-FREE-FREE

If you are using PVS-Studio for Linux/macOS, use the following command:

pvs-studio-analyzer credentials PVS-Studio Free FREE-FREE-FREE-FREE

Note. Previously, a comment was enough to activate the free license for the Linux version. Now you also need to enter this special key, because without it, some scenarios for using the analyzer turned out to be inconvenient. Read more.

Step 2. You have to write two lines of comments at the beginning of each file. Make edits in all the compilable files of your project. We mean files with the extensions c, cc, cpp, cs, java and others. You don't have to change header files.

If your project has a large number of files, then you can use the 'how-to-use-pvs-studio-free' utility. You will need to specify the comment to insert and the directory with the code. After that the utility will recursively traverse all the files in the folder and subfolders, adding necessary comments to the code. You can download the utility (together with the source code) here: how-to-use-pvs-studio-free.

You can read about some additional details of this type of free licensing in the article "How to use PVS-Studio for Free". Please, be sure to read this article in case if you decided to choose the above option of free usage.

Security experts

Public security experts, specialized in searching for vulnerabilities, can write to us and get a free license for the PVS-Studio analyzer.

Everyone who wishes to get the license and support will have to confirm, that they specialize in security issues and conduct public activities, for example, write articles. We'll specify these things by mail.

Read more: "Handing out PVS-Studio Analyzer Licenses to Security Experts".

Microsoft MVP

The first people, whom we offered free licenses, were Microsoft MVPs. The post "Free PVS-Studio licenses for MVPs" appeared back in 2011. Hardly anyone remembers about this now, but this offer still stands.

If you are a Microsoft MVP, email us and specify your MVP profile on Microsoft's website. We will send you the license, which allows using PVS-Studio for 12 months without any restrictions, including usage for commercial purposes. After it expires, it will be possible to extend the license.

Conclusion

We probably need to remind about the main scenario.

  • A trial analyzer version is available on the site. Here is the page where you can download PVS-Studio and get a trial key.
  • A company can purchase the license and get quick and proficient support. Your developers will communicate directly with our developers from the PVS-Studio team. No middlemen, support staff and so on. Only direct communication with programmers and me (technical director). Example.

Thanks for your attention and we wish you to prevent as many errors as possible by using PVS-Studio. Just don't forget that the point of static code methodology is in its regular use, not in single checks. Good luck!

Popular related articles
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: 10.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…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: 11.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…
PVS-Studio ROI

Date: 01.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 Evil within the Comparison Functions

Date: 05.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…
Free PVS-Studio for those who develops open source projects

Date: 12.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…
The Ultimate Question of Programming, Refactoring, and Everything

Date: 04.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…
Appreciate Static Code Analysis!

Date: 10.16.2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: 07.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: 05.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: 03.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…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 →
Accept