# Updated PVS\-Studio diagnostic count graph

We regularly update the history of PVS\-Studio's new features and improvements at the product website\. But the text format isn't very informative in visualizing the development intensity\. That's why we decided to write a small post and include a more informative diagnostic count graph\.

![0724_PVS_Studio_rules/image1.png](https://import.viva64.com/docx/blog/0724_PVS_Studio_rules/image1.png)

We already published a similar post, "[PVS\-Studio graph of diagnostic abilities development](https://pvs-studio.com/en/blog/posts/0632/)", about a year ago\. But since the updated graph looks so nice, why not publish it one more time? :\)

Of course, new diagnostics aren't the only new feature being added to our product\. For instance, we work a lot on integrating PVS\-Studio with various systems such as [Azure DevOps](https://pvs-studio.com/en/blog/posts/csharp/0670/), [Travis CI](https://pvs-studio.com/en/blog/posts/cpp/0636/), [CircleCI](https://pvs-studio.com/en/blog/posts/cpp/0676/), [GitLab CI/CD](https://pvs-studio.com/en/blog/posts/cpp/0686/), [Jenkins](https://pvs-studio.com/en/docs/manual/0048/), [SonarQube](https://pvs-studio.com/en/docs/manual/0037/), and so on\. It's just that the graph is the best form for visualizing the rapid development tendency\.

![0724_PVS_Studio_rules/image2.png](https://import.viva64.com/docx/blog/0724_PVS_Studio_rules/image2.png)

This graph shows the number of diagnostics added to PVS\-Studio over time\. Detailed information about new features can be found in the "[Version History](https://pvs-studio.com/en/docs/manual/0010/)" section\.

So far we've managed to maintain quite a rapid and steady growth, which also makes us a force of progress by [stimulating](https://pvs-studio.com/en/blog/posts/0659/) other tools to keep pace :\)\.

Thanks for reading\. If you'd like to take a look at figures rather than graphs, welcome to "[PVS\-Studio ROI](https://pvs-studio.com/en/blog/posts/0606/)" :\)\.