Support of developers of such projects would require significant work from our team. We also reserve the right to withdraw a particular key without explanation.Īs mentioned earlier, the ability to use free license does not apply to projects mirrors, such as Clang, Chromium, KDE and so on. However, if we feel that something has gone wrong, we reserve the right to change its terms or to stop it. The action of providing free licenses is timeless. To inform us of obvious bugs, as usually, please, write to our support. Let's discuss there questions, related to analyzer work and so on. We'd like to note that Stack Overflow isn't s bug-tracker. The article " How to use PVS-Studio for Free" (see the section "Update: Support") describes this condition in more detail. Support for free users is carried out in replies on Stack Overflow. Moreover, the previous version allows you to use the analyzer even for closed projects. For example, students can use it to test their projects without having to upload them on GitHub/GitLab/Bitbucket. The old version of free analyzer usage with adding code comments remains in force. Free license doesn't extend to projects' mirrors. The key is individual and can only be used to check open source projects published on GitHub/GitLab/Bitbucket. Upon expiration of the license, you can get a new license key in the same way. Enter the link to your GitHub/GitLab/Bitbucket profile.Enter the e-mail, where you will be sent a license key.Note: this licensing method applies only to non-commercial projects.Įveryone who wishes, can get a free license for 1 year. Authors of these projects don't have to add any comments. In response to requests, we decided to make PVS-Studio usage possible for those who takes part in development of open source projects, posted on GitHub, GitLab or Bitbucket. The article " How to use PVS-Studio for Free" tells in more detail about this type of licensing. The only condition is having a special kind of comments in your code. That's why in 2016 we offered a free version of PVS-Studio licensing. Our team is physically not able to regularly check thousands of open source projects. Even though due to our publications more than 10000 errors have been fixed in open source projects, it is obviously not enough. We help to make code of open source software better and more reliable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |