Executive summary
ambionics/phpggc falls short of our standard for production, in part because three passwords or keys sit in the current code. It scores 32.9 out of 100 and is rated Weak, and nine of its ten critical findings are security problems.
Production Readiness, at 4.6, is the weakest lens and counts most in the score. The best first steps are replacing the three exposed passwords or keys and switching the old ones off and adding tests for untested code, each worth about 27.3 points. Raising Production Readiness to 70 would lift the score to about 56.8.
Three passwords or keys in the code and three in the code's history are open to anyone who can read the repository. Three settings leave the servers or containers unsafe, and one part of the code is no longer understood by anyone working on it. Replacing each exposed password or key, correcting the unsafe settings and having someone learn the forgotten files would close these risks.
The product code is 12,324 lines, about €10,000 to rebuild.
If Production Readiness rose from 4.6 to 70, the lowest score rated Strong, the score would rise from 32.9 to about 56.8.
New since the last survey: 8 findings
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) gadgetchains/Sulu/RCE/1/chain.php
- Code Duplication · Edited copy of a member (6 corresponding lines) gadgetchains/WordPress/Guzzle/RCE/1/chain.php
- Code Duplication · Edited copy of a member (10 corresponding lines) gadgetchains/OpenCart/FW/2/chain.php
- Code Duplication · Edited copy of a member (9 corresponding lines) gadgetchains/OpenCart/FW/1/chain.php
- Code Duplication · Edited copy of a member (4 corresponding lines) gadgetchains/Laravel/RCE/16/gadgets.php
- Code Duplication · Edited copy of a member (7 corresponding lines) gadgetchains/Symfony/RCE/10/chain.php
- Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) gadgetchains/Symfony/RCE/13/chain.php
- Code Coverage · Low coverage: test-gc-compatibility.py test-gc-compatibility.py
Fixed since the last survey: 1 finding
- Code Coverage · No automated tests
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,500 to €18,000, for 58 to 184 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 33. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,324 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Bitrix.Main | 2 Doctrine.Common.Persistence.Mapping | 3 Doctrine.Common.Persistence.Mapping.Driver | 4 Doctrine.DBAL | 5 PHPGGC.GadgetChain | 6 think.model | 7 Bitrix.Main.ORM.Data | 8 Doctrine.ORM | 9 Doctrine.ORM.Mapping | 10 Doctrine.ORM.Mapping.Driver | 11 GadgetChain.Dompdf | 12 GadgetChain.Drupal.PsySH | 13 GadgetChain.Grav | 14 GadgetChain.Joomla | 15 GadgetChain.Kohana | 16 GadgetChain.Laminas | 17 GadgetChain.Magento | 18 GadgetChain.Magento2 | 19 GadgetChain.PHPCSFixer | 20 GadgetChain.PHPExcel | 21 GadgetChain.PHPWord | 22 PHPGGC.GadgetChain.RCE | 23 PHPGGC.GadgetChain.SQLI | 24 GadgetChain.Bitrix | 25 GadgetChain.CakePHP | 26 GadgetChain.CodeIgniter4 | 27 GadgetChain.Doctrine | 28 GadgetChain.Drupal | 29 GadgetChain.Drupal7 | 30 GadgetChain.Drupal9 | 31 GadgetChain.Guzzle | 32 GadgetChain.Horde | 33 GadgetChain.Laravel | 34 GadgetChain.MediaWiki | 35 GadgetChain.Monolog | 36 GadgetChain.OpenCart | 37 GadgetChain.PHPSecLib | 38 GadgetChain.Symfony | 39 GadgetChain.ThinkPHP | 40 GadgetChain.ZendFramework |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Bitrix.Main | ||||||||||||||||||||||||||||||||||||||||
| 2 Doctrine.Common.Persistence.Mapping | ||||||||||||||||||||||||||||||||||||||||
| 3 Doctrine.Common.Persistence.Mapping.Driver | ||||||||||||||||||||||||||||||||||||||||
| 4 Doctrine.DBAL | ||||||||||||||||||||||||||||||||||||||||
| 5 PHPGGC.GadgetChain | ||||||||||||||||||||||||||||||||||||||||
| 6 think.model | ||||||||||||||||||||||||||||||||||||||||
| 7 Bitrix.Main.ORM.Data | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Doctrine.ORM | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Doctrine.ORM.Mapping | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Doctrine.ORM.Mapping.Driver | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 GadgetChain.Dompdf | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 GadgetChain.Drupal.PsySH | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 GadgetChain.Grav | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 GadgetChain.Joomla | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 GadgetChain.Kohana | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 GadgetChain.Laminas | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 GadgetChain.Magento | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 GadgetChain.Magento2 | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 GadgetChain.PHPCSFixer | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 GadgetChain.PHPExcel | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 GadgetChain.PHPWord | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 PHPGGC.GadgetChain.RCE | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 PHPGGC.GadgetChain.SQLI | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 GadgetChain.Bitrix | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 GadgetChain.CakePHP | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 GadgetChain.CodeIgniter4 | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 27 GadgetChain.Doctrine | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 GadgetChain.Drupal | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 GadgetChain.Drupal7 | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 GadgetChain.Drupal9 | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 GadgetChain.Guzzle | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 GadgetChain.Horde | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 GadgetChain.Laravel | 1 | 22 | ||||||||||||||||||||||||||||||||||||||
| 34 GadgetChain.MediaWiki | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 GadgetChain.Monolog | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 36 GadgetChain.OpenCart | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 GadgetChain.PHPSecLib | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 GadgetChain.Symfony | 3 | 16 | ||||||||||||||||||||||||||||||||||||||
| 39 GadgetChain.ThinkPHP | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 40 GadgetChain.ZendFramework | 1 | 5 |
7→1 Bitrix.Main.ORM.Data uses Bitrix.Main✕
- Connections
- 1 pair of types, where a type in Bitrix.Main.ORM.Data uses a type in Bitrix.Main.
- The types involved
Bitrix.Main.ORM.Data.Result→Bitrix.Main.Result
- Direction
- Bitrix.Main.ORM.Data uses Bitrix.Main, so a change to Bitrix.Main can break Bitrix.Main.ORM.Data, while a change to Bitrix.Main.ORM.Data can't break Bitrix.Main.
- Position
- Below the diagonal: Bitrix.Main.ORM.Data uses a module listed above it, which is the healthy direction.
8→4 Doctrine.ORM uses Doctrine.DBAL✕
- Connections
- 1 pair of types, where a type in Doctrine.ORM uses a type in Doctrine.DBAL.
- The types involved
Doctrine.ORM.Configuration→Doctrine.DBAL.Configuration
- Direction
- Doctrine.ORM uses Doctrine.DBAL, so a change to Doctrine.DBAL can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.DBAL.
- Position
- Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
9→2 Doctrine.ORM.Mapping uses Doctrine.Common.Persistence.Mapping✕
- Connections
- 1 pair of types, where a type in Doctrine.ORM.Mapping uses a type in Doctrine.Common.Persistence.Mapping.
- The types involved
Doctrine.ORM.Mapping.ClassMetadataFactory→Doctrine.Common.Persistence.Mapping.AbstractClassMetadataFactory
- Direction
- Doctrine.ORM.Mapping uses Doctrine.Common.Persistence.Mapping, so a change to Doctrine.Common.Persistence.Mapping can break Doctrine.ORM.Mapping, while a change to Doctrine.ORM.Mapping can't break Doctrine.Common.Persistence.Mapping.
- Position
- Below the diagonal: Doctrine.ORM.Mapping uses a module listed above it, which is the healthy direction.
10→3 Doctrine.ORM.Mapping.Driver uses Doctrine.Common.Persistence.Mapping.Driver✕
- Connections
- 1 pair of types, where a type in Doctrine.ORM.Mapping.Driver uses a type in Doctrine.Common.Persistence.Mapping.Driver.
- The types involved
Doctrine.ORM.Mapping.Driver.AnnotationDriver→Doctrine.Common.Persistence.Mapping.Driver.AnnotationDriver
- Direction
- Doctrine.ORM.Mapping.Driver uses Doctrine.Common.Persistence.Mapping.Driver, so a change to Doctrine.Common.Persistence.Mapping.Driver can break Doctrine.ORM.Mapping.Driver, while a change to Doctrine.ORM.Mapping.Driver can't break Doctrine.Common.Persistence.Mapping.Driver.
- Position
- Below the diagonal: Doctrine.ORM.Mapping.Driver uses a module listed above it, which is the healthy direction.
11→5 GadgetChain.Dompdf uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Dompdf uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Dompdf.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.Dompdf.FD2→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.Dompdf uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Dompdf, while a change to GadgetChain.Dompdf can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Dompdf uses a module listed above it, which is the healthy direction.
12→5 GadgetChain.Drupal.PsySH uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.Drupal.PsySH uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Drupal.PsySH.INFO1→PHPGGC.GadgetChain.PHPInfo
- Direction
- GadgetChain.Drupal.PsySH uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Drupal.PsySH, while a change to GadgetChain.Drupal.PsySH can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Drupal.PsySH uses a module listed above it, which is the healthy direction.
13→5 GadgetChain.Grav uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.Grav uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Grav.FD1→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.Grav uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Grav, while a change to GadgetChain.Grav can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Grav uses a module listed above it, which is the healthy direction.
14→5 GadgetChain.Joomla uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.Joomla uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Joomla.FW1→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.Joomla uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Joomla, while a change to GadgetChain.Joomla can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Joomla uses a module listed above it, which is the healthy direction.
15→5 GadgetChain.Kohana uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.Kohana uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Kohana.FR1→PHPGGC.GadgetChain.FileRead
- Direction
- GadgetChain.Kohana uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Kohana, while a change to GadgetChain.Kohana can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Kohana uses a module listed above it, which is the healthy direction.
16→5 GadgetChain.Laminas uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Laminas uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Laminas.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.Laminas.FW1→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.Laminas uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Laminas, while a change to GadgetChain.Laminas can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Laminas uses a module listed above it, which is the healthy direction.
17→5 GadgetChain.Magento uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Magento uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Magento.FW1→PHPGGC.GadgetChain.FileWriteGadgetChain.Magento.SQLI1→PHPGGC.GadgetChain.SqlInjection
- Direction
- GadgetChain.Magento uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Magento, while a change to GadgetChain.Magento can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Magento uses a module listed above it, which is the healthy direction.
18→5 GadgetChain.Magento2 uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Magento2 uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Magento2.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.Magento2.FD2→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.Magento2 uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Magento2, while a change to GadgetChain.Magento2 can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Magento2 uses a module listed above it, which is the healthy direction.
19→5 GadgetChain.PHPCSFixer uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.PHPCSFixer uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.PHPCSFixer.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.PHPCSFixer.FD2→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.PHPCSFixer uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.PHPCSFixer, while a change to GadgetChain.PHPCSFixer can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.PHPCSFixer uses a module listed above it, which is the healthy direction.
20→5 GadgetChain.PHPExcel uses PHPGGC.GadgetChain✕
- Connections
- 4 pairs of types, where a type in GadgetChain.PHPExcel uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.PHPExcel.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.PHPExcel.FD2→PHPGGC.GadgetChain.FileDeleteGadgetChain.PHPExcel.FD3→PHPGGC.GadgetChain.FileDeleteGadgetChain.PHPExcel.FD4→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.PHPExcel uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.PHPExcel, while a change to GadgetChain.PHPExcel can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.PHPExcel uses a module listed above it, which is the healthy direction.
21→5 GadgetChain.PHPWord uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.PHPWord uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.PHPWord.FD1→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.PHPWord uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.PHPWord, while a change to GadgetChain.PHPWord can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.PHPWord uses a module listed above it, which is the healthy direction.
22→5 PHPGGC.GadgetChain.RCE uses PHPGGC.GadgetChain✕
- Connections
- 3 pairs of types, where a type in PHPGGC.GadgetChain.RCE uses a type in PHPGGC.GadgetChain.
- The types involved
PHPGGC.GadgetChain.RCE.Command→PHPGGC.GadgetChain.RCEPHPGGC.GadgetChain.RCE.FunctionCall→PHPGGC.GadgetChain.RCEPHPGGC.GadgetChain.RCE.PHPCode→PHPGGC.GadgetChain.RCE
- Direction
- PHPGGC.GadgetChain.RCE uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break PHPGGC.GadgetChain.RCE, while a change to PHPGGC.GadgetChain.RCE can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: PHPGGC.GadgetChain.RCE uses a module listed above it, which is the healthy direction.
23→5 PHPGGC.GadgetChain.SQLI uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in PHPGGC.GadgetChain.SQLI uses a type in PHPGGC.GadgetChain.
- The types involved
PHPGGC.GadgetChain.SQLI.MySQLAuthenticatedSQLI→PHPGGC.GadgetChain.SqlInjection
- Direction
- PHPGGC.GadgetChain.SQLI uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break PHPGGC.GadgetChain.SQLI, while a change to PHPGGC.GadgetChain.SQLI can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: PHPGGC.GadgetChain.SQLI uses a module listed above it, which is the healthy direction.
24→22 GadgetChain.Bitrix uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.Bitrix uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Bitrix.RCE1→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Bitrix uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Bitrix, while a change to GadgetChain.Bitrix can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Bitrix uses a module listed above it, which is the healthy direction.
25→22 GadgetChain.CakePHP uses PHPGGC.GadgetChain.RCE✕
- Connections
- 2 pairs of types, where a type in GadgetChain.CakePHP uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.CakePHP.RCE1→PHPGGC.GadgetChain.RCE.CommandGadgetChain.CakePHP.RCE2→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.CakePHP uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.CakePHP, while a change to GadgetChain.CakePHP can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.CakePHP uses a module listed above it, which is the healthy direction.
26→5 GadgetChain.CodeIgniter4 uses PHPGGC.GadgetChain✕
- Connections
- 3 pairs of types, where a type in GadgetChain.CodeIgniter4 uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.CodeIgniter4.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.CodeIgniter4.FD2→PHPGGC.GadgetChain.FileDeleteGadgetChain.CodeIgniter4.FR1→PHPGGC.GadgetChain.FileRead
- Direction
- GadgetChain.CodeIgniter4 uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.CodeIgniter4, while a change to GadgetChain.CodeIgniter4 can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.CodeIgniter4 uses a module listed above it, which is the healthy direction.
26→22 GadgetChain.CodeIgniter4 uses PHPGGC.GadgetChain.RCE✕
- Connections
- 6 pairs of types, where a type in GadgetChain.CodeIgniter4 uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.CodeIgniter4.RCE1→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.CodeIgniter4.RCE2→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.CodeIgniter4.RCE3→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.CodeIgniter4.RCE4→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.CodeIgniter4.RCE5→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.CodeIgniter4.RCE6→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.CodeIgniter4 uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.CodeIgniter4, while a change to GadgetChain.CodeIgniter4 can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.CodeIgniter4 uses a module listed above it, which is the healthy direction.
27→5 GadgetChain.Doctrine uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Doctrine uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Doctrine.FW1→PHPGGC.GadgetChain.FileWriteGadgetChain.Doctrine.FW2→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.Doctrine uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Doctrine, while a change to GadgetChain.Doctrine can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Doctrine uses a module listed above it, which is the healthy direction.
27→22 GadgetChain.Doctrine uses PHPGGC.GadgetChain.RCE✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Doctrine uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Doctrine.RCE1→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.Doctrine.RCE2→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Doctrine uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Doctrine, while a change to GadgetChain.Doctrine can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Doctrine uses a module listed above it, which is the healthy direction.
28→5 GadgetChain.Drupal uses PHPGGC.GadgetChain✕
- Connections
- 4 pairs of types, where a type in GadgetChain.Drupal uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Drupal.AT1→PHPGGC.GadgetChain.AccountTakeoverGadgetChain.Drupal.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.Drupal.SSRF1→PHPGGC.GadgetChain.SSRFGadgetChain.Drupal.XXE1→PHPGGC.GadgetChain.XXE
- Direction
- GadgetChain.Drupal uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Drupal, while a change to GadgetChain.Drupal can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Drupal uses a module listed above it, which is the healthy direction.
28→23 GadgetChain.Drupal uses PHPGGC.GadgetChain.SQLI✕
- Connections
- 1 pair of types, where a type in GadgetChain.Drupal uses a type in PHPGGC.GadgetChain.SQLI.
- The types involved
GadgetChain.Drupal.SQLI1→PHPGGC.GadgetChain.SQLI.MySQLAuthenticatedSQLI
- Direction
- GadgetChain.Drupal uses PHPGGC.GadgetChain.SQLI, so a change to PHPGGC.GadgetChain.SQLI can break GadgetChain.Drupal, while a change to GadgetChain.Drupal can't break PHPGGC.GadgetChain.SQLI.
- Position
- Below the diagonal: GadgetChain.Drupal uses a module listed above it, which is the healthy direction.
29→5 GadgetChain.Drupal7 uses PHPGGC.GadgetChain✕
- Connections
- 3 pairs of types, where a type in GadgetChain.Drupal7 uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Drupal7.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.Drupal7.SQLI1→PHPGGC.GadgetChain.SqlInjectionGadgetChain.Drupal7.SSRF1→PHPGGC.GadgetChain.SSRF
- Direction
- GadgetChain.Drupal7 uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Drupal7, while a change to GadgetChain.Drupal7 can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Drupal7 uses a module listed above it, which is the healthy direction.
29→22 GadgetChain.Drupal7 uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.Drupal7 uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Drupal7.RCE1→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Drupal7 uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Drupal7, while a change to GadgetChain.Drupal7 can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Drupal7 uses a module listed above it, which is the healthy direction.
30→22 GadgetChain.Drupal9 uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.Drupal9 uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Drupal9.RCE1→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Drupal9 uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Drupal9, while a change to GadgetChain.Drupal9 can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Drupal9 uses a module listed above it, which is the healthy direction.
31→5 GadgetChain.Guzzle uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.Guzzle uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Guzzle.FW1→PHPGGC.GadgetChain.FileWriteGadgetChain.Guzzle.INFO1→PHPGGC.GadgetChain.PHPInfo
- Direction
- GadgetChain.Guzzle uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Guzzle, while a change to GadgetChain.Guzzle can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Guzzle uses a module listed above it, which is the healthy direction.
31→22 GadgetChain.Guzzle uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.Guzzle uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Guzzle.RCE1→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Guzzle uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Guzzle, while a change to GadgetChain.Guzzle can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Guzzle uses a module listed above it, which is the healthy direction.
32→22 GadgetChain.Horde uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.Horde uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Horde.RCE1→PHPGGC.GadgetChain.RCE.PHPCode
- Direction
- GadgetChain.Horde uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Horde, while a change to GadgetChain.Horde can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Horde uses a module listed above it, which is the healthy direction.
33→5 GadgetChain.Laravel uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.Laravel uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Laravel.FD1→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.Laravel uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Laravel, while a change to GadgetChain.Laravel can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Laravel uses a module listed above it, which is the healthy direction.
33→22 GadgetChain.Laravel uses PHPGGC.GadgetChain.RCE✕
- Connections
- 22 pairs of types, where a type in GadgetChain.Laravel uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Laravel.RCE1→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE10→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE11→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE12→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE13→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE14→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE15→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE16→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE17→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE18→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.Laravel.RCE19→PHPGGC.GadgetChain.RCE.CommandGadgetChain.Laravel.RCE2→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE20→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE21→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE22→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE3→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE4→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE5→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.Laravel.RCE6→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.Laravel.RCE7→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE8→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Laravel.RCE9→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Laravel uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Laravel, while a change to GadgetChain.Laravel can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Laravel uses a module listed above it, which is the healthy direction.
34→5 GadgetChain.MediaWiki uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.MediaWiki uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.MediaWiki.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.MediaWiki.FW1→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.MediaWiki uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.MediaWiki, while a change to GadgetChain.MediaWiki can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.MediaWiki uses a module listed above it, which is the healthy direction.
34→22 GadgetChain.MediaWiki uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.MediaWiki uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.MediaWiki.RCE1→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.MediaWiki uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.MediaWiki, while a change to GadgetChain.MediaWiki can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.MediaWiki uses a module listed above it, which is the healthy direction.
35→5 GadgetChain.Monolog uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.Monolog uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Monolog.FW1→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.Monolog uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Monolog, while a change to GadgetChain.Monolog can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Monolog uses a module listed above it, which is the healthy direction.
35→22 GadgetChain.Monolog uses PHPGGC.GadgetChain.RCE✕
- Connections
- 9 pairs of types, where a type in GadgetChain.Monolog uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Monolog.RCE1→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE2→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE3→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE4→PHPGGC.GadgetChain.RCE.CommandGadgetChain.Monolog.RCE5→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE6→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE7→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE8→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Monolog.RCE9→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Monolog uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Monolog, while a change to GadgetChain.Monolog can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Monolog uses a module listed above it, which is the healthy direction.
36→5 GadgetChain.OpenCart uses PHPGGC.GadgetChain✕
- Connections
- 3 pairs of types, where a type in GadgetChain.OpenCart uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.OpenCart.FW1→PHPGGC.GadgetChain.FileWriteGadgetChain.OpenCart.FW2→PHPGGC.GadgetChain.FileWriteGadgetChain.OpenCart.FW3→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.OpenCart uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.OpenCart, while a change to GadgetChain.OpenCart can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.OpenCart uses a module listed above it, which is the healthy direction.
36→22 GadgetChain.OpenCart uses PHPGGC.GadgetChain.RCE✕
- Connections
- 2 pairs of types, where a type in GadgetChain.OpenCart uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.OpenCart.RCE1→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.OpenCart.RCE2→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.OpenCart uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.OpenCart, while a change to GadgetChain.OpenCart can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.OpenCart uses a module listed above it, which is the healthy direction.
37→22 GadgetChain.PHPSecLib uses PHPGGC.GadgetChain.RCE✕
- Connections
- 1 pair of types, where a type in GadgetChain.PHPSecLib uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.PHPSecLib.RCE1→PHPGGC.GadgetChain.RCE.PHPCode
- Direction
- GadgetChain.PHPSecLib uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.PHPSecLib, while a change to GadgetChain.PHPSecLib can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.PHPSecLib uses a module listed above it, which is the healthy direction.
38→5 GadgetChain.Symfony uses PHPGGC.GadgetChain✕
- Connections
- 3 pairs of types, where a type in GadgetChain.Symfony uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.Symfony.FD1→PHPGGC.GadgetChain.FileDeleteGadgetChain.Symfony.FW1→PHPGGC.GadgetChain.FileWriteGadgetChain.Symfony.FW2→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.Symfony uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.Symfony, while a change to GadgetChain.Symfony can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.Symfony uses a module listed above it, which is the healthy direction.
38→22 GadgetChain.Symfony uses PHPGGC.GadgetChain.RCE✕
- Connections
- 16 pairs of types, where a type in GadgetChain.Symfony uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.Symfony.RCE1→PHPGGC.GadgetChain.RCE.CommandGadgetChain.Symfony.RCE10→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE11→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE12→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE13→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE14→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE15→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE16→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE2→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.Symfony.RCE3→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.Symfony.RCE4→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE5→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE6→PHPGGC.GadgetChain.RCE.CommandGadgetChain.Symfony.RCE7→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE8→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.Symfony.RCE9→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.Symfony uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.Symfony, while a change to GadgetChain.Symfony can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.Symfony uses a module listed above it, which is the healthy direction.
39→5 GadgetChain.ThinkPHP uses PHPGGC.GadgetChain✕
- Connections
- 2 pairs of types, where a type in GadgetChain.ThinkPHP uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.ThinkPHP.FW1→PHPGGC.GadgetChain.FileWriteGadgetChain.ThinkPHP.FW2→PHPGGC.GadgetChain.FileWrite
- Direction
- GadgetChain.ThinkPHP uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.ThinkPHP, while a change to GadgetChain.ThinkPHP can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.ThinkPHP uses a module listed above it, which is the healthy direction.
39→22 GadgetChain.ThinkPHP uses PHPGGC.GadgetChain.RCE✕
- Connections
- 4 pairs of types, where a type in GadgetChain.ThinkPHP uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.ThinkPHP.RCE1→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.ThinkPHP.RCE2→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.ThinkPHP.RCE3→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.ThinkPHP.RCE4→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.ThinkPHP uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.ThinkPHP, while a change to GadgetChain.ThinkPHP can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.ThinkPHP uses a module listed above it, which is the healthy direction.
40→5 GadgetChain.ZendFramework uses PHPGGC.GadgetChain✕
- Connections
- 1 pair of types, where a type in GadgetChain.ZendFramework uses a type in PHPGGC.GadgetChain.
- The types involved
GadgetChain.ZendFramework.FD1→PHPGGC.GadgetChain.FileDelete
- Direction
- GadgetChain.ZendFramework uses PHPGGC.GadgetChain, so a change to PHPGGC.GadgetChain can break GadgetChain.ZendFramework, while a change to GadgetChain.ZendFramework can't break PHPGGC.GadgetChain.
- Position
- Below the diagonal: GadgetChain.ZendFramework uses a module listed above it, which is the healthy direction.
40→22 GadgetChain.ZendFramework uses PHPGGC.GadgetChain.RCE✕
- Connections
- 5 pairs of types, where a type in GadgetChain.ZendFramework uses a type in PHPGGC.GadgetChain.RCE.
- The types involved
GadgetChain.ZendFramework.RCE1→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.ZendFramework.RCE2→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.ZendFramework.RCE3→PHPGGC.GadgetChain.RCE.FunctionCallGadgetChain.ZendFramework.RCE4→PHPGGC.GadgetChain.RCE.PHPCodeGadgetChain.ZendFramework.RCE5→PHPGGC.GadgetChain.RCE.FunctionCall
- Direction
- GadgetChain.ZendFramework uses PHPGGC.GadgetChain.RCE, so a change to PHPGGC.GadgetChain.RCE can break GadgetChain.ZendFramework, while a change to GadgetChain.ZendFramework can't break PHPGGC.GadgetChain.RCE.
- Position
- Below the diagonal: GadgetChain.ZendFramework uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 7 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3); Resolve the 1 Low coverage finding(s) in Code Coverage — start with test-gc-compatibility.py; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). | +27.3 pts | Low | REDACTED Scanning |
| Resolve the 1 Low coverage finding(s) in Code Coverage — start with test-gc-compatibility.py. | +27.3 pts | Low | Code Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +10.0 pts | Low | ADR Quality |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (8), chain.php (2), test-gc-compatibility.py. | +8.7 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.6 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with PHPGGC.php. | +2.6 pts | Low | Knowledge Freshness |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +4.2 pts | Medium | Nullable reference types |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +3.2 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.9 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| lib/PHPGGC.php | 7.4 | Mixed | Cyclomatic Complexity: PHPGGC.parse_cmdline (cyclomatic 23) |
| gadgetchains/Sulu/RCE/1/chain.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 14+ corresponding lines) |
| gadgetchains/WordPress/Guzzle/RCE/1/chain.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (6 corresponding lines) |
| gadgetchains/OpenCart/FW/2/chain.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
| gadgetchains/OpenCart/FW/1/chain.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (9 corresponding lines) |
| gadgetchains/Laravel/RCE/16/gadgets.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (4 corresponding lines) |
| gadgetchains/Symfony/RCE/10/chain.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
| gadgetchains/Symfony/RCE/13/chain.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 3+ corresponding lines) |
| gadgetchains/ThinkPHP/FW/1/chain.php | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| gadgetchains/CodeIgniter4/RCE/1/gadgets.php | 8.5 | Near-clean | Code Duplication: Duplicated block (55 lines × 2) |
| gadgetchains/Guzzle/FW/1/gadgets.php | 8.5 | Near-clean | Code Duplication: Duplicated block (28 lines × 2) |
| gadgetchains/Laravel/RCE/5/gadgets.php | 8.5 | Near-clean | Code Duplication: Duplicated block (41 lines × 2) |
| gadgetchains/Monolog/RCE/5/gadgets.php | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| gadgetchains/SwiftMailer/FW/1/chain.php | 8.5 | Near-clean | Code Duplication: Duplicated block (23 lines × 2) |
| gadgetchains/Symfony/RCE/2/gadgets.php | 8.5 | Near-clean | Code Duplication: Duplicated block (35 lines × 2) |
| gadgetchains/Monolog/RCE/1/chain.php | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 35 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 35 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 52 of 60 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 15 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 9 of the 376 production source files in this repository: 361 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (12324 LoC, 753 module-visible types across 179 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `templates/chain.php` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in gadgetchains/CodeIgniter4/RCE/5/gadgets.php, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PHPGGC.parse_cmdline at 23.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with PHPGGC.parse_cmdline (cyclomatic 23). — Refactoring it lifts Cyclomatic Complexity from 9.5 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was PHPGGC.parse_cmdline at 36.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with PHPGGC.parse_cmdline (cognitive 36). — Refactoring it lifts Cognitive Complexity from 9.0 to about 10.0/10.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with PHPGGC.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
13 duplicated block group(s) detected. 5.9 % of the production lines (722 of 12,324) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with chain.php (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 14+ corresponding lines) finding(s) in Code Duplication — start with chain.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with chain.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
5 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 2 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 0.0% — 1 file(s) below 50%. Measured from the Python suite (repository root: `coverage run -m pytest`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 1 Low coverage finding(s) in Code Coverage — start with test-gc-compatibility.py. — One of this dimension's main actionable groups (1 warning-level).
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 12324 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
7 % of calls cross a namespace and 0 % go through an interface, but 0 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `templates/chain.php` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
15 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/PHPGGC.php. Counted over 15 of the 376 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (8), chain.php (2), test-gc-compatibility.py. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with PHPGGC.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P7 · Outbound HTTP resilience
- `new SoapClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — gadgetchains/Smarty/SSRF/1/gadgets.php:8
What to do
- Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62.0 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99.7 | Exemplary | Strongest area. |
| Maturity | 41.1 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 4.6 | Critical — gated by D8, D13, P1, P2, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 86.0 | Strong | Solid. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 79 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
- D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (gadgetchains), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 3 value object(s); its 4 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 1, command argument 2); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — no CI workflow found
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 1 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge lib/PHPGGC.php:1
Serious — 29 finding(s)
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) gadgetchains/WordPress/PHPExcel/RCE/3/chain.php:14
- Duplicated block (8 lines × 2) gadgetchains/WordPress/PHPExcel/RCE/5/chain.php:14
- PHPGGC.parse_cmdline (cyclomatic 23) lib/PHPGGC.php:768
- PHPGGC.parse_cmdline (cognitive 36) lib/PHPGGC.php:768
- ClassTooLong: PHPGGC lib/PHPGGC.php:23
- Edited copies of one member (3 members, 14+ corresponding lines) gadgetchains/Sulu/RCE/1/chain.php:17
- Edited copy of a member (6 corresponding lines) gadgetchains/WordPress/Guzzle/RCE/1/chain.php:14
- Edited copy of a member (10 corresponding lines) gadgetchains/OpenCart/FW/2/chain.php:14
- Edited copy of a member (9 corresponding lines) gadgetchains/OpenCart/FW/1/chain.php:16
- Edited copy of a member (4 corresponding lines) gadgetchains/Laravel/RCE/16/gadgets.php:13
- Edited copy of a member (7 corresponding lines) gadgetchains/Symfony/RCE/10/chain.php:13
- Edited copies of one member (3 members, 3+ corresponding lines) gadgetchains/Symfony/RCE/13/chain.php:14
- Duplicated block (14 lines × 2) gadgetchains/ThinkPHP/FW/1/chain.php:21
- Duplicated block (55 lines × 2) gadgetchains/CodeIgniter4/RCE/1/gadgets.php:8
- Duplicated block (28 lines × 2) gadgetchains/Guzzle/FW/1/gadgets.php:11
- Duplicated block (41 lines × 2) gadgetchains/Laravel/RCE/5/gadgets.php:8
- Duplicated block (12 lines × 2) gadgetchains/Monolog/RCE/5/gadgets.php:15
- Duplicated block (23 lines × 2) gadgetchains/SwiftMailer/FW/1/chain.php:13
- Duplicated block (115 lines × 2) REDACTED:19
- Duplicated block (35 lines × 2) gadgetchains/Symfony/RCE/2/gadgets.php:7
- Duplicated block (9 lines × 2) gadgetchains/Monolog/RCE/1/chain.php:13
- Duplicated block (5 lines × 2) gadgetchains/ZendFramework/RCE/1/gadgets.php:27
- Duplicated block (6 lines × 2) gadgetchains/ZendFramework/RCE/3/gadgets.php:78
- Low coverage: test-gc-compatibility.py test-gc-compatibility.py:1
- No CI pipeline
- No structured logging
- Outbound HTTP without resilience gadgetchains/Smarty/SSRF/1/gadgets.php:8
Minor — 21 finding(s)
- Orphaned file test-gc-compatibility.py:1
- Orphaned file gadgetchains/Drupal/RCE/1/gadgets.php:1
- Orphaned file lib/PHPGGC/GadgetChain.php:1
- Orphaned file gadgetchains/Doctrine/FW/1/gadgets.php:1
- Orphaned file lib/PHPGGC/Phar/Tar.php:1
- Orphaned file gadgetchains/ThinkPHP/RCE/2/gadgets.php:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file lib/PHPGGC/Phar/Format.php:1
- Orphaned file gadgetchains/Doctrine/RCE/1/chain.php:1
- Orphaned file gadgetchains/Symfony/RCE/5/gadgets.php:1
- Orphaned file gadgetchains/ThinkPHP/FW/1/gadgets.php:1
- Orphaned file gadgetchains/Doctrine/FW/1/chain.php:1
- No ADRs found REDACTED:1
- REDACTED
- Further orphaned files (smaller)
- No ADRs
- No architecture diagram/doc
- No SAST
- PHP static analysis does not check null everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-0ab9923b8d81461d887143df2945b8b4/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=525" --report-format json --report-path /tmp/watchdog-gitleaks-0ab9923b8d81461d887143df2945b8b4/history-1.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0ab9923b8d81461d887143df2945b8b4/tree.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `templates/chain.php` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |