diff --git a/demo/index.php b/demo/index.php index 1f69217..1a95927 100644 --- a/demo/index.php +++ b/demo/index.php @@ -34,12 +34,12 @@ function checkCodeLength() {
diff --git a/demo/report/index.php b/demo/report/index.php index 21d0636..d618731 100644 --- a/demo/report/index.php +++ b/demo/report/index.php @@ -89,10 +89,10 @@ function cut_string($string, $length = 1024) {
diff --git a/devinfo/index.php b/devinfo/index.php index 58bcfc0..b8766a0 100644 --- a/devinfo/index.php +++ b/devinfo/index.php @@ -7,11 +7,11 @@ + href="https://github.com/cppcheck-opensource/cppcheck/commits/main.atom" /> + href="https://trac.cppcheck.net/timeline?changeset=on&ticket=on&milestone=on&wiki=on&max=50&daysback=90&format=rss" /> + href="https://sourceforge.net/p/cppcheck/discussion/feed" /> @@ -36,12 +36,12 @@
@@ -49,7 +49,7 @@
diff --git a/index.php b/index.php index e2bcdcf..9b84d59 100644 --- a/index.php +++ b/index.php @@ -13,7 +13,7 @@ + href="https://sourceforge.net/p/cppcheck/news/feed" /> @@ -50,7 +50,7 @@

-Cppcheck is a static analysis tool +Cppcheck is a static analysis tool for C/C++ code. It provides unique code analysis to detect bugs and focuses on detecting undefined behaviour and dangerous coding constructs. The goal is to have very few false positives. Cppcheck is designed to be able to analyze your C/C++ code even if it has non-standard syntax (common in embedded projects). @@ -68,15 +68,15 @@ Windows 64-bit (No XP support) - Installer + Installer Source code (.zip) - Archive + Archive Source code (.tar.gz) - Archive + Archive @@ -108,7 +108,7 @@ { int buf[10]; if (x == 1000) - buf[x] = 0; // <- ERROR + buf[x] = 0; // <- ERROR }

Most tools can determine that the array index will be 1000 and there will be overflow.

@@ -118,7 +118,7 @@
void foo(int x)
 {
     int buf[10];
-    buf[x] = 0; // <- ERROR
+    buf[x] = 0; // <- ERROR
     if (x == 1000) {}
 }
@@ -186,26 +186,26 @@

Security experts recommend that static analysis is used. And using several tools is the best approach from a security perspective.

Coding standards

- - - - - - - - - - - - - - - +
Coding standard Open Source  Premium 
 Misra C 2012 - original rules  Partial Yes
 Misra C 2012 - amendment #1  Partial Yes
 Misra C 2012 - amendment #2  Partial Yes
 Misra C 2012 - amendment #3  Yes
 Misra C 2012 - amendment #4  Yes
 Misra C 2012 - Compliance report  Yes
 Misra C 2012 - Rule texts  User provided Yes
 Misra C 2023  Yes
 Misra C++ 2008  Yes
 Misra C++ 2023  Yes
 Cert C  Yes
 Cert C++  Yes
 Autosar  Partial
+ + + + + + + + + + + + + +
Coding standardOpen SourcePremium
Misra C 2012 - original rulesPartialYes
Misra C 2012 - amendment #1PartialYes
Misra C 2012 - amendment #2PartialYes
Misra C 2012 - amendment #3Yes
Misra C 2012 - amendment #4Yes
Misra C 2012 - Compliance reportYes
Misra C 2012 - Rule textsUser providedYes
Misra C 2023Yes
Misra C++ 2008Yes
Misra C++ 2023Yes
Cert CYes
Cert C++Yes
AutosarPartial

All checks

-

For a list of all checks in Cppcheck see: http://sourceforge.net/p/cppcheck/wiki/ListOfChecks.

+

For a list of all checks in Cppcheck see: https://sourceforge.net/p/cppcheck/wiki/ListOfChecks.

Clients and plugins

Cppcheck is integrated with many popular development tools. For instance:

@@ -213,18 +213,18 @@
  • Buildbot - integrated
  • CLion - Cppcheck plugin
  • Code::Blocks - integrated
  • -
  • CodeDX (software assurance tool) - integrated
  • +
  • CodeDX (software assurance tool) - integrated
  • CodeLite - integrated
  • -
  • CppDepend 5 - integrated
  • +
  • CppDepend 5 - integrated
  • Eclipse - Cppcheclipse
  • -
  • gedit - gedit plugin
  • -
  • github - Codacy, Codety and SoftaCheck
  • -
  • Hudson - Cppcheck Plugin
  • -
  • Jenkins - Cppcheck Plugin
  • +
  • gedit - gedit plugin
  • +
  • github - Codacy, Codety and SoftaCheck
  • +
  • Hudson - Cppcheck Plugin
  • +
  • Jenkins - Cppcheck Plugin
  • KDevelop - integrated since v5.1
  • -
  • Mercurial (Linux) - pre-commit hook - Check for new errors on commit (requires interactive terminal)
  • +
  • Mercurial (Linux) - pre-commit hook - Check for new errors on commit (requires interactive terminal)
  • QtCreator - Qt Project Tool (qpt)
  • -
  • Tortoise SVN - Adding a pre-commit hook script
  • +
  • Tortoise SVN - Adding a pre-commit hook script
  • Vim - Vim Compiler
  • Visual Studio - Visual Studio plugin
  • VScode - VScode plugin
  • @@ -258,11 +258,11 @@

    Documentation

    You can read the manual or download some -articles.

    +articles.

    Support

    @@ -281,10 +281,10 @@
    Testing
    Pick a project and test its source with the latest version of Cppcheck. - Submit tickets to Trac about the + Submit tickets to Trac about the issues you find in Cppcheck.
    Developing
    -
    Pick a ticket from Trac, +
    Pick a ticket from Trac, write a test case for it (and write a comment to the ticket for which that test case has been created). Alternatively, pick a test case that fails and try to fix it. Make a patch and submit it to Trac either inline, if it is @@ -294,7 +294,7 @@ have, the more people we have testing and the better we can become.
    Design
    Come up with some new good checks, and create tickets in - the Trac instance + the Trac instance about them.
    Integration
    Write a plugin for your favorite IDE or create a package for your diff --git a/misra.php b/misra.php index 0ddb1a2..ed17c69 100644 --- a/misra.php +++ b/misra.php @@ -8,7 +8,7 @@ - + diff --git a/package.json b/package.json index 2162515..e4347cd 100644 --- a/package.json +++ b/package.json @@ -3,13 +3,13 @@ "version": "0.2.0", "author": "XhmikosR (https://github.com/XhmikosR)", "description": "The dependencies to build cppcheck's website", - "homepage": "https://github.com/danmar/cppcheck", + "homepage": "https://github.com/cppcheck-opensource/cppcheck", "repository": { "type": "git", - "url": "https://github.com/danmar/cppcheck.git" + "url": "https://github.com/cppcheck-opensource/cppcheck.git" }, "bugs": { - "url": "http://sourceforge.net/apps/trac/cppcheck/wiki" + "url": "https://sourceforge.net/apps/trac/cppcheck/wiki" }, "license": "GPLv3", "main": "make.js",