To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (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.

Your Java analyzer is half-done: let's …

Your Java analyzer is half-done: let's wait for a couple of years

Feb 06 2019

Recently we have released PVS-Studio 7.00, the key innovation of which was the Java analyzer. The release has proved to be successful, as a big wave of beta-testing had come before that. Some of our clients who are using C++ or C# analyzers started to implement a check of Java code in their projects almost from the beta-stage. They were sending us interesting errors, which have been found in their code, as it usually happens during the first launches. There were also requests to finalize some integrations. However, some potential users were writing the following things: "Your analyzer will certainly be good. In a couple of years. When you debug it. In the meantime, we will not download and check it out". For me it sounds so strange and irrational that I decided to write this post and answer by giving a link in future.


So, at first glance, the idea to wait for a couple of years, while the product regains its feet, seems logical. Do I want to get money so much that I even make up an article-disclaimer? :-). Money is not the issue here. It's a bit insulting for me that our PVS-Studio product is used as a reason NOT to do something.

Well, let's start from the beginning. Any code analyzer includes two important components.

The first one is directly code analysis technologies. This includes Data Flow Analysis, Symbolic Execution, Type Inference, and others. Here you can read in details about technologies of code analysis, which are used in PVS-Studio. Why I am giving a link to our article posted two years ago, when nothing had been resolved about the Java analyzer? Firstly, because these technologies don't depend on the target language. Secondly, our Java analyzer uses the code from the C++ analyzer, with the help of which these technologies are implemented.

The second component is infrastructural tools. No matter how wonderful the code analysis technologies are, without auxiliary components a tool turns out to be stupid. The report has to be saved in a convenient form (let alone a convenient format), sent to colleagues at nights. When introducing an analyzer into an existing project one has to do something with old warnings. Finally, ways of introducing into the development process can be different. So, for more than 10 years we have learned to understand infrastructural issues related to code analysis very well. That's why we don't need to spend time on more research here.

Why did I write all this? If you'd like to change nothing in your development process for a couple of years and you don't want to use static analysis (no matter ours or not) then, sure, you can comfort yourself thinking that the "product is raw". Nevertheless, it has nothing to do with reality.

So, just download PVS-Studio and find bugs in your project. Even the time spent on trial, will pay off many times.

Popular related articles
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…
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…
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…
Appreciate Static Code Analysis!

Date: Oct 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…
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…
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…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
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…
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…

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 →