Executive summary
rust-lang/rust-bindgen meets our standard for a preview release, though the project keeps no record of its design decisions. It scores 66 out of 100 and is rated Strong, and all 52 of its critical findings are security problems in the build pipeline.
Maturity, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Having someone learn and document the 16 files no active contributor knows is another step, worth about 5 points. Raising Maturity to 62 would lift the score to about 68.
Forty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting each secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first.
The product code is 30,645 lines, about €41,000 to rebuild.
If Maturity rose from 57 to 62, the lowest score rated Strong, the score would rise from 66 to about 68.
New since the last survey: 8 findings
- Churn × Complexity Hotspots · Hotspot: bindgen/ir/ty.rs bindgen/ir/ty.rs
- Churn × Complexity Hotspots · Hotspot: bindgen/ir/var.rs bindgen/ir/var.rs
- Churn × Complexity Hotspots · Hotspot: bindgen/ir/analysis/derive.rs bindgen/ir/analysis/derive.rs
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 5 findings
- Explicit Debt · TodoComment bindgen/ir/var.rs
- Static Analysis (SAST) · High: REDACTED REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €41,000 · Estimate
| Cost to rebuild | €14,000 to €69,000, for 229 to 727 hours of work, about 0.3 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.9 at a score of 66. 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: 30,645 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 ir.int | 2 codegen.error | 3 ir.analysis | 4 ir.annotations | 5 ir.derive | 6 ir.dot | 7 ir.layout | 8 ir.traversal | 9 parse | 10 codegen.struct_layout | 11 ir.analysis.has_vtable | 12 ir.analysis.sizedness | 13 ir.function | 14 ir.module | 15 ir.template | 16 ir.comp | 17 codegen.impl_debug | 18 ir.item | 19 codegen.postprocessing.merge_extern_blocks | 20 codegen.serialize | 21 ir.context | 22 codegen.dyngen | 23 codegen.impl_partialeq | 24 ir.analysis.has_destructor | 25 ir.analysis.template_params | 26 ir.enum_ty | 27 ir.objc | 28 codegen | 29 clang | 30 codegen.helpers | 31 codegen.utils | 32 ir.analysis.derive | 33 callbacks | 34 bindgen | 35 ir.ty | 36 ir.var | 37 codegen.helpers.ast_ty | 38 features | 39 ir.item_kind | 40 options.cli |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ir.int | ||||||||||||||||||||||||||||||||||||||||
| 2 codegen.error | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 ir.analysis | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 ir.annotations | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 ir.derive | 8 | |||||||||||||||||||||||||||||||||||||||
| 6 ir.dot | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 ir.layout | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 ir.traversal | 1 | 11 | ||||||||||||||||||||||||||||||||||||||
| 9 parse | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 codegen.struct_layout | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 11 ir.analysis.has_vtable | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 12 ir.analysis.sizedness | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 13 ir.function | 1 | 1 | 1 | 2 | 1 | 5 | 3 | 6 | 1 | |||||||||||||||||||||||||||||||
| 14 ir.module | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 15 ir.template | 1 | 2 | 6 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 16 ir.comp | 12 | 4 | 3 | 3 | 4 | 1 | 2 | 6 | 20 | 11 | 2 | 1 | ||||||||||||||||||||||||||||
| 17 codegen.impl_debug | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 ir.item | 1 | 8 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 14 | 5 | 4 | 3 | |||||||||||||||||||||||||
| 19 codegen.postprocessing.merge_extern_blocks | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 codegen.serialize | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 ir.context | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 1 | 9 | 1 | ||||||||||||||||||||||||||||||
| 22 codegen.dyngen | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 codegen.impl_partialeq | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 ir.analysis.has_destructor | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 ir.analysis.template_params | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 26 ir.enum_ty | 1 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 ir.objc | 1 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 28 codegen | 2 | 4 | 1 | 2 | 3 | 5 | 12 | 1 | 1 | 1 | 5 | 1 | 5 | |||||||||||||||||||||||||||
| 29 clang | 2 | 1 | 1 | 2 | 6 | 1 | 7 | |||||||||||||||||||||||||||||||||
| 30 codegen.helpers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 codegen.utils | 2 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 32 ir.analysis.derive | 2 | 2 | 1 | 1 | 2 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 33 callbacks | 1 | 1 | 2 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 34 bindgen | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 ir.ty | 1 | 2 | 1 | 1 | 4 | 1 | 3 | 5 | 2 | 1 | ||||||||||||||||||||||||||||||
| 36 ir.var | 1 | 1 | 1 | 1 | 3 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||
| 37 codegen.helpers.ast_ty | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 features | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 39 ir.item_kind | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 options.cli | 1 | 4 | 3 | 2 |
2→34 codegen.error uses bindgen part of a loop✕
- Connections
- 1 pair of types, where a type in codegen.error uses a type in bindgen.
- The types involved
bindgen.codegen.error.Error→bindgen.Formatter
- Direction
- codegen.error uses bindgen, so a change to bindgen can break codegen.error, while a change to codegen.error can't break bindgen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→21 ir.analysis uses ir.context part of a loop✕
- Connections
- 1 pair of types, where a type in ir.analysis uses a type in ir.context.
- The types involved
bindgen.ir.analysis.analysis$module→bindgen.ir.context.BindgenContext
- Direction
- ir.analysis uses ir.context, so a change to ir.context can break ir.analysis, while a change to ir.analysis can't break ir.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→29 ir.annotations uses clang part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.annotations uses a type in clang.
- The types involved
bindgen.ir.annotations.Annotations→bindgen.clang.Commentbindgen.ir.annotations.Annotations→bindgen.clang.Cursor
- Direction
- ir.annotations uses clang, so a change to clang can break ir.annotations, while a change to ir.annotations can't break clang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→34 ir.annotations uses bindgen part of a loop✕
- Connections
- 1 pair of types, where a type in ir.annotations uses a type in bindgen.
- The types involved
bindgen.ir.annotations.FieldVisibilityKind→bindgen.Formatter
- Direction
- ir.annotations uses bindgen, so a change to bindgen can break ir.annotations, while a change to ir.annotations can't break bindgen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→21 ir.derive uses ir.context part of a loop✕
- Connections
- 8 pairs of types, where a type in ir.derive uses a type in ir.context.
- The types involved
bindgen.ir.derive.CanDeriveCopy→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDeriveDebug→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDeriveDefault→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDeriveEq→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDeriveHash→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDeriveOrd→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDerivePartialEq→bindgen.ir.context.BindgenContextbindgen.ir.derive.CanDerivePartialOrd→bindgen.ir.context.BindgenContext
- Direction
- ir.derive uses ir.context, so a change to ir.context can break ir.derive, while a change to ir.derive can't break ir.context.
- 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.
6→21 ir.dot uses ir.context part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.dot uses a type in ir.context.
- The types involved
bindgen.ir.dot.DotAttributes→bindgen.ir.context.BindgenContextbindgen.ir.dot.dot$module→bindgen.ir.context.BindgenContext
- Direction
- ir.dot uses ir.context, so a change to ir.context can break ir.dot, while a change to ir.dot can't break ir.context.
- 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.
7→21 ir.layout uses ir.context part of a loop✕
- Connections
- 1 pair of types, where a type in ir.layout uses a type in ir.context.
- The types involved
bindgen.ir.layout.Layout→bindgen.ir.context.BindgenContext
- Direction
- ir.layout uses ir.context, so a change to ir.context can break ir.layout, while a change to ir.layout can't break ir.context.
- 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.
7→29 ir.layout uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in ir.layout uses a type in clang.
- The types involved
bindgen.ir.layout.Layout→bindgen.clang.Type
- Direction
- ir.layout uses clang, so a change to clang can break ir.layout, while a change to ir.layout can't break clang.
- 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.
8→18 ir.traversal uses ir.item part of a loop✕
- Connections
- 1 pair of types, where a type in ir.traversal uses a type in ir.item.
- The types involved
bindgen.ir.traversal.ItemTraversal→bindgen.ir.item.Item
- Direction
- ir.traversal uses ir.item, so a change to ir.item can break ir.traversal, while a change to ir.traversal can't break ir.item.
- 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.
8→21 ir.traversal uses ir.context part of a loop✕
- Connections
- 11 pairs of types, where a type in ir.traversal uses a type in ir.context.
- The types involved
bindgen.ir.traversal.Edge→bindgen.ir.context.ItemIdbindgen.ir.traversal.ItemTraversal→bindgen.ir.context.BindgenContextbindgen.ir.traversal.ItemTraversal→bindgen.ir.context.ItemIdbindgen.ir.traversal.Paths→bindgen.ir.context.BindgenContextbindgen.ir.traversal.Paths→bindgen.ir.context.ItemIdbindgen.ir.traversal.Trace→bindgen.ir.context.BindgenContextbindgen.ir.traversal.Tracer→bindgen.ir.context.ItemIdbindgen.ir.traversal.TraversalQueue→bindgen.ir.context.ItemIdbindgen.ir.traversal.TraversalStorage→bindgen.ir.context.BindgenContextbindgen.ir.traversal.TraversalStorage→bindgen.ir.context.ItemIdbindgen.ir.traversal.traversal$module→bindgen.ir.context.BindgenContext
- Direction
- ir.traversal uses ir.context, so a change to ir.context can break ir.traversal, while a change to ir.traversal can't break ir.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→21 parse uses ir.context part of a loop✕
- Connections
- 1 pair of types, where a type in parse uses a type in ir.context.
- The types involved
bindgen.parse.ClangSubItemParser→bindgen.ir.context.BindgenContext
- Direction
- parse uses ir.context, so a change to ir.context can break parse, while a change to parse can't break ir.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→29 parse uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in parse uses a type in clang.
- The types involved
bindgen.parse.ClangSubItemParser→bindgen.clang.Cursor
- Direction
- parse uses clang, so a change to clang can break parse, while a change to parse can't break clang.
- 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.
10→4 codegen.struct_layout uses ir.annotations✕
- Connections
- 1 pair of types, where a type in codegen.struct_layout uses a type in ir.annotations.
- The types involved
bindgen.codegen.struct_layout.StructLayoutTracker→bindgen.ir.annotations.FieldVisibilityKind
- Direction
- codegen.struct_layout uses ir.annotations, so a change to ir.annotations can break codegen.struct_layout, while a change to codegen.struct_layout can't break ir.annotations.
- Position
- Below the diagonal: codegen.struct_layout uses a module listed above it, which is the healthy direction.
10→7 codegen.struct_layout uses ir.layout✕
- Connections
- 1 pair of types, where a type in codegen.struct_layout uses a type in ir.layout.
- The types involved
bindgen.codegen.struct_layout.StructLayoutTracker→bindgen.ir.layout.Layout
- Direction
- codegen.struct_layout uses ir.layout, so a change to ir.layout can break codegen.struct_layout, while a change to codegen.struct_layout can't break ir.layout.
- Position
- Below the diagonal: codegen.struct_layout uses a module listed above it, which is the healthy direction.
10→16 codegen.struct_layout uses ir.comp part of a loop✕
- Connections
- 1 pair of types, where a type in codegen.struct_layout uses a type in ir.comp.
- The types involved
bindgen.codegen.struct_layout.StructLayoutTracker→bindgen.ir.comp.CompInfo
- Direction
- codegen.struct_layout uses ir.comp, so a change to ir.comp can break codegen.struct_layout, while a change to codegen.struct_layout can't break ir.comp.
- 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.
10→21 codegen.struct_layout uses ir.context part of a loop✕
- Connections
- 1 pair of types, where a type in codegen.struct_layout uses a type in ir.context.
- The types involved
bindgen.codegen.struct_layout.StructLayoutTracker→bindgen.ir.context.BindgenContext
- Direction
- codegen.struct_layout uses ir.context, so a change to ir.context can break codegen.struct_layout, while a change to codegen.struct_layout can't break ir.context.
- 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.
10→29 codegen.struct_layout uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in codegen.struct_layout uses a type in clang.
- The types involved
bindgen.codegen.struct_layout.StructLayoutTracker→bindgen.clang.Type
- Direction
- codegen.struct_layout uses clang, so a change to clang can break codegen.struct_layout, while a change to codegen.struct_layout can't break clang.
- 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.
11→3 ir.analysis.has_vtable uses ir.analysis✕
- Connections
- 2 pairs of types, where a type in ir.analysis.has_vtable uses a type in ir.analysis.
- The types involved
bindgen.ir.analysis.has_vtable.HasVtableAnalysis→bindgen.ir.analysis.ConstrainResultbindgen.ir.analysis.has_vtable.HasVtableAnalysis→bindgen.ir.analysis.MonotoneFramework
- Direction
- ir.analysis.has_vtable uses ir.analysis, so a change to ir.analysis can break ir.analysis.has_vtable, while a change to ir.analysis.has_vtable can't break ir.analysis.
- Position
- Below the diagonal: ir.analysis.has_vtable uses a module listed above it, which is the healthy direction.
11→8 ir.analysis.has_vtable uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.analysis.has_vtable uses a type in ir.traversal.
- The types involved
bindgen.ir.analysis.has_vtable.HasVtableAnalysis→bindgen.ir.traversal.EdgeKind
- Direction
- ir.analysis.has_vtable uses ir.traversal, so a change to ir.traversal can break ir.analysis.has_vtable, while a change to ir.analysis.has_vtable can't break ir.traversal.
- Position
- Below the diagonal: ir.analysis.has_vtable uses a module listed above it, which is the healthy direction.
11→21 ir.analysis.has_vtable uses ir.context part of a loop✕
- Connections
- 3 pairs of types, where a type in ir.analysis.has_vtable uses a type in ir.context.
- The types involved
bindgen.ir.analysis.has_vtable.HasVtable→bindgen.ir.context.BindgenContextbindgen.ir.analysis.has_vtable.HasVtableAnalysis→bindgen.ir.context.BindgenContextbindgen.ir.analysis.has_vtable.HasVtableAnalysis→bindgen.ir.context.ItemId
- Direction
- ir.analysis.has_vtable uses ir.context, so a change to ir.context can break ir.analysis.has_vtable, while a change to ir.analysis.has_vtable can't break ir.context.
- 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.
12→3 ir.analysis.sizedness uses ir.analysis✕
- Connections
- 2 pairs of types, where a type in ir.analysis.sizedness uses a type in ir.analysis.
- The types involved
bindgen.ir.analysis.sizedness.SizednessAnalysis→bindgen.ir.analysis.ConstrainResultbindgen.ir.analysis.sizedness.SizednessAnalysis→bindgen.ir.analysis.MonotoneFramework
- Direction
- ir.analysis.sizedness uses ir.analysis, so a change to ir.analysis can break ir.analysis.sizedness, while a change to ir.analysis.sizedness can't break ir.analysis.
- Position
- Below the diagonal: ir.analysis.sizedness uses a module listed above it, which is the healthy direction.
12→8 ir.analysis.sizedness uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.analysis.sizedness uses a type in ir.traversal.
- The types involved
bindgen.ir.analysis.sizedness.SizednessAnalysis→bindgen.ir.traversal.EdgeKind
- Direction
- ir.analysis.sizedness uses ir.traversal, so a change to ir.traversal can break ir.analysis.sizedness, while a change to ir.analysis.sizedness can't break ir.traversal.
- Position
- Below the diagonal: ir.analysis.sizedness uses a module listed above it, which is the healthy direction.
12→21 ir.analysis.sizedness uses ir.context part of a loop✕
- Connections
- 3 pairs of types, where a type in ir.analysis.sizedness uses a type in ir.context.
- The types involved
bindgen.ir.analysis.sizedness.Sizedness→bindgen.ir.context.BindgenContextbindgen.ir.analysis.sizedness.SizednessAnalysis→bindgen.ir.context.BindgenContextbindgen.ir.analysis.sizedness.SizednessAnalysis→bindgen.ir.context.TypeId
- Direction
- ir.analysis.sizedness uses ir.context, so a change to ir.context can break ir.analysis.sizedness, while a change to ir.analysis.sizedness can't break ir.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→6 ir.function uses ir.dot✕
- Connections
- 1 pair of types, where a type in ir.function uses a type in ir.dot.
- The types involved
bindgen.ir.function.Function→bindgen.ir.dot.DotAttributes
- Direction
- ir.function uses ir.dot, so a change to ir.dot can break ir.function, while a change to ir.function can't break ir.dot.
- Position
- Below the diagonal: ir.function uses a module listed above it, which is the healthy direction.
13→8 ir.function uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.function uses a type in ir.traversal.
- The types involved
bindgen.ir.function.FunctionSig→bindgen.ir.traversal.Trace
- Direction
- ir.function uses ir.traversal, so a change to ir.traversal can break ir.function, while a change to ir.function can't break ir.traversal.
- Position
- Below the diagonal: ir.function uses a module listed above it, which is the healthy direction.
13→9 ir.function uses parse✕
- Connections
- 1 pair of types, where a type in ir.function uses a type in parse.
- The types involved
bindgen.ir.function.Function→bindgen.parse.ClangSubItemParser
- Direction
- ir.function uses parse, so a change to parse can break ir.function, while a change to ir.function can't break parse.
- Position
- Below the diagonal: ir.function uses a module listed above it, which is the healthy direction.
13→18 ir.function uses ir.item part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.function uses a type in ir.item.
- The types involved
bindgen.ir.function.Function→bindgen.ir.item.Itembindgen.ir.function.FunctionSig→bindgen.ir.item.Item
- Direction
- ir.function uses ir.item, so a change to ir.item can break ir.function, while a change to ir.function can't break ir.item.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→20 ir.function uses codegen.serialize part of a loop✕
- Connections
- 1 pair of types, where a type in ir.function uses a type in codegen.serialize.
- The types involved
bindgen.ir.function.Function→bindgen.codegen.serialize.CSerialize
- Direction
- ir.function uses codegen.serialize, so a change to codegen.serialize can break ir.function, while a change to ir.function can't break codegen.serialize.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 ir.function uses ir.context part of a loop✕
- Connections
- 5 pairs of types, where a type in ir.function uses a type in ir.context.
- The types involved
bindgen.ir.function.Function→bindgen.ir.context.BindgenContextbindgen.ir.function.Function→bindgen.ir.context.TypeIdbindgen.ir.function.FunctionSig→bindgen.ir.context.BindgenContextbindgen.ir.function.FunctionSig→bindgen.ir.context.TypeIdbindgen.ir.function.function$module→bindgen.ir.context.BindgenContext
- Direction
- ir.function uses ir.context, so a change to ir.context can break ir.function, while a change to ir.function can't break ir.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→28 ir.function uses codegen part of a loop✕
- Connections
- 3 pairs of types, where a type in ir.function uses a type in codegen.
- The types involved
bindgen.ir.function.Function→bindgen.codegen.CodeGeneratorbindgen.ir.function.Function→bindgen.codegen.CodegenResultbindgen.ir.function.FunctionSig→bindgen.codegen.TryToRustTy
- Direction
- ir.function uses codegen, so a change to codegen can break ir.function, while a change to ir.function can't break codegen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 ir.function uses clang part of a loop✕
- Connections
- 6 pairs of types, where a type in ir.function uses a type in clang.
- The types involved
bindgen.ir.function.Function→bindgen.clang.Cursorbindgen.ir.function.FunctionKind→bindgen.clang.Cursorbindgen.ir.function.FunctionSig→bindgen.clang.Cursorbindgen.ir.function.FunctionSig→bindgen.clang.Typebindgen.ir.function.function$module→bindgen.clang.Cursorbindgen.ir.function.function$module→bindgen.clang.Type
- Direction
- ir.function uses clang, so a change to clang can break ir.function, while a change to ir.function can't break clang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→34 ir.function uses bindgen part of a loop✕
- Connections
- 1 pair of types, where a type in ir.function uses a type in bindgen.
- The types involved
bindgen.ir.function.Abi→bindgen.Formatter
- Direction
- ir.function uses bindgen, so a change to bindgen can break ir.function, while a change to ir.function can't break bindgen.
- 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.
14→6 ir.module uses ir.dot✕
- Connections
- 1 pair of types, where a type in ir.module uses a type in ir.dot.
- The types involved
bindgen.ir.module.Module→bindgen.ir.dot.DotAttributes
- Direction
- ir.module uses ir.dot, so a change to ir.dot can break ir.module, while a change to ir.module can't break ir.dot.
- Position
- Below the diagonal: ir.module uses a module listed above it, which is the healthy direction.
14→9 ir.module uses parse✕
- Connections
- 1 pair of types, where a type in ir.module uses a type in parse.
- The types involved
bindgen.ir.module.Module→bindgen.parse.ClangSubItemParser
- Direction
- ir.module uses parse, so a change to parse can break ir.module, while a change to ir.module can't break parse.
- Position
- Below the diagonal: ir.module uses a module listed above it, which is the healthy direction.
14→18 ir.module uses ir.item part of a loop✕
- Connections
- 1 pair of types, where a type in ir.module uses a type in ir.item.
- The types involved
bindgen.ir.module.Module→bindgen.ir.item.Item
- Direction
- ir.module uses ir.item, so a change to ir.item can break ir.module, while a change to ir.module can't break ir.item.
- 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.
14→21 ir.module uses ir.context part of a loop✕
- Connections
- 1 pair of types, where a type in ir.module uses a type in ir.context.
- The types involved
bindgen.ir.module.Module→bindgen.ir.context.BindgenContext
- Direction
- ir.module uses ir.context, so a change to ir.context can break ir.module, while a change to ir.module can't break ir.context.
- 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.
14→28 ir.module uses codegen part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.module uses a type in codegen.
- The types involved
bindgen.ir.module.Module→bindgen.codegen.CodeGeneratorbindgen.ir.module.Module→bindgen.codegen.CodegenResult
- Direction
- ir.module uses codegen, so a change to codegen can break ir.module, while a change to ir.module can't break codegen.
- 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.
14→29 ir.module uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in ir.module uses a type in clang.
- The types involved
bindgen.ir.module.Module→bindgen.clang.Cursor
- Direction
- ir.module uses clang, so a change to clang can break ir.module, while a change to ir.module can't break clang.
- 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→8 ir.template uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.template uses a type in ir.traversal.
- The types involved
bindgen.ir.template.TemplateInstantiation→bindgen.ir.traversal.Trace
- Direction
- ir.template uses ir.traversal, so a change to ir.traversal can break ir.template, while a change to ir.template can't break ir.traversal.
- Position
- Below the diagonal: ir.template uses a module listed above it, which is the healthy direction.
15→18 ir.template uses ir.item part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.template uses a type in ir.item.
- The types involved
bindgen.ir.template.TemplateInstantiation→bindgen.ir.item.IsOpaquebindgen.ir.template.TemplateInstantiation→bindgen.ir.item.Item
- Direction
- ir.template uses ir.item, so a change to ir.item can break ir.template, while a change to ir.template can't break ir.item.
- 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→21 ir.template uses ir.context part of a loop✕
- Connections
- 6 pairs of types, where a type in ir.template uses a type in ir.context.
- The types involved
bindgen.ir.template.AsTemplateParam→bindgen.ir.context.BindgenContextbindgen.ir.template.AsTemplateParam→bindgen.ir.context.TypeIdbindgen.ir.template.TemplateInstantiation→bindgen.ir.context.BindgenContextbindgen.ir.template.TemplateInstantiation→bindgen.ir.context.TypeIdbindgen.ir.template.TemplateParameters→bindgen.ir.context.BindgenContextbindgen.ir.template.TemplateParameters→bindgen.ir.context.TypeId
- Direction
- ir.template uses ir.context, so a change to ir.context can break ir.template, while a change to ir.template can't break ir.context.
- 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→28 ir.template uses codegen part of a loop✕
- Connections
- 4 pairs of types, where a type in ir.template uses a type in codegen.
- The types involved
bindgen.ir.template.TemplateInstantiation→bindgen.codegen.CodeGeneratorbindgen.ir.template.TemplateInstantiation→bindgen.codegen.CodegenResultbindgen.ir.template.TemplateInstantiation→bindgen.codegen.TryToOpaquebindgen.ir.template.TemplateInstantiation→bindgen.codegen.TryToRustTy
- Direction
- ir.template uses codegen, so a change to codegen can break ir.template, while a change to ir.template can't break codegen.
- 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→29 ir.template uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in ir.template uses a type in clang.
- The types involved
bindgen.ir.template.TemplateInstantiation→bindgen.clang.Type
- Direction
- ir.template uses clang, so a change to clang can break ir.template, while a change to ir.template can't break clang.
- 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→4 ir.comp uses ir.annotations✕
- Connections
- 12 pairs of types, where a type in ir.comp uses a type in ir.annotations.
- The types involved
bindgen.ir.comp.Bitfield→bindgen.ir.annotations.Annotationsbindgen.ir.comp.Bitfield→bindgen.ir.annotations.FieldAccessorKindbindgen.ir.comp.Bitfield→bindgen.ir.annotations.FieldVisibilityKindbindgen.ir.comp.BitfieldUnit→bindgen.ir.annotations.FieldAccessorKindbindgen.ir.comp.BitfieldUnit→bindgen.ir.annotations.FieldVisibilityKindbindgen.ir.comp.Field→bindgen.ir.annotations.FieldAccessorKindbindgen.ir.comp.Field→bindgen.ir.annotations.FieldVisibilityKindbindgen.ir.comp.FieldData→bindgen.ir.annotations.Annotationsbindgen.ir.comp.FieldData→bindgen.ir.annotations.FieldAccessorKindbindgen.ir.comp.FieldData→bindgen.ir.annotations.FieldVisibilityKindbindgen.ir.comp.FieldMethods→bindgen.ir.annotations.Annotationsbindgen.ir.comp.RawField→bindgen.ir.annotations.Annotations
- Direction
- ir.comp uses ir.annotations, so a change to ir.annotations can break ir.comp, while a change to ir.comp can't break ir.annotations.
- Position
- Below the diagonal: ir.comp uses a module listed above it, which is the healthy direction.
16→6 ir.comp uses ir.dot✕
- Connections
- 4 pairs of types, where a type in ir.comp uses a type in ir.dot.
- The types involved
bindgen.ir.comp.Bitfield→bindgen.ir.dot.DotAttributesbindgen.ir.comp.CompInfo→bindgen.ir.dot.DotAttributesbindgen.ir.comp.Field→bindgen.ir.dot.DotAttributesbindgen.ir.comp.FieldData→bindgen.ir.dot.DotAttributes
- Direction
- ir.comp uses ir.dot, so a change to ir.dot can break ir.comp, while a change to ir.comp can't break ir.dot.
- Position
- Below the diagonal: ir.comp uses a module listed above it, which is the healthy direction.
16→7 ir.comp uses ir.layout✕
- Connections
- 3 pairs of types, where a type in ir.comp uses a type in ir.layout.
- The types involved
bindgen.ir.comp.BitfieldUnit→bindgen.ir.layout.Layoutbindgen.ir.comp.CompInfo→bindgen.ir.layout.Layoutbindgen.ir.comp.Field→bindgen.ir.layout.Layout
- Direction
- ir.comp uses ir.layout, so a change to ir.layout can break ir.comp, while a change to ir.comp can't break ir.layout.
- Position
- Below the diagonal: ir.comp uses a module listed above it, which is the healthy direction.
16→8 ir.comp uses ir.traversal✕
- Connections
- 3 pairs of types, where a type in ir.comp uses a type in ir.traversal.
- The types involved
bindgen.ir.comp.CompFields→bindgen.ir.traversal.Tracebindgen.ir.comp.CompInfo→bindgen.ir.traversal.Tracebindgen.ir.comp.Field→bindgen.ir.traversal.Trace
- Direction
- ir.comp uses ir.traversal, so a change to ir.traversal can break ir.comp, while a change to ir.comp can't break ir.traversal.
- Position
- Below the diagonal: ir.comp uses a module listed above it, which is the healthy direction.
16→10 ir.comp uses codegen.struct_layout✕
- Connections
- 4 pairs of types, where a type in ir.comp uses a type in codegen.struct_layout.
- The types involved
bindgen.ir.comp.Bitfield→bindgen.codegen.struct_layout.StructLayoutTrackerbindgen.ir.comp.BitfieldUnit→bindgen.codegen.struct_layout.StructLayoutTrackerbindgen.ir.comp.Field→bindgen.codegen.struct_layout.StructLayoutTrackerbindgen.ir.comp.FieldData→bindgen.codegen.struct_layout.StructLayoutTracker
- Direction
- ir.comp uses codegen.struct_layout, so a change to codegen.struct_layout can break ir.comp, while a change to ir.comp can't break codegen.struct_layout.
- Position
- Below the diagonal: ir.comp uses a module listed above it, which is the healthy direction.
16→15 ir.comp uses ir.template✕
- Connections
- 1 pair of types, where a type in ir.comp uses a type in ir.template.
- The types involved
bindgen.ir.comp.CompInfo→bindgen.ir.template.TemplateParameters
- Direction
- ir.comp uses ir.template, so a change to ir.template can break ir.comp, while a change to ir.comp can't break ir.template.
- Position
- Below the diagonal: ir.comp uses a module listed above it, which is the healthy direction.
16→17 ir.comp uses codegen.impl_debug part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.comp uses a type in codegen.impl_debug.
- The types involved
bindgen.ir.comp.BitfieldUnit→bindgen.codegen.impl_debug.ImplDebugbindgen.ir.comp.FieldData→bindgen.codegen.impl_debug.ImplDebug
- Direction
- ir.comp uses codegen.impl_debug, so a change to codegen.impl_debug can break ir.comp, while a change to ir.comp can't break codegen.impl_debug.
- 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→18 ir.comp uses ir.item part of a loop✕
- Connections
- 6 pairs of types, where a type in ir.comp uses a type in ir.item.
- The types involved
bindgen.ir.comp.Bitfield→bindgen.ir.item.Itembindgen.ir.comp.BitfieldUnit→bindgen.ir.item.Itembindgen.ir.comp.CompInfo→bindgen.ir.item.IsOpaquebindgen.ir.comp.CompInfo→bindgen.ir.item.Itembindgen.ir.comp.Field→bindgen.ir.item.Itembindgen.ir.comp.FieldData→bindgen.ir.item.Item
- Direction
- ir.comp uses ir.item, so a change to ir.item can break ir.comp, while a change to ir.comp can't break ir.item.
- 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→21 ir.comp uses ir.context part of a loop✕
- Connections
- 20 pairs of types, where a type in ir.comp uses a type in ir.context.
- The types involved
bindgen.ir.comp.Base→bindgen.ir.context.BindgenContextbindgen.ir.comp.Base→bindgen.ir.context.TypeIdbindgen.ir.comp.Bitfield→bindgen.ir.context.BindgenContextbindgen.ir.comp.Bitfield→bindgen.ir.context.TypeIdbindgen.ir.comp.BitfieldUnit→bindgen.ir.context.BindgenContextbindgen.ir.comp.CompFields→bindgen.ir.context.BindgenContextbindgen.ir.comp.CompFields→bindgen.ir.context.TypeIdbindgen.ir.comp.CompInfo→bindgen.ir.context.BindgenContextbindgen.ir.comp.CompInfo→bindgen.ir.context.FunctionIdbindgen.ir.comp.CompInfo→bindgen.ir.context.ItemIdbindgen.ir.comp.CompInfo→bindgen.ir.context.TypeIdbindgen.ir.comp.CompInfo→bindgen.ir.context.VarIdbindgen.ir.comp.Field→bindgen.ir.context.BindgenContextbindgen.ir.comp.FieldData→bindgen.ir.context.BindgenContextbindgen.ir.comp.FieldData→bindgen.ir.context.TypeIdbindgen.ir.comp.FieldMethods→bindgen.ir.context.TypeIdbindgen.ir.comp.Method→bindgen.ir.context.BindgenContextbindgen.ir.comp.Method→bindgen.ir.context.FunctionIdbindgen.ir.comp.RawField→bindgen.ir.context.TypeIdbindgen.ir.comp.comp$module→bindgen.ir.context.BindgenContext
- Direction
- ir.comp uses ir.context, so a change to ir.context can break ir.comp, while a change to ir.comp can't break ir.context.
- 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→28 ir.comp uses codegen part of a loop✕
- Connections
- 11 pairs of types, where a type in ir.comp uses a type in codegen.
- The types involved
bindgen.ir.comp.Bitfield→bindgen.codegen.CodegenResultbindgen.ir.comp.Bitfield→bindgen.codegen.FieldCodegenbindgen.ir.comp.BitfieldUnit→bindgen.codegen.CodegenResultbindgen.ir.comp.BitfieldUnit→bindgen.codegen.FieldCodegenbindgen.ir.comp.CompInfo→bindgen.codegen.CodeGeneratorbindgen.ir.comp.CompInfo→bindgen.codegen.CodegenResultbindgen.ir.comp.Field→bindgen.codegen.CodegenResultbindgen.ir.comp.Field→bindgen.codegen.FieldCodegenbindgen.ir.comp.FieldData→bindgen.codegen.CodegenResultbindgen.ir.comp.FieldData→bindgen.codegen.FieldCodegenbindgen.ir.comp.Method→bindgen.codegen.CodegenResult
- Direction
- ir.comp uses codegen, so a change to codegen can break ir.comp, while a change to ir.comp can't break codegen.
- 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→29 ir.comp uses clang part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.comp uses a type in clang.
- The types involved
bindgen.ir.comp.CompInfo→bindgen.clang.Cursorbindgen.ir.comp.CompInfo→bindgen.clang.Type
- Direction
- ir.comp uses clang, so a change to clang can break ir.comp, while a change to ir.comp can't break clang.
- 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→33 ir.comp uses callbacks part of a loop✕
- Connections
- 1 pair of types, where a type in ir.comp uses a type in callbacks.
- The types involved
bindgen.ir.comp.Method→bindgen.callbacks.DiscoveredItemId
- Direction
- ir.comp uses callbacks, so a change to callbacks can break ir.comp, while a change to ir.comp can't break callbacks.
- 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→16 codegen.impl_debug uses ir.comp✕
- Connections
- 1 pair of types, where a type in codegen.impl_debug uses a type in ir.comp.
- The types involved
bindgen.codegen.impl_debug.impl_debug$module→bindgen.ir.comp.CompKind
- Direction
- codegen.impl_debug uses ir.comp, so a change to ir.comp can break codegen.impl_debug, while a change to codegen.impl_debug can't break ir.comp.
- Position
- Below the diagonal: codegen.impl_debug uses a module listed above it, which is the healthy direction.
17→18 codegen.impl_debug uses ir.item part of a loop✕
- Connections
- 1 pair of types, where a type in codegen.impl_debug uses a type in ir.item.
- The types involved
bindgen.codegen.impl_debug.impl_debug$module→bindgen.ir.item.Item
- Direction
- codegen.impl_debug uses ir.item, so a change to ir.item can break codegen.impl_debug, while a change to codegen.impl_debug can't break ir.item.
- 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→21 codegen.impl_debug uses ir.context part of a loop✕
- Connections
- 2 pairs of types, where a type in codegen.impl_debug uses a type in ir.context.
- The types involved
bindgen.codegen.impl_debug.ImplDebug→bindgen.ir.context.BindgenContextbindgen.codegen.impl_debug.impl_debug$module→bindgen.ir.context.BindgenContext
- Direction
- codegen.impl_debug uses ir.context, so a change to ir.context can break codegen.impl_debug, while a change to codegen.impl_debug can't break ir.context.
- 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→4 ir.item uses ir.annotations✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in ir.annotations.
- The types involved
bindgen.ir.item.Item→bindgen.ir.annotations.Annotations
- Direction
- ir.item uses ir.annotations, so a change to ir.annotations can break ir.item, while a change to ir.item can't break ir.annotations.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→5 ir.item uses ir.derive✕
- Connections
- 8 pairs of types, where a type in ir.item uses a type in ir.derive.
- The types involved
bindgen.ir.item.Item→bindgen.ir.derive.CanDeriveCopybindgen.ir.item.Item→bindgen.ir.derive.CanDeriveDebugbindgen.ir.item.Item→bindgen.ir.derive.CanDeriveDefaultbindgen.ir.item.Item→bindgen.ir.derive.CanDeriveEqbindgen.ir.item.Item→bindgen.ir.derive.CanDeriveHashbindgen.ir.item.Item→bindgen.ir.derive.CanDeriveOrdbindgen.ir.item.Item→bindgen.ir.derive.CanDerivePartialEqbindgen.ir.item.Item→bindgen.ir.derive.CanDerivePartialOrd
- Direction
- ir.item uses ir.derive, so a change to ir.derive can break ir.item, while a change to ir.item can't break ir.derive.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→6 ir.item uses ir.dot✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in ir.dot.
- The types involved
bindgen.ir.item.Item→bindgen.ir.dot.DotAttributes
- Direction
- ir.item uses ir.dot, so a change to ir.dot can break ir.item, while a change to ir.item can't break ir.dot.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→8 ir.item uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in ir.traversal.
- The types involved
bindgen.ir.item.Item→bindgen.ir.traversal.Trace
- Direction
- ir.item uses ir.traversal, so a change to ir.traversal can break ir.item, while a change to ir.item can't break ir.traversal.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→11 ir.item uses ir.analysis.has_vtable✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in ir.analysis.has_vtable.
- The types involved
bindgen.ir.item.Item→bindgen.ir.analysis.has_vtable.HasVtable
- Direction
- ir.item uses ir.analysis.has_vtable, so a change to ir.analysis.has_vtable can break ir.item, while a change to ir.item can't break ir.analysis.has_vtable.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→12 ir.item uses ir.analysis.sizedness✕
- Connections
- 2 pairs of types, where a type in ir.item uses a type in ir.analysis.sizedness.
- The types involved
bindgen.ir.item.Item→bindgen.ir.analysis.sizedness.Sizednessbindgen.ir.item.Item→bindgen.ir.analysis.sizedness.SizednessResult
- Direction
- ir.item uses ir.analysis.sizedness, so a change to ir.analysis.sizedness can break ir.item, while a change to ir.item can't break ir.analysis.sizedness.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→13 ir.item uses ir.function✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in ir.function.
- The types involved
bindgen.ir.item.Item→bindgen.ir.function.Function
- Direction
- ir.item uses ir.function, so a change to ir.function can break ir.item, while a change to ir.item can't break ir.function.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→14 ir.item uses ir.module✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in ir.module.
- The types involved
bindgen.ir.item.Item→bindgen.ir.module.Module
- Direction
- ir.item uses ir.module, so a change to ir.module can break ir.item, while a change to ir.item can't break ir.module.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→15 ir.item uses ir.template✕
- Connections
- 2 pairs of types, where a type in ir.item uses a type in ir.template.
- The types involved
bindgen.ir.item.Item→bindgen.ir.template.AsTemplateParambindgen.ir.item.Item→bindgen.ir.template.TemplateParameters
- Direction
- ir.item uses ir.template, so a change to ir.template can break ir.item, while a change to ir.item can't break ir.template.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→17 ir.item uses codegen.impl_debug✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in codegen.impl_debug.
- The types involved
bindgen.ir.item.Item→bindgen.codegen.impl_debug.ImplDebug
- Direction
- ir.item uses codegen.impl_debug, so a change to codegen.impl_debug can break ir.item, while a change to ir.item can't break codegen.impl_debug.
- Position
- Below the diagonal: ir.item uses a module listed above it, which is the healthy direction.
18→20 ir.item uses codegen.serialize part of a loop✕
- Connections
- 1 pair of types, where a type in ir.item uses a type in codegen.serialize.
- The types involved
bindgen.ir.item.Item→bindgen.codegen.serialize.CSerialize
- Direction
- ir.item uses codegen.serialize, so a change to codegen.serialize can break ir.item, while a change to ir.item can't break codegen.serialize.
- 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→21 ir.item uses ir.context part of a loop✕
- Connections
- 14 pairs of types, where a type in ir.item uses a type in ir.context.
- The types involved
bindgen.ir.item.DebugOnlyItemSet→bindgen.ir.context.ItemIdbindgen.ir.item.HasTypeParamInArray→bindgen.ir.context.BindgenContextbindgen.ir.item.IsOpaque→bindgen.ir.context.BindgenContextbindgen.ir.item.Item→bindgen.ir.context.BindgenContextbindgen.ir.item.Item→bindgen.ir.context.ItemIdbindgen.ir.item.Item→bindgen.ir.context.TypeIdbindgen.ir.item.ItemAncestors→bindgen.ir.context.BindgenContextbindgen.ir.item.ItemAncestorsIter→bindgen.ir.context.BindgenContextbindgen.ir.item.ItemAncestorsIter→bindgen.ir.context.ItemIdbindgen.ir.item.ItemCanonicalName→bindgen.ir.context.BindgenContextbindgen.ir.item.ItemCanonicalPath→bindgen.ir.context.BindgenContextbindgen.ir.item.NameOptions→bindgen.ir.context.BindgenContextbindgen.ir.item.item$module→bindgen.ir.context.BindgenContextbindgen.ir.item.item$module→bindgen.ir.context.ItemId
- Direction
- ir.item uses ir.context, so a change to ir.context can break ir.item, while a change to ir.item can't break ir.context.
- 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→28 ir.item uses codegen part of a loop✕
- Connections
- 5 pairs of types, where a type in ir.item uses a type in codegen.
- The types involved
bindgen.ir.item.Item→bindgen.codegen.AliasVariationbindgen.ir.item.Item→bindgen.codegen.CodeGeneratorbindgen.ir.item.Item→bindgen.codegen.CodegenResultbindgen.ir.item.Item→bindgen.codegen.TryToOpaquebindgen.ir.item.Item→bindgen.codegen.TryToRustTy
- Direction
- ir.item uses codegen, so a change to codegen can break ir.item, while a change to ir.item can't break codegen.
- 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→29 ir.item uses clang part of a loop✕
- Connections
- 4 pairs of types, where a type in ir.item uses a type in clang.
- The types involved
bindgen.ir.item.Item→bindgen.clang.Cursorbindgen.ir.item.Item→bindgen.clang.Typebindgen.ir.item.item$module→bindgen.clang.Cursorbindgen.ir.item.item$module→bindgen.clang.Type
- Direction
- ir.item uses clang, so a change to clang can break ir.item, while a change to ir.item can't break clang.
- 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→33 ir.item uses callbacks part of a loop✕
- Connections
- 3 pairs of types, where a type in ir.item uses a type in callbacks.
- The types involved
bindgen.ir.item.Item→bindgen.callbacks.ItemKindbindgen.ir.item.Item→bindgen.callbacks.SourceLocationbindgen.ir.item.Item→bindgen.callbacks.TypeKind
- Direction
- ir.item uses callbacks, so a change to callbacks can break ir.item, while a change to ir.item can't break callbacks.
- 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.
19→18 codegen.postprocessing.merge_extern_blocks uses ir.item✕
- Connections
- 1 pair of types, where a type in codegen.postprocessing.merge_extern_blocks uses a type in ir.item.
- The types involved
bindgen.codegen.postprocessing.merge_extern_blocks.merge_extern_blocks$module→bindgen.ir.item.Item
- Direction
- codegen.postprocessing.merge_extern_blocks uses ir.item, so a change to ir.item can break codegen.postprocessing.merge_extern_blocks, while a change to codegen.postprocessing.merge_extern_blocks can't break ir.item.
- Position
- Below the diagonal: codegen.postprocessing.merge_extern_blocks uses a module listed above it, which is the healthy direction.
19→29 codegen.postprocessing.merge_extern_blocks uses clang part of a loop✕
- Connections
- 2 pairs of types, where a type in codegen.postprocessing.merge_extern_blocks uses a type in clang.
- The types involved
bindgen.codegen.postprocessing.merge_extern_blocks.Visitor→bindgen.clang.Filebindgen.codegen.postprocessing.merge_extern_blocks.merge_extern_blocks$module→bindgen.clang.File
- Direction
- codegen.postprocessing.merge_extern_blocks uses clang, so a change to clang can break codegen.postprocessing.merge_extern_blocks, while a change to codegen.postprocessing.merge_extern_blocks can't break clang.
- 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→18 codegen.serialize uses ir.item✕
- Connections
- 1 pair of types, where a type in codegen.serialize uses a type in ir.item.
- The types involved
bindgen.codegen.serialize.serialize$module→bindgen.ir.item.Item
- Direction
- codegen.serialize uses ir.item, so a change to ir.item can break codegen.serialize, while a change to codegen.serialize can't break ir.item.
- Position
- Below the diagonal: codegen.serialize uses a module listed above it, which is the healthy direction.
20→21 codegen.serialize uses ir.context part of a loop✕
- Connections
- 2 pairs of types, where a type in codegen.serialize uses a type in ir.context.
- The types involved
bindgen.codegen.serialize.CSerialize→bindgen.ir.context.BindgenContextbindgen.codegen.serialize.serialize$module→bindgen.ir.context.BindgenContext
- Direction
- codegen.serialize uses ir.context, so a change to ir.context can break codegen.serialize, while a change to codegen.serialize can't break ir.context.
- 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→5 ir.context uses ir.derive✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in ir.derive.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.ir.derive.CanDerive
- Direction
- ir.context uses ir.derive, so a change to ir.derive can break ir.context, while a change to ir.context can't break ir.derive.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→8 ir.context uses ir.traversal✕
- Connections
- 2 pairs of types, where a type in ir.context uses a type in ir.traversal.
- The types involved
bindgen.ir.context.AllowlistedItemsTraversal→bindgen.ir.traversal.ItemTraversalbindgen.ir.context.ItemId→bindgen.ir.traversal.Edge
- Direction
- ir.context uses ir.traversal, so a change to ir.traversal can break ir.context, while a change to ir.context can't break ir.traversal.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→11 ir.context uses ir.analysis.has_vtable✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in ir.analysis.has_vtable.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.ir.analysis.has_vtable.HasVtableResult
- Direction
- ir.context uses ir.analysis.has_vtable, so a change to ir.analysis.has_vtable can break ir.context, while a change to ir.context can't break ir.analysis.has_vtable.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→12 ir.context uses ir.analysis.sizedness✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in ir.analysis.sizedness.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.ir.analysis.sizedness.SizednessResult
- Direction
- ir.context uses ir.analysis.sizedness, so a change to ir.analysis.sizedness can break ir.context, while a change to ir.context can't break ir.analysis.sizedness.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→13 ir.context uses ir.function✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in ir.function.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.ir.function.Function
- Direction
- ir.context uses ir.function, so a change to ir.function can break ir.context, while a change to ir.context can't break ir.function.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→15 ir.context uses ir.template✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in ir.template.
- The types involved
bindgen.ir.context.PartialType→bindgen.ir.template.TemplateParameters
- Direction
- ir.context uses ir.template, so a change to ir.template can break ir.context, while a change to ir.context can't break ir.template.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→18 ir.context uses ir.item✕
- Connections
- 2 pairs of types, where a type in ir.context uses a type in ir.item.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.ir.item.Itembindgen.ir.context.ItemResolver→bindgen.ir.item.Item
- Direction
- ir.context uses ir.item, so a change to ir.item can break ir.context, while a change to ir.context can't break ir.item.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→20 ir.context uses codegen.serialize✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in codegen.serialize.
- The types involved
bindgen.ir.context.TypeId→bindgen.codegen.serialize.CSerialize
- Direction
- ir.context uses codegen.serialize, so a change to codegen.serialize can break ir.context, while a change to ir.context can't break codegen.serialize.
- Position
- Below the diagonal: ir.context uses a module listed above it, which is the healthy direction.
21→29 ir.context uses clang part of a loop✕
- Connections
- 9 pairs of types, where a type in ir.context uses a type in clang.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.clang.ABIKindbindgen.ir.context.BindgenContext→bindgen.clang.CanonicalTypeDeclarationbindgen.ir.context.BindgenContext→bindgen.clang.Cursorbindgen.ir.context.BindgenContext→bindgen.clang.EvalResultbindgen.ir.context.BindgenContext→bindgen.clang.FallbackTranslationUnitbindgen.ir.context.BindgenContext→bindgen.clang.TargetInfobindgen.ir.context.BindgenContext→bindgen.clang.TranslationUnitbindgen.ir.context.BindgenContext→bindgen.clang.Typebindgen.ir.context.PartialType→bindgen.clang.Cursor
- Direction
- ir.context uses clang, so a change to clang can break ir.context, while a change to ir.context can't break clang.
- 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→32 ir.context uses ir.analysis.derive part of a loop✕
- Connections
- 1 pair of types, where a type in ir.context uses a type in ir.analysis.derive.
- The types involved
bindgen.ir.context.BindgenContext→bindgen.ir.analysis.derive.DeriveTrait
- Direction
- ir.context uses ir.analysis.derive, so a change to ir.analysis.derive can break ir.context, while a change to ir.context can't break ir.analysis.derive.
- 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→13 codegen.dyngen uses ir.function✕
- Connections
- 1 pair of types, where a type in codegen.dyngen uses a type in ir.function.
- The types involved
bindgen.codegen.dyngen.DynamicItems→bindgen.ir.function.ClangAbi
- Direction
- codegen.dyngen uses ir.function, so a change to ir.function can break codegen.dyngen, while a change to codegen.dyngen can't break ir.function.
- Position
- Below the diagonal: codegen.dyngen uses a module listed above it, which is the healthy direction.
22→21 codegen.dyngen uses ir.context✕
- Connections
- 1 pair of types, where a type in codegen.dyngen uses a type in ir.context.
- The types involved
bindgen.codegen.dyngen.DynamicItems→bindgen.ir.context.BindgenContext
- Direction
- codegen.dyngen uses ir.context, so a change to ir.context can break codegen.dyngen, while a change to codegen.dyngen can't break ir.context.
- Position
- Below the diagonal: codegen.dyngen uses a module listed above it, which is the healthy direction.
23→16 codegen.impl_partialeq uses ir.comp✕
- Connections
- 1 pair of types, where a type in codegen.impl_partialeq uses a type in ir.comp.
- The types involved
bindgen.codegen.impl_partialeq.impl_partialeq$module→bindgen.ir.comp.CompInfo
- Direction
- codegen.impl_partialeq uses ir.comp, so a change to ir.comp can break codegen.impl_partialeq, while a change to codegen.impl_partialeq can't break ir.comp.
- Position
- Below the diagonal: codegen.impl_partialeq uses a module listed above it, which is the healthy direction.
23→18 codegen.impl_partialeq uses ir.item✕
- Connections
- 1 pair of types, where a type in codegen.impl_partialeq uses a type in ir.item.
- The types involved
bindgen.codegen.impl_partialeq.impl_partialeq$module→bindgen.ir.item.Item
- Direction
- codegen.impl_partialeq uses ir.item, so a change to ir.item can break codegen.impl_partialeq, while a change to codegen.impl_partialeq can't break ir.item.
- Position
- Below the diagonal: codegen.impl_partialeq uses a module listed above it, which is the healthy direction.
23→21 codegen.impl_partialeq uses ir.context✕
- Connections
- 1 pair of types, where a type in codegen.impl_partialeq uses a type in ir.context.
- The types involved
bindgen.codegen.impl_partialeq.impl_partialeq$module→bindgen.ir.context.BindgenContext
- Direction
- codegen.impl_partialeq uses ir.context, so a change to ir.context can break codegen.impl_partialeq, while a change to codegen.impl_partialeq can't break ir.context.
- Position
- Below the diagonal: codegen.impl_partialeq uses a module listed above it, which is the healthy direction.
24→3 ir.analysis.has_destructor uses ir.analysis✕
- Connections
- 2 pairs of types, where a type in ir.analysis.has_destructor uses a type in ir.analysis.
- The types involved
bindgen.ir.analysis.has_destructor.HasDestructorAnalysis→bindgen.ir.analysis.ConstrainResultbindgen.ir.analysis.has_destructor.HasDestructorAnalysis→bindgen.ir.analysis.MonotoneFramework
- Direction
- ir.analysis.has_destructor uses ir.analysis, so a change to ir.analysis can break ir.analysis.has_destructor, while a change to ir.analysis.has_destructor can't break ir.analysis.
- Position
- Below the diagonal: ir.analysis.has_destructor uses a module listed above it, which is the healthy direction.
24→8 ir.analysis.has_destructor uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.analysis.has_destructor uses a type in ir.traversal.
- The types involved
bindgen.ir.analysis.has_destructor.HasDestructorAnalysis→bindgen.ir.traversal.EdgeKind
- Direction
- ir.analysis.has_destructor uses ir.traversal, so a change to ir.traversal can break ir.analysis.has_destructor, while a change to ir.analysis.has_destructor can't break ir.traversal.
- Position
- Below the diagonal: ir.analysis.has_destructor uses a module listed above it, which is the healthy direction.
24→21 ir.analysis.has_destructor uses ir.context✕
- Connections
- 2 pairs of types, where a type in ir.analysis.has_destructor uses a type in ir.context.
- The types involved
bindgen.ir.analysis.has_destructor.HasDestructorAnalysis→bindgen.ir.context.BindgenContextbindgen.ir.analysis.has_destructor.HasDestructorAnalysis→bindgen.ir.context.ItemId
- Direction
- ir.analysis.has_destructor uses ir.context, so a change to ir.context can break ir.analysis.has_destructor, while a change to ir.analysis.has_destructor can't break ir.context.
- Position
- Below the diagonal: ir.analysis.has_destructor uses a module listed above it, which is the healthy direction.
25→3 ir.analysis.template_params uses ir.analysis✕
- Connections
- 2 pairs of types, where a type in ir.analysis.template_params uses a type in ir.analysis.
- The types involved
bindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.analysis.ConstrainResultbindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.analysis.MonotoneFramework
- Direction
- ir.analysis.template_params uses ir.analysis, so a change to ir.analysis can break ir.analysis.template_params, while a change to ir.analysis.template_params can't break ir.analysis.
- Position
- Below the diagonal: ir.analysis.template_params uses a module listed above it, which is the healthy direction.
25→8 ir.analysis.template_params uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.analysis.template_params uses a type in ir.traversal.
- The types involved
bindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.traversal.EdgeKind
- Direction
- ir.analysis.template_params uses ir.traversal, so a change to ir.traversal can break ir.analysis.template_params, while a change to ir.analysis.template_params can't break ir.traversal.
- Position
- Below the diagonal: ir.analysis.template_params uses a module listed above it, which is the healthy direction.
25→15 ir.analysis.template_params uses ir.template✕
- Connections
- 1 pair of types, where a type in ir.analysis.template_params uses a type in ir.template.
- The types involved
bindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.template.TemplateInstantiation
- Direction
- ir.analysis.template_params uses ir.template, so a change to ir.template can break ir.analysis.template_params, while a change to ir.analysis.template_params can't break ir.template.
- Position
- Below the diagonal: ir.analysis.template_params uses a module listed above it, which is the healthy direction.
25→18 ir.analysis.template_params uses ir.item✕
- Connections
- 1 pair of types, where a type in ir.analysis.template_params uses a type in ir.item.
- The types involved
bindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.item.Item
- Direction
- ir.analysis.template_params uses ir.item, so a change to ir.item can break ir.analysis.template_params, while a change to ir.analysis.template_params can't break ir.item.
- Position
- Below the diagonal: ir.analysis.template_params uses a module listed above it, which is the healthy direction.
25→21 ir.analysis.template_params uses ir.context✕
- Connections
- 2 pairs of types, where a type in ir.analysis.template_params uses a type in ir.context.
- The types involved
bindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.context.BindgenContextbindgen.ir.analysis.template_params.UsedTemplateParameters→bindgen.ir.context.ItemId
- Direction
- ir.analysis.template_params uses ir.context, so a change to ir.context can break ir.analysis.template_params, while a change to ir.analysis.template_params can't break ir.context.
- Position
- Below the diagonal: ir.analysis.template_params uses a module listed above it, which is the healthy direction.
26→18 ir.enum_ty uses ir.item✕
- Connections
- 1 pair of types, where a type in ir.enum_ty uses a type in ir.item.
- The types involved
bindgen.ir.enum_ty.Enum→bindgen.ir.item.Item
- Direction
- ir.enum_ty uses ir.item, so a change to ir.item can break ir.enum_ty, while a change to ir.enum_ty can't break ir.item.
- Position
- Below the diagonal: ir.enum_ty uses a module listed above it, which is the healthy direction.
26→21 ir.enum_ty uses ir.context✕
- Connections
- 3 pairs of types, where a type in ir.enum_ty uses a type in ir.context.
- The types involved
bindgen.ir.enum_ty.Enum→bindgen.ir.context.BindgenContextbindgen.ir.enum_ty.Enum→bindgen.ir.context.TypeIdbindgen.ir.enum_ty.EnumVariant→bindgen.ir.context.BindgenContext
- Direction
- ir.enum_ty uses ir.context, so a change to ir.context can break ir.enum_ty, while a change to ir.enum_ty can't break ir.context.
- Position
- Below the diagonal: ir.enum_ty uses a module listed above it, which is the healthy direction.
26→28 ir.enum_ty uses codegen part of a loop✕
- Connections
- 3 pairs of types, where a type in ir.enum_ty uses a type in codegen.
- The types involved
bindgen.ir.enum_ty.Enum→bindgen.codegen.CodeGeneratorbindgen.ir.enum_ty.Enum→bindgen.codegen.CodegenResultbindgen.ir.enum_ty.Enum→bindgen.codegen.EnumVariation
- Direction
- ir.enum_ty uses codegen, so a change to codegen can break ir.enum_ty, while a change to ir.enum_ty can't break codegen.
- 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.
26→29 ir.enum_ty uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in ir.enum_ty uses a type in clang.
- The types involved
bindgen.ir.enum_ty.Enum→bindgen.clang.Type
- Direction
- ir.enum_ty uses clang, so a change to clang can break ir.enum_ty, while a change to ir.enum_ty can't break clang.
- 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.
27→8 ir.objc uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.objc uses a type in ir.traversal.
- The types involved
bindgen.ir.objc.ObjCInterface→bindgen.ir.traversal.Trace
- Direction
- ir.objc uses ir.traversal, so a change to ir.traversal can break ir.objc, while a change to ir.objc can't break ir.traversal.
- Position
- Below the diagonal: ir.objc uses a module listed above it, which is the healthy direction.
27→13 ir.objc uses ir.function✕
- Connections
- 1 pair of types, where a type in ir.objc uses a type in ir.function.
- The types involved
bindgen.ir.objc.ObjCMethod→bindgen.ir.function.FunctionSig
- Direction
- ir.objc uses ir.function, so a change to ir.function can break ir.objc, while a change to ir.objc can't break ir.function.
- Position
- Below the diagonal: ir.objc uses a module listed above it, which is the healthy direction.
27→18 ir.objc uses ir.item✕
- Connections
- 1 pair of types, where a type in ir.objc uses a type in ir.item.
- The types involved
bindgen.ir.objc.ObjCInterface→bindgen.ir.item.Item
- Direction
- ir.objc uses ir.item, so a change to ir.item can break ir.objc, while a change to ir.objc can't break ir.item.
- Position
- Below the diagonal: ir.objc uses a module listed above it, which is the healthy direction.
27→21 ir.objc uses ir.context✕
- Connections
- 2 pairs of types, where a type in ir.objc uses a type in ir.context.
- The types involved
bindgen.ir.objc.ObjCInterface→bindgen.ir.context.BindgenContextbindgen.ir.objc.ObjCInterface→bindgen.ir.context.ItemId
- Direction
- ir.objc uses ir.context, so a change to ir.context can break ir.objc, while a change to ir.objc can't break ir.context.
- Position
- Below the diagonal: ir.objc uses a module listed above it, which is the healthy direction.
27→28 ir.objc uses codegen part of a loop✕
- Connections
- 2 pairs of types, where a type in ir.objc uses a type in codegen.
- The types involved
bindgen.ir.objc.ObjCInterface→bindgen.codegen.CodeGeneratorbindgen.ir.objc.ObjCInterface→bindgen.codegen.CodegenResult
- Direction
- ir.objc uses codegen, so a change to codegen can break ir.objc, while a change to ir.objc can't break codegen.
- 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.
27→29 ir.objc uses clang part of a loop✕
- Connections
- 1 pair of types, where a type in ir.objc uses a type in clang.
- The types involved
bindgen.ir.objc.ObjCInterface→bindgen.clang.Cursor
- Direction
- ir.objc uses clang, so a change to clang can break ir.objc, while a change to ir.objc can't break clang.
- 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.
28→2 codegen uses codegen.error✕
- Connections
- 2 pairs of types, where a type in codegen uses a type in codegen.error.
- The types involved
bindgen.codegen.CodegenError→bindgen.codegen.error.Errorbindgen.codegen.codegen$module→bindgen.codegen.error.Error
- Direction
- codegen uses codegen.error, so a change to codegen.error can break codegen, while a change to codegen can't break codegen.error.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→4 codegen uses ir.annotations✕
- Connections
- 4 pairs of types, where a type in codegen uses a type in ir.annotations.
- The types involved
bindgen.codegen.FieldCodegen→bindgen.ir.annotations.FieldAccessorKindbindgen.codegen.FieldCodegen→bindgen.ir.annotations.FieldVisibilityKindbindgen.codegen.codegen$module→bindgen.ir.annotations.Annotationsbindgen.codegen.codegen$module→bindgen.ir.annotations.FieldVisibilityKind
- Direction
- codegen uses ir.annotations, so a change to ir.annotations can break codegen, while a change to codegen can't break ir.annotations.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→7 codegen uses ir.layout✕
- Connections
- 1 pair of types, where a type in codegen uses a type in ir.layout.
- The types involved
bindgen.codegen.ToOpaque→bindgen.ir.layout.Layout
- Direction
- codegen uses ir.layout, so a change to ir.layout can break codegen, while a change to codegen can't break ir.layout.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→10 codegen uses codegen.struct_layout✕
- Connections
- 2 pairs of types, where a type in codegen uses a type in codegen.struct_layout.
- The types involved
bindgen.codegen.FieldCodegen→bindgen.codegen.struct_layout.StructLayoutTrackerbindgen.codegen.codegen$module→bindgen.codegen.struct_layout.StructLayoutTracker
- Direction
- codegen uses codegen.struct_layout, so a change to codegen.struct_layout can break codegen, while a change to codegen can't break codegen.struct_layout.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→16 codegen uses ir.comp✕
- Connections
- 3 pairs of types, where a type in codegen uses a type in ir.comp.
- The types involved
bindgen.codegen.FieldCodegen→bindgen.ir.comp.CompInfobindgen.codegen.Vtable→bindgen.ir.comp.CompInfobindgen.codegen.codegen$module→bindgen.ir.comp.Bitfield
- Direction
- codegen uses ir.comp, so a change to ir.comp can break codegen, while a change to codegen can't break ir.comp.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→18 codegen uses ir.item✕
- Connections
- 5 pairs of types, where a type in codegen uses a type in ir.item.
- The types involved
bindgen.codegen.FieldCodegen→bindgen.ir.item.Itembindgen.codegen.Vtable→bindgen.ir.item.Itembindgen.codegen.Vtable→bindgen.ir.item.ItemCanonicalNamebindgen.codegen.WithImplicitTemplateParams→bindgen.ir.item.Itembindgen.codegen.codegen$module→bindgen.ir.item.Item
- Direction
- codegen uses ir.item, so a change to ir.item can break codegen, while a change to codegen can't break ir.item.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→21 codegen uses ir.context✕
- Connections
- 12 pairs of types, where a type in codegen uses a type in ir.context.
- The types involved
bindgen.codegen.CodeGenerator→bindgen.ir.context.BindgenContextbindgen.codegen.EnumBuilder→bindgen.ir.context.BindgenContextbindgen.codegen.FieldCodegen→bindgen.ir.context.BindgenContextbindgen.codegen.ToOpaque→bindgen.ir.context.BindgenContextbindgen.codegen.ToRustTyOrOpaque→bindgen.ir.context.BindgenContextbindgen.codegen.TryToOpaque→bindgen.ir.context.BindgenContextbindgen.codegen.TryToRustTy→bindgen.ir.context.BindgenContextbindgen.codegen.TryToRustTyOrOpaque→bindgen.ir.context.BindgenContextbindgen.codegen.Vtable→bindgen.ir.context.BindgenContextbindgen.codegen.Vtable→bindgen.ir.context.ItemIdbindgen.codegen.WithImplicitTemplateParams→bindgen.ir.context.BindgenContextbindgen.codegen.codegen$module→bindgen.ir.context.BindgenContext
- Direction
- codegen uses ir.context, so a change to ir.context can break codegen, while a change to codegen can't break ir.context.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→22 codegen uses codegen.dyngen✕
- Connections
- 1 pair of types, where a type in codegen uses a type in codegen.dyngen.
- The types involved
bindgen.codegen.CodegenResult→bindgen.codegen.dyngen.DynamicItems
- Direction
- codegen uses codegen.dyngen, so a change to codegen.dyngen can break codegen, while a change to codegen can't break codegen.dyngen.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→26 codegen uses ir.enum_ty✕
- Connections
- 1 pair of types, where a type in codegen uses a type in ir.enum_ty.
- The types involved
bindgen.codegen.EnumBuilder→bindgen.ir.enum_ty.EnumVariant
- Direction
- codegen uses ir.enum_ty, so a change to ir.enum_ty can break codegen, while a change to codegen can't break ir.enum_ty.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→27 codegen uses ir.objc✕
- Connections
- 1 pair of types, where a type in codegen uses a type in ir.objc.
- The types involved
bindgen.codegen.codegen$module→bindgen.ir.objc.ObjCMethod
- Direction
- codegen uses ir.objc, so a change to ir.objc can break codegen, while a change to codegen can't break ir.objc.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
28→29 codegen uses clang part of a loop✕
- Connections
- 5 pairs of types, where a type in codegen uses a type in clang.
- The types involved
bindgen.codegen.EnumBuilder→bindgen.clang.Typebindgen.codegen.ToOpaque→bindgen.clang.Typebindgen.codegen.ToPtr→bindgen.clang.Typebindgen.codegen.ToRustTyOrOpaque→bindgen.clang.Typebindgen.codegen.codegen$module→bindgen.clang.Type
- Direction
- codegen uses clang, so a change to clang can break codegen, while a change to codegen can't break clang.
- 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.
28→33 codegen uses callbacks part of a loop✕
- Connections
- 1 pair of types, where a type in codegen uses a type in callbacks.
- The types involved
bindgen.codegen.codegen$module→bindgen.callbacks.SourceLocation
- Direction
- codegen uses callbacks, so a change to callbacks can break codegen, while a change to codegen can't break callbacks.
- 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.
28→34 codegen uses bindgen part of a loop✕
- Connections
- 5 pairs of types, where a type in codegen uses a type in bindgen.
- The types involved
bindgen.codegen.AliasVariation→bindgen.Formatterbindgen.codegen.CodegenError→bindgen.Formatterbindgen.codegen.EnumVariation→bindgen.Formatterbindgen.codegen.MacroTypeVariation→bindgen.Formatterbindgen.codegen.NonCopyUnionStyle→bindgen.Formatter
- Direction
- codegen uses bindgen, so a change to bindgen can break codegen, while a change to codegen can't break bindgen.
- 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.
29→18 clang uses ir.item✕
- Connections
- 2 pairs of types, where a type in clang uses a type in ir.item.
- The types involved
bindgen.clang.ClangTokenIterator→bindgen.ir.item.Itembindgen.clang.Type→bindgen.ir.item.Item
- Direction
- clang uses ir.item, so a change to ir.item can break clang, while a change to clang can't break ir.item.
- Position
- Below the diagonal: clang uses a module listed above it, which is the healthy direction.
29→19 clang uses codegen.postprocessing.merge_extern_blocks✕
- Connections
- 1 pair of types, where a type in clang uses a type in codegen.postprocessing.merge_extern_blocks.
- The types involved
bindgen.clang.Cursor→bindgen.codegen.postprocessing.merge_extern_blocks.Visitor
- Direction
- clang uses codegen.postprocessing.merge_extern_blocks, so a change to codegen.postprocessing.merge_extern_blocks can break clang, while a change to clang can't break codegen.postprocessing.merge_extern_blocks.
- Position
- Below the diagonal: clang uses a module listed above it, which is the healthy direction.
29→20 clang uses codegen.serialize✕
- Connections
- 1 pair of types, where a type in clang uses a type in codegen.serialize.
- The types involved
bindgen.clang.Type→bindgen.codegen.serialize.CSerialize
- Direction
- clang uses codegen.serialize, so a change to codegen.serialize can break clang, while a change to clang can't break codegen.serialize.
- Position
- Below the diagonal: clang uses a module listed above it, which is the healthy direction.
29→21 clang uses ir.context✕
- Connections
- 2 pairs of types, where a type in clang uses a type in ir.context.
- The types involved
bindgen.clang.Cursor→bindgen.ir.context.BindgenContextbindgen.clang.Type→bindgen.ir.context.BindgenContext
- Direction
- clang uses ir.context, so a change to ir.context can break clang, while a change to clang can't break ir.context.
- Position
- Below the diagonal: clang uses a module listed above it, which is the healthy direction.
29→28 clang uses codegen✕
- Connections
- 6 pairs of types, where a type in clang uses a type in codegen.
- The types involved
bindgen.clang.Type→bindgen.codegen.CodeGeneratorbindgen.clang.Type→bindgen.codegen.CodegenResultbindgen.clang.Type→bindgen.codegen.ToPtrbindgen.clang.Type→bindgen.codegen.TryToOpaquebindgen.clang.Type→bindgen.codegen.TryToRustTybindgen.clang.Type→bindgen.codegen.WithImplicitTemplateParams
- Direction
- clang uses codegen, so a change to codegen can break clang, while a change to clang can't break codegen.
- Position
- Below the diagonal: clang uses a module listed above it, which is the healthy direction.
29→33 clang uses callbacks part of a loop✕
- Connections
- 1 pair of types, where a type in clang uses a type in callbacks.
- The types involved
bindgen.clang.Cursor→bindgen.callbacks.SourceLocation
- Direction
- clang uses callbacks, so a change to callbacks can break clang, while a change to clang can't break callbacks.
- 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.
29→34 clang uses bindgen part of a loop✕
- Connections
- 7 pairs of types, where a type in clang uses a type in bindgen.
- The types involved
bindgen.clang.Cursor→bindgen.Formatterbindgen.clang.FallbackTranslationUnit→bindgen.Formatterbindgen.clang.Index→bindgen.Formatterbindgen.clang.SourceLocation→bindgen.Formatterbindgen.clang.TranslationUnit→bindgen.Formatterbindgen.clang.Type→bindgen.Formatterbindgen.clang.UnsavedFile→bindgen.Formatter
- Direction
- clang uses bindgen, so a change to bindgen can break clang, while a change to clang can't break bindgen.
- 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.
30→7 codegen.helpers uses ir.layout✕
- Connections
- 1 pair of types, where a type in codegen.helpers uses a type in ir.layout.
- The types involved
bindgen.codegen.helpers.helpers$module→bindgen.ir.layout.Layout
- Direction
- codegen.helpers uses ir.layout, so a change to ir.layout can break codegen.helpers, while a change to codegen.helpers can't break ir.layout.
- Position
- Below the diagonal: codegen.helpers uses a module listed above it, which is the healthy direction.
30→21 codegen.helpers uses ir.context✕
- Connections
- 1 pair of types, where a type in codegen.helpers uses a type in ir.context.
- The types involved
bindgen.codegen.helpers.helpers$module→bindgen.ir.context.BindgenContext
- Direction
- codegen.helpers uses ir.context, so a change to ir.context can break codegen.helpers, while a change to codegen.helpers can't break ir.context.
- Position
- Below the diagonal: codegen.helpers uses a module listed above it, which is the healthy direction.
30→29 codegen.helpers uses clang✕
- Connections
- 1 pair of types, where a type in codegen.helpers uses a type in clang.
- The types involved
bindgen.codegen.helpers.helpers$module→bindgen.clang.Type
- Direction
- codegen.helpers uses clang, so a change to clang can break codegen.helpers, while a change to codegen.helpers can't break clang.
- Position
- Below the diagonal: codegen.helpers uses a module listed above it, which is the healthy direction.
31→13 codegen.utils uses ir.function✕
- Connections
- 2 pairs of types, where a type in codegen.utils uses a type in ir.function.
- The types involved
bindgen.codegen.utils.utils$module→bindgen.ir.function.ClangAbibindgen.codegen.utils.utils$module→bindgen.ir.function.FunctionSig
- Direction
- codegen.utils uses ir.function, so a change to ir.function can break codegen.utils, while a change to codegen.utils can't break ir.function.
- Position
- Below the diagonal: codegen.utils uses a module listed above it, which is the healthy direction.
31→18 codegen.utils uses ir.item✕
- Connections
- 1 pair of types, where a type in codegen.utils uses a type in ir.item.
- The types involved
bindgen.codegen.utils.utils$module→bindgen.ir.item.Item
- Direction
- codegen.utils uses ir.item, so a change to ir.item can break codegen.utils, while a change to codegen.utils can't break ir.item.
- Position
- Below the diagonal: codegen.utils uses a module listed above it, which is the healthy direction.
31→21 codegen.utils uses ir.context✕
- Connections
- 2 pairs of types, where a type in codegen.utils uses a type in ir.context.
- The types involved
bindgen.codegen.utils.utils$module→bindgen.ir.context.BindgenContextbindgen.codegen.utils.utils$module→bindgen.ir.context.TypeId
- Direction
- codegen.utils uses ir.context, so a change to ir.context can break codegen.utils, while a change to codegen.utils can't break ir.context.
- Position
- Below the diagonal: codegen.utils uses a module listed above it, which is the healthy direction.
31→28 codegen.utils uses codegen✕
- Connections
- 2 pairs of types, where a type in codegen.utils uses a type in codegen.
- The types involved
bindgen.codegen.utils.utils$module→bindgen.codegen.CodegenResultbindgen.codegen.utils.utils$module→bindgen.codegen.WrapAsVariadic
- Direction
- codegen.utils uses codegen, so a change to codegen can break codegen.utils, while a change to codegen.utils can't break codegen.
- Position
- Below the diagonal: codegen.utils uses a module listed above it, which is the healthy direction.
31→29 codegen.utils uses clang✕
- Connections
- 1 pair of types, where a type in codegen.utils uses a type in clang.
- The types involved
bindgen.codegen.utils.utils$module→bindgen.clang.Type
- Direction
- codegen.utils uses clang, so a change to clang can break codegen.utils, while a change to codegen.utils can't break clang.
- Position
- Below the diagonal: codegen.utils uses a module listed above it, which is the healthy direction.
32→3 ir.analysis.derive uses ir.analysis✕
- Connections
- 2 pairs of types, where a type in ir.analysis.derive uses a type in ir.analysis.
- The types involved
bindgen.ir.analysis.derive.CannotDerive→bindgen.ir.analysis.ConstrainResultbindgen.ir.analysis.derive.CannotDerive→bindgen.ir.analysis.MonotoneFramework
- Direction
- ir.analysis.derive uses ir.analysis, so a change to ir.analysis can break ir.analysis.derive, while a change to ir.analysis.derive can't break ir.analysis.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→5 ir.analysis.derive uses ir.derive✕
- Connections
- 2 pairs of types, where a type in ir.analysis.derive uses a type in ir.derive.
- The types involved
bindgen.ir.analysis.derive.CannotDerive→bindgen.ir.derive.CanDerivebindgen.ir.analysis.derive.DeriveTrait→bindgen.ir.derive.CanDerive
- Direction
- ir.analysis.derive uses ir.derive, so a change to ir.derive can break ir.analysis.derive, while a change to ir.analysis.derive can't break ir.derive.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→8 ir.analysis.derive uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.analysis.derive uses a type in ir.traversal.
- The types involved
bindgen.ir.analysis.derive.derive$module→bindgen.ir.traversal.EdgeKind
- Direction
- ir.analysis.derive uses ir.traversal, so a change to ir.traversal can break ir.analysis.derive, while a change to ir.analysis.derive can't break ir.traversal.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→13 ir.analysis.derive uses ir.function✕
- Connections
- 1 pair of types, where a type in ir.analysis.derive uses a type in ir.function.
- The types involved
bindgen.ir.analysis.derive.DeriveTrait→bindgen.ir.function.FunctionSig
- Direction
- ir.analysis.derive uses ir.function, so a change to ir.function can break ir.analysis.derive, while a change to ir.analysis.derive can't break ir.function.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→18 ir.analysis.derive uses ir.item✕
- Connections
- 2 pairs of types, where a type in ir.analysis.derive uses a type in ir.item.
- The types involved
bindgen.ir.analysis.derive.CannotDerive→bindgen.ir.item.Itembindgen.ir.analysis.derive.DeriveTrait→bindgen.ir.item.Item
- Direction
- ir.analysis.derive uses ir.item, so a change to ir.item can break ir.analysis.derive, while a change to ir.analysis.derive can't break ir.item.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→21 ir.analysis.derive uses ir.context✕
- Connections
- 3 pairs of types, where a type in ir.analysis.derive uses a type in ir.context.
- The types involved
bindgen.ir.analysis.derive.CannotDerive→bindgen.ir.context.BindgenContextbindgen.ir.analysis.derive.CannotDerive→bindgen.ir.context.ItemIdbindgen.ir.analysis.derive.DeriveTrait→bindgen.ir.context.BindgenContext
- Direction
- ir.analysis.derive uses ir.context, so a change to ir.context can break ir.analysis.derive, while a change to ir.analysis.derive can't break ir.context.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→29 ir.analysis.derive uses clang✕
- Connections
- 1 pair of types, where a type in ir.analysis.derive uses a type in clang.
- The types involved
bindgen.ir.analysis.derive.CannotDerive→bindgen.clang.Type
- Direction
- ir.analysis.derive uses clang, so a change to clang can break ir.analysis.derive, while a change to ir.analysis.derive can't break clang.
- Position
- Below the diagonal: ir.analysis.derive uses a module listed above it, which is the healthy direction.
32→33 ir.analysis.derive uses callbacks part of a loop✕
- Connections
- 1 pair of types, where a type in ir.analysis.derive uses a type in callbacks.
- The types involved
bindgen.ir.analysis.derive.DeriveTrait→bindgen.callbacks.TypeKind
- Direction
- ir.analysis.derive uses callbacks, so a change to callbacks can break ir.analysis.derive, while a change to ir.analysis.derive can't break callbacks.
- 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.
32→34 ir.analysis.derive uses bindgen part of a loop✕
- Connections
- 1 pair of types, where a type in ir.analysis.derive uses a type in bindgen.
- The types involved
bindgen.ir.analysis.derive.DeriveTrait→bindgen.Formatter
- Direction
- ir.analysis.derive uses bindgen, so a change to bindgen can break ir.analysis.derive, while a change to ir.analysis.derive can't break bindgen.
- 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.
33→1 callbacks uses ir.int✕
- Connections
- 1 pair of types, where a type in callbacks uses a type in ir.int.
- The types involved
bindgen.callbacks.ParseCallbacks→bindgen.ir.int.IntKind
- Direction
- callbacks uses ir.int, so a change to ir.int can break callbacks, while a change to callbacks can't break ir.int.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
33→4 callbacks uses ir.annotations✕
- Connections
- 1 pair of types, where a type in callbacks uses a type in ir.annotations.
- The types involved
bindgen.callbacks.ParseCallbacks→bindgen.ir.annotations.FieldVisibilityKind
- Direction
- callbacks uses ir.annotations, so a change to ir.annotations can break callbacks, while a change to callbacks can't break ir.annotations.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
33→15 callbacks uses ir.template✕
- Connections
- 2 pairs of types, where a type in callbacks uses a type in ir.template.
- The types involved
bindgen.callbacks.ItemKind→bindgen.ir.template.AsTemplateParambindgen.callbacks.ItemKind→bindgen.ir.template.TemplateParameters
- Direction
- callbacks uses ir.template, so a change to ir.template can break callbacks, while a change to callbacks can't break ir.template.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
33→18 callbacks uses ir.item✕
- Connections
- 1 pair of types, where a type in callbacks uses a type in ir.item.
- The types involved
bindgen.callbacks.ItemKind→bindgen.ir.item.Item
- Direction
- callbacks uses ir.item, so a change to ir.item can break callbacks, while a change to callbacks can't break ir.item.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
33→21 callbacks uses ir.context✕
- Connections
- 2 pairs of types, where a type in callbacks uses a type in ir.context.
- The types involved
bindgen.callbacks.ItemKind→bindgen.ir.context.BindgenContextbindgen.callbacks.ItemKind→bindgen.ir.context.TypeId
- Direction
- callbacks uses ir.context, so a change to ir.context can break callbacks, while a change to callbacks can't break ir.context.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
33→26 callbacks uses ir.enum_ty✕
- Connections
- 2 pairs of types, where a type in callbacks uses a type in ir.enum_ty.
- The types involved
bindgen.callbacks.ParseCallbacks→bindgen.ir.enum_ty.EnumVariantCustomBehaviorbindgen.callbacks.ParseCallbacks→bindgen.ir.enum_ty.EnumVariantValue
- Direction
- callbacks uses ir.enum_ty, so a change to ir.enum_ty can break callbacks, while a change to callbacks can't break ir.enum_ty.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
33→32 callbacks uses ir.analysis.derive✕
- Connections
- 1 pair of types, where a type in callbacks uses a type in ir.analysis.derive.
- The types involved
bindgen.callbacks.ParseCallbacks→bindgen.ir.analysis.derive.DeriveTrait
- Direction
- callbacks uses ir.analysis.derive, so a change to ir.analysis.derive can break callbacks, while a change to callbacks can't break ir.analysis.derive.
- Position
- Below the diagonal: callbacks uses a module listed above it, which is the healthy direction.
34→2 bindgen uses codegen.error✕
- Connections
- 1 pair of types, where a type in bindgen uses a type in codegen.error.
- The types involved
bindgen.BindgenError→bindgen.codegen.error.Error
- Direction
- bindgen uses codegen.error, so a change to codegen.error can break bindgen, while a change to bindgen can't break codegen.error.
- Position
- Below the diagonal: bindgen uses a module listed above it, which is the healthy direction.
34→21 bindgen uses ir.context✕
- Connections
- 2 pairs of types, where a type in bindgen uses a type in ir.context.
- The types involved
bindgen.bindgen$module→bindgen.ir.context.BindgenContextbindgen.bindgen$module→bindgen.ir.context.ItemId
- Direction
- bindgen uses ir.context, so a change to ir.context can break bindgen, while a change to bindgen can't break ir.context.
- Position
- Below the diagonal: bindgen uses a module listed above it, which is the healthy direction.
34→29 bindgen uses clang✕
- Connections
- 1 pair of types, where a type in bindgen uses a type in clang.
- The types involved
bindgen.bindgen$module→bindgen.clang.Cursor
- Direction
- bindgen uses clang, so a change to clang can break bindgen, while a change to bindgen can't break clang.
- Position
- Below the diagonal: bindgen uses a module listed above it, which is the healthy direction.
34→33 bindgen uses callbacks✕
- Connections
- 1 pair of types, where a type in bindgen uses a type in callbacks.
- The types involved
bindgen.CargoCallbacks→bindgen.callbacks.ParseCallbacks
- Direction
- bindgen uses callbacks, so a change to callbacks can break bindgen, while a change to bindgen can't break callbacks.
- Position
- Below the diagonal: bindgen uses a module listed above it, which is the healthy direction.
35→1 ir.ty uses ir.int✕
- Connections
- 1 pair of types, where a type in ir.ty uses a type in ir.int.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.int.IntKind
- Direction
- ir.ty uses ir.int, so a change to ir.int can break ir.ty, while a change to ir.ty can't break ir.int.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→6 ir.ty uses ir.dot✕
- Connections
- 2 pairs of types, where a type in ir.ty uses a type in ir.dot.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.dot.DotAttributesbindgen.ir.ty.TypeKind→bindgen.ir.dot.DotAttributes
- Direction
- ir.ty uses ir.dot, so a change to ir.dot can break ir.ty, while a change to ir.ty can't break ir.dot.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→7 ir.ty uses ir.layout✕
- Connections
- 1 pair of types, where a type in ir.ty uses a type in ir.layout.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.layout.Layout
- Direction
- ir.ty uses ir.layout, so a change to ir.layout can break ir.ty, while a change to ir.ty can't break ir.layout.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→8 ir.ty uses ir.traversal✕
- Connections
- 1 pair of types, where a type in ir.ty uses a type in ir.traversal.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.traversal.Trace
- Direction
- ir.ty uses ir.traversal, so a change to ir.traversal can break ir.ty, while a change to ir.ty can't break ir.traversal.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→15 ir.ty uses ir.template✕
- Connections
- 4 pairs of types, where a type in ir.ty uses a type in ir.template.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.template.AsTemplateParambindgen.ir.ty.Type→bindgen.ir.template.TemplateParametersbindgen.ir.ty.TypeKind→bindgen.ir.template.AsTemplateParambindgen.ir.ty.TypeKind→bindgen.ir.template.TemplateParameters
- Direction
- ir.ty uses ir.template, so a change to ir.template can break ir.ty, while a change to ir.ty can't break ir.template.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→16 ir.ty uses ir.comp✕
- Connections
- 1 pair of types, where a type in ir.ty uses a type in ir.comp.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.comp.CompInfo
- Direction
- ir.ty uses ir.comp, so a change to ir.comp can break ir.ty, while a change to ir.ty can't break ir.comp.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→18 ir.ty uses ir.item✕
- Connections
- 3 pairs of types, where a type in ir.ty uses a type in ir.item.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.item.IsOpaquebindgen.ir.ty.Type→bindgen.ir.item.Itembindgen.ir.ty.TypeKind→bindgen.ir.item.Item
- Direction
- ir.ty uses ir.item, so a change to ir.item can break ir.ty, while a change to ir.ty can't break ir.item.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→21 ir.ty uses ir.context✕
- Connections
- 5 pairs of types, where a type in ir.ty uses a type in ir.context.
- The types involved
bindgen.ir.ty.Type→bindgen.ir.context.BindgenContextbindgen.ir.ty.Type→bindgen.ir.context.ItemIdbindgen.ir.ty.Type→bindgen.ir.context.TypeIdbindgen.ir.ty.TypeKind→bindgen.ir.context.BindgenContextbindgen.ir.ty.TypeKind→bindgen.ir.context.TypeId
- Direction
- ir.ty uses ir.context, so a change to ir.context can break ir.ty, while a change to ir.ty can't break ir.context.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→29 ir.ty uses clang✕
- Connections
- 2 pairs of types, where a type in ir.ty uses a type in clang.
- The types involved
bindgen.ir.ty.Type→bindgen.clang.Cursorbindgen.ir.ty.Type→bindgen.clang.Type
- Direction
- ir.ty uses clang, so a change to clang can break ir.ty, while a change to ir.ty can't break clang.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
35→33 ir.ty uses callbacks✕
- Connections
- 1 pair of types, where a type in ir.ty uses a type in callbacks.
- The types involved
bindgen.ir.ty.Type→bindgen.callbacks.TypeKind
- Direction
- ir.ty uses callbacks, so a change to callbacks can break ir.ty, while a change to ir.ty can't break callbacks.
- Position
- Below the diagonal: ir.ty uses a module listed above it, which is the healthy direction.
36→1 ir.var uses ir.int✕
- Connections
- 1 pair of types, where a type in ir.var uses a type in ir.int.
- The types involved
bindgen.ir.var.var$module→bindgen.ir.int.IntKind
- Direction
- ir.var uses ir.int, so a change to ir.int can break ir.var, while a change to ir.var can't break ir.int.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→6 ir.var uses ir.dot✕
- Connections
- 1 pair of types, where a type in ir.var uses a type in ir.dot.
- The types involved
bindgen.ir.var.Var→bindgen.ir.dot.DotAttributes
- Direction
- ir.var uses ir.dot, so a change to ir.dot can break ir.var, while a change to ir.var can't break ir.dot.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→9 ir.var uses parse✕
- Connections
- 1 pair of types, where a type in ir.var uses a type in parse.
- The types involved
bindgen.ir.var.Var→bindgen.parse.ClangSubItemParser
- Direction
- ir.var uses parse, so a change to parse can break ir.var, while a change to ir.var can't break parse.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→18 ir.var uses ir.item✕
- Connections
- 1 pair of types, where a type in ir.var uses a type in ir.item.
- The types involved
bindgen.ir.var.Var→bindgen.ir.item.Item
- Direction
- ir.var uses ir.item, so a change to ir.item can break ir.var, while a change to ir.var can't break ir.item.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→21 ir.var uses ir.context✕
- Connections
- 3 pairs of types, where a type in ir.var uses a type in ir.context.
- The types involved
bindgen.ir.var.Var→bindgen.ir.context.BindgenContextbindgen.ir.var.Var→bindgen.ir.context.TypeIdbindgen.ir.var.var$module→bindgen.ir.context.BindgenContext
- Direction
- ir.var uses ir.context, so a change to ir.context can break ir.var, while a change to ir.var can't break ir.context.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→28 ir.var uses codegen✕
- Connections
- 2 pairs of types, where a type in ir.var uses a type in codegen.
- The types involved
bindgen.ir.var.Var→bindgen.codegen.CodeGeneratorbindgen.ir.var.Var→bindgen.codegen.CodegenResult
- Direction
- ir.var uses codegen, so a change to codegen can break ir.var, while a change to ir.var can't break codegen.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→29 ir.var uses clang✕
- Connections
- 4 pairs of types, where a type in ir.var uses a type in clang.
- The types involved
bindgen.ir.var.MacroEvalResult→bindgen.clang.EvalResultbindgen.ir.var.Var→bindgen.clang.Cursorbindgen.ir.var.var$module→bindgen.clang.Cursorbindgen.ir.var.var$module→bindgen.clang.EvalResult
- Direction
- ir.var uses clang, so a change to clang can break ir.var, while a change to ir.var can't break clang.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
36→33 ir.var uses callbacks✕
- Connections
- 1 pair of types, where a type in ir.var uses a type in callbacks.
- The types involved
bindgen.ir.var.var$module→bindgen.callbacks.SourceLocation
- Direction
- ir.var uses callbacks, so a change to callbacks can break ir.var, while a change to ir.var can't break callbacks.
- Position
- Below the diagonal: ir.var uses a module listed above it, which is the healthy direction.
37→1 codegen.helpers.ast_ty uses ir.int✕
- Connections
- 1 pair of types, where a type in codegen.helpers.ast_ty uses a type in ir.int.
- The types involved
bindgen.codegen.helpers.ast_ty.ast_ty$module→bindgen.ir.int.IntKind
- Direction
- codegen.helpers.ast_ty uses ir.int, so a change to ir.int can break codegen.helpers.ast_ty, while a change to codegen.helpers.ast_ty can't break ir.int.
- Position
- Below the diagonal: codegen.helpers.ast_ty uses a module listed above it, which is the healthy direction.
37→7 codegen.helpers.ast_ty uses ir.layout✕
- Connections
- 1 pair of types, where a type in codegen.helpers.ast_ty uses a type in ir.layout.
- The types involved
bindgen.codegen.helpers.ast_ty.ast_ty$module→bindgen.ir.layout.Layout
- Direction
- codegen.helpers.ast_ty uses ir.layout, so a change to ir.layout can break codegen.helpers.ast_ty, while a change to codegen.helpers.ast_ty can't break ir.layout.
- Position
- Below the diagonal: codegen.helpers.ast_ty uses a module listed above it, which is the healthy direction.
37→13 codegen.helpers.ast_ty uses ir.function✕
- Connections
- 1 pair of types, where a type in codegen.helpers.ast_ty uses a type in ir.function.
- The types involved
bindgen.codegen.helpers.ast_ty.ast_ty$module→bindgen.ir.function.FunctionSig
- Direction
- codegen.helpers.ast_ty uses ir.function, so a change to ir.function can break codegen.helpers.ast_ty, while a change to codegen.helpers.ast_ty can't break ir.function.
- Position
- Below the diagonal: codegen.helpers.ast_ty uses a module listed above it, which is the healthy direction.
37→21 codegen.helpers.ast_ty uses ir.context✕
- Connections
- 1 pair of types, where a type in codegen.helpers.ast_ty uses a type in ir.context.
- The types involved
bindgen.codegen.helpers.ast_ty.ast_ty$module→bindgen.ir.context.BindgenContext
- Direction
- codegen.helpers.ast_ty uses ir.context, so a change to ir.context can break codegen.helpers.ast_ty, while a change to codegen.helpers.ast_ty can't break ir.context.
- Position
- Below the diagonal: codegen.helpers.ast_ty uses a module listed above it, which is the healthy direction.
37→29 codegen.helpers.ast_ty uses clang✕
- Connections
- 1 pair of types, where a type in codegen.helpers.ast_ty uses a type in clang.
- The types involved
bindgen.codegen.helpers.ast_ty.ast_ty$module→bindgen.clang.Type
- Direction
- codegen.helpers.ast_ty uses clang, so a change to clang can break codegen.helpers.ast_ty, while a change to codegen.helpers.ast_ty can't break clang.
- Position
- Below the diagonal: codegen.helpers.ast_ty uses a module listed above it, which is the healthy direction.
37→35 codegen.helpers.ast_ty uses ir.ty✕
- Connections
- 1 pair of types, where a type in codegen.helpers.ast_ty uses a type in ir.ty.
- The types involved
bindgen.codegen.helpers.ast_ty.ast_ty$module→bindgen.ir.ty.FloatKind
- Direction
- codegen.helpers.ast_ty uses ir.ty, so a change to ir.ty can break codegen.helpers.ast_ty, while a change to codegen.helpers.ast_ty can't break ir.ty.
- Position
- Below the diagonal: codegen.helpers.ast_ty uses a module listed above it, which is the healthy direction.
38→2 features uses codegen.error✕
- Connections
- 2 pairs of types, where a type in features uses a type in codegen.error.
- The types involved
bindgen.features.InvalidRustEdition→bindgen.codegen.error.Errorbindgen.features.features$module→bindgen.codegen.error.Error
- Direction
- features uses codegen.error, so a change to codegen.error can break features, while a change to features can't break codegen.error.
- Position
- Below the diagonal: features uses a module listed above it, which is the healthy direction.
38→34 features uses bindgen✕
- Connections
- 4 pairs of types, where a type in features uses a type in bindgen.
- The types involved
bindgen.features.InvalidRustEdition→bindgen.Formatterbindgen.features.InvalidRustTarget→bindgen.Formatterbindgen.features.RustEdition→bindgen.Formatterbindgen.features.RustTarget→bindgen.Formatter
- Direction
- features uses bindgen, so a change to bindgen can break features, while a change to features can't break bindgen.
- Position
- Below the diagonal: features uses a module listed above it, which is the healthy direction.
39→6 ir.item_kind uses ir.dot✕
- Connections
- 1 pair of types, where a type in ir.item_kind uses a type in ir.dot.
- The types involved
bindgen.ir.item_kind.ItemKind→bindgen.ir.dot.DotAttributes
- Direction
- ir.item_kind uses ir.dot, so a change to ir.dot can break ir.item_kind, while a change to ir.item_kind can't break ir.dot.
- Position
- Below the diagonal: ir.item_kind uses a module listed above it, which is the healthy direction.
39→13 ir.item_kind uses ir.function✕
- Connections
- 1 pair of types, where a type in ir.item_kind uses a type in ir.function.
- The types involved
bindgen.ir.item_kind.ItemKind→bindgen.ir.function.Function
- Direction
- ir.item_kind uses ir.function, so a change to ir.function can break ir.item_kind, while a change to ir.item_kind can't break ir.function.
- Position
- Below the diagonal: ir.item_kind uses a module listed above it, which is the healthy direction.
39→14 ir.item_kind uses ir.module✕
- Connections
- 1 pair of types, where a type in ir.item_kind uses a type in ir.module.
- The types involved
bindgen.ir.item_kind.ItemKind→bindgen.ir.module.Module
- Direction
- ir.item_kind uses ir.module, so a change to ir.module can break ir.item_kind, while a change to ir.item_kind can't break ir.module.
- Position
- Below the diagonal: ir.item_kind uses a module listed above it, which is the healthy direction.
39→21 ir.item_kind uses ir.context✕
- Connections
- 1 pair of types, where a type in ir.item_kind uses a type in ir.context.
- The types involved
bindgen.ir.item_kind.ItemKind→bindgen.ir.context.BindgenContext
- Direction
- ir.item_kind uses ir.context, so a change to ir.context can break ir.item_kind, while a change to ir.item_kind can't break ir.context.
- Position
- Below the diagonal: ir.item_kind uses a module listed above it, which is the healthy direction.
39→29 ir.item_kind uses clang✕
- Connections
- 1 pair of types, where a type in ir.item_kind uses a type in clang.
- The types involved
bindgen.ir.item_kind.ItemKind→bindgen.clang.Type
- Direction
- ir.item_kind uses clang, so a change to clang can break ir.item_kind, while a change to ir.item_kind can't break clang.
- Position
- Below the diagonal: ir.item_kind uses a module listed above it, which is the healthy direction.
39→36 ir.item_kind uses ir.var✕
- Connections
- 1 pair of types, where a type in ir.item_kind uses a type in ir.var.
- The types involved
bindgen.ir.item_kind.ItemKind→bindgen.ir.var.Var
- Direction
- ir.item_kind uses ir.var, so a change to ir.var can break ir.item_kind, while a change to ir.item_kind can't break ir.var.
- Position
- Below the diagonal: ir.item_kind uses a module listed above it, which is the healthy direction.
40→4 options.cli uses ir.annotations✕
- Connections
- 1 pair of types, where a type in options.cli uses a type in ir.annotations.
- The types involved
bindgen.options.cli.BindgenCommand→bindgen.ir.annotations.FieldVisibilityKind
- Direction
- options.cli uses ir.annotations, so a change to ir.annotations can break options.cli, while a change to options.cli can't break ir.annotations.
- Position
- Below the diagonal: options.cli uses a module listed above it, which is the healthy direction.
40→28 options.cli uses codegen✕
- Connections
- 4 pairs of types, where a type in options.cli uses a type in codegen.
- The types involved
bindgen.options.cli.BindgenCommand→bindgen.codegen.AliasVariationbindgen.options.cli.BindgenCommand→bindgen.codegen.EnumVariationbindgen.options.cli.BindgenCommand→bindgen.codegen.MacroTypeVariationbindgen.options.cli.BindgenCommand→bindgen.codegen.NonCopyUnionStyle
- Direction
- options.cli uses codegen, so a change to codegen can break options.cli, while a change to options.cli can't break codegen.
- Position
- Below the diagonal: options.cli uses a module listed above it, which is the healthy direction.
40→34 options.cli uses bindgen✕
- Connections
- 3 pairs of types, where a type in options.cli uses a type in bindgen.
- The types involved
bindgen.options.cli.BindgenCommand→bindgen.CodegenConfigbindgen.options.cli.BindgenCommand→bindgen.Formatterbindgen.options.cli.CliArg→bindgen.Builder
- Direction
- options.cli uses bindgen, so a change to bindgen can break options.cli, while a change to options.cli can't break bindgen.
- Position
- Below the diagonal: options.cli uses a module listed above it, which is the healthy direction.
40→38 options.cli uses features✕
- Connections
- 2 pairs of types, where a type in options.cli uses a type in features.
- The types involved
bindgen.options.cli.BindgenCommand→bindgen.features.RustEditionbindgen.options.cli.BindgenCommand→bindgen.features.RustTarget
- Direction
- options.cli uses features, so a change to features can break options.cli, while a change to options.cli can't break features.
- Position
- Below the diagonal: options.cli 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 | 52 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | Medium |
Roadmap
Begin by establishing architectural governance by documenting significant design decisions in a dedicated ADR folder and resolving the single gap in ADR quality. Next, stabilize the codebase by addressing the sixteen orphaned files, prioritizing traversal.rs, mod.rs, and template.rs, while simultaneously mitigating risk in the six high-churn complexity hotspots, starting with mod.rs, ty.rs, and var.rs. Finally, improve onboarding by adding a clear build and run quick-start section to the root README.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.2 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.9 pts | Medium | Architecture documentation |
| Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with traversal.rs, mod.rs, template.rs. | +4.9 pts | Medium | Knowledge Freshness |
| Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs, ty.rs, var.rs. | +4.1 pts | High | Churn × Complexity Hotspots |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.5 pts | Medium | Documentation (README) |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.9 pts | Medium | Deployment & Rollback |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.5 pts | Medium | Observability |
| Reconcile the README with reality: CONTRIBUTING.md links to `./tests/quickchecking/README.md`, but `tests/quickchecking/README.md` does not exist. | +1.3 pts | Medium | Documentation accuracy |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| bindgen/codegen/mod.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| bindgen/ir/ty.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| bindgen/ir/comp.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| bindgen/ir/var.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| bindgen/ir/function.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| bindgen/ir/analysis/derive.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| bindgen/features.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| bindgen/options/cli.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| bindgen/ir/context.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| bindgen/lib.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| bindgen/ir/item.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| bindgen/clang.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| bindgen/codegen/helpers.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| bindgen/codegen/struct_layout.rs | 6.7 | Mixed | Explicit Debt: FixmeComment |
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
Watchdog 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. 58 of 58 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 58 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, 278 of 298 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 18 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 — Watchdog 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 deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog 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.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- PF1 Benchmark discipline — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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.
- X16 Unfloored truncation loop — not measured this run — Watchdog 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP 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.
- X5 Nullable reference types — not measured this run — Watchdog 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
30 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CompInfo::codegen at 94. A further 4 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 BindgenContext::build_builtin_ty at 33 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: bindgen/codegen/helpers.rs (bindgen::codegen::helpers::ast_ty::int_kind_rust_type at 27), bindgen/codegen/postprocessing/sort_semantically.rs (bindgen::codegen::postprocessing::sort_semantically::visit_items at 17). 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 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with CompInfo::codegen (cyclomatic 94), Type::from_clang_ty (cyclomatic 65). — 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 2 together lifts Cyclomatic Complexity from 5.7 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
45 method(s) exceeded the cognitive complexity threshold of 15; the worst was CompInfo::codegen at 181.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with CompInfo::codegen (cognitive 181). — Refactoring it lifts Cognitive Complexity from 3.4 to about 4.1/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
25 god class(es) detected.
What to do
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with context.rs (2), ty.rs, comp.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 FileTooLong finding(s) in God Classes — start with context.rs, clang.rs, item.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with context.rs, clang.rs, item.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
17 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with impl_partialeq.rs, has_float.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mod.rs, has_destructor.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
3 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 1 of the 3 (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).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 47 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with context.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
98 test methods: 59 unit, 39 integration, 0 BDD, 0 e2e. The Rust suite contributes 98 `#[test]` function(s) across 18 file(s) declaring at least one; its unit/integration split is Cargo's own — 7 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
8 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 70 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: bindgen/codegen/mod.rs (15×94=1410); bindgen/ir/ty.rs (5×65=325); bindgen/ir/var.rs (3×40=120)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs, ty.rs, var.rs. — One of this dimension's main actionable groups (6 warning-level).
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 43 of the 59 production source files in this repository: 15 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
79 deducted task-comment markers across 30645 LoC (0.2/KLoC) → score 9.5. 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 46 TodoComment finding(s) in Explicit Debt — start with mod.rs (14), item.rs (5), comp.rs (4). — One of this dimension's main actionable groups (46 warning-level).
- Resolve the 28 FixmeComment finding(s) in Explicit Debt — start with mod.rs (8), function.rs (4), clang.rs (3). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 4 XxxComment finding(s) in Explicit Debt — start with ty.rs (2), clang.rs, lib.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 4 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
52 finding(s): 0 critical, 52 high, 0 medium, 0 low. 43 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) — `bindgen-integration/cpp/Test.h` (lines 27–28, lines 30–31, line 53) — 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 4 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 43 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 (43 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
16 of 44 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is bindgen/ir/traversal.rs. Counted over 44 of the 59 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 16 Orphaned file finding(s) in Knowledge Freshness — start with traversal.rs, mod.rs, template.rs. — One of this dimension's main actionable groups (16 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge 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
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 4 of 4 project(s) that lack one — worth up to 2 pts.
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.
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.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `./tests/quickchecking/README.md`, but `tests/quickchecking/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:259
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `./tests/quickchecking/README.md`, but `tests/quickchecking/README.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Strong | Solid. |
| Security | 74% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 80% | Strong | Solid. |
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 — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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 — ~3777 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (17 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- 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: 56 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not 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
- 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.
- 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 52 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
- REDACTED
- REDACTED
- REDACTED
Serious — 213 finding(s)
- TodoComment bindgen-tests/build.rs:25
- TodoComment bindgen-tests/tests/tests.rs:809
- TodoComment bindgen-tests/tests/expectations/build.rs:11
- TodoComment bindgen/callbacks.rs:214
- TodoComment bindgen/clang.rs:2417
- TodoComment bindgen/options/cli.rs:864
- TodoComment bindgen/ir/comp.rs:570
- TodoComment bindgen/ir/comp.rs:601
- TodoComment bindgen/ir/comp.rs:1090
- TodoComment bindgen/ir/comp.rs:1099
- TodoComment bindgen/ir/context.rs:545
- TodoComment bindgen/ir/context.rs:856
- TodoComment bindgen/ir/context.rs:1509
- TodoComment bindgen/ir/function.rs:360
- TodoComment bindgen/ir/int.rs:96
- TodoComment bindgen/ir/item.rs:301
- TodoComment bindgen/ir/item.rs:676
- TodoComment bindgen/ir/item.rs:1009
- TodoComment bindgen/ir/item.rs:1706
- TodoComment bindgen/ir/item.rs:1815
- TodoComment bindgen/ir/template.rs:294
- TodoComment bindgen/ir/ty.rs:1206
- TodoComment bindgen/ir/ty.rs:1226
- TodoComment bindgen/ir/ty.rs:1267
- TodoComment bindgen/ir/var.rs:373
- FixmeComment bindgen-tests/tests/quickchecking/src/fuzzers.rs:629
- FixmeComment bindgen/clang.rs:34
- FixmeComment bindgen/clang.rs:513
- FixmeComment bindgen/clang.rs:2446
- FixmeComment bindgen/diagnostics.rs:92
- FixmeComment bindgen/features.rs:342
- FixmeComment bindgen/features.rs:376
- FixmeComment bindgen/ir/comp.rs:565
- FixmeComment bindgen/ir/comp.rs:1020
- FixmeComment bindgen/ir/context.rs:1054
- FixmeComment bindgen/ir/function.rs:33
- FixmeComment bindgen/ir/function.rs:356
- FixmeComment bindgen/ir/function.rs:478
- FixmeComment bindgen/ir/function.rs:632
- FixmeComment bindgen/ir/item.rs:490
- FixmeComment bindgen/ir/item.rs:584
- FixmeComment bindgen/ir/ty.rs:747
- FixmeComment bindgen/ir/var.rs:707
- FixmeComment bindgen/ir/analysis/derive.rs:512
- FixmeComment bindgen/codegen/mod.rs:158
- FixmeComment bindgen/codegen/mod.rs:1047
- FixmeComment bindgen/codegen/mod.rs:1333
- FixmeComment bindgen/codegen/mod.rs:1336
- FixmeComment bindgen/codegen/mod.rs:2283
- FixmeComment bindgen/codegen/mod.rs:2830
- MethodTooLong: Type.from_clang_ty bindgen/ir/ty.rs:700
- MethodTooLong: CompInfo.from_ty bindgen/ir/comp.rs:1321
- MethodTooLong: CannotDerive.constrain_type bindgen/ir/analysis/derive.rs:139
- MethodTooLong: Var.parse bindgen/ir/var.rs:176
- MethodTooLong: BindgenContext.instantiate_template bindgen/ir/context.rs:1623
- MethodTooLong: FunctionSig.from_ty bindgen/ir/function.rs:413
- MethodTooLong: BindgenContext.compute_allowlisted_and_codegen_items bindgen/ir/context.rs:2438
- MethodTooLong: Bindings.generate bindgen/lib.rs:769
- BindgenContext::compute_allowlisted_and_codegen_items (cognitive 40) bindgen/ir/context.rs:2438
- BindgenContext::compute_enum_typedef_combos (cognitive 39) bindgen/ir/context.rs:2671
- BindgenContext::try_ensure_fallback_translation_unit (cognitive 25) bindgen/ir/context.rs:2081
- BindgenContext::add_item (cognitive 23) bindgen/ir/context.rs:698
- BindgenContext::instantiate_template (cognitive 23) bindgen/ir/context.rs:1623
- BindgenContext::process_replacements (cognitive 22) bindgen/ir/context.rs:1047
- BindgenContext::builtin_or_resolved_ty (cognitive 21) bindgen/ir/context.rs:1847
- FileTooLong: ir/context.rs bindgen/ir/context.rs
- FileTooLong: bindgen/clang.rs bindgen/clang.rs
- FileTooLong: ir/item.rs bindgen/ir/item.rs
- FileTooLong: ir/comp.rs bindgen/ir/comp.rs
- FileTooLong: options/cli.rs bindgen/options/cli.rs
- FileTooLong: bindgen/lib.rs bindgen/lib.rs
- FileTooLong: ir/ty.rs bindgen/ir/ty.rs
- Hotspot: bindgen/codegen/mod.rs bindgen/codegen/mod.rs:2255
- Hotspot: bindgen/ir/ty.rs bindgen/ir/ty.rs:700
- Hotspot: bindgen/ir/var.rs bindgen/ir/var.rs:176
- Hotspot: bindgen/codegen/struct_layout.rs bindgen/codegen/struct_layout.rs:155
- Hotspot: bindgen/ir/analysis/derive.rs bindgen/ir/analysis/derive.rs:139
- Hotspot: bindgen/options/cli.rs bindgen/options/cli.rs:587
- bindgen::options::cli::builder_from_flags (cognitive 29) bindgen/options/cli.rs:587
- bindgen::codegen::impl_partialeq::gen_partialeq_impl (cognitive 22) bindgen/codegen/impl_partialeq.rs:8
- bindgen::regex_set::invalid_regex_warning (cognitive 22) bindgen/regex_set.rs:139
- bindgen::clang::ast_dump::print_cursor (cognitive 19) bindgen/clang.rs:2110
- bindgen::codegen::postprocessing::merge_extern_blocks::visit_items (cognitive 16) bindgen/codegen/postprocessing/merge_extern_blocks.rs:26
- Type::from_clang_ty (cyclomatic 65) bindgen/ir/ty.rs:700
- Type::serialize (cyclomatic 52) bindgen/codegen/serialize.rs:219
- Type::try_to_rust_ty (cyclomatic 34) bindgen/codegen/mod.rs:4456
- Type::codegen (cyclomatic 30) bindgen/codegen/mod.rs:912
- XxxComment bindgen/clang.rs:200
- XxxComment bindgen/lib.rs:614
- XxxComment bindgen/ir/ty.rs:1055
- XxxComment bindgen/ir/ty.rs:1066
- Type::from_clang_ty (cognitive 112) bindgen/ir/ty.rs:700
- Type::codegen (cognitive 49) bindgen/codegen/mod.rs:912
- Type::serialize (cognitive 47) bindgen/codegen/serialize.rs:219
- Type::try_to_rust_ty (cognitive 24) bindgen/codegen/mod.rs:4456
- Item::from_ty_with_id (cognitive 31) bindgen/ir/item.rs:1582
- Item::real_canonical_name (cognitive 27) bindgen/ir/item.rs:844
- Item::type_param (cognitive 19) bindgen/ir/item.rs:1753
- Item::parse (cognitive 16) bindgen/ir/item.rs:1342
- TooManyMethods: BindgenContext bindgen/ir/context.rs:311
- TooManyMethods: Cursor bindgen/clang.rs:58
- TooManyMethods: Item bindgen/ir/item.rs:374
- TooManyMethods: Type bindgen/ir/ty.rs:29
- ClassTooLong: BindgenContext bindgen/ir/context.rs:311
- ClassTooLong: Item bindgen/ir/item.rs:374
- ClassTooLong: Type bindgen/ir/ty.rs:29
- ClassTooLong: CompInfo bindgen/ir/comp.rs:1047
- bindgen::options::cli::builder_from_flags (cyclomatic 28) bindgen/options/cli.rs:587
- bindgen::ir::var::eval_result_to_macro_result (cyclomatic 24) bindgen/ir/var.rs:479
- bindgen::clang::ast_dump::print_cursor (cyclomatic 17) bindgen/clang.rs:2110
- Item::from_ty_with_id (cyclomatic 24) bindgen/ir/item.rs:1582
- Item::parse (cyclomatic 21) bindgen/ir/item.rs:1342
- Item::real_canonical_name (cyclomatic 18) bindgen/ir/item.rs:844
- Function::codegen (cognitive 38) bindgen/codegen/mod.rs:4726
- Function::parse (cognitive 18) bindgen/ir/function.rs:721
- Function::serialize (cognitive 17) bindgen/codegen/serialize.rs:57
- CompInfo::codegen (cyclomatic 94) bindgen/codegen/mod.rs:2255
- CompInfo::from_ty (cyclomatic 47) bindgen/ir/comp.rs:1321
- Var::parse (cyclomatic 40) bindgen/ir/var.rs:176
- Var::codegen (cyclomatic 22) bindgen/codegen/mod.rs:697
- Function::codegen (cyclomatic 30) bindgen/codegen/mod.rs:4726
- Function::parse (cyclomatic 18) bindgen/ir/function.rs:721
- CompInfo::codegen (cognitive 181) bindgen/codegen/mod.rs:2255
- CompInfo::from_ty (cognitive 70) bindgen/ir/comp.rs:1321
- Enum::codegen (cognitive 66) bindgen/codegen/mod.rs:3779
- Enum::from_ty (cognitive 16) bindgen/ir/enum_ty.rs:57
- Var::parse (cognitive 56) bindgen/ir/var.rs:176
- Var::codegen (cognitive 47) bindgen/codegen/mod.rs:697
- ObjCInterface::codegen (cognitive 34) bindgen/codegen/mod.rs:5140
- ObjCInterface::from_ty (cognitive 22) bindgen/ir/objc.rs:124
- Bindings::generate (cognitive 20) bindgen/lib.rs:769
- Bindings::generate::detect_include_paths (cognitive 16) bindgen/lib.rs:815
- TooManyFields: BindgenCommand bindgen/options/cli.rs:172
- TooManyFields: BindgenContext bindgen/ir/context.rs:311
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) bindgen/codegen/mod.rs:3657
- Duplicated block (14 lines × 2) bindgen/codegen/mod.rs:5025
- Duplicated block (11 lines × 2) bindgen/codegen/impl_partialeq.rs:81
- Duplicated block (11 lines × 2) bindgen/ir/analysis/has_float.rs:117
- Duplicated block (8 lines × 2) bindgen/codegen/mod.rs:1620
- Duplicated block (8 lines × 2) bindgen/ir/analysis/has_destructor.rs:95
- FunctionSig::from_ty (cyclomatic 39) bindgen/ir/function.rs:413
- CannotDerive::constrain_type (cyclomatic 38) bindgen/ir/analysis/derive.rs:139
- Enum::codegen (cyclomatic 37) bindgen/codegen/mod.rs:3779
- RustFeatures::new (cyclomatic 35) bindgen/features.rs:279
- BindgenContext::compute_allowlisted_and_codegen_items (cyclomatic 26) bindgen/ir/context.rs:2438
- Bindings::generate (cyclomatic 25) bindgen/lib.rs:769
- Method::codegen_method (cyclomatic 23) bindgen/codegen/mod.rs:3149
- FieldData::codegen (cyclomatic 21) bindgen/codegen/mod.rs:1584
- CompFields::assign_field_names (cyclomatic 20) bindgen/ir/comp.rs:721
- Annotations::parse (cyclomatic 18) bindgen/ir/annotations.rs:209
- Module::codegen (cyclomatic 18) bindgen/codegen/mod.rs:598
- HasFloat::constrain (cyclomatic 17) bindgen/ir/analysis/has_float.rs:99
- SizednessAnalysis::constrain (cyclomatic 17) bindgen/ir/analysis/sizedness.rs:198
- ObjCInterface::codegen (cyclomatic 16) bindgen/codegen/mod.rs:5140
- HackComment bindgen/ir/ty.rs:224
- FunctionSig::from_ty (cognitive 52) bindgen/ir/function.rs:413
- CannotDerive::constrain_type (cognitive 51) bindgen/ir/analysis/derive.rs:139
- RustFeatures::new (cognitive 46) bindgen/features.rs:279
- CompFields::assign_field_names (cognitive 44) bindgen/ir/comp.rs:721
- FieldData::codegen (cognitive 32) bindgen/codegen/mod.rs:1584
- Method::codegen_method (cognitive 23) bindgen/codegen/mod.rs:3149
- Module::codegen (cognitive 23) bindgen/codegen/mod.rs:598
- StructLayoutTracker::pad_to_offset (cognitive 22) bindgen/codegen/struct_layout.rs:155
- HasDestructorAnalysis::constrain (cognitive 22) bindgen/ir/analysis/has_destructor.rs:88
- HasFloat::constrain (cognitive 20) bindgen/ir/analysis/has_float.rs:99
- HasTypeParameterInArray::constrain (cognitive 19) bindgen/ir/analysis/has_type_param_in_array.rs:102
- RustTarget::from_str (cognitive 16) bindgen/features.rs:420
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (29–31 lines × 2) bindgen/options/cli.rs:1055
- Duplicated block (19–21 lines × 3) bindgen/ir/analysis/derive.rs:86
- Duplicated block (17 lines × 2) bindgen/ir/analysis/derive.rs:607
- Duplicated block (14–15 lines × 2) bindgen/codegen/mod.rs:5258
- Duplicated block (13–15 lines × 2) bindgen/ir/analysis/has_float.rs:104
- Duplicated block (14 lines × 3) bindgen/ir/analysis/derive.rs:124
- Duplicated block (6 lines × 2) bindgen/codegen/postprocessing/merge_extern_blocks.rs:18
- Duplicated block (8 lines × 6) bindgen/ir/analysis/derive.rs:662
- Duplicated block (9 lines × 3) bindgen/ir/comp.rs:968
- Duplicated block (10 lines × 4) bindgen/ir/analysis/has_destructor.rs:73
- Duplicated block (12 lines × 2) bindgen/ir/context.rs:1749
- Off the main sequence: bindgen
- Low cohesion: ItemId (LCOM4 5) bindgen/ir/context.rs:38
Minor — 25 finding(s)
- Orphaned file bindgen/ir/traversal.rs:1
- Orphaned file bindgen/ir/analysis/mod.rs:1
- Orphaned file bindgen/ir/template.rs:1
- Orphaned file bindgen/ir/enum_ty.rs:1
- Orphaned file csmith-fuzzing/predicate.py:1
- Orphaned file bindgen/ir/annotations.rs:1
- Orphaned file csmith-fuzzing/driver.py:1
- Orphaned file bindgen/ir/analysis/has_vtable.rs:1
- Orphaned file bindgen/ir/analysis/has_destructor.rs:1
- Orphaned file bindgen/regex_set.rs:1
- Orphaned file bindgen/diagnostics.rs:1
- Orphaned file bindgen/ir/derive.rs:1
- Orphaned file bindgen/ir/item_kind.rs:1
- Orphaned file bindgen/ir/int.rs:1
- Orphaned file bindgen/ir/module.rs:1
- Orphaned file bindgen/ir/dot.rs:1
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift CONTRIBUTING.md:259
- Logging is not universal
- No release approval gate
Minor — 8 finding(s)
- Outdated: bitflags
- Outdated: cc
- Outdated: clap
- Outdated: clap_complete
- Outdated: prettyplease
- Outdated: quickcheck
- Outdated: rustc-hash
- Outdated: syn
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d3b91176580f46b7acb1fbc263f216f8/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d3b91176580f46b7acb1fbc263f216f8/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/watchdog-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 bindgen-tests/tests/expectations/tests/libclang-22 . | 52 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |