Executive summary
zao111222333/liberty-db falls short of our standard for a preview release because 34 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 55.8 out of 100 and is rated Adequate, and all 43 of its critical findings are security problems.
Maturity, at 43.8, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 34 files no active contributor knows, worth about 10.8 points. Recording design decisions comes next, worth about 8.1 points. Raising Maturity to 62 would lift the score to about 60.9.
Thirty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and two weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, limiting each secret to its own step and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and giving the pull-request workflow read-only access would deal with the pipeline that outsiders can trigger with write access.
The product code is 25,948 lines, about €27,000 to rebuild.
If Maturity rose from 43.8 to 62, the lowest score rated Strong, the score would rise from 55.8 to about 60.9.
Rebuild cost: about €27,000 · Estimate
| Cost to rebuild | €8,900 to €45,000, for 148 to 469 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 56. 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: 25,948 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 dev | 2 dev_utils | 3 docs | 4 docs.static | 5 docs.static.js | 6 liberty2json | 7 liberty2json.ast | 8 liberty2json.parser.attribute_parser | 9 liberty2json.parser.base | 10 liberty2json.parser.cell_parser | 11 liberty_db.ast.fmt | 12 liberty_macros.attribute | 13 dev._impl_bench | 14 liberty_db.common.char_config | 15 liberty_db.common.items | 16 liberty_db.expression.boolean_expression | 17 liberty_db.expression.boolean_expression.logic | 18 liberty_macros.group | 19 liberty_db.pin.items | 20 liberty_db.cell.items | 21 liberty_db.cell | 22 liberty_db.ast | 23 liberty_db.ast.parser | 24 liberty_db.expression.boolean_expression.latch_ff | 25 liberty_db.expression.formula | 26 liberty_db.expression.sdf | 27 liberty_db.internal_power | 28 liberty_db.table | 29 liberty_db.timing.items | 30 liberty_db.timing.timing_type | 31 liberty_db.units | 32 liberty_db.ccsn | 33 liberty_db.common.demo | 34 liberty_db.library.items | 35 liberty_db.library | 36 liberty_db.pin | 37 liberty_db.pin.bus | 38 liberty_db.timing | 39 liberty_db.timing.impls | 40 liberty_db.library.test |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 dev | ||||||||||||||||||||||||||||||||||||||||
| 2 dev_utils | ||||||||||||||||||||||||||||||||||||||||
| 3 docs | ||||||||||||||||||||||||||||||||||||||||
| 4 docs.static | ||||||||||||||||||||||||||||||||||||||||
| 5 docs.static.js | ||||||||||||||||||||||||||||||||||||||||
| 6 liberty2json | ||||||||||||||||||||||||||||||||||||||||
| 7 liberty2json.ast | ||||||||||||||||||||||||||||||||||||||||
| 8 liberty2json.parser.attribute_parser | ||||||||||||||||||||||||||||||||||||||||
| 9 liberty2json.parser.base | ||||||||||||||||||||||||||||||||||||||||
| 10 liberty2json.parser.cell_parser | ||||||||||||||||||||||||||||||||||||||||
| 11 liberty_db.ast.fmt | ||||||||||||||||||||||||||||||||||||||||
| 12 liberty_macros.attribute | ||||||||||||||||||||||||||||||||||||||||
| 13 dev._impl_bench | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 liberty_db.common.char_config | 4 | 18 | ||||||||||||||||||||||||||||||||||||||
| 15 liberty_db.common.items | 3 | 14 | ||||||||||||||||||||||||||||||||||||||
| 16 liberty_db.expression.boolean_expression | 3 | 12 | ||||||||||||||||||||||||||||||||||||||
| 17 liberty_db.expression.boolean_expression.logic | 2 | 9 | ||||||||||||||||||||||||||||||||||||||
| 18 liberty_macros.group | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 liberty_db.pin.items | 12 | 2 | 56 | |||||||||||||||||||||||||||||||||||||
| 20 liberty_db.cell.items | 9 | 3 | 9 | 1 | 1 | 65 | ||||||||||||||||||||||||||||||||||
| 21 liberty_db.cell | 1 | 1 | 7 | 4 | ||||||||||||||||||||||||||||||||||||
| 22 liberty_db.ast | 10 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 liberty_db.ast.parser | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 liberty_db.expression.boolean_expression.latch_ff | 1 | 10 | 8 | |||||||||||||||||||||||||||||||||||||
| 25 liberty_db.expression.formula | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 26 liberty_db.expression.sdf | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 27 liberty_db.internal_power | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 liberty_db.table | 8 | 7 | 72 | |||||||||||||||||||||||||||||||||||||
| 29 liberty_db.timing.items | 2 | 1 | 1 | 11 | ||||||||||||||||||||||||||||||||||||
| 30 liberty_db.timing.timing_type | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 31 liberty_db.units | 6 | 24 | ||||||||||||||||||||||||||||||||||||||
| 32 liberty_db.ccsn | 2 | 2 | 13 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 liberty_db.common.demo | 1 | 1 | 9 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 liberty_db.library.items | 12 | 1 | 66 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 35 liberty_db.library | 1 | 3 | 6 | 3 | ||||||||||||||||||||||||||||||||||||
| 36 liberty_db.pin | 1 | 1 | 3 | 1 | 13 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 37 liberty_db.pin.bus | 3 | 15 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 liberty_db.timing | 1 | 2 | 2 | 3 | 1 | 2 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 39 liberty_db.timing.impls | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 liberty_db.library.test | 1 |
13→1 dev._impl_bench uses dev✕
- Connections
- 2 pairs of types, where a type in dev._impl_bench uses a type in dev.
- The types involved
dev._impl_bench.OpenTimerLibrary→dev.ProjLibrarydev._impl_bench.Si2drLibertyLibrary→dev.ProjLibrary
- Direction
- dev._impl_bench uses dev, so a change to dev can break dev._impl_bench, while a change to dev._impl_bench can't break dev.
- Position
- Below the diagonal: dev._impl_bench uses a module listed above it, which is the healthy direction.
14→11 liberty_db.common.char_config uses liberty_db.ast.fmt✕
- Connections
- 4 pairs of types, where a type in liberty_db.common.char_config uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.common.char_config.CharModeMethod→liberty_db.ast.fmt.CodeFormatterliberty_db.common.char_config.CharModeValue→liberty_db.ast.fmt.CodeFormatterliberty_db.common.char_config.InternalPowerCalculation→liberty_db.ast.fmt.CodeFormatterliberty_db.common.char_config.ThreeStateDisableMeasurementMethod→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.common.char_config uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.common.char_config, while a change to liberty_db.common.char_config can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.common.char_config uses a module listed above it, which is the healthy direction.
14→22 liberty_db.common.char_config uses liberty_db.ast part of a loop✕
- Connections
- 18 pairs of types, where a type in liberty_db.common.char_config uses a type in liberty_db.ast.
- The types involved
liberty_db.common.char_config.CharConfig→liberty_db.ast.GroupCommentsliberty_db.common.char_config.CharConfig→liberty_db.ast.GroupFnliberty_db.common.char_config.CharModeMethod→liberty_db.ast.BuilderScopeliberty_db.common.char_config.CharModeMethod→liberty_db.ast.ComplexAttriliberty_db.common.char_config.CharModeMethod→liberty_db.ast.ParseScopeliberty_db.common.char_config.CharModeMethod→liberty_db.ast.ParsingBuilderliberty_db.common.char_config.CharModeValue→liberty_db.ast.BuilderScopeliberty_db.common.char_config.CharModeValue→liberty_db.ast.ComplexAttriliberty_db.common.char_config.CharModeValue→liberty_db.ast.ParseScopeliberty_db.common.char_config.CharModeValue→liberty_db.ast.ParsingBuilderliberty_db.common.char_config.InternalPowerCalculation→liberty_db.ast.BuilderScopeliberty_db.common.char_config.InternalPowerCalculation→liberty_db.ast.ParseScopeliberty_db.common.char_config.InternalPowerCalculation→liberty_db.ast.ParsingBuilderliberty_db.common.char_config.InternalPowerCalculation→liberty_db.ast.SimpleAttriliberty_db.common.char_config.ThreeStateDisableMeasurementMethod→liberty_db.ast.BuilderScopeliberty_db.common.char_config.ThreeStateDisableMeasurementMethod→liberty_db.ast.ParseScopeliberty_db.common.char_config.ThreeStateDisableMeasurementMethod→liberty_db.ast.ParsingBuilderliberty_db.common.char_config.ThreeStateDisableMeasurementMethod→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.common.char_config uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.common.char_config, while a change to liberty_db.common.char_config can't break liberty_db.ast.
- 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.
15→11 liberty_db.common.items uses liberty_db.ast.fmt✕
- Connections
- 3 pairs of types, where a type in liberty_db.common.items uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.common.items.IdVector→liberty_db.ast.fmt.CodeFormatterliberty_db.common.items.SdfEdgeType→liberty_db.ast.fmt.CodeFormatterliberty_db.common.items.WordSet→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.common.items uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.common.items, while a change to liberty_db.common.items can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.common.items uses a module listed above it, which is the healthy direction.
15→22 liberty_db.common.items uses liberty_db.ast part of a loop✕
- Connections
- 14 pairs of types, where a type in liberty_db.common.items uses a type in liberty_db.ast.
- The types involved
liberty_db.common.items.DummyGroup→liberty_db.ast.GroupCommentsliberty_db.common.items.DummyGroup→liberty_db.ast.GroupFnliberty_db.common.items.IdVector→liberty_db.ast.BuilderScopeliberty_db.common.items.IdVector→liberty_db.ast.ComplexAttriliberty_db.common.items.IdVector→liberty_db.ast.ParseScopeliberty_db.common.items.IdVector→liberty_db.ast.ParsingBuilderliberty_db.common.items.SdfEdgeType→liberty_db.ast.BuilderScopeliberty_db.common.items.SdfEdgeType→liberty_db.ast.ParseScopeliberty_db.common.items.SdfEdgeType→liberty_db.ast.ParsingBuilderliberty_db.common.items.SdfEdgeType→liberty_db.ast.SimpleAttriliberty_db.common.items.WordSet→liberty_db.ast.BuilderScopeliberty_db.common.items.WordSet→liberty_db.ast.ParseScopeliberty_db.common.items.WordSet→liberty_db.ast.ParsingBuilderliberty_db.common.items.WordSet→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.common.items uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.common.items, while a change to liberty_db.common.items can't break liberty_db.ast.
- 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.
16→11 liberty_db.expression.boolean_expression uses liberty_db.ast.fmt✕
- Connections
- 3 pairs of types, where a type in liberty_db.expression.boolean_expression uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.expression.boolean_expression.BooleanExpression→liberty_db.ast.fmt.CodeFormatterliberty_db.expression.boolean_expression.LogicBooleanExpression→liberty_db.ast.fmt.CodeFormatterliberty_db.expression.boolean_expression.PowerGroundBooleanExpression→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.expression.boolean_expression uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.expression.boolean_expression, while a change to liberty_db.expression.boolean_expression can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.expression.boolean_expression uses a module listed above it, which is the healthy direction.
16→22 liberty_db.expression.boolean_expression uses liberty_db.ast part of a loop✕
- Connections
- 12 pairs of types, where a type in liberty_db.expression.boolean_expression uses a type in liberty_db.ast.
- The types involved
liberty_db.expression.boolean_expression.BooleanExpression→liberty_db.ast.BuilderScopeliberty_db.expression.boolean_expression.BooleanExpression→liberty_db.ast.ParseScopeliberty_db.expression.boolean_expression.BooleanExpression→liberty_db.ast.ParsingBuilderliberty_db.expression.boolean_expression.BooleanExpression→liberty_db.ast.SimpleAttriliberty_db.expression.boolean_expression.LogicBooleanExpression→liberty_db.ast.BuilderScopeliberty_db.expression.boolean_expression.LogicBooleanExpression→liberty_db.ast.ParseScopeliberty_db.expression.boolean_expression.LogicBooleanExpression→liberty_db.ast.ParsingBuilderliberty_db.expression.boolean_expression.LogicBooleanExpression→liberty_db.ast.SimpleAttriliberty_db.expression.boolean_expression.PowerGroundBooleanExpression→liberty_db.ast.BuilderScopeliberty_db.expression.boolean_expression.PowerGroundBooleanExpression→liberty_db.ast.ParseScopeliberty_db.expression.boolean_expression.PowerGroundBooleanExpression→liberty_db.ast.ParsingBuilderliberty_db.expression.boolean_expression.PowerGroundBooleanExpression→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.expression.boolean_expression uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.expression.boolean_expression, while a change to liberty_db.expression.boolean_expression can't break liberty_db.ast.
- 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.
17→11 liberty_db.expression.boolean_expression.logic uses liberty_db.ast.fmt✕
- Connections
- 2 pairs of types, where a type in liberty_db.expression.boolean_expression.logic uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.expression.boolean_expression.logic.Edge→liberty_db.ast.fmt.CodeFormatterliberty_db.expression.boolean_expression.logic.Normal→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.expression.boolean_expression.logic uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.expression.boolean_expression.logic, while a change to liberty_db.expression.boolean_expression.logic can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.expression.boolean_expression.logic uses a module listed above it, which is the healthy direction.
17→22 liberty_db.expression.boolean_expression.logic uses liberty_db.ast part of a loop✕
- Connections
- 9 pairs of types, where a type in liberty_db.expression.boolean_expression.logic uses a type in liberty_db.ast.
- The types involved
liberty_db.expression.boolean_expression.logic.Edge→liberty_db.ast.BuilderScopeliberty_db.expression.boolean_expression.logic.Edge→liberty_db.ast.ComplexAttriliberty_db.expression.boolean_expression.logic.Edge→liberty_db.ast.ParseScopeliberty_db.expression.boolean_expression.logic.Edge→liberty_db.ast.ParsingBuilderliberty_db.expression.boolean_expression.logic.Edge→liberty_db.ast.SimpleAttriliberty_db.expression.boolean_expression.logic.Normal→liberty_db.ast.BuilderScopeliberty_db.expression.boolean_expression.logic.Normal→liberty_db.ast.ParseScopeliberty_db.expression.boolean_expression.logic.Normal→liberty_db.ast.ParsingBuilderliberty_db.expression.boolean_expression.logic.Normal→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.expression.boolean_expression.logic uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.expression.boolean_expression.logic, while a change to liberty_db.expression.boolean_expression.logic can't break liberty_db.ast.
- 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.
18→12 liberty_macros.group uses liberty_macros.attribute✕
- Connections
- 1 pair of types, where a type in liberty_macros.group uses a type in liberty_macros.attribute.
- The types involved
liberty_macros.group.group$module→liberty_macros.attribute.AttriType
- Direction
- liberty_macros.group uses liberty_macros.attribute, so a change to liberty_macros.attribute can break liberty_macros.group, while a change to liberty_macros.group can't break liberty_macros.attribute.
- Position
- Below the diagonal: liberty_macros.group uses a module listed above it, which is the healthy direction.
19→11 liberty_db.pin.items uses liberty_db.ast.fmt✕
- Connections
- 12 pairs of types, where a type in liberty_db.pin.items uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.pin.items.AllDriverType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.AntennaDiodeType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.Direction→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.DontFault→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.NextstateType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.OneZero→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.PinFuncType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.RestoreEdgeType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.RetentionPin→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.SignalType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.SlewControl→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.items.TwoValue→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.pin.items uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.pin.items, while a change to liberty_db.pin.items can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.pin.items uses a module listed above it, which is the healthy direction.
19→17 liberty_db.pin.items uses liberty_db.expression.boolean_expression.logic✕
- Connections
- 2 pairs of types, where a type in liberty_db.pin.items uses a type in liberty_db.expression.boolean_expression.logic.
- The types involved
liberty_db.pin.items.RetentionPin→liberty_db.expression.boolean_expression.logic.Staticliberty_db.pin.items.TLatch→liberty_db.expression.boolean_expression.logic.Edge
- Direction
- liberty_db.pin.items uses liberty_db.expression.boolean_expression.logic, so a change to liberty_db.expression.boolean_expression.logic can break liberty_db.pin.items, while a change to liberty_db.pin.items can't break liberty_db.expression.boolean_expression.logic.
- Position
- Below the diagonal: liberty_db.pin.items uses a module listed above it, which is the healthy direction.
19→22 liberty_db.pin.items uses liberty_db.ast part of a loop✕
- Connections
- 56 pairs of types, where a type in liberty_db.pin.items uses a type in liberty_db.ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
liberty_db.pin.items.AllDriverType→liberty_db.ast.BuilderScopeliberty_db.pin.items.AllDriverType→liberty_db.ast.ParseScopeliberty_db.pin.items.AllDriverType→liberty_db.ast.ParsingBuilderliberty_db.pin.items.AllDriverType→liberty_db.ast.SimpleAttriliberty_db.pin.items.AntennaDiodeType→liberty_db.ast.BuilderScopeliberty_db.pin.items.AntennaDiodeType→liberty_db.ast.ParseScopeliberty_db.pin.items.AntennaDiodeType→liberty_db.ast.ParsingBuilderliberty_db.pin.items.AntennaDiodeType→liberty_db.ast.SimpleAttriliberty_db.pin.items.Direction→liberty_db.ast.BuilderScopeliberty_db.pin.items.Direction→liberty_db.ast.ParseScopeliberty_db.pin.items.Direction→liberty_db.ast.ParsingBuilderliberty_db.pin.items.Direction→liberty_db.ast.SimpleAttriliberty_db.pin.items.DontFault→liberty_db.ast.BuilderScopeliberty_db.pin.items.DontFault→liberty_db.ast.ParseScopeliberty_db.pin.items.DontFault→liberty_db.ast.ParsingBuilderliberty_db.pin.items.DontFault→liberty_db.ast.SimpleAttriliberty_db.pin.items.HyperbolicNoise→liberty_db.ast.GroupCommentsliberty_db.pin.items.HyperbolicNoise→liberty_db.ast.GroupFnliberty_db.pin.items.MemoryRead→liberty_db.ast.GroupCommentsliberty_db.pin.items.MemoryRead→liberty_db.ast.GroupFnliberty_db.pin.items.MemoryWrite→liberty_db.ast.GroupCommentsliberty_db.pin.items.MemoryWrite→liberty_db.ast.GroupFnliberty_db.pin.items.NextstateType→liberty_db.ast.BuilderScopeliberty_db.pin.items.NextstateType→liberty_db.ast.ParseScopeliberty_db.pin.items.NextstateType→liberty_db.ast.ParsingBuilder
- Direction
- liberty_db.pin.items uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.pin.items, while a change to liberty_db.pin.items can't break liberty_db.ast.
- 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.
20→11 liberty_db.cell.items uses liberty_db.ast.fmt✕
- Connections
- 9 pairs of types, where a type in liberty_db.cell.items uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.cell.items.ClockGatingIntegratedCell→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.FpgaCellType→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.LevelShifterType→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.MemoryType→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.PgType→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.PinOpposite→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.Statetable→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.SwitchCellType→liberty_db.ast.fmt.CodeFormatterliberty_db.cell.items.Table→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.cell.items uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.cell.items, while a change to liberty_db.cell.items can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.cell.items uses a module listed above it, which is the healthy direction.
20→15 liberty_db.cell.items uses liberty_db.common.items✕
- Connections
- 3 pairs of types, where a type in liberty_db.cell.items uses a type in liberty_db.common.items.
- The types involved
liberty_db.cell.items.DynamicCurrent→liberty_db.common.items.WordSetliberty_db.cell.items.LeakagePower→liberty_db.common.items.WordSetliberty_db.cell.items.PinOpposite→liberty_db.common.items.WordSet
- Direction
- liberty_db.cell.items uses liberty_db.common.items, so a change to liberty_db.common.items can break liberty_db.cell.items, while a change to liberty_db.cell.items can't break liberty_db.common.items.
- Position
- Below the diagonal: liberty_db.cell.items uses a module listed above it, which is the healthy direction.
20→16 liberty_db.cell.items uses liberty_db.expression.boolean_expression✕
- Connections
- 9 pairs of types, where a type in liberty_db.cell.items uses a type in liberty_db.expression.boolean_expression.
- The types involved
liberty_db.cell.items.DynamicCurrent→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.cell.items.IntrinsicParasitic→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.cell.items.LeakageCurrent→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.cell.items.LeakagePower→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.cell.items.PgPin→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.cell.items.PgPin→liberty_db.expression.boolean_expression.PowerGroundBooleanExpressionliberty_db.cell.items.RetentionCondition→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.cell.items.RetentionCondition→liberty_db.expression.boolean_expression.PowerGroundBooleanExpressionliberty_db.cell.items.RresetCondition→liberty_db.expression.boolean_expression.LogicBooleanExpression
- Direction
- liberty_db.cell.items uses liberty_db.expression.boolean_expression, so a change to liberty_db.expression.boolean_expression can break liberty_db.cell.items, while a change to liberty_db.cell.items can't break liberty_db.expression.boolean_expression.
- Position
- Below the diagonal: liberty_db.cell.items uses a module listed above it, which is the healthy direction.
20→17 liberty_db.cell.items uses liberty_db.expression.boolean_expression.logic✕
- Connections
- 1 pair of types, where a type in liberty_db.cell.items uses a type in liberty_db.expression.boolean_expression.logic.
- The types involved
liberty_db.cell.items.SwitchingGroup→liberty_db.expression.boolean_expression.logic.Edge
- Direction
- liberty_db.cell.items uses liberty_db.expression.boolean_expression.logic, so a change to liberty_db.expression.boolean_expression.logic can break liberty_db.cell.items, while a change to liberty_db.cell.items can't break liberty_db.expression.boolean_expression.logic.
- Position
- Below the diagonal: liberty_db.cell.items uses a module listed above it, which is the healthy direction.
20→19 liberty_db.cell.items uses liberty_db.pin.items✕
- Connections
- 1 pair of types, where a type in liberty_db.cell.items uses a type in liberty_db.pin.items.
- The types involved
liberty_db.cell.items.PgPin→liberty_db.pin.items.Direction
- Direction
- liberty_db.cell.items uses liberty_db.pin.items, so a change to liberty_db.pin.items can break liberty_db.cell.items, while a change to liberty_db.cell.items can't break liberty_db.pin.items.
- Position
- Below the diagonal: liberty_db.cell.items uses a module listed above it, which is the healthy direction.
20→22 liberty_db.cell.items uses liberty_db.ast part of a loop✕
- Connections
- 65 pairs of types, where a type in liberty_db.cell.items uses a type in liberty_db.ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
liberty_db.cell.items.ClockGatingIntegratedCell→liberty_db.ast.BuilderScopeliberty_db.cell.items.ClockGatingIntegratedCell→liberty_db.ast.ParseScopeliberty_db.cell.items.ClockGatingIntegratedCell→liberty_db.ast.ParsingBuilderliberty_db.cell.items.ClockGatingIntegratedCell→liberty_db.ast.SimpleAttriliberty_db.cell.items.DynamicCurrent→liberty_db.ast.GroupCommentsliberty_db.cell.items.DynamicCurrent→liberty_db.ast.GroupFnliberty_db.cell.items.FpgaCellType→liberty_db.ast.BuilderScopeliberty_db.cell.items.FpgaCellType→liberty_db.ast.ParseScopeliberty_db.cell.items.FpgaCellType→liberty_db.ast.ParsingBuilderliberty_db.cell.items.FpgaCellType→liberty_db.ast.SimpleAttriliberty_db.cell.items.GateLeakage→liberty_db.ast.GroupCommentsliberty_db.cell.items.GateLeakage→liberty_db.ast.GroupFnliberty_db.cell.items.IntrinsicCapacitance→liberty_db.ast.GroupCommentsliberty_db.cell.items.IntrinsicCapacitance→liberty_db.ast.GroupFnliberty_db.cell.items.IntrinsicParasitic→liberty_db.ast.GroupCommentsliberty_db.cell.items.IntrinsicParasitic→liberty_db.ast.GroupFnliberty_db.cell.items.IntrinsicResistance→liberty_db.ast.GroupCommentsliberty_db.cell.items.IntrinsicResistance→liberty_db.ast.GroupFnliberty_db.cell.items.LeakageCurrent→liberty_db.ast.GroupCommentsliberty_db.cell.items.LeakageCurrent→liberty_db.ast.GroupFnliberty_db.cell.items.LeakagePower→liberty_db.ast.GroupCommentsliberty_db.cell.items.LeakagePower→liberty_db.ast.GroupFnliberty_db.cell.items.LevelShifterType→liberty_db.ast.BuilderScopeliberty_db.cell.items.LevelShifterType→liberty_db.ast.ParseScopeliberty_db.cell.items.LevelShifterType→liberty_db.ast.ParsingBuilder
- Direction
- liberty_db.cell.items uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.cell.items, while a change to liberty_db.cell.items can't break liberty_db.ast.
- 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.
21→14 liberty_db.cell uses liberty_db.common.char_config✕
- Connections
- 1 pair of types, where a type in liberty_db.cell uses a type in liberty_db.common.char_config.
- The types involved
liberty_db.cell.Cell→liberty_db.common.char_config.CharConfig
- Direction
- liberty_db.cell uses liberty_db.common.char_config, so a change to liberty_db.common.char_config can break liberty_db.cell, while a change to liberty_db.cell can't break liberty_db.common.char_config.
- Position
- Below the diagonal: liberty_db.cell uses a module listed above it, which is the healthy direction.
21→19 liberty_db.cell uses liberty_db.pin.items✕
- Connections
- 1 pair of types, where a type in liberty_db.cell uses a type in liberty_db.pin.items.
- The types involved
liberty_db.cell.Cell→liberty_db.pin.items.AntennaDiodeType
- Direction
- liberty_db.cell uses liberty_db.pin.items, so a change to liberty_db.pin.items can break liberty_db.cell, while a change to liberty_db.cell can't break liberty_db.pin.items.
- Position
- Below the diagonal: liberty_db.cell uses a module listed above it, which is the healthy direction.
21→20 liberty_db.cell uses liberty_db.cell.items✕
- Connections
- 7 pairs of types, where a type in liberty_db.cell uses a type in liberty_db.cell.items.
- The types involved
liberty_db.cell.Cell→liberty_db.cell.items.ClockGatingIntegratedCellliberty_db.cell.Cell→liberty_db.cell.items.FpgaCellTypeliberty_db.cell.Cell→liberty_db.cell.items.LevelShifterTypeliberty_db.cell.Cell→liberty_db.cell.items.Memoryliberty_db.cell.Cell→liberty_db.cell.items.PinOppositeliberty_db.cell.Cell→liberty_db.cell.items.Statetableliberty_db.cell.Cell→liberty_db.cell.items.SwitchCellType
- Direction
- liberty_db.cell uses liberty_db.cell.items, so a change to liberty_db.cell.items can break liberty_db.cell, while a change to liberty_db.cell can't break liberty_db.cell.items.
- Position
- Below the diagonal: liberty_db.cell uses a module listed above it, which is the healthy direction.
21→22 liberty_db.cell uses liberty_db.ast part of a loop✕
- Connections
- 4 pairs of types, where a type in liberty_db.cell uses a type in liberty_db.ast.
- The types involved
liberty_db.cell.Cell→liberty_db.ast.GroupCommentsliberty_db.cell.TestCell→liberty_db.ast.BuilderScopeliberty_db.cell.TestCell→liberty_db.ast.GroupCommentsliberty_db.cell.TestCell→liberty_db.ast.GroupFn
- Direction
- liberty_db.cell uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.cell, while a change to liberty_db.cell can't break liberty_db.ast.
- 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.
22→11 liberty_db.ast uses liberty_db.ast.fmt✕
- Connections
- 10 pairs of types, where a type in liberty_db.ast uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.ast.ComplexAttri→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.ComplexWrapper→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.FlattenNameAttri→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.Format→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.GroupAttri→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.GroupWrapper→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.NameAttri→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.NamedGroup→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.SimpleAttri→liberty_db.ast.fmt.CodeFormatterliberty_db.ast.ast$module→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.ast uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.ast, while a change to liberty_db.ast can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.ast uses a module listed above it, which is the healthy direction.
22→21 liberty_db.ast uses liberty_db.cell✕
- Connections
- 1 pair of types, where a type in liberty_db.ast uses a type in liberty_db.cell.
- The types involved
liberty_db.ast.BuilderScope→liberty_db.cell.DefaultCellCtx
- Direction
- liberty_db.ast uses liberty_db.cell, so a change to liberty_db.cell can break liberty_db.ast, while a change to liberty_db.ast can't break liberty_db.cell.
- Position
- Below the diagonal: liberty_db.ast uses a module listed above it, which is the healthy direction.
23→22 liberty_db.ast.parser uses liberty_db.ast✕
- Connections
- 1 pair of types, where a type in liberty_db.ast.parser uses a type in liberty_db.ast.
- The types involved
liberty_db.ast.parser.parser$module→liberty_db.ast.ParseScope
- Direction
- liberty_db.ast.parser uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.ast.parser, while a change to liberty_db.ast.parser can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.ast.parser uses a module listed above it, which is the healthy direction.
24→11 liberty_db.expression.boolean_expression.latch_ff uses liberty_db.ast.fmt✕
- Connections
- 1 pair of types, where a type in liberty_db.expression.boolean_expression.latch_ff uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.expression.boolean_expression.latch_ff.ClearPresetState→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.expression.boolean_expression.latch_ff uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.expression.boolean_expression.latch_ff, while a change to liberty_db.expression.boolean_expression.latch_ff can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.expression.boolean_expression.latch_ff uses a module listed above it, which is the healthy direction.
24→16 liberty_db.expression.boolean_expression.latch_ff uses liberty_db.expression.boolean_expression✕
- Connections
- 10 pairs of types, where a type in liberty_db.expression.boolean_expression.latch_ff uses a type in liberty_db.expression.boolean_expression.
- The types involved
liberty_db.expression.boolean_expression.latch_ff.FF→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.FF→liberty_db.expression.boolean_expression.PowerGroundBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.FFBank→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.FFBank→liberty_db.expression.boolean_expression.PowerGroundBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.Latch→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.Latch→liberty_db.expression.boolean_expression.PowerGroundBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.LatchBank→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.LatchBank→liberty_db.expression.boolean_expression.PowerGroundBooleanExpressionliberty_db.expression.boolean_expression.latch_ff.LatchFF→liberty_db.expression.boolean_expression.BooleanExpressionliberty_db.expression.boolean_expression.latch_ff.__LatchFF→liberty_db.expression.boolean_expression.LogicBooleanExpression
- Direction
- liberty_db.expression.boolean_expression.latch_ff uses liberty_db.expression.boolean_expression, so a change to liberty_db.expression.boolean_expression can break liberty_db.expression.boolean_expression.latch_ff, while a change to liberty_db.expression.boolean_expression.latch_ff can't break liberty_db.expression.boolean_expression.
- Position
- Below the diagonal: liberty_db.expression.boolean_expression.latch_ff uses a module listed above it, which is the healthy direction.
24→22 liberty_db.expression.boolean_expression.latch_ff uses liberty_db.ast✕
- Connections
- 8 pairs of types, where a type in liberty_db.expression.boolean_expression.latch_ff uses a type in liberty_db.ast.
- The types involved
liberty_db.expression.boolean_expression.latch_ff.ClearPresetState→liberty_db.ast.BuilderScopeliberty_db.expression.boolean_expression.latch_ff.ClearPresetState→liberty_db.ast.ParseScopeliberty_db.expression.boolean_expression.latch_ff.ClearPresetState→liberty_db.ast.ParsingBuilderliberty_db.expression.boolean_expression.latch_ff.ClearPresetState→liberty_db.ast.SimpleAttriliberty_db.expression.boolean_expression.latch_ff.FF→liberty_db.ast.GroupCommentsliberty_db.expression.boolean_expression.latch_ff.FFBank→liberty_db.ast.GroupCommentsliberty_db.expression.boolean_expression.latch_ff.Latch→liberty_db.ast.GroupCommentsliberty_db.expression.boolean_expression.latch_ff.LatchBank→liberty_db.ast.GroupComments
- Direction
- liberty_db.expression.boolean_expression.latch_ff uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.expression.boolean_expression.latch_ff, while a change to liberty_db.expression.boolean_expression.latch_ff can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.expression.boolean_expression.latch_ff uses a module listed above it, which is the healthy direction.
25→11 liberty_db.expression.formula uses liberty_db.ast.fmt✕
- Connections
- 1 pair of types, where a type in liberty_db.expression.formula uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.expression.formula.Formula→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.expression.formula uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.expression.formula, while a change to liberty_db.expression.formula can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.expression.formula uses a module listed above it, which is the healthy direction.
25→22 liberty_db.expression.formula uses liberty_db.ast✕
- Connections
- 4 pairs of types, where a type in liberty_db.expression.formula uses a type in liberty_db.ast.
- The types involved
liberty_db.expression.formula.Formula→liberty_db.ast.BuilderScopeliberty_db.expression.formula.Formula→liberty_db.ast.ParseScopeliberty_db.expression.formula.Formula→liberty_db.ast.ParsingBuilderliberty_db.expression.formula.Formula→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.expression.formula uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.expression.formula, while a change to liberty_db.expression.formula can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.expression.formula uses a module listed above it, which is the healthy direction.
26→11 liberty_db.expression.sdf uses liberty_db.ast.fmt✕
- Connections
- 1 pair of types, where a type in liberty_db.expression.sdf uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.expression.sdf.SdfExpression→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.expression.sdf uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.expression.sdf, while a change to liberty_db.expression.sdf can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.expression.sdf uses a module listed above it, which is the healthy direction.
26→22 liberty_db.expression.sdf uses liberty_db.ast✕
- Connections
- 4 pairs of types, where a type in liberty_db.expression.sdf uses a type in liberty_db.ast.
- The types involved
liberty_db.expression.sdf.SdfExpression→liberty_db.ast.BuilderScopeliberty_db.expression.sdf.SdfExpression→liberty_db.ast.ParseScopeliberty_db.expression.sdf.SdfExpression→liberty_db.ast.ParsingBuilderliberty_db.expression.sdf.SdfExpression→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.expression.sdf uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.expression.sdf, while a change to liberty_db.expression.sdf can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.expression.sdf uses a module listed above it, which is the healthy direction.
27→15 liberty_db.internal_power uses liberty_db.common.items✕
- Connections
- 1 pair of types, where a type in liberty_db.internal_power uses a type in liberty_db.common.items.
- The types involved
liberty_db.internal_power.InternalPower→liberty_db.common.items.WordSet
- Direction
- liberty_db.internal_power uses liberty_db.common.items, so a change to liberty_db.common.items can break liberty_db.internal_power, while a change to liberty_db.internal_power can't break liberty_db.common.items.
- Position
- Below the diagonal: liberty_db.internal_power uses a module listed above it, which is the healthy direction.
27→16 liberty_db.internal_power uses liberty_db.expression.boolean_expression✕
- Connections
- 1 pair of types, where a type in liberty_db.internal_power uses a type in liberty_db.expression.boolean_expression.
- The types involved
liberty_db.internal_power.InternalPower→liberty_db.expression.boolean_expression.LogicBooleanExpression
- Direction
- liberty_db.internal_power uses liberty_db.expression.boolean_expression, so a change to liberty_db.expression.boolean_expression can break liberty_db.internal_power, while a change to liberty_db.internal_power can't break liberty_db.expression.boolean_expression.
- Position
- Below the diagonal: liberty_db.internal_power uses a module listed above it, which is the healthy direction.
27→22 liberty_db.internal_power uses liberty_db.ast✕
- Connections
- 2 pairs of types, where a type in liberty_db.internal_power uses a type in liberty_db.ast.
- The types involved
liberty_db.internal_power.InternalPower→liberty_db.ast.GroupCommentsliberty_db.internal_power.InternalPower→liberty_db.ast.GroupFn
- Direction
- liberty_db.internal_power uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.internal_power, while a change to liberty_db.internal_power can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.internal_power uses a module listed above it, which is the healthy direction.
28→11 liberty_db.table uses liberty_db.ast.fmt✕
- Connections
- 8 pairs of types, where a type in liberty_db.table uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.table.DisplayTableLookUp→liberty_db.ast.fmt.CodeFormatterliberty_db.table.DisplayValues→liberty_db.ast.fmt.CodeFormatterliberty_db.table.SigmaType→liberty_db.ast.fmt.CodeFormatterliberty_db.table.Values→liberty_db.ast.fmt.CodeFormatterliberty_db.table.Variable→liberty_db.ast.fmt.CodeFormatterliberty_db.table.VariableTypeCompactLutTemplateIndex12→liberty_db.ast.fmt.CodeFormatterliberty_db.table.VariableTypeCompactLutTemplateIndex3→liberty_db.ast.fmt.CodeFormatterliberty_db.table.VariableTypePropagationLutTemplate→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.table uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.table, while a change to liberty_db.table can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.table uses a module listed above it, which is the healthy direction.
28→20 liberty_db.table uses liberty_db.cell.items✕
- Connections
- 7 pairs of types, where a type in liberty_db.table uses a type in liberty_db.cell.items.
- The types involved
liberty_db.table.OcvSigmaTable→liberty_db.cell.items.Tableliberty_db.table.ReferenceTimeVector3D→liberty_db.cell.items.Tableliberty_db.table.TableLookUp2D→liberty_db.cell.items.Tableliberty_db.table.TableLookUpDomain→liberty_db.cell.items.Tableliberty_db.table.TableLookUpMultiSegment→liberty_db.cell.items.Tableliberty_db.table.Vector3D→liberty_db.cell.items.Tableliberty_db.table.Vector4D→liberty_db.cell.items.Table
- Direction
- liberty_db.table uses liberty_db.cell.items, so a change to liberty_db.cell.items can break liberty_db.table, while a change to liberty_db.table can't break liberty_db.cell.items.
- Position
- Below the diagonal: liberty_db.table uses a module listed above it, which is the healthy direction.
28→22 liberty_db.table uses liberty_db.ast✕
- Connections
- 72 pairs of types, where a type in liberty_db.table uses a type in liberty_db.ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
liberty_db.table.CompactCcsPower→liberty_db.ast.BuilderScopeliberty_db.table.CompactCcsPower→liberty_db.ast.GroupCommentsliberty_db.table.CompactCcsPower→liberty_db.ast.GroupFnliberty_db.table.CompactCcsTable→liberty_db.ast.BuilderScopeliberty_db.table.CompactCcsTable→liberty_db.ast.GroupCommentsliberty_db.table.CompactCcsTable→liberty_db.ast.GroupFnliberty_db.table.CompactLutTemplate→liberty_db.ast.BuilderScopeliberty_db.table.CompactLutTemplate→liberty_db.ast.GroupCommentsliberty_db.table.CompactLutTemplate→liberty_db.ast.GroupFnliberty_db.table.DriverWaveform→liberty_db.ast.BuilderScopeliberty_db.table.DriverWaveform→liberty_db.ast.GroupCommentsliberty_db.table.DriverWaveform→liberty_db.ast.GroupFnliberty_db.table.OcvSigmaTable→liberty_db.ast.BuilderScopeliberty_db.table.OcvSigmaTable→liberty_db.ast.GroupCommentsliberty_db.table.OcvSigmaTable→liberty_db.ast.GroupFnliberty_db.table.PolyTemplateDomain→liberty_db.ast.GroupCommentsliberty_db.table.PolyTemplateDomain→liberty_db.ast.GroupFnliberty_db.table.PropagationLutTemplate→liberty_db.ast.BuilderScopeliberty_db.table.PropagationLutTemplate→liberty_db.ast.GroupCommentsliberty_db.table.PropagationLutTemplate→liberty_db.ast.GroupFnliberty_db.table.ReferenceTimeVector3D→liberty_db.ast.BuilderScopeliberty_db.table.ReferenceTimeVector3D→liberty_db.ast.GroupCommentsliberty_db.table.ReferenceTimeVector3D→liberty_db.ast.GroupFnliberty_db.table.ReferenceTimeVector3DGrpup→liberty_db.ast.GroupCommentsliberty_db.table.ReferenceTimeVector3DGrpup→liberty_db.ast.GroupFn
- Direction
- liberty_db.table uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.table, while a change to liberty_db.table can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.table uses a module listed above it, which is the healthy direction.
29→11 liberty_db.timing.items uses liberty_db.ast.fmt✕
- Connections
- 2 pairs of types, where a type in liberty_db.timing.items uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.timing.items.TimingSenseType→liberty_db.ast.fmt.CodeFormatterliberty_db.timing.items.TimingTableLookUp→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.timing.items uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.timing.items, while a change to liberty_db.timing.items can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.timing.items uses a module listed above it, which is the healthy direction.
29→17 liberty_db.timing.items uses liberty_db.expression.boolean_expression.logic✕
- Connections
- 1 pair of types, where a type in liberty_db.timing.items uses a type in liberty_db.expression.boolean_expression.logic.
- The types involved
liberty_db.timing.items.TimingSenseType→liberty_db.expression.boolean_expression.logic.Edge
- Direction
- liberty_db.timing.items uses liberty_db.expression.boolean_expression.logic, so a change to liberty_db.expression.boolean_expression.logic can break liberty_db.timing.items, while a change to liberty_db.timing.items can't break liberty_db.expression.boolean_expression.logic.
- Position
- Below the diagonal: liberty_db.timing.items uses a module listed above it, which is the healthy direction.
29→20 liberty_db.timing.items uses liberty_db.cell.items✕
- Connections
- 1 pair of types, where a type in liberty_db.timing.items uses a type in liberty_db.cell.items.
- The types involved
liberty_db.timing.items.TimingTableLookUp→liberty_db.cell.items.Table
- Direction
- liberty_db.timing.items uses liberty_db.cell.items, so a change to liberty_db.cell.items can break liberty_db.timing.items, while a change to liberty_db.timing.items can't break liberty_db.cell.items.
- Position
- Below the diagonal: liberty_db.timing.items uses a module listed above it, which is the healthy direction.
29→22 liberty_db.timing.items uses liberty_db.ast✕
- Connections
- 11 pairs of types, where a type in liberty_db.timing.items uses a type in liberty_db.ast.
- The types involved
liberty_db.timing.items.CellDegradation→liberty_db.ast.GroupCommentsliberty_db.timing.items.CellDegradation→liberty_db.ast.GroupFnliberty_db.timing.items.TimingSenseType→liberty_db.ast.BuilderScopeliberty_db.timing.items.TimingSenseType→liberty_db.ast.ParseScopeliberty_db.timing.items.TimingSenseType→liberty_db.ast.ParsingBuilderliberty_db.timing.items.TimingSenseType→liberty_db.ast.SimpleAttriliberty_db.timing.items.TimingTableLookUp→liberty_db.ast.BuilderScopeliberty_db.timing.items.TimingTableLookUp→liberty_db.ast.Groupliberty_db.timing.items.TimingTableLookUp→liberty_db.ast.GroupAttriliberty_db.timing.items.TimingTableLookUp→liberty_db.ast.ParseScopeliberty_db.timing.items.TimingTableLookUp→liberty_db.ast.ParsingBuilder
- Direction
- liberty_db.timing.items uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.timing.items, while a change to liberty_db.timing.items can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.timing.items uses a module listed above it, which is the healthy direction.
30→11 liberty_db.timing.timing_type uses liberty_db.ast.fmt✕
- Connections
- 1 pair of types, where a type in liberty_db.timing.timing_type uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.timing.timing_type.TimingType→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.timing.timing_type uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.timing.timing_type, while a change to liberty_db.timing.timing_type can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.timing.timing_type uses a module listed above it, which is the healthy direction.
30→22 liberty_db.timing.timing_type uses liberty_db.ast✕
- Connections
- 4 pairs of types, where a type in liberty_db.timing.timing_type uses a type in liberty_db.ast.
- The types involved
liberty_db.timing.timing_type.TimingType→liberty_db.ast.BuilderScopeliberty_db.timing.timing_type.TimingType→liberty_db.ast.ParseScopeliberty_db.timing.timing_type.TimingType→liberty_db.ast.ParsingBuilderliberty_db.timing.timing_type.TimingType→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.timing.timing_type uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.timing.timing_type, while a change to liberty_db.timing.timing_type can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.timing.timing_type uses a module listed above it, which is the healthy direction.
31→11 liberty_db.units uses liberty_db.ast.fmt✕
- Connections
- 6 pairs of types, where a type in liberty_db.units uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.units.CapacitiveLoadUnit→liberty_db.ast.fmt.CodeFormatterliberty_db.units.CurrentUnit→liberty_db.ast.fmt.CodeFormatterliberty_db.units.LeakagePowerUnit→liberty_db.ast.fmt.CodeFormatterliberty_db.units.PullingResistanceUnit→liberty_db.ast.fmt.CodeFormatterliberty_db.units.TimeUnit→liberty_db.ast.fmt.CodeFormatterliberty_db.units.VoltageUnit→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.units uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.units, while a change to liberty_db.units can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.units uses a module listed above it, which is the healthy direction.
31→22 liberty_db.units uses liberty_db.ast✕
- Connections
- 24 pairs of types, where a type in liberty_db.units uses a type in liberty_db.ast.
- The types involved
liberty_db.units.CapacitiveLoadUnit→liberty_db.ast.BuilderScopeliberty_db.units.CapacitiveLoadUnit→liberty_db.ast.ComplexAttriliberty_db.units.CapacitiveLoadUnit→liberty_db.ast.ParseScopeliberty_db.units.CapacitiveLoadUnit→liberty_db.ast.ParsingBuilderliberty_db.units.CurrentUnit→liberty_db.ast.BuilderScopeliberty_db.units.CurrentUnit→liberty_db.ast.ParseScopeliberty_db.units.CurrentUnit→liberty_db.ast.ParsingBuilderliberty_db.units.CurrentUnit→liberty_db.ast.SimpleAttriliberty_db.units.LeakagePowerUnit→liberty_db.ast.BuilderScopeliberty_db.units.LeakagePowerUnit→liberty_db.ast.ParseScopeliberty_db.units.LeakagePowerUnit→liberty_db.ast.ParsingBuilderliberty_db.units.LeakagePowerUnit→liberty_db.ast.SimpleAttriliberty_db.units.PullingResistanceUnit→liberty_db.ast.BuilderScopeliberty_db.units.PullingResistanceUnit→liberty_db.ast.ParseScopeliberty_db.units.PullingResistanceUnit→liberty_db.ast.ParsingBuilderliberty_db.units.PullingResistanceUnit→liberty_db.ast.SimpleAttriliberty_db.units.TimeUnit→liberty_db.ast.BuilderScopeliberty_db.units.TimeUnit→liberty_db.ast.ParseScopeliberty_db.units.TimeUnit→liberty_db.ast.ParsingBuilderliberty_db.units.TimeUnit→liberty_db.ast.SimpleAttriliberty_db.units.VoltageUnit→liberty_db.ast.BuilderScopeliberty_db.units.VoltageUnit→liberty_db.ast.ParseScopeliberty_db.units.VoltageUnit→liberty_db.ast.ParsingBuilderliberty_db.units.VoltageUnit→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.units uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.units, while a change to liberty_db.units can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.units uses a module listed above it, which is the healthy direction.
32→11 liberty_db.ccsn uses liberty_db.ast.fmt✕
- Connections
- 2 pairs of types, where a type in liberty_db.ccsn uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.ccsn.PropagatingCcb→liberty_db.ast.fmt.CodeFormatterliberty_db.ccsn.StageType→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.ccsn uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.ccsn, while a change to liberty_db.ccsn can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.ccsn uses a module listed above it, which is the healthy direction.
32→16 liberty_db.ccsn uses liberty_db.expression.boolean_expression✕
- Connections
- 2 pairs of types, where a type in liberty_db.ccsn uses a type in liberty_db.expression.boolean_expression.
- The types involved
liberty_db.ccsn.CCSNStage→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.ccsn.ReceiverCapacitance→liberty_db.expression.boolean_expression.LogicBooleanExpression
- Direction
- liberty_db.ccsn uses liberty_db.expression.boolean_expression, so a change to liberty_db.expression.boolean_expression can break liberty_db.ccsn, while a change to liberty_db.ccsn can't break liberty_db.expression.boolean_expression.
- Position
- Below the diagonal: liberty_db.ccsn uses a module listed above it, which is the healthy direction.
32→22 liberty_db.ccsn uses liberty_db.ast✕
- Connections
- 13 pairs of types, where a type in liberty_db.ccsn uses a type in liberty_db.ast.
- The types involved
liberty_db.ccsn.CCSNStage→liberty_db.ast.BuilderScopeliberty_db.ccsn.CCSNStage→liberty_db.ast.GroupCommentsliberty_db.ccsn.CCSNStage→liberty_db.ast.GroupFnliberty_db.ccsn.PropagatingCcb→liberty_db.ast.BuilderScopeliberty_db.ccsn.PropagatingCcb→liberty_db.ast.ComplexAttriliberty_db.ccsn.PropagatingCcb→liberty_db.ast.ParseScopeliberty_db.ccsn.PropagatingCcb→liberty_db.ast.ParsingBuilderliberty_db.ccsn.ReceiverCapacitance→liberty_db.ast.GroupCommentsliberty_db.ccsn.ReceiverCapacitance→liberty_db.ast.GroupFnliberty_db.ccsn.StageType→liberty_db.ast.BuilderScopeliberty_db.ccsn.StageType→liberty_db.ast.ParseScopeliberty_db.ccsn.StageType→liberty_db.ast.ParsingBuilderliberty_db.ccsn.StageType→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.ccsn uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.ccsn, while a change to liberty_db.ccsn can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.ccsn uses a module listed above it, which is the healthy direction.
32→28 liberty_db.ccsn uses liberty_db.table✕
- Connections
- 2 pairs of types, where a type in liberty_db.ccsn uses a type in liberty_db.table.
- The types involved
liberty_db.ccsn.CCSNStage→liberty_db.table.Vector3DGrpupliberty_db.ccsn.CCSNStage→liberty_db.table.Vector4DGrpup
- Direction
- liberty_db.ccsn uses liberty_db.table, so a change to liberty_db.table can break liberty_db.ccsn, while a change to liberty_db.ccsn can't break liberty_db.table.
- Position
- Below the diagonal: liberty_db.ccsn uses a module listed above it, which is the healthy direction.
33→11 liberty_db.common.demo uses liberty_db.ast.fmt✕
- Connections
- 1 pair of types, where a type in liberty_db.common.demo uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.common.demo.FF→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.common.demo uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.common.demo, while a change to liberty_db.common.demo can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.common.demo uses a module listed above it, which is the healthy direction.
33→20 liberty_db.common.demo uses liberty_db.cell.items✕
- Connections
- 1 pair of types, where a type in liberty_db.common.demo uses a type in liberty_db.cell.items.
- The types involved
liberty_db.common.demo.Cell→liberty_db.cell.items.Statetable
- Direction
- liberty_db.common.demo uses liberty_db.cell.items, so a change to liberty_db.cell.items can break liberty_db.common.demo, while a change to liberty_db.common.demo can't break liberty_db.cell.items.
- Position
- Below the diagonal: liberty_db.common.demo uses a module listed above it, which is the healthy direction.
33→22 liberty_db.common.demo uses liberty_db.ast✕
- Connections
- 9 pairs of types, where a type in liberty_db.common.demo uses a type in liberty_db.ast.
- The types involved
liberty_db.common.demo.Cell→liberty_db.ast.GroupCommentsliberty_db.common.demo.Cell→liberty_db.ast.GroupFnliberty_db.common.demo.FF→liberty_db.ast.GroupCommentsliberty_db.common.demo.FF→liberty_db.ast.GroupFnliberty_db.common.demo.FF→liberty_db.ast.NamedGroupliberty_db.common.demo.Pin→liberty_db.ast.GroupCommentsliberty_db.common.demo.Pin→liberty_db.ast.GroupFnliberty_db.common.demo.Timing→liberty_db.ast.GroupCommentsliberty_db.common.demo.Timing→liberty_db.ast.GroupFn
- Direction
- liberty_db.common.demo uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.common.demo, while a change to liberty_db.common.demo can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.common.demo uses a module listed above it, which is the healthy direction.
33→29 liberty_db.common.demo uses liberty_db.timing.items✕
- Connections
- 1 pair of types, where a type in liberty_db.common.demo uses a type in liberty_db.timing.items.
- The types involved
liberty_db.common.demo.Timing→liberty_db.timing.items.TimingTableLookUp
- Direction
- liberty_db.common.demo uses liberty_db.timing.items, so a change to liberty_db.timing.items can break liberty_db.common.demo, while a change to liberty_db.common.demo can't break liberty_db.timing.items.
- Position
- Below the diagonal: liberty_db.common.demo uses a module listed above it, which is the healthy direction.
33→30 liberty_db.common.demo uses liberty_db.timing.timing_type✕
- Connections
- 1 pair of types, where a type in liberty_db.common.demo uses a type in liberty_db.timing.timing_type.
- The types involved
liberty_db.common.demo.Timing→liberty_db.timing.timing_type.TimingType
- Direction
- liberty_db.common.demo uses liberty_db.timing.timing_type, so a change to liberty_db.timing.timing_type can break liberty_db.common.demo, while a change to liberty_db.common.demo can't break liberty_db.timing.timing_type.
- Position
- Below the diagonal: liberty_db.common.demo uses a module listed above it, which is the healthy direction.
34→11 liberty_db.library.items uses liberty_db.ast.fmt✕
- Connections
- 12 pairs of types, where a type in liberty_db.library.items uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.library.items.BaseCurveType→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.Define→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.DefineCellArea→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.DefineGroup→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.DelayModel→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.FPGASlew→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.FanoutLength→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.SensitizationVector→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.Technology→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.TreeType→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.VoltageMap→liberty_db.ast.fmt.CodeFormatterliberty_db.library.items.VoltageMapping→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.library.items uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.library.items, while a change to liberty_db.library.items can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.library.items uses a module listed above it, which is the healthy direction.
34→17 liberty_db.library.items uses liberty_db.expression.boolean_expression.logic✕
- Connections
- 1 pair of types, where a type in liberty_db.library.items uses a type in liberty_db.expression.boolean_expression.logic.
- The types involved
liberty_db.library.items.SensitizationVector→liberty_db.expression.boolean_expression.logic.Static
- Direction
- liberty_db.library.items uses liberty_db.expression.boolean_expression.logic, so a change to liberty_db.expression.boolean_expression.logic can break liberty_db.library.items, while a change to liberty_db.library.items can't break liberty_db.expression.boolean_expression.logic.
- Position
- Below the diagonal: liberty_db.library.items uses a module listed above it, which is the healthy direction.
34→22 liberty_db.library.items uses liberty_db.ast✕
- Connections
- 66 pairs of types, where a type in liberty_db.library.items uses a type in liberty_db.ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
liberty_db.library.items.BaseCurveType→liberty_db.ast.BuilderScopeliberty_db.library.items.BaseCurveType→liberty_db.ast.ParseScopeliberty_db.library.items.BaseCurveType→liberty_db.ast.ParsingBuilderliberty_db.library.items.BaseCurveType→liberty_db.ast.SimpleAttriliberty_db.library.items.BaseCurves→liberty_db.ast.GroupCommentsliberty_db.library.items.BaseCurves→liberty_db.ast.GroupFnliberty_db.library.items.Define→liberty_db.ast.BuilderScopeliberty_db.library.items.Define→liberty_db.ast.ComplexAttriliberty_db.library.items.Define→liberty_db.ast.ParseScopeliberty_db.library.items.Define→liberty_db.ast.ParsingBuilderliberty_db.library.items.DefineCellArea→liberty_db.ast.BuilderScopeliberty_db.library.items.DefineCellArea→liberty_db.ast.ComplexAttriliberty_db.library.items.DefineCellArea→liberty_db.ast.ParseScopeliberty_db.library.items.DefineCellArea→liberty_db.ast.ParsingBuilderliberty_db.library.items.DefineGroup→liberty_db.ast.BuilderScopeliberty_db.library.items.DefineGroup→liberty_db.ast.ComplexAttriliberty_db.library.items.DefineGroup→liberty_db.ast.ParseScopeliberty_db.library.items.DefineGroup→liberty_db.ast.ParsingBuilderliberty_db.library.items.DelayModel→liberty_db.ast.BuilderScopeliberty_db.library.items.DelayModel→liberty_db.ast.ParseScopeliberty_db.library.items.DelayModel→liberty_db.ast.ParsingBuilderliberty_db.library.items.DelayModel→liberty_db.ast.SimpleAttriliberty_db.library.items.FPGASlew→liberty_db.ast.BuilderScopeliberty_db.library.items.FPGASlew→liberty_db.ast.ParseScopeliberty_db.library.items.FPGASlew→liberty_db.ast.ParsingBuilder
- Direction
- liberty_db.library.items uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.library.items, while a change to liberty_db.library.items can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.library.items uses a module listed above it, which is the healthy direction.
34→25 liberty_db.library.items uses liberty_db.expression.formula✕
- Connections
- 2 pairs of types, where a type in liberty_db.library.items uses a type in liberty_db.expression.formula.
- The types involved
liberty_db.library.items.InputVoltage→liberty_db.expression.formula.Formulaliberty_db.library.items.OutputVoltage→liberty_db.expression.formula.Formula
- Direction
- liberty_db.library.items uses liberty_db.expression.formula, so a change to liberty_db.expression.formula can break liberty_db.library.items, while a change to liberty_db.library.items can't break liberty_db.expression.formula.
- Position
- Below the diagonal: liberty_db.library.items uses a module listed above it, which is the healthy direction.
34→28 liberty_db.library.items uses liberty_db.table✕
- Connections
- 1 pair of types, where a type in liberty_db.library.items uses a type in liberty_db.table.
- The types involved
liberty_db.library.items.VoltageMapping→liberty_db.table.VoltageName
- Direction
- liberty_db.library.items uses liberty_db.table, so a change to liberty_db.table can break liberty_db.library.items, while a change to liberty_db.library.items can't break liberty_db.table.
- Position
- Below the diagonal: liberty_db.library.items uses a module listed above it, which is the healthy direction.
35→14 liberty_db.library uses liberty_db.common.char_config✕
- Connections
- 1 pair of types, where a type in liberty_db.library uses a type in liberty_db.common.char_config.
- The types involved
liberty_db.library.Library→liberty_db.common.char_config.CharConfig
- Direction
- liberty_db.library uses liberty_db.common.char_config, so a change to liberty_db.common.char_config can break liberty_db.library, while a change to liberty_db.library can't break liberty_db.common.char_config.
- Position
- Below the diagonal: liberty_db.library uses a module listed above it, which is the healthy direction.
35→22 liberty_db.library uses liberty_db.ast✕
- Connections
- 3 pairs of types, where a type in liberty_db.library uses a type in liberty_db.ast.
- The types involved
liberty_db.library.Library→liberty_db.ast.BuilderScopeliberty_db.library.Library→liberty_db.ast.GroupCommentsliberty_db.library.Library→liberty_db.ast.GroupFn
- Direction
- liberty_db.library uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.library, while a change to liberty_db.library can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.library uses a module listed above it, which is the healthy direction.
35→31 liberty_db.library uses liberty_db.units✕
- Connections
- 6 pairs of types, where a type in liberty_db.library uses a type in liberty_db.units.
- The types involved
liberty_db.library.Library→liberty_db.units.CapacitiveLoadUnitliberty_db.library.Library→liberty_db.units.CurrentUnitliberty_db.library.Library→liberty_db.units.LeakagePowerUnitliberty_db.library.Library→liberty_db.units.PullingResistanceUnitliberty_db.library.Library→liberty_db.units.TimeUnitliberty_db.library.Library→liberty_db.units.VoltageUnit
- Direction
- liberty_db.library uses liberty_db.units, so a change to liberty_db.units can break liberty_db.library, while a change to liberty_db.library can't break liberty_db.units.
- Position
- Below the diagonal: liberty_db.library uses a module listed above it, which is the healthy direction.
35→34 liberty_db.library uses liberty_db.library.items✕
- Connections
- 3 pairs of types, where a type in liberty_db.library uses a type in liberty_db.library.items.
- The types involved
liberty_db.library.Library→liberty_db.library.items.DelayModelliberty_db.library.Library→liberty_db.library.items.PowerSupplyliberty_db.library.Library→liberty_db.library.items.Technology
- Direction
- liberty_db.library uses liberty_db.library.items, so a change to liberty_db.library.items can break liberty_db.library, while a change to liberty_db.library can't break liberty_db.library.items.
- Position
- Below the diagonal: liberty_db.library uses a module listed above it, which is the healthy direction.
36→14 liberty_db.pin uses liberty_db.common.char_config✕
- Connections
- 1 pair of types, where a type in liberty_db.pin uses a type in liberty_db.common.char_config.
- The types involved
liberty_db.pin.Pin→liberty_db.common.char_config.CharConfig
- Direction
- liberty_db.pin uses liberty_db.common.char_config, so a change to liberty_db.common.char_config can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.common.char_config.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
36→15 liberty_db.pin uses liberty_db.common.items✕
- Connections
- 1 pair of types, where a type in liberty_db.pin uses a type in liberty_db.common.items.
- The types involved
liberty_db.pin.Pin→liberty_db.common.items.WordSet
- Direction
- liberty_db.pin uses liberty_db.common.items, so a change to liberty_db.common.items can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.common.items.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
36→16 liberty_db.pin uses liberty_db.expression.boolean_expression✕
- Connections
- 3 pairs of types, where a type in liberty_db.pin uses a type in liberty_db.expression.boolean_expression.
- The types involved
liberty_db.pin.Pin→liberty_db.expression.boolean_expression.BooleanExpressionliberty_db.pin.Pin→liberty_db.expression.boolean_expression.LogicBooleanExpressionliberty_db.pin.Pin→liberty_db.expression.boolean_expression.PowerGroundBooleanExpression
- Direction
- liberty_db.pin uses liberty_db.expression.boolean_expression, so a change to liberty_db.expression.boolean_expression can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.expression.boolean_expression.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
36→17 liberty_db.pin uses liberty_db.expression.boolean_expression.logic✕
- Connections
- 1 pair of types, where a type in liberty_db.pin uses a type in liberty_db.expression.boolean_expression.logic.
- The types involved
liberty_db.pin.Pin→liberty_db.expression.boolean_expression.logic.Normal
- Direction
- liberty_db.pin uses liberty_db.expression.boolean_expression.logic, so a change to liberty_db.expression.boolean_expression.logic can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.expression.boolean_expression.logic.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
36→19 liberty_db.pin uses liberty_db.pin.items✕
- Connections
- 13 pairs of types, where a type in liberty_db.pin uses a type in liberty_db.pin.items.
- The types involved
liberty_db.pin.Pin→liberty_db.pin.items.AllDriverTypeliberty_db.pin.Pin→liberty_db.pin.items.AntennaDiodeTypeliberty_db.pin.Pin→liberty_db.pin.items.Directionliberty_db.pin.Pin→liberty_db.pin.items.DontFaultliberty_db.pin.Pin→liberty_db.pin.items.HyperbolicNoiseliberty_db.pin.Pin→liberty_db.pin.items.NextstateTypeliberty_db.pin.Pin→liberty_db.pin.items.OneZeroliberty_db.pin.Pin→liberty_db.pin.items.PinFuncTypeliberty_db.pin.Pin→liberty_db.pin.items.RestoreEdgeTypeliberty_db.pin.Pin→liberty_db.pin.items.RetentionPinliberty_db.pin.Pin→liberty_db.pin.items.SignalTypeliberty_db.pin.Pin→liberty_db.pin.items.SlewControlliberty_db.pin.Pin→liberty_db.pin.items.TwoValue
- Direction
- liberty_db.pin uses liberty_db.pin.items, so a change to liberty_db.pin.items can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.pin.items.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
36→22 liberty_db.pin uses liberty_db.ast✕
- Connections
- 2 pairs of types, where a type in liberty_db.pin uses a type in liberty_db.ast.
- The types involved
liberty_db.pin.Pin→liberty_db.ast.GroupCommentsliberty_db.pin.Pin→liberty_db.ast.GroupFn
- Direction
- liberty_db.pin uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
36→33 liberty_db.pin uses liberty_db.common.demo✕
- Connections
- 1 pair of types, where a type in liberty_db.pin uses a type in liberty_db.common.demo.
- The types involved
liberty_db.pin.Pin→liberty_db.common.demo.Pin
- Direction
- liberty_db.pin uses liberty_db.common.demo, so a change to liberty_db.common.demo can break liberty_db.pin, while a change to liberty_db.pin can't break liberty_db.common.demo.
- Position
- Below the diagonal: liberty_db.pin uses a module listed above it, which is the healthy direction.
37→11 liberty_db.pin.bus uses liberty_db.ast.fmt✕
- Connections
- 3 pairs of types, where a type in liberty_db.pin.bus uses a type in liberty_db.ast.fmt.
- The types involved
liberty_db.pin.bus.BaseType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.bus.DataType→liberty_db.ast.fmt.CodeFormatterliberty_db.pin.bus.SimpleBusType→liberty_db.ast.fmt.CodeFormatter
- Direction
- liberty_db.pin.bus uses liberty_db.ast.fmt, so a change to liberty_db.ast.fmt can break liberty_db.pin.bus, while a change to liberty_db.pin.bus can't break liberty_db.ast.fmt.
- Position
- Below the diagonal: liberty_db.pin.bus uses a module listed above it, which is the healthy direction.
37→22 liberty_db.pin.bus uses liberty_db.ast✕
- Connections
- 15 pairs of types, where a type in liberty_db.pin.bus uses a type in liberty_db.ast.
- The types involved
liberty_db.pin.bus.BaseType→liberty_db.ast.BuilderScopeliberty_db.pin.bus.BaseType→liberty_db.ast.ParseScopeliberty_db.pin.bus.BaseType→liberty_db.ast.ParsingBuilderliberty_db.pin.bus.BaseType→liberty_db.ast.SimpleAttriliberty_db.pin.bus.BusType→liberty_db.ast.BuilderScopeliberty_db.pin.bus.BusType→liberty_db.ast.GroupCommentsliberty_db.pin.bus.BusType→liberty_db.ast.GroupFnliberty_db.pin.bus.DataType→liberty_db.ast.BuilderScopeliberty_db.pin.bus.DataType→liberty_db.ast.ParseScopeliberty_db.pin.bus.DataType→liberty_db.ast.ParsingBuilderliberty_db.pin.bus.DataType→liberty_db.ast.SimpleAttriliberty_db.pin.bus.SimpleBusType→liberty_db.ast.BuilderScopeliberty_db.pin.bus.SimpleBusType→liberty_db.ast.ParseScopeliberty_db.pin.bus.SimpleBusType→liberty_db.ast.ParsingBuilderliberty_db.pin.bus.SimpleBusType→liberty_db.ast.SimpleAttri
- Direction
- liberty_db.pin.bus uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.pin.bus, while a change to liberty_db.pin.bus can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.pin.bus uses a module listed above it, which is the healthy direction.
37→33 liberty_db.pin.bus uses liberty_db.common.demo✕
- Connections
- 1 pair of types, where a type in liberty_db.pin.bus uses a type in liberty_db.common.demo.
- The types involved
liberty_db.pin.bus.BusType→liberty_db.common.demo.Pin
- Direction
- liberty_db.pin.bus uses liberty_db.common.demo, so a change to liberty_db.common.demo can break liberty_db.pin.bus, while a change to liberty_db.pin.bus can't break liberty_db.common.demo.
- Position
- Below the diagonal: liberty_db.pin.bus uses a module listed above it, which is the healthy direction.
38→14 liberty_db.timing uses liberty_db.common.char_config✕
- Connections
- 1 pair of types, where a type in liberty_db.timing uses a type in liberty_db.common.char_config.
- The types involved
liberty_db.timing.Timing→liberty_db.common.char_config.CharConfig
- Direction
- liberty_db.timing uses liberty_db.common.char_config, so a change to liberty_db.common.char_config can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.common.char_config.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→15 liberty_db.timing uses liberty_db.common.items✕
- Connections
- 2 pairs of types, where a type in liberty_db.timing uses a type in liberty_db.common.items.
- The types involved
liberty_db.timing.Timing→liberty_db.common.items.SdfEdgeTypeliberty_db.timing.Timing→liberty_db.common.items.WordSet
- Direction
- liberty_db.timing uses liberty_db.common.items, so a change to liberty_db.common.items can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.common.items.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→16 liberty_db.timing uses liberty_db.expression.boolean_expression✕
- Connections
- 2 pairs of types, where a type in liberty_db.timing uses a type in liberty_db.expression.boolean_expression.
- The types involved
liberty_db.timing.Timing→liberty_db.expression.boolean_expression.BooleanExpressionliberty_db.timing.Timing→liberty_db.expression.boolean_expression.LogicBooleanExpression
- Direction
- liberty_db.timing uses liberty_db.expression.boolean_expression, so a change to liberty_db.expression.boolean_expression can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.expression.boolean_expression.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→22 liberty_db.timing uses liberty_db.ast✕
- Connections
- 3 pairs of types, where a type in liberty_db.timing uses a type in liberty_db.ast.
- The types involved
liberty_db.timing.Timing→liberty_db.ast.BuilderScopeliberty_db.timing.Timing→liberty_db.ast.GroupCommentsliberty_db.timing.Timing→liberty_db.ast.GroupFn
- Direction
- liberty_db.timing uses liberty_db.ast, so a change to liberty_db.ast can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.ast.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→26 liberty_db.timing uses liberty_db.expression.sdf✕
- Connections
- 1 pair of types, where a type in liberty_db.timing uses a type in liberty_db.expression.sdf.
- The types involved
liberty_db.timing.Timing→liberty_db.expression.sdf.SdfExpression
- Direction
- liberty_db.timing uses liberty_db.expression.sdf, so a change to liberty_db.expression.sdf can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.expression.sdf.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→28 liberty_db.timing uses liberty_db.table✕
- Connections
- 2 pairs of types, where a type in liberty_db.timing uses a type in liberty_db.table.
- The types involved
liberty_db.timing.Timing→liberty_db.table.CompactCcsTableliberty_db.timing.Timing→liberty_db.table.ReferenceTimeVector3DGrpup
- Direction
- liberty_db.timing uses liberty_db.table, so a change to liberty_db.table can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.table.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→29 liberty_db.timing uses liberty_db.timing.items✕
- Connections
- 2 pairs of types, where a type in liberty_db.timing uses a type in liberty_db.timing.items.
- The types involved
liberty_db.timing.Timing→liberty_db.timing.items.TimingSenseTypeliberty_db.timing.Timing→liberty_db.timing.items.TimingTableLookUp
- Direction
- liberty_db.timing uses liberty_db.timing.items, so a change to liberty_db.timing.items can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.timing.items.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→30 liberty_db.timing uses liberty_db.timing.timing_type✕
- Connections
- 1 pair of types, where a type in liberty_db.timing uses a type in liberty_db.timing.timing_type.
- The types involved
liberty_db.timing.Timing→liberty_db.timing.timing_type.TimingType
- Direction
- liberty_db.timing uses liberty_db.timing.timing_type, so a change to liberty_db.timing.timing_type can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.timing.timing_type.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→32 liberty_db.timing uses liberty_db.ccsn✕
- Connections
- 1 pair of types, where a type in liberty_db.timing uses a type in liberty_db.ccsn.
- The types involved
liberty_db.timing.Timing→liberty_db.ccsn.PropagatingCcb
- Direction
- liberty_db.timing uses liberty_db.ccsn, so a change to liberty_db.ccsn can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.ccsn.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
38→33 liberty_db.timing uses liberty_db.common.demo✕
- Connections
- 1 pair of types, where a type in liberty_db.timing uses a type in liberty_db.common.demo.
- The types involved
liberty_db.timing.Timing→liberty_db.common.demo.Timing
- Direction
- liberty_db.timing uses liberty_db.common.demo, so a change to liberty_db.common.demo can break liberty_db.timing, while a change to liberty_db.timing can't break liberty_db.common.demo.
- Position
- Below the diagonal: liberty_db.timing uses a module listed above it, which is the healthy direction.
39→33 liberty_db.timing.impls uses liberty_db.common.demo✕
- Connections
- 1 pair of types, where a type in liberty_db.timing.impls uses a type in liberty_db.common.demo.
- The types involved
liberty_db.timing.impls.impls$module→liberty_db.common.demo.Timing
- Direction
- liberty_db.timing.impls uses liberty_db.common.demo, so a change to liberty_db.common.demo can break liberty_db.timing.impls, while a change to liberty_db.timing.impls can't break liberty_db.common.demo.
- Position
- Below the diagonal: liberty_db.timing.impls uses a module listed above it, which is the healthy direction.
40→35 liberty_db.library.test uses liberty_db.library✕
- Connections
- 1 pair of types, where a type in liberty_db.library.test uses a type in liberty_db.library.
- The types involved
liberty_db.library.test.test$module→liberty_db.library.Library
- Direction
- liberty_db.library.test uses liberty_db.library, so a change to liberty_db.library can break liberty_db.library.test, while a change to liberty_db.library.test can't break liberty_db.library.
- Position
- Below the diagonal: liberty_db.library.test 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 44 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
Roadmap
Top priorities: Resolve the 34 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (5), items.rs (4), parser.rs (3); 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 34 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (5), items.rs (4), parser.rs (3). | +10.8 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +8.1 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.7 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with mod.rs, table.rs, items.rs. | +1.5 pts | Low | Knowledge Freshness |
| 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. | +1.9 pts | Medium | Documentation (README) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/pin/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/library/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/timing/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/expression/boolean_expression/latch_ff.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/timing/items.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/lib.rs | 6.4 | Mixed | Explicit Debt: TodoComment |
| src/cell/mod.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/timing/timing_type.rs | 7.0 | Near-clean | Cyclomatic Complexity: ArcSequential::fmt (cyclomatic 18) |
| dev/utils/src/lib.rs | 7.0 | Near-clean | Cognitive Complexity: dev_utils::text_diff (cognitive 27) |
| dev/src/lib.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| src/expression/boolean_expression/logic.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| macros/src/group.rs | 7.0 | Near-clean | Cyclomatic Complexity: liberty_macros::group::inner (cyclomatic 16) |
| src/ast/parser.rs | 7.0 | Near-clean | God Classes: TooManyFunctions: liberty_db::ast::parser |
| macros/src/attribute.rs | 7.1 | Near-clean | Cyclomatic Complexity: liberty_macros::attribute::parse_fields_type (cyclomatic 19) |
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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 42 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, 235 of 246 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
- 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. Not scored — 42 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 Cargo manifests but commits no Cargo.lock, so its dependency graph was closed from the manifests over the crates.io index, and part of it could not be read: no published release of byteorder satisfies `1.5.*`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 576 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in 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.
- 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.
- PF1 Benchmark discipline — 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. 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.
- 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.
- X3 Exception handling — 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- 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.
- 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.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was liberty_db::ast::attributs_set_undefined_attri at 24. A further 6 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 TimingType::from_str at 36 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/table.rs (Variable::from_str at 29), docs/header.html (header.html.IFRAME at 19), src/expression/boolean_expression/logic.rs (State::combine_bgn_end at 16). 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 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with liberty_db::ast::attributs_set_undefined_attri (cyclomatic 24), liberty_macros::attribute::parse_fields_type (cyclomatic 19), ArcSequential::fmt (cyclomatic 18). — 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 7 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was liberty_db::ast::attributs_set_undefined_attri at 61.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with liberty_db::ast::attributs_set_undefined_attri (cognitive 61), liberty_macros::group::inner (cognitive 44), liberty_macros::duplicate::attrs_config (cognitive 37). — 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 10 together lifts Cognitive Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
15 god class(es) detected.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with items.rs (3), table.rs, mod.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 TooManyFields finding(s) in God Classes — start with mod.rs (4), char_config.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with group.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
25 duplicated block group(s) detected. 3.8 % of the production lines (983 of 25,948) are in a reported copy. A further 17 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 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with items.rs (2), attribute.rs, latch_ff.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with items.rs (2), group.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with items.rs, parser.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
4 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
1 of 33 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 71.6% — 7 file(s) below 50%. Measured from the Rust suite (repository root: `cargo nextest run` and the doc tests instrumented, 3 run(s), 45 production file(s)). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 7 Low coverage finding(s) in Code Coverage — start with lib.rs (3), logic.rs, mod.rs. — One of this dimension's main actionable groups (7 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 24 test files): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: macros/src/group.rs (4×16=64); macros/src/attribute.rs (3×19=57)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with group.rs, attribute.rs. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
27 deducted task-comment markers across 25948 LoC (0.1/KLoC) → score 9.8. 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 26 TodoComment finding(s) in Explicit Debt — start with mod.rs (12), lib.rs (7), impls.rs (2). — One of this dimension's main actionable groups (26 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 4 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
44 finding(s): 0 critical, 42 high, 2 medium, 0 low. 37 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. semgrep hit a parse error in 1 file(s) — `src/ast/mod.rs` (line 100, line 121, line 148, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- 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 37 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 (37 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
37 of 37 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/timing/mod.rs. Counted over 37 of the 45 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 34 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (5), items.rs (4), parser.rs (3). — One of this dimension's main actionable groups (34 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with mod.rs, table.rs, items.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
- `parse_json` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/library/mod.rs:948
- `fmt_json` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/library/mod.rs:953
- `parse_db` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/library/mod.rs:961
- `fmt_db` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/library/mod.rs:966
What to do
- Finish or delete the functions that are still `todo!()`/`unimplemented!()` or panic "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `parse_json` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — src/library/mod.rs:948
- `fmt_json` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — src/library/mod.rs:953
- `parse_db` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — src/library/mod.rs:961
- `fmt_db` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — src/library/mod.rs:966
- `need_timing_sense_when_related_pin_is_output` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/timing/impls.rs:35
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- 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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `eval` is public and takes a `FormulaExpr` as its receiver from its caller, and it calls itself at line 90 with a piece of the document (and at line 91, line 94, line 95, line 98, line 99, line 102, line 103, line 105) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `eval` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/expression/formula.rs:90
- `fmt` is public, takes a document from its caller (line 194) and hands it to `fmt_with`, which calls itself at line 155 with a piece of the document (and at line 158, line 160, line 163, line 165, line 168, line 170, line 173, line 175) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `fmt_with` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/expression/formula.rs:155
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
- `writer` (line 840) is a `BufWriter` this function owns and never releases: no `flush()` (or `into_inner()`) on any path, and it is not handed on. Rust drops it at the end of the scope, and a buffered writer that is dropped flushes and throws the error away, so a failed write reports success. Release it where the work ends. — src/library/mod.rs:840
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
- `SimpleBusType.ctx` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/pin/bus.rs:117
- `DefaultTableCtx.___p` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/table.rs:156
- `DefaultCompactTableCtx.___p` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/table.rs:177
- `DefaultPropagationTable.___p` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/table.rs:199
- `DefaultPolyTableCtx.___p` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/table.rs:224
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- `self.inner.iter().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `fmt` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/common/items.rs:75
- `core::str::from_utf8(bytes)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_num` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/ast/fmt.rs:80
- `f.ident.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `inner` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — macros/src/duplicate.rs:200
- `name_field.ident.clone()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `inner` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — macros/src/group.rs:294
- `field.ident.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `inner` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — macros/src/group.rs:326
- `name_vec[0].1.ident.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `inner` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — macros/src/group.rs:447
- `fs::read_dir(search_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cpp_files` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:11
- `entry` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cpp_files` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:13
- `env::var("OUT_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:25
- `env::var("CARGO_MANIFEST_DIR")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:29
- `fs::remove_dir_all(&build_dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:33
- `fs::create_dir(&build_dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:35
- `Command::new("make").arg("-f").arg(projs_dir.join("si2libertyParser/Makefile").display().to_string()).current_dir(&build_dir).status()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:42
- `Command::new("g++").args(["-std=c++17","-fPIC","-shared",&format!("-I{}",projs_dir.display()),"-O3","-o",&out_dir.join("libprojs.so").display().to_string(),&format!("{}",projs_dir.join("projs.cpp").display()),]).args(cpp_files(&[projs_dir.join("ot/liberty"),projs_dir.join("ot/unit")])).args([&format!("-L{}",build_dir.display()),"-lsi2dr_liberty","-lstdc++fs",]).status()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/build.rs:67
- `path.file_name()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `all_files` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/utils/src/lib.rs:56
- `path.file_name().unwrap().to_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `all_files` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/utils/src/lib.rs:56
- `std::fs::metadata(path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `all_files` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/utils/src/lib.rs:57
- `CString::new(s)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `parse` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — dev/src/_impl_bench.rs:237, dev/src/_impl_bench.rs:272
- `read_to_string(file_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `parse_bench` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/src/lib.rs:94
- `read_to_string(file_path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_bench` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — dev/src/lib.rs:115
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85.0 | Strong | Solid. |
| Architecture | 95.1 | Exemplary | Strongest area. |
| Maturity | 43.8 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 82.1 | Exemplary | Solid. |
| Security | 46.0 | Weak — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 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 — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (20 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 1 markup document under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can 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.
- 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 Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) 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 starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves 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, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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 Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) 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 Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~491 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Not scored — 42 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Crate licences not graded — the lock-less Cargo graph could not be read in full
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust 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; comments in this repository's .py, .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — 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 (a Cargo manifest — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- 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
- M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 45 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 43 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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 — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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 — 43 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 157 finding(s)
- TodoComment src/ctx.rs:69
- TodoComment src/lib.rs:81
- TodoComment src/lib.rs:82
- TodoComment src/lib.rs:90
- TodoComment src/lib.rs:104
- TodoComment src/timing/impls.rs:14
- TodoComment src/cell/mod.rs:778
- TodoComment src/lib.rs:128
- TodoComment src/lib.rs:131
- TodoComment src/lib.rs:150
- TodoComment src/timing/impls.rs:38
- TodoComment src/pin/mod.rs:1217
- TodoComment src/pin/mod.rs:1219
- TodoComment src/pin/mod.rs:1221
- TodoComment src/pin/mod.rs:1223
- TodoComment src/timing/items.rs:506
- TodoComment src/timing/items.rs:510
- TodoComment src/timing/mod.rs:169
- TodoComment src/timing/mod.rs:198
- TodoComment src/timing/mod.rs:222
- TodoComment src/library/mod.rs:946
- TodoComment src/library/mod.rs:951
- TodoComment src/library/mod.rs:959
- TodoComment src/library/mod.rs:964
- TodoComment src/expression/boolean_expression/latch_ff.rs:18
- Symbol treated as nullable, then dereferenced unguarded src/common/items.rs:75
- Symbol treated as nullable, then dereferenced unguarded src/ast/fmt.rs:80
- Symbol treated as nullable, then dereferenced unguarded macros/src/duplicate.rs:200
- Symbol treated as nullable, then dereferenced unguarded macros/src/group.rs:294
- Symbol treated as nullable, then dereferenced unguarded macros/src/group.rs:326
- Symbol treated as nullable, then dereferenced unguarded macros/src/group.rs:447
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:11
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:13
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:25
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:29
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:33
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:35
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:42
- Symbol treated as nullable, then dereferenced unguarded dev/build.rs:67
- Symbol treated as nullable, then dereferenced unguarded dev/utils/src/lib.rs:56
- Symbol treated as nullable, then dereferenced unguarded dev/utils/src/lib.rs:56
- Symbol treated as nullable, then dereferenced unguarded dev/utils/src/lib.rs:57
- Symbol treated as nullable, then dereferenced unguarded dev/src/_impl_bench.rs:237
- Symbol treated as nullable, then dereferenced unguarded dev/src/_impl_bench.rs:272
- Symbol treated as nullable, then dereferenced unguarded dev/src/lib.rs:94
- Symbol treated as nullable, then dereferenced unguarded dev/src/lib.rs:115
- FileTooLong: src/table.rs src/table.rs
- FileTooLong: ast/mod.rs src/ast/mod.rs
- FileTooLong: cell/items.rs src/cell/items.rs
- FileTooLong: library/items.rs src/library/items.rs
- FileTooLong: boolean_expression/latch_ff.rs src/expression/boolean_expression/latch_ff.rs
- FileTooLong: timing/items.rs src/timing/items.rs
- FileTooLong: common/impls.rs src/common/impls.rs
- Low coverage: dev/src/lib.rs dev/src/lib.rs:1
- Low coverage: dev/utils/src/lib.rs dev/utils/src/lib.rs:1
- Low coverage: macros/src/lib.rs macros/src/lib.rs:1
- Low coverage: src/expression/boolean_expression/logic.rs src/expression/boolean_expression/logic.rs:1
- Low coverage: src/internal_power/mod.rs src/internal_power/mod.rs:1
- Low coverage: src/timing/timing_type.rs src/timing/timing_type.rs:1
- Low coverage: src/units.rs src/units.rs:1
- liberty_macros::group::inner (cognitive 44) macros/src/group.rs:248
- liberty_macros::duplicate::attrs_config (cognitive 37) macros/src/duplicate.rs:98
- liberty_macros::duplicate::inner (cognitive 37) macros/src/duplicate.rs:179
- liberty_macros::attribute::parse_fields_type (cognitive 35) macros/src/attribute.rs:60
- liberty_macros::attribute::parse_field_attrs (cognitive 18) macros/src/attribute.rs:175
- liberty_macros::group::group_field_fn (cognitive 16) macros/src/group.rs:7
- TooManyFields: Pin src/pin/mod.rs:138
- TooManyFields: Library src/library/mod.rs:38
- TooManyFields: Timing src/timing/mod.rs:57
- TooManyFields: Cell src/cell/mod.rs:203
- TooManyFields: CharConfig src/common/char_config.rs:63
- Configuration option is read nowhere src/pin/bus.rs:117
- Configuration option is read nowhere src/table.rs:156
- Configuration option is read nowhere src/table.rs:177
- Configuration option is read nowhere src/table.rs:199
- Configuration option is read nowhere src/table.rs:224
- Duplicated block (8 lines × 2) macros/src/attribute.rs:240
- Duplicated block (8 lines × 2) src/library/items.rs:788
- Duplicated block (8 lines × 2) src/timing/items.rs:740
- Duplicated block (8 lines × 2) src/expression/boolean_expression/latch_ff.rs:594
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:948
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:953
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:961
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:966
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:948
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:953
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:961
- Unfinished stub — body is todo!() / unimplemented!() src/library/mod.rs:966
- liberty_macros::attribute::parse_fields_type (cyclomatic 19) macros/src/attribute.rs:60
- liberty_macros::duplicate::attrs_config (cyclomatic 16) macros/src/duplicate.rs:98
- liberty_macros::group::inner (cyclomatic 16) macros/src/group.rs:248
- Duplicated block (5 lines × 2) src/cell/items.rs:260
- Duplicated block (5 lines × 2) macros/src/group.rs:449
- Duplicated block (5 lines × 2) src/timing/items.rs:208
- liberty_db::ast::attributs_set_undefined_attri (cyclomatic 24) src/ast/mod.rs:482
- liberty_db::expression::boolean_expression::parser::_fmt (cyclomatic 18) src/expression/boolean_expression/parser.rs:25
- Hotspot: macros/src/group.rs macros/src/group.rs:248
- Hotspot: macros/src/attribute.rs macros/src/attribute.rs:60
- liberty_db::ast::attributs_set_undefined_attri (cognitive 61) src/ast/mod.rs:482
- liberty_db::expression::boolean_expression::parser::_fmt (cognitive 21) src/expression/boolean_expression/parser.rs:25
- FunctionTooLong: liberty_macros::group::inner macros/src/group.rs:248
- FunctionTooLong: liberty_macros::group::group_field_fn macros/src/group.rs:7
- Edited copy of a member (21 corresponding lines) src/cell/items.rs:1994
- Edited copy of a member (21 corresponding lines) src/ast/parser.rs:361
- Duplicated block (13 lines × 2) src/timing/items.rs:218
- Duplicated block (13 lines × 2) src/timing/items.rs:242
- Duplicated block (8 lines × 4) src/expression/boolean_expression/parser.rs:77
- Duplicated block (8 lines × 4) src/expression/boolean_expression/parser.rs:60
- Duplicated block (6 lines × 4) src/expression/boolean_expression/latch_ff.rs:659
- Duplicated block (6 lines × 4) src/table.rs:1379
- Duplicated block (6 lines × 2) macros/src/group.rs:456
- Duplicated block (6 lines × 2) src/ast/parser.rs:385
- Recursive walk over a caller-supplied document has no depth cap src/expression/formula.rs:90
- Recursive walk over a caller-supplied document has no depth cap src/expression/formula.rs:155
- ArcSequential::fmt (cyclomatic 18) src/timing/timing_type.rs:461
- AllDriverType::fmt (cyclomatic 16) src/pin/items.rs:352
- FixmeComment src/timing/mod.rs:1797
- AllDriverType::fmt (cognitive 28) src/pin/items.rs:352
- dev_utils::text_diff (cognitive 27) dev/utils/src/lib.rs:2
- REDACTED
- REDACTED
- TooManyFunctions: liberty_db::ast::parser src/ast/parser.rs:27
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (31 shared lines) src/timing/items.rs:207
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/table.rs:1378
- Edited copy of a member (64 corresponding lines) src/expression/boolean_expression/latch_ff.rs:616
- Edited copy of a member (28 corresponding lines) macros/src/attribute.rs:239
- Edited copy of a member (24 corresponding lines) src/table.rs:1492
- Edited copy of a member (16 corresponding lines) src/cell/parser.rs:19
- Edited copy of a member (17 corresponding lines) src/library/items.rs:787
- Edited copy of a member (15 corresponding lines) dev/src/lib.rs:93
- Edited copy of a member (19 corresponding lines) src/expression/boolean_expression/logic.rs:410
- Edited copy of a member (11 corresponding lines) src/expression/boolean_expression/latch_ff.rs:589
- Edited copy of a member (20 corresponding lines) src/ast/mod.rs:1257
- Edited copies of one member (5 members, 23+ corresponding lines) src/ast/parser.rs:418
- Edited copies of one member (6 members, 14+ corresponding lines) src/common/char_config.rs:755
- Edited copies of one member (3 members, 7+ corresponding lines) src/ast/parser.rs:353
- Edited copy of a member (7 corresponding lines) src/expression/boolean_expression/parser.rs:276
- Duplicated block (23–24 lines × 2) src/expression/boolean_expression/latch_ff.rs:624
- Duplicated block (17 lines × 2) macros/src/attribute.rs:250
- Duplicated block (15 lines × 3) src/ast/parser.rs:426
- Duplicated block (15 lines × 2) src/ast/parser.rs:497
- Duplicated block (11 lines × 2) src/common/char_config.rs:797
- Duplicated block (7–10 lines × 2) src/expression/boolean_expression/latch_ff.rs:663
- Duplicated block (10 lines × 2) src/library/items.rs:181
- Duplicated block (9 lines × 2) src/library/items.rs:353
- Duplicated block (6 lines × 3) src/library/mod.rs:981
- Duplicated block (3–6 lines × 3) src/cell/parser.rs:20
- Low cohesion: Library (LCOM4 13) src/library/mod.rs:38
- Empty method body — does nothing with its inputs src/timing/impls.rs:35
- Coverage reaches no merge REDACTED:114
- Coverage collected but not gated
- Explicit release owed and not made on every path src/library/mod.rs:840
Minor — 46 finding(s)
- Orphaned file src/expression/boolean_expression/latch_ff.rs:1
- Orphaned file src/library/items.rs:1
- Orphaned file src/pin/mod.rs:1
- Orphaned file src/library/mod.rs:1
- Orphaned file src/common/char_config.rs:1
- Orphaned file src/ast/mod.rs:1
- Orphaned file src/cell/mod.rs:1
- Orphaned file src/timing/timing_type.rs:1
- Orphaned file src/timing/items.rs:1
- Orphaned file src/pin/items.rs:1
- Orphaned file macros/src/group.rs:1
- Orphaned file src/cell/test.rs:1
- Orphaned file src/common/impls.rs:1
- Orphaned file src/ccsn.rs:1
- Orphaned file src/ast/parser.rs:1
- Orphaned file src/expression/boolean_expression/mod.rs:1
- Orphaned file macros/src/attribute.rs:1
- Orphaned file src/library/test.rs:1
- Orphaned file src/expression/boolean_expression/logic.rs:1
- Orphaned file src/expression/formula.rs:1
- Orphaned file dev/src/lib.rs:1
- Orphaned file src/units.rs:1
- Orphaned file src/expression/boolean_expression/parser.rs:1
- Orphaned file src/common/demo.rs:1
- Orphaned file dev/src/_impl_bench.rs:1
- Most significant orphaned file src/timing/mod.rs:1
- Most significant orphaned file src/table.rs:1
- Most significant orphaned file src/cell/items.rs:1
- Projects may be oversized for their cohesion Cargo.toml:1
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-5c0a09e874a542419d542dbb3949ec07/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=376" --report-format json --report-path /tmp/watchdog-gitleaks-5c0a09e874a542419d542dbb3949ec07/history-1.json --exit-code 0 --source . | 6 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5c0a09e874a542419d542dbb3949ec07/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 --exclude dev/include . | 44 | 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 (a Cargo manifest — 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 (a Cargo manifest — not scanned yet). | 0 | — |