Static analysis of C/C++ code. Checks for: memory leaks, mismatching allocation-deallocation, buffer overrun, and many more. The goal is 0% false positives. See http://cppcheck.sourceforge.net for more information.
License
GNU General Public License version 3.0 (GPLv3)Follow cppcheck
You Might Also Like
DataHub is the leading open-source data catalog helping teams discover, understand, and govern their data assets. Icon
DataHub is the leading open-source data catalog helping teams discover, understand, and govern their data assets.
Modern Data Catalog and Metadata Platform
Built on an open source foundation with a thriving community of 13,000+ members, DataHub gives you unmatched flexibility to customize and extend without vendor lock-in. DataHub Cloud is a modern metadata platform with REST and GraphQL APIs that optimize performance for complex queries, essential for AI-ready data management and ML lifecycle support.
Learn More
Rate This Project
Login To Rate This Project
User Ratings
★★★★★
★★★★
★★★
★★
★
68
2
4
1
2
ease
1 of 5
2 of 5
3 of 5
4 of 5
5 of 5
4 / 5
features
1 of 5
2 of 5
3 of 5
4 of 5
5 of 5
4 / 5
design
1 of 5
2 of 5
3 of 5
4 of 5
5 of 5
4 / 5
support
1 of 5
2 of 5
3 of 5
4 of 5
5 of 5
4 / 5
User Reviews
-
german-mso Posted 2024年05月10日It gets the job done.
-
perijah Posted 2023年05月08日Great tool. Compared to other (paid) tools, the ease of use of Cppcheck is remarkable. It does find issues if you configure it correctly. Via Cmake I was able to custom targets to my solution that check the project in the way I want it to. It's very fast. The Misra2012 addon finds a lot of issues that Polyspace doesn't, but the same is true the other way around. I think the 2 tools complement each other nicely. The support in the discussion forum is greatly appreciated and makes the tool better. Regards
-
h3nrikoo Posted 2022年02月14日Great open source tool with good support!
-
reddyquan Posted 2020年11月13日Bug
-
smbika Edited 2020年08月21日Looks good so far - I was in error in my assessment as to building the tool. I was using 2010 and not 2019. 2019 worked fine. Also, I noticed an installer too. So my original comment was a knee-jerk. Apologies.