Executive summary
nikic/PHP-Parser falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 62 out of 100 and is rated Adequate, and all 13 of its critical findings are security problems in the build pipeline.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Adding a diagnostic log is another step, worth about 4 points. Raising Maturity to 70 would lift the score to about 65.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step runs a download nobody checks. Pinning each tool to an exact version and checking the download against a checksum would close both risks.
The product code is 22,236 lines, about €33,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 62 to about 65.
New since the last survey: 10 findings
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) lib/PhpParser/Builder/Class_.php
- Code Duplication · Edited copy of a member (7 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php
- Code Duplication · Edited copy of a member (10 corresponding lines) lib/PhpParser/Lexer/TokenEmulator/AttributeEmulator.php
- Code Duplication · Edited copy of a member (8 corresponding lines) lib/PhpParser/Node/Expr/Closure.php
- Code Duplication · Edited copy of a member (5 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php
- Code Duplication · Edited copy of a member (7 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php
- Code Duplication · Edited copy of a member (10 corresponding lines) lib/PhpParser/PrettyPrinterAbstract.php
- Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) lib/PhpParser/Node/PropertyHook.php
- Code Duplication · Edited copy of a member (3 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php
- Code Duplication · Edited copy of a member (4 corresponding lines) lib/PhpParser/Node/Stmt/Interface_.php
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (6 lines × 2) lib/PhpParser/Lexer/TokenEmulator/AttributeEmulator.php
- Documentation (README) · README may be stale
Rebuild cost: about €33,000 · Estimate
| Cost to rebuild | €11,000 to €54,000, for 180 to 571 hours of work, about 0.2 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.8 at a score of 62. 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 | Medium: 22,236 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: which parts of the code depend on which
| uses → | 1 grammar | 2 PhpParser.Comment | 3 PhpParser.Node.Expr | 4 PhpParser.Node | 5 PhpParser.Node.Expr.AssignOp | 6 PhpParser.Node.Expr.BinaryOp | 7 PhpParser.Node.Expr.Cast | 8 PhpParser.Builder | 9 PhpParser.Internal | 10 PhpParser.Node.Name | 11 PhpParser.Node.Scalar | 12 PhpParser.Node.Stmt | 13 PhpParser | 14 PhpParser.Node.Scalar.MagicConst | 15 PhpParser.Node.Stmt.TraitUseAdaptation | 16 PhpParser.ErrorHandler | 17 PhpParser.Lexer | 18 PhpParser.Lexer.TokenEmulator | 19 PhpParser.NodeVisitor | 20 PhpParser.Parser | 21 PhpParser.PrettyPrinter |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 grammar | |||||||||||||||||||||
| 2 PhpParser.Comment | 1 | ||||||||||||||||||||
| 3 PhpParser.Node.Expr | 47 | 12 | |||||||||||||||||||
| 4 PhpParser.Node | 2 | 24 | |||||||||||||||||||
| 5 PhpParser.Node.Expr.AssignOp | 13 | ||||||||||||||||||||
| 6 PhpParser.Node.Expr.BinaryOp | 28 | ||||||||||||||||||||
| 7 PhpParser.Node.Expr.Cast | 8 | ||||||||||||||||||||
| 8 PhpParser.Builder | 10 | 23 | |||||||||||||||||||
| 9 PhpParser.Internal | 1 | 2 | |||||||||||||||||||
| 10 PhpParser.Node.Name | 2 | ||||||||||||||||||||
| 11 PhpParser.Node.Scalar | 5 | ||||||||||||||||||||
| 12 PhpParser.Node.Stmt | 1 | 66 | 5 | ||||||||||||||||||
| 13 PhpParser | 3 | 14 | 17 | 1 | 14 | 3 | 1 | 1 | 10 | ||||||||||||
| 14 PhpParser.Node.Scalar.MagicConst | 9 | ||||||||||||||||||||
| 15 PhpParser.Node.Stmt.TraitUseAdaptation | 3 | 2 | |||||||||||||||||||
| 16 PhpParser.ErrorHandler | 4 | ||||||||||||||||||||
| 17 PhpParser.Lexer | 3 | ||||||||||||||||||||
| 18 PhpParser.Lexer.TokenEmulator | 16 | ||||||||||||||||||||
| 19 PhpParser.NodeVisitor | 2 | 16 | |||||||||||||||||||
| 20 PhpParser.Parser | 2 | ||||||||||||||||||||
| 21 PhpParser.PrettyPrinter | 42 | 21 | 13 | 28 | 8 | 2 | 4 | 41 | 2 | 9 | 2 |
2→13 PhpParser.Comment uses PhpParser part of a loop✕
- Connections
- 1 pair of types, where a type in PhpParser.Comment uses a type in PhpParser.
- The types involved
PhpParser.Comment.Doc→PhpParser.Comment
- Direction
- PhpParser.Comment uses PhpParser, so a change to PhpParser can break PhpParser.Comment, while a change to PhpParser.Comment can't break PhpParser.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→4 PhpParser.Node.Expr uses PhpParser.Node part of a loop✕
- Connections
- 47 pairs of types, where a type in PhpParser.Node.Expr uses a type in PhpParser.Node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
PhpParser.Node.Expr.ArrayDimFetch→PhpParser.Node.ExprPhpParser.Node.Expr.Array_→PhpParser.Node.ExprPhpParser.Node.Expr.ArrowFunction→PhpParser.Node.ExprPhpParser.Node.Expr.ArrowFunction→PhpParser.Node.FunctionLikePhpParser.Node.Expr.Assign→PhpParser.Node.ExprPhpParser.Node.Expr.AssignOp→PhpParser.Node.ExprPhpParser.Node.Expr.AssignRef→PhpParser.Node.ExprPhpParser.Node.Expr.BinaryOp→PhpParser.Node.ExprPhpParser.Node.Expr.BitwiseNot→PhpParser.Node.ExprPhpParser.Node.Expr.BooleanNot→PhpParser.Node.ExprPhpParser.Node.Expr.CallLike→PhpParser.Node.ArgPhpParser.Node.Expr.CallLike→PhpParser.Node.ExprPhpParser.Node.Expr.Cast→PhpParser.Node.ExprPhpParser.Node.Expr.ClassConstFetch→PhpParser.Node.ExprPhpParser.Node.Expr.Clone_→PhpParser.Node.ExprPhpParser.Node.Expr.Closure→PhpParser.Node.ExprPhpParser.Node.Expr.Closure→PhpParser.Node.FunctionLikePhpParser.Node.Expr.ConstFetch→PhpParser.Node.ExprPhpParser.Node.Expr.ConstFetch→PhpParser.Node.NamePhpParser.Node.Expr.Empty_→PhpParser.Node.ExprPhpParser.Node.Expr.Error→PhpParser.Node.ExprPhpParser.Node.Expr.ErrorSuppress→PhpParser.Node.ExprPhpParser.Node.Expr.Eval_→PhpParser.Node.ExprPhpParser.Node.Expr.Exit_→PhpParser.Node.ExprPhpParser.Node.Expr.Include_→PhpParser.Node.Expr
- Direction
- PhpParser.Node.Expr uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Node.Expr, while a change to PhpParser.Node.Expr can't break PhpParser.Node.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→13 PhpParser.Node.Expr uses PhpParser part of a loop✕
- Connections
- 12 pairs of types, where a type in PhpParser.Node.Expr uses a type in PhpParser.
- The types involved
PhpParser.Node.Expr.ArrowFunction→PhpParser.NodePhpParser.Node.Expr.ClassConstFetch→PhpParser.NodePhpParser.Node.Expr.Closure→PhpParser.NodePhpParser.Node.Expr.FuncCall→PhpParser.NodePhpParser.Node.Expr.Instanceof_→PhpParser.NodePhpParser.Node.Expr.MethodCall→PhpParser.NodePhpParser.Node.Expr.New_→PhpParser.NodePhpParser.Node.Expr.NullsafeMethodCall→PhpParser.NodePhpParser.Node.Expr.NullsafePropertyFetch→PhpParser.NodePhpParser.Node.Expr.PropertyFetch→PhpParser.NodePhpParser.Node.Expr.StaticCall→PhpParser.NodePhpParser.Node.Expr.StaticPropertyFetch→PhpParser.Node
- Direction
- PhpParser.Node.Expr uses PhpParser, so a change to PhpParser can break PhpParser.Node.Expr, while a change to PhpParser.Node.Expr can't break PhpParser.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→3 PhpParser.Node uses PhpParser.Node.Expr✕
- Connections
- 2 pairs of types, where a type in PhpParser.Node uses a type in PhpParser.Node.Expr.
- The types involved
PhpParser.Node.ClosureUse→PhpParser.Node.Expr.VariablePhpParser.Node.StaticVar→PhpParser.Node.Expr.Variable
- Direction
- PhpParser.Node uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.Node, while a change to PhpParser.Node can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.Node uses a module listed above it, which is the healthy direction.
4→13 PhpParser.Node uses PhpParser part of a loop✕
- Connections
- 24 pairs of types, where a type in PhpParser.Node uses a type in PhpParser.
- The types involved
PhpParser.Node.Arg→PhpParser.NodeAbstractPhpParser.Node.ArgPlaceholder→PhpParser.NodeAbstractPhpParser.Node.ArrayItem→PhpParser.NodeAbstractPhpParser.Node.Attribute→PhpParser.NodeAbstractPhpParser.Node.AttributeGroup→PhpParser.NodeAbstractPhpParser.Node.ClosureUse→PhpParser.NodeAbstractPhpParser.Node.ComplexType→PhpParser.NodeAbstractPhpParser.Node.Const_→PhpParser.NodeAbstractPhpParser.Node.DeclareItem→PhpParser.NodeAbstractPhpParser.Node.Expr→PhpParser.NodeAbstractPhpParser.Node.FunctionLike→PhpParser.NodePhpParser.Node.Identifier→PhpParser.NodeAbstractPhpParser.Node.InterpolatedStringPart→PhpParser.NodeAbstractPhpParser.Node.MatchArm→PhpParser.NodeAbstractPhpParser.Node.Name→PhpParser.NodeAbstractPhpParser.Node.NullableType→PhpParser.NodePhpParser.Node.Param→PhpParser.NodePhpParser.Node.Param→PhpParser.NodeAbstractPhpParser.Node.PropertyHook→PhpParser.NodeAbstractPhpParser.Node.PropertyItem→PhpParser.NodeAbstractPhpParser.Node.StaticVar→PhpParser.NodeAbstractPhpParser.Node.Stmt→PhpParser.NodeAbstractPhpParser.Node.UseItem→PhpParser.NodeAbstractPhpParser.Node.VariadicPlaceholder→PhpParser.NodeAbstract
- Direction
- PhpParser.Node uses PhpParser, so a change to PhpParser can break PhpParser.Node, while a change to PhpParser.Node can't break PhpParser.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→3 PhpParser.Node.Expr.AssignOp uses PhpParser.Node.Expr✕
- Connections
- 13 pairs of types, where a type in PhpParser.Node.Expr.AssignOp uses a type in PhpParser.Node.Expr.
- The types involved
PhpParser.Node.Expr.AssignOp.BitwiseAnd→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.BitwiseOr→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.BitwiseXor→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Coalesce→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Concat→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Div→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Minus→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Mod→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Mul→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Plus→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.Pow→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.ShiftLeft→PhpParser.Node.Expr.AssignOpPhpParser.Node.Expr.AssignOp.ShiftRight→PhpParser.Node.Expr.AssignOp
- Direction
- PhpParser.Node.Expr.AssignOp uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.Node.Expr.AssignOp, while a change to PhpParser.Node.Expr.AssignOp can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.Node.Expr.AssignOp uses a module listed above it, which is the healthy direction.
6→3 PhpParser.Node.Expr.BinaryOp uses PhpParser.Node.Expr✕
- Connections
- 28 pairs of types, where a type in PhpParser.Node.Expr.BinaryOp uses a type in PhpParser.Node.Expr. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
PhpParser.Node.Expr.BinaryOp.BitwiseAnd→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.BitwiseOr→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.BitwiseXor→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.BooleanAnd→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.BooleanOr→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Coalesce→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Concat→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Div→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Equal→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Greater→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.GreaterOrEqual→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Identical→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.LogicalAnd→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.LogicalOr→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.LogicalXor→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Minus→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Mod→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Mul→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.NotEqual→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.NotIdentical→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Pipe→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Plus→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.Pow→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.ShiftLeft→PhpParser.Node.Expr.BinaryOpPhpParser.Node.Expr.BinaryOp.ShiftRight→PhpParser.Node.Expr.BinaryOp
- Direction
- PhpParser.Node.Expr.BinaryOp uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.Node.Expr.BinaryOp, while a change to PhpParser.Node.Expr.BinaryOp can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.Node.Expr.BinaryOp uses a module listed above it, which is the healthy direction.
7→3 PhpParser.Node.Expr.Cast uses PhpParser.Node.Expr✕
- Connections
- 8 pairs of types, where a type in PhpParser.Node.Expr.Cast uses a type in PhpParser.Node.Expr.
- The types involved
PhpParser.Node.Expr.Cast.Array_→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.Bool_→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.Double→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.Int_→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.Object_→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.String_→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.Unset_→PhpParser.Node.Expr.CastPhpParser.Node.Expr.Cast.Void_→PhpParser.Node.Expr.Cast
- Direction
- PhpParser.Node.Expr.Cast uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.Node.Expr.Cast, while a change to PhpParser.Node.Expr.Cast can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.Node.Expr.Cast uses a module listed above it, which is the healthy direction.
8→4 PhpParser.Builder uses PhpParser.Node✕
- Connections
- 10 pairs of types, where a type in PhpParser.Builder uses a type in PhpParser.Node.
- The types involved
PhpParser.Builder.Class_→PhpParser.Node.NamePhpParser.Builder.EnumCase→PhpParser.Node.ExprPhpParser.Builder.Enum_→PhpParser.Node.IdentifierPhpParser.Builder.Namespace_→PhpParser.Node.NamePhpParser.Builder.Param→PhpParser.Node.ExprPhpParser.Builder.Property→PhpParser.Node.ExprPhpParser.Builder.Property→PhpParser.Node.PropertyHookPhpParser.Builder.TraitUseAdaptation→PhpParser.Node.IdentifierPhpParser.Builder.TraitUseAdaptation→PhpParser.Node.NamePhpParser.Builder.Use_→PhpParser.Node.Name
- Direction
- PhpParser.Builder uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Builder, while a change to PhpParser.Builder can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.Builder uses a module listed above it, which is the healthy direction.
8→13 PhpParser.Builder uses PhpParser part of a loop✕
- Connections
- 23 pairs of types, where a type in PhpParser.Builder uses a type in PhpParser.
- The types involved
PhpParser.Builder.ClassConst→PhpParser.BuilderPhpParser.Builder.ClassConst→PhpParser.NodePhpParser.Builder.Class_→PhpParser.NodePhpParser.Builder.Declaration→PhpParser.BuilderPhpParser.Builder.EnumCase→PhpParser.BuilderPhpParser.Builder.EnumCase→PhpParser.NodePhpParser.Builder.Enum_→PhpParser.NodePhpParser.Builder.FunctionLike→PhpParser.NodePhpParser.Builder.Function_→PhpParser.NodePhpParser.Builder.Interface_→PhpParser.NodePhpParser.Builder.Method→PhpParser.NodePhpParser.Builder.Namespace_→PhpParser.NodePhpParser.Builder.Param→PhpParser.BuilderPhpParser.Builder.Param→PhpParser.NodePhpParser.Builder.Property→PhpParser.BuilderPhpParser.Builder.Property→PhpParser.NodePhpParser.Builder.TraitUse→PhpParser.BuilderPhpParser.Builder.TraitUse→PhpParser.NodePhpParser.Builder.TraitUseAdaptation→PhpParser.BuilderPhpParser.Builder.TraitUseAdaptation→PhpParser.NodePhpParser.Builder.Trait_→PhpParser.NodePhpParser.Builder.Use_→PhpParser.BuilderPhpParser.Builder.Use_→PhpParser.Node
- Direction
- PhpParser.Builder uses PhpParser, so a change to PhpParser can break PhpParser.Builder, while a change to PhpParser.Builder can't break PhpParser.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 PhpParser.Internal uses PhpParser.Node.Expr✕
- Connections
- 1 pair of types, where a type in PhpParser.Internal uses a type in PhpParser.Node.Expr.
- The types involved
PhpParser.Internal.PrintableNewAnonClassNode→PhpParser.Node.Expr.New_
- Direction
- PhpParser.Internal uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.Internal, while a change to PhpParser.Internal can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.Internal uses a module listed above it, which is the healthy direction.
9→4 PhpParser.Internal uses PhpParser.Node✕
- Connections
- 2 pairs of types, where a type in PhpParser.Internal uses a type in PhpParser.Node.
- The types involved
PhpParser.Internal.PrintableNewAnonClassNode→PhpParser.Node.ExprPhpParser.Internal.PrintableNewAnonClassNode→PhpParser.Node.Name
- Direction
- PhpParser.Internal uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Internal, while a change to PhpParser.Internal can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.Internal uses a module listed above it, which is the healthy direction.
10→4 PhpParser.Node.Name uses PhpParser.Node✕
- Connections
- 2 pairs of types, where a type in PhpParser.Node.Name uses a type in PhpParser.Node.
- The types involved
PhpParser.Node.Name.FullyQualified→PhpParser.Node.NamePhpParser.Node.Name.Relative→PhpParser.Node.Name
- Direction
- PhpParser.Node.Name uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Node.Name, while a change to PhpParser.Node.Name can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.Node.Name uses a module listed above it, which is the healthy direction.
11→4 PhpParser.Node.Scalar uses PhpParser.Node✕
- Connections
- 5 pairs of types, where a type in PhpParser.Node.Scalar uses a type in PhpParser.Node.
- The types involved
PhpParser.Node.Scalar.Float_→PhpParser.Node.ScalarPhpParser.Node.Scalar.Int_→PhpParser.Node.ScalarPhpParser.Node.Scalar.InterpolatedString→PhpParser.Node.ScalarPhpParser.Node.Scalar.MagicConst→PhpParser.Node.ScalarPhpParser.Node.Scalar.String_→PhpParser.Node.Scalar
- Direction
- PhpParser.Node.Scalar uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Node.Scalar, while a change to PhpParser.Node.Scalar can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.Node.Scalar uses a module listed above it, which is the healthy direction.
12→3 PhpParser.Node.Stmt uses PhpParser.Node.Expr✕
- Connections
- 1 pair of types, where a type in PhpParser.Node.Stmt uses a type in PhpParser.Node.Expr.
- The types involved
PhpParser.Node.Stmt.Catch_→PhpParser.Node.Expr.Variable
- Direction
- PhpParser.Node.Stmt uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.Node.Stmt, while a change to PhpParser.Node.Stmt can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.Node.Stmt uses a module listed above it, which is the healthy direction.
12→4 PhpParser.Node.Stmt uses PhpParser.Node✕
- Connections
- 66 pairs of types, where a type in PhpParser.Node.Stmt uses a type in PhpParser.Node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
PhpParser.Node.Stmt.Block→PhpParser.Node.StmtPhpParser.Node.Stmt.Break_→PhpParser.Node.ExprPhpParser.Node.Stmt.Break_→PhpParser.Node.StmtPhpParser.Node.Stmt.Case_→PhpParser.Node.ExprPhpParser.Node.Stmt.Case_→PhpParser.Node.StmtPhpParser.Node.Stmt.Catch_→PhpParser.Node.StmtPhpParser.Node.Stmt.ClassConst→PhpParser.Node.StmtPhpParser.Node.Stmt.ClassLike→PhpParser.Node.IdentifierPhpParser.Node.Stmt.ClassLike→PhpParser.Node.NamePhpParser.Node.Stmt.ClassLike→PhpParser.Node.StmtPhpParser.Node.Stmt.ClassMethod→PhpParser.Node.FunctionLikePhpParser.Node.Stmt.ClassMethod→PhpParser.Node.IdentifierPhpParser.Node.Stmt.ClassMethod→PhpParser.Node.StmtPhpParser.Node.Stmt.Class_→PhpParser.Node.NamePhpParser.Node.Stmt.Const_→PhpParser.Node.StmtPhpParser.Node.Stmt.Continue_→PhpParser.Node.ExprPhpParser.Node.Stmt.Continue_→PhpParser.Node.StmtPhpParser.Node.Stmt.Declare_→PhpParser.Node.StmtPhpParser.Node.Stmt.Do_→PhpParser.Node.ExprPhpParser.Node.Stmt.Do_→PhpParser.Node.StmtPhpParser.Node.Stmt.Echo_→PhpParser.Node.StmtPhpParser.Node.Stmt.ElseIf_→PhpParser.Node.ExprPhpParser.Node.Stmt.ElseIf_→PhpParser.Node.StmtPhpParser.Node.Stmt.Else_→PhpParser.Node.StmtPhpParser.Node.Stmt.EnumCase→PhpParser.Node.Expr
- Direction
- PhpParser.Node.Stmt uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Node.Stmt, while a change to PhpParser.Node.Stmt can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.Node.Stmt uses a module listed above it, which is the healthy direction.
12→13 PhpParser.Node.Stmt uses PhpParser part of a loop✕
- Connections
- 5 pairs of types, where a type in PhpParser.Node.Stmt uses a type in PhpParser.
- The types involved
PhpParser.Node.Stmt.ClassConst→PhpParser.NodePhpParser.Node.Stmt.ClassMethod→PhpParser.NodePhpParser.Node.Stmt.Enum_→PhpParser.NodePhpParser.Node.Stmt.Function_→PhpParser.NodePhpParser.Node.Stmt.Property→PhpParser.Node
- Direction
- PhpParser.Node.Stmt uses PhpParser, so a change to PhpParser can break PhpParser.Node.Stmt, while a change to PhpParser.Node.Stmt can't break PhpParser.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 PhpParser uses PhpParser.Comment✕
- Connections
- 3 pairs of types, where a type in PhpParser uses a type in PhpParser.Comment.
- The types involved
PhpParser.BuilderHelpers→PhpParser.Comment.DocPhpParser.Node→PhpParser.Comment.DocPhpParser.NodeAbstract→PhpParser.Comment.Doc
- Direction
- PhpParser uses PhpParser.Comment, so a change to PhpParser.Comment can break PhpParser, while a change to PhpParser can't break PhpParser.Comment.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→3 PhpParser uses PhpParser.Node.Expr✕
- Connections
- 14 pairs of types, where a type in PhpParser uses a type in PhpParser.Node.Expr.
- The types involved
PhpParser.BuilderFactory→PhpParser.Node.Expr.ClassConstFetchPhpParser.BuilderFactory→PhpParser.Node.Expr.ConstFetchPhpParser.BuilderFactory→PhpParser.Node.Expr.FuncCallPhpParser.BuilderFactory→PhpParser.Node.Expr.MethodCallPhpParser.BuilderFactory→PhpParser.Node.Expr.New_PhpParser.BuilderFactory→PhpParser.Node.Expr.PropertyFetchPhpParser.BuilderFactory→PhpParser.Node.Expr.StaticCallPhpParser.BuilderFactory→PhpParser.Node.Expr.VariablePhpParser.ConstExprEvaluator→PhpParser.Node.Expr.Array_PhpParser.ConstExprEvaluator→PhpParser.Node.Expr.BinaryOpPhpParser.ConstExprEvaluator→PhpParser.Node.Expr.ConstFetchPhpParser.ConstExprEvaluator→PhpParser.Node.Expr.TernaryPhpParser.ParserAbstract→PhpParser.Node.Expr.Array_PhpParser.ParserAbstract→PhpParser.Node.Expr.List_
- Direction
- PhpParser uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser, while a change to PhpParser can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→4 PhpParser uses PhpParser.Node✕
- Connections
- 17 pairs of types, where a type in PhpParser uses a type in PhpParser.Node.
- The types involved
PhpParser.BuilderFactory→PhpParser.Node.AttributePhpParser.BuilderFactory→PhpParser.Node.ExprPhpParser.BuilderHelpers→PhpParser.Node.AttributeGroupPhpParser.BuilderHelpers→PhpParser.Node.ExprPhpParser.BuilderHelpers→PhpParser.Node.IdentifierPhpParser.BuilderHelpers→PhpParser.Node.NamePhpParser.BuilderHelpers→PhpParser.Node.StmtPhpParser.ConstExprEvaluator→PhpParser.Node.ExprPhpParser.NameContext→PhpParser.Node.NamePhpParser.ParserAbstract→PhpParser.Node.ExprPhpParser.ParserAbstract→PhpParser.Node.IdentifierPhpParser.ParserAbstract→PhpParser.Node.NamePhpParser.ParserAbstract→PhpParser.Node.ParamPhpParser.ParserAbstract→PhpParser.Node.PropertyHookPhpParser.ParserAbstract→PhpParser.Node.UseItemPhpParser.PrettyPrinter→PhpParser.Node.ExprPhpParser.PrettyPrinterAbstract→PhpParser.Node.Expr
- Direction
- PhpParser uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser, while a change to PhpParser can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→6 PhpParser uses PhpParser.Node.Expr.BinaryOp✕
- Connections
- 1 pair of types, where a type in PhpParser uses a type in PhpParser.Node.Expr.BinaryOp.
- The types involved
PhpParser.BuilderFactory→PhpParser.Node.Expr.BinaryOp.Concat
- Direction
- PhpParser uses PhpParser.Node.Expr.BinaryOp, so a change to PhpParser.Node.Expr.BinaryOp can break PhpParser, while a change to PhpParser can't break PhpParser.Node.Expr.BinaryOp.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→8 PhpParser uses PhpParser.Builder✕
- Connections
- 14 pairs of types, where a type in PhpParser uses a type in PhpParser.Builder.
- The types involved
PhpParser.BuilderFactory→PhpParser.Builder.ClassConstPhpParser.BuilderFactory→PhpParser.Builder.Class_PhpParser.BuilderFactory→PhpParser.Builder.EnumCasePhpParser.BuilderFactory→PhpParser.Builder.Enum_PhpParser.BuilderFactory→PhpParser.Builder.Function_PhpParser.BuilderFactory→PhpParser.Builder.Interface_PhpParser.BuilderFactory→PhpParser.Builder.MethodPhpParser.BuilderFactory→PhpParser.Builder.Namespace_PhpParser.BuilderFactory→PhpParser.Builder.ParamPhpParser.BuilderFactory→PhpParser.Builder.PropertyPhpParser.BuilderFactory→PhpParser.Builder.TraitUsePhpParser.BuilderFactory→PhpParser.Builder.TraitUseAdaptationPhpParser.BuilderFactory→PhpParser.Builder.Trait_PhpParser.BuilderFactory→PhpParser.Builder.Use_
- Direction
- PhpParser uses PhpParser.Builder, so a change to PhpParser.Builder can break PhpParser, while a change to PhpParser can't break PhpParser.Builder.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→9 PhpParser uses PhpParser.Internal✕
- Connections
- 3 pairs of types, where a type in PhpParser uses a type in PhpParser.Internal.
- The types involved
PhpParser.PrettyPrinterAbstract→PhpParser.Internal.DifferPhpParser.PrettyPrinterAbstract→PhpParser.Internal.TokenStreamPhpParser.Token→PhpParser.Internal.TokenPolyfill
- Direction
- PhpParser uses PhpParser.Internal, so a change to PhpParser.Internal can break PhpParser, while a change to PhpParser can't break PhpParser.Internal.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→10 PhpParser uses PhpParser.Node.Name✕
- Connections
- 1 pair of types, where a type in PhpParser uses a type in PhpParser.Node.Name.
- The types involved
PhpParser.NameContext→PhpParser.Node.Name.FullyQualified
- Direction
- PhpParser uses PhpParser.Node.Name, so a change to PhpParser.Node.Name can break PhpParser, while a change to PhpParser can't break PhpParser.Node.Name.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→11 PhpParser uses PhpParser.Node.Scalar✕
- Connections
- 1 pair of types, where a type in PhpParser uses a type in PhpParser.Node.Scalar.
- The types involved
PhpParser.ParserAbstract→PhpParser.Node.Scalar.Int_
- Direction
- PhpParser uses PhpParser.Node.Scalar, so a change to PhpParser.Node.Scalar can break PhpParser, while a change to PhpParser can't break PhpParser.Node.Scalar.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
13→12 PhpParser uses PhpParser.Node.Stmt✕
- Connections
- 10 pairs of types, where a type in PhpParser uses a type in PhpParser.Node.Stmt.
- The types involved
PhpParser.ParserAbstract→PhpParser.Node.Stmt.ClassConstPhpParser.ParserAbstract→PhpParser.Node.Stmt.ClassMethodPhpParser.ParserAbstract→PhpParser.Node.Stmt.Class_PhpParser.ParserAbstract→PhpParser.Node.Stmt.Const_PhpParser.ParserAbstract→PhpParser.Node.Stmt.Enum_PhpParser.ParserAbstract→PhpParser.Node.Stmt.Interface_PhpParser.ParserAbstract→PhpParser.Node.Stmt.Namespace_PhpParser.ParserAbstract→PhpParser.Node.Stmt.NopPhpParser.ParserAbstract→PhpParser.Node.Stmt.PropertyPhpParser.ParserAbstract→PhpParser.Node.Stmt.TryCatch
- Direction
- PhpParser uses PhpParser.Node.Stmt, so a change to PhpParser.Node.Stmt can break PhpParser, while a change to PhpParser can't break PhpParser.Node.Stmt.
- Position
- Below the diagonal: PhpParser uses a module listed above it, which is the healthy direction.
14→11 PhpParser.Node.Scalar.MagicConst uses PhpParser.Node.Scalar✕
- Connections
- 9 pairs of types, where a type in PhpParser.Node.Scalar.MagicConst uses a type in PhpParser.Node.Scalar.
- The types involved
PhpParser.Node.Scalar.MagicConst.Class_→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Dir→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.File→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Function_→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Line→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Method→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Namespace_→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Property→PhpParser.Node.Scalar.MagicConstPhpParser.Node.Scalar.MagicConst.Trait_→PhpParser.Node.Scalar.MagicConst
- Direction
- PhpParser.Node.Scalar.MagicConst uses PhpParser.Node.Scalar, so a change to PhpParser.Node.Scalar can break PhpParser.Node.Scalar.MagicConst, while a change to PhpParser.Node.Scalar.MagicConst can't break PhpParser.Node.Scalar.
- Position
- Below the diagonal: PhpParser.Node.Scalar.MagicConst uses a module listed above it, which is the healthy direction.
15→4 PhpParser.Node.Stmt.TraitUseAdaptation uses PhpParser.Node✕
- Connections
- 3 pairs of types, where a type in PhpParser.Node.Stmt.TraitUseAdaptation uses a type in PhpParser.Node.
- The types involved
PhpParser.Node.Stmt.TraitUseAdaptation.Alias→PhpParser.Node.IdentifierPhpParser.Node.Stmt.TraitUseAdaptation.Alias→PhpParser.Node.NamePhpParser.Node.Stmt.TraitUseAdaptation.Precedence→PhpParser.Node.Name
- Direction
- PhpParser.Node.Stmt.TraitUseAdaptation uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.Node.Stmt.TraitUseAdaptation, while a change to PhpParser.Node.Stmt.TraitUseAdaptation can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.Node.Stmt.TraitUseAdaptation uses a module listed above it, which is the healthy direction.
15→12 PhpParser.Node.Stmt.TraitUseAdaptation uses PhpParser.Node.Stmt✕
- Connections
- 2 pairs of types, where a type in PhpParser.Node.Stmt.TraitUseAdaptation uses a type in PhpParser.Node.Stmt.
- The types involved
PhpParser.Node.Stmt.TraitUseAdaptation.Alias→PhpParser.Node.Stmt.TraitUseAdaptationPhpParser.Node.Stmt.TraitUseAdaptation.Precedence→PhpParser.Node.Stmt.TraitUseAdaptation
- Direction
- PhpParser.Node.Stmt.TraitUseAdaptation uses PhpParser.Node.Stmt, so a change to PhpParser.Node.Stmt can break PhpParser.Node.Stmt.TraitUseAdaptation, while a change to PhpParser.Node.Stmt.TraitUseAdaptation can't break PhpParser.Node.Stmt.
- Position
- Below the diagonal: PhpParser.Node.Stmt.TraitUseAdaptation uses a module listed above it, which is the healthy direction.
16→13 PhpParser.ErrorHandler uses PhpParser✕
- Connections
- 4 pairs of types, where a type in PhpParser.ErrorHandler uses a type in PhpParser.
- The types involved
PhpParser.ErrorHandler.Collecting→PhpParser.ErrorPhpParser.ErrorHandler.Collecting→PhpParser.ErrorHandlerPhpParser.ErrorHandler.Throwing→PhpParser.ErrorPhpParser.ErrorHandler.Throwing→PhpParser.ErrorHandler
- Direction
- PhpParser.ErrorHandler uses PhpParser, so a change to PhpParser can break PhpParser.ErrorHandler, while a change to PhpParser.ErrorHandler can't break PhpParser.
- Position
- Below the diagonal: PhpParser.ErrorHandler uses a module listed above it, which is the healthy direction.
17→13 PhpParser.Lexer uses PhpParser✕
- Connections
- 3 pairs of types, where a type in PhpParser.Lexer uses a type in PhpParser.
- The types involved
PhpParser.Lexer.Emulative→PhpParser.ErrorHandlerPhpParser.Lexer.Emulative→PhpParser.LexerPhpParser.Lexer.Emulative→PhpParser.PhpVersion
- Direction
- PhpParser.Lexer uses PhpParser, so a change to PhpParser can break PhpParser.Lexer, while a change to PhpParser.Lexer can't break PhpParser.
- Position
- Below the diagonal: PhpParser.Lexer uses a module listed above it, which is the healthy direction.
18→13 PhpParser.Lexer.TokenEmulator uses PhpParser✕
- Connections
- 16 pairs of types, where a type in PhpParser.Lexer.TokenEmulator uses a type in PhpParser.
- The types involved
PhpParser.Lexer.TokenEmulator.AsymmetricVisibilityTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.AsymmetricVisibilityTokenEmulator→PhpParser.TokenPhpParser.Lexer.TokenEmulator.AttributeEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.EnumTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.ExplicitOctalEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.FnTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.KeywordEmulator→PhpParser.TokenPhpParser.Lexer.TokenEmulator.MatchTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.NullsafeTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.PipeOperatorEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.PropertyTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.ReadonlyFunctionTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.ReadonlyTokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.ReverseEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.TokenEmulator→PhpParser.PhpVersionPhpParser.Lexer.TokenEmulator.VoidCastEmulator→PhpParser.PhpVersion
- Direction
- PhpParser.Lexer.TokenEmulator uses PhpParser, so a change to PhpParser can break PhpParser.Lexer.TokenEmulator, while a change to PhpParser.Lexer.TokenEmulator can't break PhpParser.
- Position
- Below the diagonal: PhpParser.Lexer.TokenEmulator uses a module listed above it, which is the healthy direction.
19→4 PhpParser.NodeVisitor uses PhpParser.Node✕
- Connections
- 2 pairs of types, where a type in PhpParser.NodeVisitor uses a type in PhpParser.Node.
- The types involved
PhpParser.NodeVisitor.NameResolver→PhpParser.Node.NamePhpParser.NodeVisitor.NameResolver→PhpParser.Node.UseItem
- Direction
- PhpParser.NodeVisitor uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.NodeVisitor, while a change to PhpParser.NodeVisitor can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.NodeVisitor uses a module listed above it, which is the healthy direction.
19→13 PhpParser.NodeVisitor uses PhpParser✕
- Connections
- 16 pairs of types, where a type in PhpParser.NodeVisitor uses a type in PhpParser.
- The types involved
PhpParser.NodeVisitor.CloningVisitor→PhpParser.NodePhpParser.NodeVisitor.CloningVisitor→PhpParser.NodeVisitorAbstractPhpParser.NodeVisitor.CommentAnnotatingVisitor→PhpParser.NodePhpParser.NodeVisitor.CommentAnnotatingVisitor→PhpParser.NodeVisitorAbstractPhpParser.NodeVisitor.FindingVisitor→PhpParser.NodePhpParser.NodeVisitor.FindingVisitor→PhpParser.NodeVisitorAbstractPhpParser.NodeVisitor.FirstFindingVisitor→PhpParser.NodePhpParser.NodeVisitor.FirstFindingVisitor→PhpParser.NodeVisitorAbstractPhpParser.NodeVisitor.NameResolver→PhpParser.ErrorHandlerPhpParser.NodeVisitor.NameResolver→PhpParser.NameContextPhpParser.NodeVisitor.NameResolver→PhpParser.NodePhpParser.NodeVisitor.NameResolver→PhpParser.NodeVisitorAbstractPhpParser.NodeVisitor.NodeConnectingVisitor→PhpParser.NodePhpParser.NodeVisitor.NodeConnectingVisitor→PhpParser.NodeVisitorAbstractPhpParser.NodeVisitor.ParentConnectingVisitor→PhpParser.NodePhpParser.NodeVisitor.ParentConnectingVisitor→PhpParser.NodeVisitorAbstract
- Direction
- PhpParser.NodeVisitor uses PhpParser, so a change to PhpParser can break PhpParser.NodeVisitor, while a change to PhpParser.NodeVisitor can't break PhpParser.
- Position
- Below the diagonal: PhpParser.NodeVisitor uses a module listed above it, which is the healthy direction.
20→13 PhpParser.Parser uses PhpParser✕
- Connections
- 2 pairs of types, where a type in PhpParser.Parser uses a type in PhpParser.
- The types involved
PhpParser.Parser.Php7→PhpParser.ParserAbstractPhpParser.Parser.Php8→PhpParser.ParserAbstract
- Direction
- PhpParser.Parser uses PhpParser, so a change to PhpParser can break PhpParser.Parser, while a change to PhpParser.Parser can't break PhpParser.
- Position
- Below the diagonal: PhpParser.Parser uses a module listed above it, which is the healthy direction.
21→3 PhpParser.PrettyPrinter uses PhpParser.Node.Expr✕
- Connections
- 42 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Expr. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ArrayDimFetchPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Array_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ArrowFunctionPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignRefPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BitwiseNotPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BooleanNotPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ClassConstFetchPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Clone_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ClosurePhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ConstFetchPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Empty_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ErrorPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.ErrorSuppressPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Eval_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Exit_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.FuncCallPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Include_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Instanceof_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Isset_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.List_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Match_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.MethodCallPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.New_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.NullsafeMethodCall
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Expr, so a change to PhpParser.Node.Expr can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Expr.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→4 PhpParser.PrettyPrinter uses PhpParser.Node✕
- Connections
- 21 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.ArgPhpParser.PrettyPrinter.Standard→PhpParser.Node.ArgPlaceholderPhpParser.PrettyPrinter.Standard→PhpParser.Node.ArrayItemPhpParser.PrettyPrinter.Standard→PhpParser.Node.AttributePhpParser.PrettyPrinter.Standard→PhpParser.Node.AttributeGroupPhpParser.PrettyPrinter.Standard→PhpParser.Node.ClosureUsePhpParser.PrettyPrinter.Standard→PhpParser.Node.Const_PhpParser.PrettyPrinter.Standard→PhpParser.Node.DeclareItemPhpParser.PrettyPrinter.Standard→PhpParser.Node.IdentifierPhpParser.PrettyPrinter.Standard→PhpParser.Node.IntersectionTypePhpParser.PrettyPrinter.Standard→PhpParser.Node.MatchArmPhpParser.PrettyPrinter.Standard→PhpParser.Node.NamePhpParser.PrettyPrinter.Standard→PhpParser.Node.NullableTypePhpParser.PrettyPrinter.Standard→PhpParser.Node.ParamPhpParser.PrettyPrinter.Standard→PhpParser.Node.PropertyHookPhpParser.PrettyPrinter.Standard→PhpParser.Node.PropertyItemPhpParser.PrettyPrinter.Standard→PhpParser.Node.StaticVarPhpParser.PrettyPrinter.Standard→PhpParser.Node.UnionTypePhpParser.PrettyPrinter.Standard→PhpParser.Node.UseItemPhpParser.PrettyPrinter.Standard→PhpParser.Node.VarLikeIdentifierPhpParser.PrettyPrinter.Standard→PhpParser.Node.VariadicPlaceholder
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→5 PhpParser.PrettyPrinter uses PhpParser.Node.Expr.AssignOp✕
- Connections
- 13 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Expr.AssignOp.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.BitwiseAndPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.BitwiseOrPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.BitwiseXorPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.CoalescePhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.ConcatPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.DivPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.MinusPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.ModPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.MulPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.PlusPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.PowPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.ShiftLeftPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.AssignOp.ShiftRight
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Expr.AssignOp, so a change to PhpParser.Node.Expr.AssignOp can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Expr.AssignOp.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→6 PhpParser.PrettyPrinter uses PhpParser.Node.Expr.BinaryOp✕
- Connections
- 28 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Expr.BinaryOp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.BitwiseAndPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.BitwiseOrPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.BitwiseXorPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.BooleanAndPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.BooleanOrPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.CoalescePhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.ConcatPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.DivPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.EqualPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.GreaterPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.GreaterOrEqualPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.IdenticalPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.LogicalAndPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.LogicalOrPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.LogicalXorPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.MinusPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.ModPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.MulPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.NotEqualPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.NotIdenticalPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.PipePhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.PlusPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.PowPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.ShiftLeftPhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.BinaryOp.ShiftRight
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Expr.BinaryOp, so a change to PhpParser.Node.Expr.BinaryOp can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Expr.BinaryOp.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→7 PhpParser.PrettyPrinter uses PhpParser.Node.Expr.Cast✕
- Connections
- 8 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Expr.Cast.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.Array_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.Bool_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.DoublePhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.Int_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.Object_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.String_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.Unset_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Expr.Cast.Void_
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Expr.Cast, so a change to PhpParser.Node.Expr.Cast can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Expr.Cast.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→10 PhpParser.PrettyPrinter uses PhpParser.Node.Name✕
- Connections
- 2 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Name.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Name.FullyQualifiedPhpParser.PrettyPrinter.Standard→PhpParser.Node.Name.Relative
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Name, so a change to PhpParser.Node.Name can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Name.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→11 PhpParser.PrettyPrinter uses PhpParser.Node.Scalar✕
- Connections
- 4 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Scalar.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.Float_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.Int_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.InterpolatedStringPhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.String_
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Scalar, so a change to PhpParser.Node.Scalar can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Scalar.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→12 PhpParser.PrettyPrinter uses PhpParser.Node.Stmt✕
- Connections
- 41 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Stmt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.BlockPhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Break_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Case_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Catch_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.ClassConstPhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.ClassMethodPhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Class_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Const_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Continue_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Declare_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Do_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Echo_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.ElseIf_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Else_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.EnumCasePhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Enum_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.ExpressionPhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Finally_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.For_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Foreach_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Function_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Global_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.Goto_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.GroupUsePhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.HaltCompiler
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Stmt, so a change to PhpParser.Node.Stmt can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Stmt.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→13 PhpParser.PrettyPrinter uses PhpParser✕
- Connections
- 2 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.NodePhpParser.PrettyPrinter.Standard→PhpParser.PrettyPrinterAbstract
- Direction
- PhpParser.PrettyPrinter uses PhpParser, so a change to PhpParser can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→14 PhpParser.PrettyPrinter uses PhpParser.Node.Scalar.MagicConst✕
- Connections
- 9 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Scalar.MagicConst.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.Class_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.DirPhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.FilePhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.Function_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.LinePhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.MethodPhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.Namespace_PhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.PropertyPhpParser.PrettyPrinter.Standard→PhpParser.Node.Scalar.MagicConst.Trait_
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Scalar.MagicConst, so a change to PhpParser.Node.Scalar.MagicConst can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Scalar.MagicConst.
- Position
- Below the diagonal: PhpParser.PrettyPrinter uses a module listed above it, which is the healthy direction.
21→15 PhpParser.PrettyPrinter uses PhpParser.Node.Stmt.TraitUseAdaptation✕
- Connections
- 2 pairs of types, where a type in PhpParser.PrettyPrinter uses a type in PhpParser.Node.Stmt.TraitUseAdaptation.
- The types involved
PhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.TraitUseAdaptation.AliasPhpParser.PrettyPrinter.Standard→PhpParser.Node.Stmt.TraitUseAdaptation.Precedence
- Direction
- PhpParser.PrettyPrinter uses PhpParser.Node.Stmt.TraitUseAdaptation, so a change to PhpParser.Node.Stmt.TraitUseAdaptation can break PhpParser.PrettyPrinter, while a change to PhpParser.PrettyPrinter can't break PhpParser.Node.Stmt.TraitUseAdaptation.
- Position
- Below the diagonal: PhpParser.PrettyPrinter 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 |
|---|---|---|
| A05:2025 — Injection | 13 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json; 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +6.5 pts | Low | ADR Quality |
| 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. | +5.5 pts | Medium | Architecture documentation |
| 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. | +4.3 pts | Medium | Observability |
| 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. | +3.6 pts | Medium | Nullable reference types |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.7 pts | Medium | Documentation (README) |
| Resolve the 4 Orphaned file finding(s) in Knowledge Freshness — start with phpyLang.php, TraitUseAdaptation.php, ClassConst.php. | +0.8 pts | Low | Knowledge Freshness |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.7 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.7 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| lib/PhpParser/ParserAbstract.php | 5.5 | Mixed | Cyclomatic Complexity: ParserAbstract.doParse (cyclomatic 43) |
| lib/PhpParser/Parser/Php7.php | 5.6 | Mixed | Cyclomatic Complexity: Php7.initReduceCallbacks (cyclomatic 22) |
| lib/PhpParser/PrettyPrinterAbstract.php | 6.0 | Mixed | Explicit Debt: FixmeComment |
| lib/PhpParser/Lexer/TokenEmulator/AttributeEmulator.php | 6.7 | Mixed | Explicit Debt: TodoComment |
| lib/PhpParser/PrettyPrinter/Standard.php | 7.0 | Mixed | Cognitive Complexity: Standard.pScalar_String (cognitive 26) |
| lib/PhpParser/NodeTraverser.php | 7.1 | Mixed | Cyclomatic Complexity: NodeTraverser.traverseArray (cyclomatic 24) |
| lib/PhpParser/Parser/Php8.php | 7.1 | Mixed | Cyclomatic Complexity: Php8.initReduceCallbacks (cyclomatic 22) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| lib/PhpParser/NodeVisitor/NameResolver.php | 7.4 | Mixed | Cyclomatic Complexity: NameResolver.enterNode (cyclomatic 51) |
| lib/PhpParser/Internal/TokenPolyfill.php | 7.4 | Mixed | Cyclomatic Complexity: TokenPolyfill.tokenize (cyclomatic 19) |
| lib/PhpParser/NodeDumper.php | 7.8 | Mixed | Cyclomatic Complexity: NodeDumper.dumpRecursive (cyclomatic 37) |
| lib/PhpParser/Internal/Differ.php | 7.8 | Mixed | Cognitive Complexity: Differ.calculateTrace (cognitive 18) |
| lib/PhpParser/Lexer/TokenEmulator/VoidCastEmulator.php | 7.8 | Mixed | Cognitive Complexity: VoidCastEmulator.emulate (cognitive 18) |
| lib/PhpParser/Builder/Class_.php | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 15+ corresponding lines) |
| test/PhpParser/PrettyPrinterTest.php | 7.8 | Mixed | Test Quality: No assertions: testPrettyPrint |
| lib/PhpParser/Comment.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/PhpParser/Internal/TokenStream.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/PhpParser/NameContext.php | 8.5 | Near-clean | Cognitive Complexity: NameContext.getPossibleNames (cognitive 21) |
| lib/PhpParser/NodeVisitor/CommentAnnotatingVisitor.php | 8.5 | Near-clean | Cognitive Complexity: CommentAnnotatingVisitor.enterNode (cognitive 20) |
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 38 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 — 38 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, 115 of 125 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`phpunit --coverage`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.php), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D11 Test Reliability — 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. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. This repository's dependency manifest (composer.json) was found, but this pass cannot parse it for hygiene, 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 — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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 — 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- 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.
- 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 Dockerfile) is simply not read here yet.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- 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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala 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 and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- P7 Outbound HTTP resilience — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. No service entry point was found in the PHP source it does read, and the rest of this repository's production source is , which it does not read yet — the service may well be there — a gap in this analyzer's language reach, not a finding about the code.
- 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala 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.
- 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala 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.
- 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala 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.
- 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.
- X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin 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.
- X29 Per-element action decided by a fixed element — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala 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.
- 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 and Rust 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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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").
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PrettyPrinterAbstract.pArray at 60. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ConstExprEvaluator.evaluateBinaryOp at 35 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: lib/PhpParser/ConstExprEvaluator.php (ConstExprEvaluator.evaluateBinaryOp at 35). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PrettyPrinterAbstract.pArray (cyclomatic 60), NameResolver.enterNode (cyclomatic 51), ParserAbstract.doParse (cyclomatic 43). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cyclomatic Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
24 method(s) exceeded the cognitive complexity threshold of 15; the worst was PrettyPrinterAbstract.pArray at 142.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with PrettyPrinterAbstract.pArray (cognitive 142), ParserAbstract.doParse (cognitive 104), NodeDumper.dumpRecursive (cognitive 78). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 5.7 to about 6.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
18 god class(es) detected.
What to do
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with Php8.php, Php7.php, PrettyPrinterAbstract.php. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with Php8.php, Php7.php, PrettyPrinterAbstract.php. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with Php8.php, Php7.php, PrettyPrinterAbstract.php. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 1.6 % of the production lines (356 of 22,236) are in a reported copy. A further 10 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 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with Standard.php (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with AttributeEmulator.php, PrettyPrinterAbstract.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with VoidCastEmulator.php, AsymmetricVisibilityTokenEmulator.php. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 33 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ParserAbstract.php. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
2 skipped (2 with a documented reason), 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 306 tests.
What to do
- Resolve the 2 No assertions finding(s) in Test Quality — start with PrettyPrinterTest.php (2). — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is test_old/run.php. Counted over 56 of the 278 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
14 deducted task-comment markers across 22236 LoC (0.1/KLoC) → score 9.9. 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.
What to do
- Resolve the 13 TodoComment finding(s) in Explicit Debt — start with PrettyPrinterAbstract.php (10), Comment.php, AttributeEmulator.php. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with PrettyPrinterAbstract.php. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 16 document(s) read across 1 unit(s).
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 composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Composer) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
35 % of calls cross a namespace and 1 % go through an interface, but 44 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
13 finding(s): 0 critical, 13 high, 0 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
4 of 56 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is grammar/phpyLang.php. Counted over 56 of the 278 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Php7.php↔Php8.php 88%; DNumber.php↔LNumber.php 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with Php7.php, DNumber.php. — One of this dimension's main actionable groups (2 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
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
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
- `tokenize` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `xdebug.scream` ini setting (changed at line 29, put back at line 35) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — lib/PhpParser/Lexer.php:24
What to do
- Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a `cwd` and `env` passed to Symfony `Process` or `proc_open`, an absolute path, or an explicit `DateTimeZone`/locale/encoding argument is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move (an error handler around a call that warns), a `try`/`finally` is the least that makes the restore unconditional.
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
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 | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 92% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 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 applicable: this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- 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.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed PHP surface was not measured.
- 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. 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, 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
- 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 (composer.json — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- 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 (composer.json — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- 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 and Scala, 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
- P7 Outbound HTTP resilience — 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
- 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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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
- 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
- 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.
- X27 Collection changed while being enumerated — 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
- X29 Per-element action decided by a fixed element — 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
- 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 — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 97 finding(s)
- TodoComment lib/PhpParser/Comment.php:200
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:581
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:814
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:865
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:975
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:998
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:1491
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:1520
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:1538
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:1641
- TodoComment lib/PhpParser/PrettyPrinterAbstract.php:1719
- TodoComment lib/PhpParser/Lexer/TokenEmulator/AttributeEmulator.php:35
- TodoComment lib/PhpParser/Internal/TokenStream.php:233
- MethodTooLong: Php8.initReduceCallbacks lib/PhpParser/Parser/Php8.php:1276
- MethodTooLong: Php7.initReduceCallbacks lib/PhpParser/Parser/Php7.php:1259
- MethodTooLong: PrettyPrinterAbstract.pArray lib/PhpParser/PrettyPrinterAbstract.php:785
- MethodTooLong: NameResolver.enterNode lib/PhpParser/NodeVisitor/NameResolver.php:55
- MethodTooLong: ParserAbstract.doParse lib/PhpParser/ParserAbstract.php:229
- ClassTooLong: Php8 lib/PhpParser/Parser/Php8.php:19
- ClassTooLong: Php7 lib/PhpParser/Parser/Php7.php:19
- ClassTooLong: PrettyPrinterAbstract lib/PhpParser/PrettyPrinterAbstract.php:22
- ClassTooLong: Standard lib/PhpParser/PrettyPrinter/Standard.php:16
- ClassTooLong: ParserAbstract lib/PhpParser/ParserAbstract.php:39
- FileTooLong: Parser/Php8.php lib/PhpParser/Parser/Php8.php
- FileTooLong: Parser/Php7.php lib/PhpParser/Parser/Php7.php
- FileTooLong: PhpParser/PrettyPrinterAbstract.php lib/PhpParser/PrettyPrinterAbstract.php
- FileTooLong: PhpParser/ParserAbstract.php lib/PhpParser/ParserAbstract.php
- FileTooLong: PrettyPrinter/Standard.php lib/PhpParser/PrettyPrinter/Standard.php
- TooManyMethods: Standard lib/PhpParser/PrettyPrinter/Standard.php:16
- TooManyMethods: ParserAbstract lib/PhpParser/ParserAbstract.php:39
- TooManyMethods: PrettyPrinterAbstract lib/PhpParser/PrettyPrinterAbstract.php:22
- No assertions: testPrettyPrint test/PhpParser/PrettyPrinterTest.php:40
- No assertions: testPrettyPrintFile test/PhpParser/PrettyPrinterTest.php:47
- Change coupling: Php7.php ↔ Php8.php lib/PhpParser/Parser/Php7.php:1
- Change coupling: DNumber.php ↔ LNumber.php lib/PhpParser/Node/Scalar/DNumber.php:1
- Edited copy of a member (7 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php:677
- Edited copy of a member (7 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php:592
- Edited copy of a member (10 corresponding lines) lib/PhpParser/Lexer/TokenEmulator/AttributeEmulator.php:20
- Edited copy of a member (10 corresponding lines) lib/PhpParser/PrettyPrinterAbstract.php:393
- Duplicated block (6 lines × 2) lib/PhpParser/Lexer/TokenEmulator/VoidCastEmulator.php:26
- Duplicated block (6 lines × 2) lib/PhpParser/Lexer/TokenEmulator/AsymmetricVisibilityTokenEmulator.php:73
- Duplicated block (10 lines × 2) lib/PhpParser/Node/Stmt/Goto_.php:19
- Duplicated block (10 lines × 2) lib/PhpParser/Error.php:149
- PrettyPrinterAbstract.pArray (cyclomatic 60) lib/PhpParser/PrettyPrinterAbstract.php:785
- NameResolver.enterNode (cyclomatic 51) lib/PhpParser/NodeVisitor/NameResolver.php:55
- ParserAbstract.doParse (cyclomatic 43) lib/PhpParser/ParserAbstract.php:229
- NodeDumper.dumpRecursive (cyclomatic 37) lib/PhpParser/NodeDumper.php:69
- PrettyPrinterAbstract.p (cyclomatic 32) lib/PhpParser/PrettyPrinterAbstract.php:604
- PrettyPrinterAbstract.pFixup (cyclomatic 27) lib/PhpParser/PrettyPrinterAbstract.php:1063
- NodeTraverser.traverseArray (cyclomatic 24) lib/PhpParser/NodeTraverser.php:181
- Php7.initReduceCallbacks (cyclomatic 22) lib/PhpParser/Parser/Php7.php:1259
- Php8.initReduceCallbacks (cyclomatic 22) lib/PhpParser/Parser/Php8.php:1276
- NodeTraverser.traverseNode (cyclomatic 20) lib/PhpParser/NodeTraverser.php:93
- TokenPolyfill.tokenize (cyclomatic 19) lib/PhpParser/Internal/TokenPolyfill.php:124
- FixmeComment lib/PhpParser/PrettyPrinterAbstract.php:62
- PrettyPrinterAbstract.pArray (cognitive 142) lib/PhpParser/PrettyPrinterAbstract.php:785
- ParserAbstract.doParse (cognitive 104) lib/PhpParser/ParserAbstract.php:229
- NodeDumper.dumpRecursive (cognitive 78) lib/PhpParser/NodeDumper.php:69
- PrettyPrinterAbstract.p (cognitive 63) lib/PhpParser/PrettyPrinterAbstract.php:604
- TokenPolyfill.tokenize (cognitive 59) lib/PhpParser/Internal/TokenPolyfill.php:124
- NameResolver.enterNode (cognitive 50) lib/PhpParser/NodeVisitor/NameResolver.php:55
- NodeTraverser.traverseArray (cognitive 34) lib/PhpParser/NodeTraverser.php:181
- NodeTraverser.traverseNode (cognitive 33) lib/PhpParser/NodeTraverser.php:93
- Php7.initReduceCallbacks (cognitive 31) lib/PhpParser/Parser/Php7.php:1259
- Php8.initReduceCallbacks (cognitive 31) lib/PhpParser/Parser/Php8.php:1276
- ParserAbstract.handleNamespaces (cognitive 28) lib/PhpParser/ParserAbstract.php:591
- PrettyPrinterAbstract.pFixup (cognitive 28) lib/PhpParser/PrettyPrinterAbstract.php:1063
- Standard.pScalar_String (cognitive 26) lib/PhpParser/PrettyPrinter/Standard.php:143
- ParserAbstract.parseDocString (cognitive 25) lib/PhpParser/ParserAbstract.php:866
- NameContext.getPossibleNames (cognitive 21) lib/PhpParser/NameContext.php:156
- ParserAbstract.getNamespacingStyle (cognitive 21) lib/PhpParser/ParserAbstract.php:688
- CommentAnnotatingVisitor.enterNode (cognitive 20) lib/PhpParser/NodeVisitor/CommentAnnotatingVisitor.php:36
- Differ.calculateTrace (cognitive 18) lib/PhpParser/Internal/Differ.php:62
- Differ.coalesceReplacements (cognitive 18) lib/PhpParser/Internal/Differ.php:142
- Emulative.fixupTokens (cognitive 18) lib/PhpParser/Lexer/Emulative.php:131
- VoidCastEmulator.emulate (cognitive 18) lib/PhpParser/Lexer/TokenEmulator/VoidCastEmulator.php:17
- ParserAbstract.getExpectedTokens (cognitive 18) lib/PhpParser/ParserAbstract.php:476
- BuilderHelpers.normalizeValue (cognitive 17) lib/PhpParser/BuilderHelpers.php:222
- TokenPolyfill.is (cognitive 17) lib/PhpParser/Internal/TokenPolyfill.php:69
- REDACTED
- Edited copies of one member (3 members, 15+ corresponding lines) lib/PhpParser/Builder/Class_.php:107
- Edited copy of a member (8 corresponding lines) lib/PhpParser/Node/Expr/Closure.php:48
- Edited copy of a member (5 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php:808
- Edited copies of one member (4 members, 7+ corresponding lines) lib/PhpParser/Node/PropertyHook.php:45
- Edited copy of a member (3 corresponding lines) lib/PhpParser/PrettyPrinter/Standard.php:919
- Edited copy of a member (4 corresponding lines) lib/PhpParser/Node/Stmt/Interface_.php:26
- Duplicated block (22 lines × 2) lib/PhpParser/NodeTraverser.php:130
- Duplicated block (11 lines × 3) lib/PhpParser/Builder/Class_.php:111
- Duplicated block (9 lines × 2) lib/PhpParser/NodeTraverser.php:119
- Duplicated block (8 lines × 2) lib/PhpParser/NodeVisitor/NodeConnectingVisitor.php:42
- Duplicated block (16 lines × 2) lib/PhpParser/Node/Expr/MethodCall.php:29
- Duplicated block (11 lines × 2) lib/PhpParser/Node/Expr/NullsafePropertyFetch.php:23
- Duplicated block (5 lines × 2) lib/PhpParser/Node/Arg.php:30
- Low cohesion: ParserAbstract (LCOM4 10) lib/PhpParser/ParserAbstract.php:39
- Coverage collected but not gated
- No structured logging
- Process-global state is restored only on the happy path lib/PhpParser/Lexer.php:24
Minor — 13 finding(s)
- Orphaned file grammar/phpyLang.php:1
- Orphaned file lib/PhpParser/Builder/TraitUseAdaptation.php:1
- Orphaned file lib/PhpParser/Builder/ClassConst.php:1
- Orphaned file lib/PhpParser/Builder/Enum_.php:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found composer.json:39
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- PHP static analysis does not check null everywhere
Minor — 2 finding(s)
- Skipped (documented): testNormalizeValueEnum test/PhpParser/BuilderHelpersTest.php:227
- Skipped (documented): testError test/PhpParser/LexerTest.php:16
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 --report-format json --report-path /tmp/watchdog-gitleaks-af25837e7c35491190c3e64bdae92296/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.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-af25837e7c35491190c3e64bdae92296/tree.json --exit-code 0 --source . | 0 | 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 . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): 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 (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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. | 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 (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): 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 (composer.json — not scanned yet). | 0 | — |