Executive summary
dtolnay/cxx falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 59 out of 100 and is rated Adequate, and 43 of its 44 critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 48, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Adding a diagnostic log would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 67.
Thirty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and one pipeline step installs packages that can change without warning. Pinning each tool to an exact version, updating the vulnerable packages and pinning what the pipeline installs would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 19,242 lines, about €24,000 to rebuild.
If Production Readiness rose from 48 to 70, the lowest score rated Strong, the score would rise from 59 to about 67.
Fixed since the last survey: 1 finding
- Churn × Complexity Hotspots · Hotspot: syntax/parse.rs syntax/parse.rs
Rebuild cost: about €24,000 · Estimate
| Cost to rebuild | €7,800 to €39,000, for 131 to 414 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 19,242 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 cxx.extern_type | 2 cxx.syntax.discriminant | 3 cxx.syntax.doc | 4 cxx.syntax.symbol | 5 cxx_build.error | 6 cxx | 7 cxx.bridge.src.pragma | 8 cxx.syntax.names | 9 cxx.syntax.report | 10 cxxbridge_cmd | 11 cxx.bridge.src.builtin | 12 cxx.syntax.cfg | 13 cxx.syntax.set.unordered | 14 cxx.unique_ptr | 15 cxx.shared_ptr | 16 cxx.syntax.file | 17 cxx.syntax.map.unordered | 18 cxx.syntax.instantiate | 19 cxx_gen.error | 20 cxx.cxx_vector | 21 cxx.syntax.map.ordered | 22 cxxbridge_macro.generics | 23 cxx.cxx_string | 24 cxx.syntax.namespace | 25 cxx.syntax.set.ordered | 26 cxx.syntax.attrs | 27 cxx.syntax.resolve | 28 cxx.syntax | 29 cxx.syntax.parse | 30 cxx.syntax.trivial | 31 cxx.syntax.types | 32 cxx.bridge.src.out | 33 cxx.syntax.check | 34 cxx.syntax.mangle | 35 cxxbridge_macro.expand | 36 cxx.bridge.src.guard | 37 cxx.bridge.src.include | 38 cxx.bridge.src.write | 39 cxx.bridge.src | 40 cxx.bridge.src.cfg |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cxx.extern_type | ||||||||||||||||||||||||||||||||||||||||
| 2 cxx.syntax.discriminant | ||||||||||||||||||||||||||||||||||||||||
| 3 cxx.syntax.doc | ||||||||||||||||||||||||||||||||||||||||
| 4 cxx.syntax.symbol | ||||||||||||||||||||||||||||||||||||||||
| 5 cxx_build.error | ||||||||||||||||||||||||||||||||||||||||
| 6 cxx | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 cxx.bridge.src.pragma | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 cxx.syntax.names | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 cxx.syntax.report | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 cxxbridge_cmd | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 cxx.bridge.src.builtin | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 cxx.syntax.cfg | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 cxx.syntax.set.unordered | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 cxx.unique_ptr | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 cxx.shared_ptr | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 cxx.syntax.file | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 cxx.syntax.map.unordered | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 cxx.syntax.instantiate | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 19 cxx_gen.error | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 cxx.cxx_vector | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 cxx.syntax.map.ordered | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 cxxbridge_macro.generics | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||||||
| 23 cxx.cxx_string | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 cxx.syntax.namespace | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 cxx.syntax.set.ordered | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 cxx.syntax.attrs | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 cxx.syntax.resolve | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 cxx.syntax | 1 | 7 | 2 | 9 | 1 | 9 | 1 | 1 | 1 | 2 | 1 | 8 | 1 | |||||||||||||||||||||||||||
| 29 cxx.syntax.parse | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 30 cxx.syntax.trivial | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 cxx.syntax.types | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 32 cxx.bridge.src.out | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 cxx.syntax.check | 1 | 2 | 15 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 cxx.syntax.mangle | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 cxxbridge_macro.expand | 1 | 1 | 1 | 1 | 1 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||
| 36 cxx.bridge.src.guard | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 cxx.bridge.src.include | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 cxx.bridge.src.write | 1 | 1 | 1 | 1 | 1 | 1 | 9 | 1 | 1 | |||||||||||||||||||||||||||||||
| 39 cxx.bridge.src | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 cxx.bridge.src.cfg | 1 | 1 | 1 | 2 |
6→4 cxx uses cxx.syntax.symbol✕
- Connections
- 2 pairs of types, where a type in cxx uses a type in cxx.syntax.symbol.
- The types involved
cxx.T→cxx.syntax.symbol.Segmentcxx.T→cxx.syntax.symbol.Symbol
- Direction
- cxx uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx, while a change to cxx can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx uses a module listed above it, which is the healthy direction.
7→32 cxx.bridge.src.pragma uses cxx.bridge.src.out part of a loop✕
- Connections
- 2 pairs of types, where a type in cxx.bridge.src.pragma uses a type in cxx.bridge.src.out.
- The types involved
cxx.bridge.src.pragma.Pragma→cxx.bridge.src.out.Contentcxx.bridge.src.pragma.pragma$module→cxx.bridge.src.out.OutFile
- Direction
- cxx.bridge.src.pragma uses cxx.bridge.src.out, so a change to cxx.bridge.src.out can break cxx.bridge.src.pragma, while a change to cxx.bridge.src.pragma can't break cxx.bridge.src.out.
- 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→4 cxx.syntax.names uses cxx.syntax.symbol✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.names uses a type in cxx.syntax.symbol.
- The types involved
cxx.syntax.names.ForeignName→cxx.syntax.symbol.Segmentcxx.syntax.names.ForeignName→cxx.syntax.symbol.Symbol
- Direction
- cxx.syntax.names uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.syntax.names, while a change to cxx.syntax.names can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.syntax.names uses a module listed above it, which is the healthy direction.
9→5 cxx.syntax.report uses cxx_build.error✕
- Connections
- 1 pair of types, where a type in cxx.syntax.report uses a type in cxx_build.error.
- The types involved
cxx.syntax.report.Errors→cxx_build.error.Error
- Direction
- cxx.syntax.report uses cxx_build.error, so a change to cxx_build.error can break cxx.syntax.report, while a change to cxx.syntax.report can't break cxx_build.error.
- Position
- Below the diagonal: cxx.syntax.report uses a module listed above it, which is the healthy direction.
10→37 cxxbridge_cmd uses cxx.bridge.src.include part of a loop✕
- Connections
- 1 pair of types, where a type in cxxbridge_cmd uses a type in cxx.bridge.src.include.
- The types involved
cxxbridge_cmd.Opt→cxx.bridge.src.include.Include
- Direction
- cxxbridge_cmd uses cxx.bridge.src.include, so a change to cxx.bridge.src.include can break cxxbridge_cmd, while a change to cxxbridge_cmd can't break cxx.bridge.src.include.
- 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→7 cxx.bridge.src.builtin uses cxx.bridge.src.pragma✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.builtin uses a type in cxx.bridge.src.pragma.
- The types involved
cxx.bridge.src.builtin.builtin$module→cxx.bridge.src.pragma.Pragma
- Direction
- cxx.bridge.src.builtin uses cxx.bridge.src.pragma, so a change to cxx.bridge.src.pragma can break cxx.bridge.src.builtin, while a change to cxx.bridge.src.builtin can't break cxx.bridge.src.pragma.
- Position
- Below the diagonal: cxx.bridge.src.builtin uses a module listed above it, which is the healthy direction.
11→32 cxx.bridge.src.builtin uses cxx.bridge.src.out part of a loop✕
- Connections
- 3 pairs of types, where a type in cxx.bridge.src.builtin uses a type in cxx.bridge.src.out.
- The types involved
cxx.bridge.src.builtin.Builtins→cxx.bridge.src.out.Contentcxx.bridge.src.builtin.builtin$module→cxx.bridge.src.out.Contentcxx.bridge.src.builtin.builtin$module→cxx.bridge.src.out.OutFile
- Direction
- cxx.bridge.src.builtin uses cxx.bridge.src.out, so a change to cxx.bridge.src.out can break cxx.bridge.src.builtin, while a change to cxx.bridge.src.builtin can't break cxx.bridge.src.out.
- 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→37 cxx.bridge.src.builtin uses cxx.bridge.src.include part of a loop✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.builtin uses a type in cxx.bridge.src.include.
- The types involved
cxx.bridge.src.builtin.builtin$module→cxx.bridge.src.include.Includes
- Direction
- cxx.bridge.src.builtin uses cxx.bridge.src.include, so a change to cxx.bridge.src.include can break cxx.bridge.src.builtin, while a change to cxx.bridge.src.builtin can't break cxx.bridge.src.include.
- 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→6 cxx.syntax.cfg uses cxx✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.cfg uses a type in cxx.
- The types involved
cxx.syntax.cfg.CfgExpr→cxx.Hcxx.syntax.cfg.ComputedCfg→cxx.H
- Direction
- cxx.syntax.cfg uses cxx, so a change to cxx can break cxx.syntax.cfg, while a change to cxx.syntax.cfg can't break cxx.
- Position
- Below the diagonal: cxx.syntax.cfg uses a module listed above it, which is the healthy direction.
13→6 cxx.syntax.set.unordered uses cxx✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.set.unordered uses a type in cxx.
- The types involved
cxx.syntax.set.unordered.UnorderedSet→cxx.Qcxx.syntax.set.unordered.UnorderedSet→cxx.T
- Direction
- cxx.syntax.set.unordered uses cxx, so a change to cxx can break cxx.syntax.set.unordered, while a change to cxx.syntax.set.unordered can't break cxx.
- Position
- Below the diagonal: cxx.syntax.set.unordered uses a module listed above it, which is the healthy direction.
14→6 cxx.unique_ptr uses cxx✕
- Connections
- 2 pairs of types, where a type in cxx.unique_ptr uses a type in cxx.
- The types involved
cxx.unique_ptr.UniquePtr→cxx.Hcxx.unique_ptr.UniquePtr→cxx.T
- Direction
- cxx.unique_ptr uses cxx, so a change to cxx can break cxx.unique_ptr, while a change to cxx.unique_ptr can't break cxx.
- Position
- Below the diagonal: cxx.unique_ptr uses a module listed above it, which is the healthy direction.
15→6 cxx.shared_ptr uses cxx✕
- Connections
- 2 pairs of types, where a type in cxx.shared_ptr uses a type in cxx.
- The types involved
cxx.shared_ptr.SharedPtr→cxx.Hcxx.shared_ptr.SharedPtr→cxx.T
- Direction
- cxx.shared_ptr uses cxx, so a change to cxx can break cxx.shared_ptr, while a change to cxx.shared_ptr can't break cxx.
- Position
- Below the diagonal: cxx.shared_ptr uses a module listed above it, which is the healthy direction.
15→14 cxx.shared_ptr uses cxx.unique_ptr✕
- Connections
- 1 pair of types, where a type in cxx.shared_ptr uses a type in cxx.unique_ptr.
- The types involved
cxx.shared_ptr.SharedPtr→cxx.unique_ptr.UniquePtr
- Direction
- cxx.shared_ptr uses cxx.unique_ptr, so a change to cxx.unique_ptr can break cxx.shared_ptr, while a change to cxx.shared_ptr can't break cxx.unique_ptr.
- Position
- Below the diagonal: cxx.shared_ptr uses a module listed above it, which is the healthy direction.
16→12 cxx.syntax.file uses cxx.syntax.cfg✕
- Connections
- 1 pair of types, where a type in cxx.syntax.file uses a type in cxx.syntax.cfg.
- The types involved
cxx.syntax.file.Module→cxx.syntax.cfg.CfgExpr
- Direction
- cxx.syntax.file uses cxx.syntax.cfg, so a change to cxx.syntax.cfg can break cxx.syntax.file, while a change to cxx.syntax.file can't break cxx.syntax.cfg.
- Position
- Below the diagonal: cxx.syntax.file uses a module listed above it, which is the healthy direction.
16→24 cxx.syntax.file uses cxx.syntax.namespace part of a loop✕
- Connections
- 1 pair of types, where a type in cxx.syntax.file uses a type in cxx.syntax.namespace.
- The types involved
cxx.syntax.file.Module→cxx.syntax.namespace.Namespace
- Direction
- cxx.syntax.file uses cxx.syntax.namespace, so a change to cxx.syntax.namespace can break cxx.syntax.file, while a change to cxx.syntax.file can't break cxx.syntax.namespace.
- 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→6 cxx.syntax.map.unordered uses cxx✕
- Connections
- 3 pairs of types, where a type in cxx.syntax.map.unordered uses a type in cxx.
- The types involved
cxx.syntax.map.unordered.UnorderedMap→cxx.Kcxx.syntax.map.unordered.UnorderedMap→cxx.Qcxx.syntax.map.unordered.UnorderedMap→cxx.V
- Direction
- cxx.syntax.map.unordered uses cxx, so a change to cxx can break cxx.syntax.map.unordered, while a change to cxx.syntax.map.unordered can't break cxx.
- Position
- Below the diagonal: cxx.syntax.map.unordered uses a module listed above it, which is the healthy direction.
17→13 cxx.syntax.map.unordered uses cxx.syntax.set.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.map.unordered uses a type in cxx.syntax.set.unordered.
- The types involved
cxx.syntax.map.unordered.UnorderedMap→cxx.syntax.set.unordered.UnorderedSet
- Direction
- cxx.syntax.map.unordered uses cxx.syntax.set.unordered, so a change to cxx.syntax.set.unordered can break cxx.syntax.map.unordered, while a change to cxx.syntax.map.unordered can't break cxx.syntax.set.unordered.
- Position
- Below the diagonal: cxx.syntax.map.unordered uses a module listed above it, which is the healthy direction.
18→4 cxx.syntax.instantiate uses cxx.syntax.symbol✕
- Connections
- 1 pair of types, where a type in cxx.syntax.instantiate uses a type in cxx.syntax.symbol.
- The types involved
cxx.syntax.instantiate.NamedImplKey→cxx.syntax.symbol.Symbol
- Direction
- cxx.syntax.instantiate uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.syntax.instantiate, while a change to cxx.syntax.instantiate can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.syntax.instantiate uses a module listed above it, which is the healthy direction.
18→6 cxx.syntax.instantiate uses cxx✕
- Connections
- 1 pair of types, where a type in cxx.syntax.instantiate uses a type in cxx.
- The types involved
cxx.syntax.instantiate.NamedImplKey→cxx.H
- Direction
- cxx.syntax.instantiate uses cxx, so a change to cxx can break cxx.syntax.instantiate, while a change to cxx.syntax.instantiate can't break cxx.
- Position
- Below the diagonal: cxx.syntax.instantiate uses a module listed above it, which is the healthy direction.
18→17 cxx.syntax.instantiate uses cxx.syntax.map.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.instantiate uses a type in cxx.syntax.map.unordered.
- The types involved
cxx.syntax.instantiate.NamedImplKey→cxx.syntax.map.unordered.UnorderedMap
- Direction
- cxx.syntax.instantiate uses cxx.syntax.map.unordered, so a change to cxx.syntax.map.unordered can break cxx.syntax.instantiate, while a change to cxx.syntax.instantiate can't break cxx.syntax.map.unordered.
- Position
- Below the diagonal: cxx.syntax.instantiate uses a module listed above it, which is the healthy direction.
18→28 cxx.syntax.instantiate uses cxx.syntax part of a loop✕
- Connections
- 3 pairs of types, where a type in cxx.syntax.instantiate uses a type in cxx.syntax.
- The types involved
cxx.syntax.instantiate.ImplKey→cxx.syntax.Typecxx.syntax.instantiate.NamedImplKey→cxx.syntax.Ty1cxx.syntax.instantiate.NamedImplKey→cxx.syntax.Type
- Direction
- cxx.syntax.instantiate uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.instantiate, while a change to cxx.syntax.instantiate can't break cxx.syntax.
- 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→31 cxx.syntax.instantiate uses cxx.syntax.types part of a loop✕
- Connections
- 1 pair of types, where a type in cxx.syntax.instantiate uses a type in cxx.syntax.types.
- The types involved
cxx.syntax.instantiate.ImplKey→cxx.syntax.types.Types
- Direction
- cxx.syntax.instantiate uses cxx.syntax.types, so a change to cxx.syntax.types can break cxx.syntax.instantiate, while a change to cxx.syntax.instantiate can't break cxx.syntax.types.
- 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→5 cxx_gen.error uses cxx_build.error✕
- Connections
- 1 pair of types, where a type in cxx_gen.error uses a type in cxx_build.error.
- The types involved
cxx_gen.error.Error→cxx_build.error.Error
- Direction
- cxx_gen.error uses cxx_build.error, so a change to cxx_build.error can break cxx_gen.error, while a change to cxx_gen.error can't break cxx_build.error.
- Position
- Below the diagonal: cxx_gen.error uses a module listed above it, which is the healthy direction.
19→16 cxx_gen.error uses cxx.syntax.file✕
- Connections
- 1 pair of types, where a type in cxx_gen.error uses a type in cxx.syntax.file.
- The types involved
cxx_gen.error.IntoIter→cxx.syntax.file.Item
- Direction
- cxx_gen.error uses cxx.syntax.file, so a change to cxx.syntax.file can break cxx_gen.error, while a change to cxx_gen.error can't break cxx.syntax.file.
- Position
- Below the diagonal: cxx_gen.error uses a module listed above it, which is the healthy direction.
20→6 cxx.cxx_vector uses cxx✕
- Connections
- 1 pair of types, where a type in cxx.cxx_vector uses a type in cxx.
- The types involved
cxx.cxx_vector.CxxVector→cxx.T
- Direction
- cxx.cxx_vector uses cxx, so a change to cxx can break cxx.cxx_vector, while a change to cxx.cxx_vector can't break cxx.
- Position
- Below the diagonal: cxx.cxx_vector uses a module listed above it, which is the healthy direction.
20→14 cxx.cxx_vector uses cxx.unique_ptr✕
- Connections
- 2 pairs of types, where a type in cxx.cxx_vector uses a type in cxx.unique_ptr.
- The types involved
cxx.cxx_vector.CxxVector→cxx.unique_ptr.UniquePtrcxx.cxx_vector.CxxVector→cxx.unique_ptr.UniquePtrTarget
- Direction
- cxx.cxx_vector uses cxx.unique_ptr, so a change to cxx.unique_ptr can break cxx.cxx_vector, while a change to cxx.cxx_vector can't break cxx.unique_ptr.
- Position
- Below the diagonal: cxx.cxx_vector uses a module listed above it, which is the healthy direction.
20→16 cxx.cxx_vector uses cxx.syntax.file✕
- Connections
- 2 pairs of types, where a type in cxx.cxx_vector uses a type in cxx.syntax.file.
- The types involved
cxx.cxx_vector.Iter→cxx.syntax.file.Itemcxx.cxx_vector.IterMut→cxx.syntax.file.Item
- Direction
- cxx.cxx_vector uses cxx.syntax.file, so a change to cxx.syntax.file can break cxx.cxx_vector, while a change to cxx.cxx_vector can't break cxx.syntax.file.
- Position
- Below the diagonal: cxx.cxx_vector uses a module listed above it, which is the healthy direction.
20→19 cxx.cxx_vector uses cxx_gen.error✕
- Connections
- 1 pair of types, where a type in cxx.cxx_vector uses a type in cxx_gen.error.
- The types involved
cxx.cxx_vector.CxxVector→cxx_gen.error.IntoIter
- Direction
- cxx.cxx_vector uses cxx_gen.error, so a change to cxx_gen.error can break cxx.cxx_vector, while a change to cxx.cxx_vector can't break cxx_gen.error.
- Position
- Below the diagonal: cxx.cxx_vector uses a module listed above it, which is the healthy direction.
21→6 cxx.syntax.map.ordered uses cxx✕
- Connections
- 3 pairs of types, where a type in cxx.syntax.map.ordered uses a type in cxx.
- The types involved
cxx.syntax.map.ordered.OrderedMap→cxx.Kcxx.syntax.map.ordered.OrderedMap→cxx.Qcxx.syntax.map.ordered.OrderedMap→cxx.V
- Direction
- cxx.syntax.map.ordered uses cxx, so a change to cxx can break cxx.syntax.map.ordered, while a change to cxx.syntax.map.ordered can't break cxx.
- Position
- Below the diagonal: cxx.syntax.map.ordered uses a module listed above it, which is the healthy direction.
21→19 cxx.syntax.map.ordered uses cxx_gen.error✕
- Connections
- 1 pair of types, where a type in cxx.syntax.map.ordered uses a type in cxx_gen.error.
- The types involved
cxx.syntax.map.ordered.OrderedMap→cxx_gen.error.IntoIter
- Direction
- cxx.syntax.map.ordered uses cxx_gen.error, so a change to cxx_gen.error can break cxx.syntax.map.ordered, while a change to cxx.syntax.map.ordered can't break cxx_gen.error.
- Position
- Below the diagonal: cxx.syntax.map.ordered uses a module listed above it, which is the healthy direction.
22→18 cxxbridge_macro.generics uses cxx.syntax.instantiate✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.generics uses a type in cxx.syntax.instantiate.
- The types involved
cxxbridge_macro.generics.generics$module→cxx.syntax.instantiate.NamedImplKey
- Direction
- cxxbridge_macro.generics uses cxx.syntax.instantiate, so a change to cxx.syntax.instantiate can break cxxbridge_macro.generics, while a change to cxxbridge_macro.generics can't break cxx.syntax.instantiate.
- Position
- Below the diagonal: cxxbridge_macro.generics uses a module listed above it, which is the healthy direction.
22→28 cxxbridge_macro.generics uses cxx.syntax part of a loop✕
- Connections
- 4 pairs of types, where a type in cxxbridge_macro.generics uses a type in cxx.syntax.
- The types involved
cxxbridge_macro.generics.ResolvedGenericType→cxx.syntax.Typecxxbridge_macro.generics.UnderscoreLifetimes→cxx.syntax.Lifetimescxxbridge_macro.generics.generics$module→cxx.syntax.Lifetimescxxbridge_macro.generics.generics$module→cxx.syntax.Type
- Direction
- cxxbridge_macro.generics uses cxx.syntax, so a change to cxx.syntax can break cxxbridge_macro.generics, while a change to cxxbridge_macro.generics can't break cxx.syntax.
- 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→31 cxxbridge_macro.generics uses cxx.syntax.types part of a loop✕
- Connections
- 3 pairs of types, where a type in cxxbridge_macro.generics uses a type in cxx.syntax.types.
- The types involved
cxxbridge_macro.generics.ResolvedGenericType→cxx.syntax.types.Typescxxbridge_macro.generics.generics$module→cxx.syntax.types.ConditionalImplcxxbridge_macro.generics.generics$module→cxx.syntax.types.Types
- Direction
- cxxbridge_macro.generics uses cxx.syntax.types, so a change to cxx.syntax.types can break cxxbridge_macro.generics, while a change to cxxbridge_macro.generics can't break cxx.syntax.types.
- 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.
23→6 cxx.cxx_string uses cxx✕
- Connections
- 1 pair of types, where a type in cxx.cxx_string uses a type in cxx.
- The types involved
cxx.cxx_string.CxxString→cxx.H
- Direction
- cxx.cxx_string uses cxx, so a change to cxx can break cxx.cxx_string, while a change to cxx.cxx_string can't break cxx.
- Position
- Below the diagonal: cxx.cxx_string uses a module listed above it, which is the healthy direction.
23→14 cxx.cxx_string uses cxx.unique_ptr✕
- Connections
- 1 pair of types, where a type in cxx.cxx_string uses a type in cxx.unique_ptr.
- The types involved
cxx.cxx_string.CxxString→cxx.unique_ptr.UniquePtrTarget
- Direction
- cxx.cxx_string uses cxx.unique_ptr, so a change to cxx.unique_ptr can break cxx.cxx_string, while a change to cxx.cxx_string can't break cxx.unique_ptr.
- Position
- Below the diagonal: cxx.cxx_string uses a module listed above it, which is the healthy direction.
23→15 cxx.cxx_string uses cxx.shared_ptr✕
- Connections
- 1 pair of types, where a type in cxx.cxx_string uses a type in cxx.shared_ptr.
- The types involved
cxx.cxx_string.CxxString→cxx.shared_ptr.SharedPtrTarget
- Direction
- cxx.cxx_string uses cxx.shared_ptr, so a change to cxx.shared_ptr can break cxx.cxx_string, while a change to cxx.cxx_string can't break cxx.shared_ptr.
- Position
- Below the diagonal: cxx.cxx_string uses a module listed above it, which is the healthy direction.
23→20 cxx.cxx_string uses cxx.cxx_vector✕
- Connections
- 2 pairs of types, where a type in cxx.cxx_string uses a type in cxx.cxx_vector.
- The types involved
cxx.cxx_string.CxxString→cxx.cxx_vector.CxxVectorcxx.cxx_string.CxxString→cxx.cxx_vector.VectorElement
- Direction
- cxx.cxx_string uses cxx.cxx_vector, so a change to cxx.cxx_vector can break cxx.cxx_string, while a change to cxx.cxx_string can't break cxx.cxx_vector.
- Position
- Below the diagonal: cxx.cxx_string uses a module listed above it, which is the healthy direction.
24→4 cxx.syntax.namespace uses cxx.syntax.symbol✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.namespace uses a type in cxx.syntax.symbol.
- The types involved
cxx.syntax.namespace.Namespace→cxx.syntax.symbol.Segmentcxx.syntax.namespace.Namespace→cxx.syntax.symbol.Symbol
- Direction
- cxx.syntax.namespace uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.syntax.namespace, while a change to cxx.syntax.namespace can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.syntax.namespace uses a module listed above it, which is the healthy direction.
24→6 cxx.syntax.namespace uses cxx✕
- Connections
- 1 pair of types, where a type in cxx.syntax.namespace uses a type in cxx.
- The types involved
cxx.syntax.namespace.Namespace→cxx.I
- Direction
- cxx.syntax.namespace uses cxx, so a change to cxx can break cxx.syntax.namespace, while a change to cxx.syntax.namespace can't break cxx.
- Position
- Below the diagonal: cxx.syntax.namespace uses a module listed above it, which is the healthy direction.
24→19 cxx.syntax.namespace uses cxx_gen.error✕
- Connections
- 1 pair of types, where a type in cxx.syntax.namespace uses a type in cxx_gen.error.
- The types involved
cxx.syntax.namespace.Namespace→cxx_gen.error.IntoIter
- Direction
- cxx.syntax.namespace uses cxx_gen.error, so a change to cxx_gen.error can break cxx.syntax.namespace, while a change to cxx.syntax.namespace can't break cxx_gen.error.
- Position
- Below the diagonal: cxx.syntax.namespace uses a module listed above it, which is the healthy direction.
24→20 cxx.syntax.namespace uses cxx.cxx_vector✕
- Connections
- 1 pair of types, where a type in cxx.syntax.namespace uses a type in cxx.cxx_vector.
- The types involved
cxx.syntax.namespace.Namespace→cxx.cxx_vector.Iter
- Direction
- cxx.syntax.namespace uses cxx.cxx_vector, so a change to cxx.cxx_vector can break cxx.syntax.namespace, while a change to cxx.syntax.namespace can't break cxx.cxx_vector.
- Position
- Below the diagonal: cxx.syntax.namespace uses a module listed above it, which is the healthy direction.
25→6 cxx.syntax.set.ordered uses cxx✕
- Connections
- 1 pair of types, where a type in cxx.syntax.set.ordered uses a type in cxx.
- The types involved
cxx.syntax.set.ordered.OrderedSet→cxx.T
- Direction
- cxx.syntax.set.ordered uses cxx, so a change to cxx can break cxx.syntax.set.ordered, while a change to cxx.syntax.set.ordered can't break cxx.
- Position
- Below the diagonal: cxx.syntax.set.ordered uses a module listed above it, which is the healthy direction.
25→13 cxx.syntax.set.ordered uses cxx.syntax.set.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.set.ordered uses a type in cxx.syntax.set.unordered.
- The types involved
cxx.syntax.set.ordered.OrderedSet→cxx.syntax.set.unordered.UnorderedSet
- Direction
- cxx.syntax.set.ordered uses cxx.syntax.set.unordered, so a change to cxx.syntax.set.unordered can break cxx.syntax.set.ordered, while a change to cxx.syntax.set.ordered can't break cxx.syntax.set.unordered.
- Position
- Below the diagonal: cxx.syntax.set.ordered uses a module listed above it, which is the healthy direction.
25→19 cxx.syntax.set.ordered uses cxx_gen.error✕
- Connections
- 1 pair of types, where a type in cxx.syntax.set.ordered uses a type in cxx_gen.error.
- The types involved
cxx.syntax.set.ordered.OrderedSet→cxx_gen.error.IntoIter
- Direction
- cxx.syntax.set.ordered uses cxx_gen.error, so a change to cxx_gen.error can break cxx.syntax.set.ordered, while a change to cxx.syntax.set.ordered can't break cxx_gen.error.
- Position
- Below the diagonal: cxx.syntax.set.ordered uses a module listed above it, which is the healthy direction.
25→20 cxx.syntax.set.ordered uses cxx.cxx_vector✕
- Connections
- 1 pair of types, where a type in cxx.syntax.set.ordered uses a type in cxx.cxx_vector.
- The types involved
cxx.syntax.set.ordered.OrderedSet→cxx.cxx_vector.Iter
- Direction
- cxx.syntax.set.ordered uses cxx.cxx_vector, so a change to cxx.cxx_vector can break cxx.syntax.set.ordered, while a change to cxx.syntax.set.ordered can't break cxx.cxx_vector.
- Position
- Below the diagonal: cxx.syntax.set.ordered uses a module listed above it, which is the healthy direction.
26→3 cxx.syntax.attrs uses cxx.syntax.doc✕
- Connections
- 1 pair of types, where a type in cxx.syntax.attrs uses a type in cxx.syntax.doc.
- The types involved
cxx.syntax.attrs.Parser→cxx.syntax.doc.Doc
- Direction
- cxx.syntax.attrs uses cxx.syntax.doc, so a change to cxx.syntax.doc can break cxx.syntax.attrs, while a change to cxx.syntax.attrs can't break cxx.syntax.doc.
- Position
- Below the diagonal: cxx.syntax.attrs uses a module listed above it, which is the healthy direction.
26→8 cxx.syntax.attrs uses cxx.syntax.names✕
- Connections
- 1 pair of types, where a type in cxx.syntax.attrs uses a type in cxx.syntax.names.
- The types involved
cxx.syntax.attrs.Parser→cxx.syntax.names.ForeignName
- Direction
- cxx.syntax.attrs uses cxx.syntax.names, so a change to cxx.syntax.names can break cxx.syntax.attrs, while a change to cxx.syntax.attrs can't break cxx.syntax.names.
- Position
- Below the diagonal: cxx.syntax.attrs uses a module listed above it, which is the healthy direction.
26→9 cxx.syntax.attrs uses cxx.syntax.report✕
- Connections
- 1 pair of types, where a type in cxx.syntax.attrs uses a type in cxx.syntax.report.
- The types involved
cxx.syntax.attrs.attrs$module→cxx.syntax.report.Errors
- Direction
- cxx.syntax.attrs uses cxx.syntax.report, so a change to cxx.syntax.report can break cxx.syntax.attrs, while a change to cxx.syntax.attrs can't break cxx.syntax.report.
- Position
- Below the diagonal: cxx.syntax.attrs uses a module listed above it, which is the healthy direction.
26→12 cxx.syntax.attrs uses cxx.syntax.cfg✕
- Connections
- 1 pair of types, where a type in cxx.syntax.attrs uses a type in cxx.syntax.cfg.
- The types involved
cxx.syntax.attrs.Parser→cxx.syntax.cfg.CfgExpr
- Direction
- cxx.syntax.attrs uses cxx.syntax.cfg, so a change to cxx.syntax.cfg can break cxx.syntax.attrs, while a change to cxx.syntax.attrs can't break cxx.syntax.cfg.
- Position
- Below the diagonal: cxx.syntax.attrs uses a module listed above it, which is the healthy direction.
26→24 cxx.syntax.attrs uses cxx.syntax.namespace✕
- Connections
- 1 pair of types, where a type in cxx.syntax.attrs uses a type in cxx.syntax.namespace.
- The types involved
cxx.syntax.attrs.Parser→cxx.syntax.namespace.Namespace
- Direction
- cxx.syntax.attrs uses cxx.syntax.namespace, so a change to cxx.syntax.namespace can break cxx.syntax.attrs, while a change to cxx.syntax.attrs can't break cxx.syntax.namespace.
- Position
- Below the diagonal: cxx.syntax.attrs uses a module listed above it, which is the healthy direction.
27→26 cxx.syntax.resolve uses cxx.syntax.attrs✕
- Connections
- 1 pair of types, where a type in cxx.syntax.resolve uses a type in cxx.syntax.attrs.
- The types involved
cxx.syntax.resolve.Resolution→cxx.syntax.attrs.OtherAttrs
- Direction
- cxx.syntax.resolve uses cxx.syntax.attrs, so a change to cxx.syntax.attrs can break cxx.syntax.resolve, while a change to cxx.syntax.resolve can't break cxx.syntax.attrs.
- Position
- Below the diagonal: cxx.syntax.resolve uses a module listed above it, which is the healthy direction.
27→28 cxx.syntax.resolve uses cxx.syntax part of a loop✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.resolve uses a type in cxx.syntax.
- The types involved
cxx.syntax.resolve.Resolution→cxx.syntax.Lifetimescxx.syntax.resolve.Resolution→cxx.syntax.Pair
- Direction
- cxx.syntax.resolve uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.resolve, while a change to cxx.syntax.resolve can't break cxx.syntax.
- 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 cxx.syntax uses cxx.syntax.discriminant✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxx.syntax.discriminant.
- The types involved
cxx.syntax.Variant→cxx.syntax.discriminant.Discriminant
- Direction
- cxx.syntax uses cxx.syntax.discriminant, so a change to cxx.syntax.discriminant can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.discriminant.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→3 cxx.syntax uses cxx.syntax.doc✕
- Connections
- 7 pairs of types, where a type in cxx.syntax uses a type in cxx.syntax.doc.
- The types involved
cxx.syntax.Enum→cxx.syntax.doc.Doccxx.syntax.ExternFn→cxx.syntax.doc.Doccxx.syntax.ExternType→cxx.syntax.doc.Doccxx.syntax.Struct→cxx.syntax.doc.Doccxx.syntax.TypeAlias→cxx.syntax.doc.Doccxx.syntax.Var→cxx.syntax.doc.Doccxx.syntax.Variant→cxx.syntax.doc.Doc
- Direction
- cxx.syntax uses cxx.syntax.doc, so a change to cxx.syntax.doc can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.doc.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→4 cxx.syntax uses cxx.syntax.symbol✕
- Connections
- 2 pairs of types, where a type in cxx.syntax uses a type in cxx.syntax.symbol.
- The types involved
cxx.syntax.Pair→cxx.syntax.symbol.Segmentcxx.syntax.Pair→cxx.syntax.symbol.Symbol
- Direction
- cxx.syntax uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→6 cxx.syntax uses cxx✕
- Connections
- 9 pairs of types, where a type in cxx.syntax uses a type in cxx.
- The types involved
cxx.syntax.Array→cxx.Hcxx.syntax.Lifetimes→cxx.Hcxx.syntax.Ptr→cxx.Hcxx.syntax.Receiver→cxx.Hcxx.syntax.Ref→cxx.Hcxx.syntax.Signature→cxx.Hcxx.syntax.SliceRef→cxx.Hcxx.syntax.Ty1→cxx.Hcxx.syntax.Type→cxx.H
- Direction
- cxx.syntax uses cxx, so a change to cxx can break cxx.syntax, while a change to cxx.syntax can't break cxx.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→8 cxx.syntax uses cxx.syntax.names✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxx.syntax.names.
- The types involved
cxx.syntax.Pair→cxx.syntax.names.ForeignName
- Direction
- cxx.syntax uses cxx.syntax.names, so a change to cxx.syntax.names can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.names.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→12 cxx.syntax uses cxx.syntax.cfg✕
- Connections
- 9 pairs of types, where a type in cxx.syntax uses a type in cxx.syntax.cfg.
- The types involved
cxx.syntax.Enum→cxx.syntax.cfg.CfgExprcxx.syntax.ExternFn→cxx.syntax.cfg.CfgExprcxx.syntax.ExternType→cxx.syntax.cfg.CfgExprcxx.syntax.Impl→cxx.syntax.cfg.CfgExprcxx.syntax.Include→cxx.syntax.cfg.CfgExprcxx.syntax.Struct→cxx.syntax.cfg.CfgExprcxx.syntax.TypeAlias→cxx.syntax.cfg.CfgExprcxx.syntax.Var→cxx.syntax.cfg.CfgExprcxx.syntax.Variant→cxx.syntax.cfg.CfgExpr
- Direction
- cxx.syntax uses cxx.syntax.cfg, so a change to cxx.syntax.cfg can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.cfg.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→17 cxx.syntax uses cxx.syntax.map.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxx.syntax.map.unordered.
- The types involved
cxx.syntax.Type→cxx.syntax.map.unordered.UnorderedMap
- Direction
- cxx.syntax uses cxx.syntax.map.unordered, so a change to cxx.syntax.map.unordered can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.map.unordered.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→18 cxx.syntax uses cxx.syntax.instantiate✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxx.syntax.instantiate.
- The types involved
cxx.syntax.Type→cxx.syntax.instantiate.ImplKey
- Direction
- cxx.syntax uses cxx.syntax.instantiate, so a change to cxx.syntax.instantiate can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.instantiate.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→22 cxx.syntax uses cxxbridge_macro.generics✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxxbridge_macro.generics.
- The types involved
cxx.syntax.Lifetimes→cxxbridge_macro.generics.UnderscoreLifetimes
- Direction
- cxx.syntax uses cxxbridge_macro.generics, so a change to cxxbridge_macro.generics can break cxx.syntax, while a change to cxx.syntax can't break cxxbridge_macro.generics.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→24 cxx.syntax uses cxx.syntax.namespace✕
- Connections
- 2 pairs of types, where a type in cxx.syntax uses a type in cxx.syntax.namespace.
- The types involved
cxx.syntax.Api→cxx.syntax.namespace.Namespacecxx.syntax.Pair→cxx.syntax.namespace.Namespace
- Direction
- cxx.syntax uses cxx.syntax.namespace, so a change to cxx.syntax.namespace can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.namespace.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→25 cxx.syntax uses cxx.syntax.set.ordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxx.syntax.set.ordered.
- The types involved
cxx.syntax.Signature→cxx.syntax.set.ordered.OrderedSet
- Direction
- cxx.syntax uses cxx.syntax.set.ordered, so a change to cxx.syntax.set.ordered can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.set.ordered.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→26 cxx.syntax uses cxx.syntax.attrs✕
- Connections
- 8 pairs of types, where a type in cxx.syntax uses a type in cxx.syntax.attrs.
- The types involved
cxx.syntax.Enum→cxx.syntax.attrs.OtherAttrscxx.syntax.ExternFn→cxx.syntax.attrs.OtherAttrscxx.syntax.ExternType→cxx.syntax.attrs.OtherAttrscxx.syntax.Impl→cxx.syntax.attrs.OtherAttrscxx.syntax.Struct→cxx.syntax.attrs.OtherAttrscxx.syntax.TypeAlias→cxx.syntax.attrs.OtherAttrscxx.syntax.Var→cxx.syntax.attrs.OtherAttrscxx.syntax.Variant→cxx.syntax.attrs.OtherAttrs
- Direction
- cxx.syntax uses cxx.syntax.attrs, so a change to cxx.syntax.attrs can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.attrs.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
28→27 cxx.syntax uses cxx.syntax.resolve✕
- Connections
- 1 pair of types, where a type in cxx.syntax uses a type in cxx.syntax.resolve.
- The types involved
cxx.syntax.NamedType→cxx.syntax.resolve.UnresolvedName
- Direction
- cxx.syntax uses cxx.syntax.resolve, so a change to cxx.syntax.resolve can break cxx.syntax, while a change to cxx.syntax can't break cxx.syntax.resolve.
- Position
- Below the diagonal: cxx.syntax uses a module listed above it, which is the healthy direction.
29→2 cxx.syntax.parse uses cxx.syntax.discriminant✕
- Connections
- 1 pair of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.discriminant.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.discriminant.DiscriminantSet
- Direction
- cxx.syntax.parse uses cxx.syntax.discriminant, so a change to cxx.syntax.discriminant can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.discriminant.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→8 cxx.syntax.parse uses cxx.syntax.names✕
- Connections
- 1 pair of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.names.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.names.ForeignName
- Direction
- cxx.syntax.parse uses cxx.syntax.names, so a change to cxx.syntax.names can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.names.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→9 cxx.syntax.parse uses cxx.syntax.report✕
- Connections
- 1 pair of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.report.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.report.Errors
- Direction
- cxx.syntax.parse uses cxx.syntax.report, so a change to cxx.syntax.report can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.report.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→12 cxx.syntax.parse uses cxx.syntax.cfg✕
- Connections
- 1 pair of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.cfg.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.cfg.CfgExpr
- Direction
- cxx.syntax.parse uses cxx.syntax.cfg, so a change to cxx.syntax.cfg can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.cfg.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→16 cxx.syntax.parse uses cxx.syntax.file✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.file.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.file.Itemcxx.syntax.parse.parse$module→cxx.syntax.file.ItemForeignMod
- Direction
- cxx.syntax.parse uses cxx.syntax.file, so a change to cxx.syntax.file can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.file.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→24 cxx.syntax.parse uses cxx.syntax.namespace✕
- Connections
- 1 pair of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.namespace.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.namespace.Namespace
- Direction
- cxx.syntax.parse uses cxx.syntax.namespace, so a change to cxx.syntax.namespace can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.namespace.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→26 cxx.syntax.parse uses cxx.syntax.attrs✕
- Connections
- 1 pair of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.attrs.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.attrs.OtherAttrs
- Direction
- cxx.syntax.parse uses cxx.syntax.attrs, so a change to cxx.syntax.attrs can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.attrs.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
29→28 cxx.syntax.parse uses cxx.syntax✕
- Connections
- 4 pairs of types, where a type in cxx.syntax.parse uses a type in cxx.syntax.
- The types involved
cxx.syntax.parse.parse$module→cxx.syntax.Apicxx.syntax.parse.parse$module→cxx.syntax.Langcxx.syntax.parse.parse$module→cxx.syntax.Lifetimescxx.syntax.parse.parse$module→cxx.syntax.Pair
- Direction
- cxx.syntax.parse uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.parse, while a change to cxx.syntax.parse can't break cxx.syntax.
- Position
- Below the diagonal: cxx.syntax.parse uses a module listed above it, which is the healthy direction.
30→13 cxx.syntax.trivial uses cxx.syntax.set.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.trivial uses a type in cxx.syntax.set.unordered.
- The types involved
cxx.syntax.trivial.trivial$module→cxx.syntax.set.unordered.UnorderedSet
- Direction
- cxx.syntax.trivial uses cxx.syntax.set.unordered, so a change to cxx.syntax.set.unordered can break cxx.syntax.trivial, while a change to cxx.syntax.trivial can't break cxx.syntax.set.unordered.
- Position
- Below the diagonal: cxx.syntax.trivial uses a module listed above it, which is the healthy direction.
30→17 cxx.syntax.trivial uses cxx.syntax.map.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.trivial uses a type in cxx.syntax.map.unordered.
- The types involved
cxx.syntax.trivial.trivial$module→cxx.syntax.map.unordered.UnorderedMap
- Direction
- cxx.syntax.trivial uses cxx.syntax.map.unordered, so a change to cxx.syntax.map.unordered can break cxx.syntax.trivial, while a change to cxx.syntax.trivial can't break cxx.syntax.map.unordered.
- Position
- Below the diagonal: cxx.syntax.trivial uses a module listed above it, which is the healthy direction.
30→21 cxx.syntax.trivial uses cxx.syntax.map.ordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.trivial uses a type in cxx.syntax.map.ordered.
- The types involved
cxx.syntax.trivial.trivial$module→cxx.syntax.map.ordered.OrderedMap
- Direction
- cxx.syntax.trivial uses cxx.syntax.map.ordered, so a change to cxx.syntax.map.ordered can break cxx.syntax.trivial, while a change to cxx.syntax.trivial can't break cxx.syntax.map.ordered.
- Position
- Below the diagonal: cxx.syntax.trivial uses a module listed above it, which is the healthy direction.
30→28 cxx.syntax.trivial uses cxx.syntax✕
- Connections
- 1 pair of types, where a type in cxx.syntax.trivial uses a type in cxx.syntax.
- The types involved
cxx.syntax.trivial.trivial$module→cxx.syntax.Pair
- Direction
- cxx.syntax.trivial uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.trivial, while a change to cxx.syntax.trivial can't break cxx.syntax.
- Position
- Below the diagonal: cxx.syntax.trivial uses a module listed above it, which is the healthy direction.
31→9 cxx.syntax.types uses cxx.syntax.report✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.types uses a type in cxx.syntax.report.
- The types involved
cxx.syntax.types.Types→cxx.syntax.report.Errorscxx.syntax.types.types$module→cxx.syntax.report.Errors
- Direction
- cxx.syntax.types uses cxx.syntax.report, so a change to cxx.syntax.report can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.report.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→12 cxx.syntax.types uses cxx.syntax.cfg✕
- Connections
- 1 pair of types, where a type in cxx.syntax.types uses a type in cxx.syntax.cfg.
- The types involved
cxx.syntax.types.ConditionalImpl→cxx.syntax.cfg.ComputedCfg
- Direction
- cxx.syntax.types uses cxx.syntax.cfg, so a change to cxx.syntax.cfg can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.cfg.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→13 cxx.syntax.types uses cxx.syntax.set.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.types uses a type in cxx.syntax.set.unordered.
- The types involved
cxx.syntax.types.Types→cxx.syntax.set.unordered.UnorderedSet
- Direction
- cxx.syntax.types uses cxx.syntax.set.unordered, so a change to cxx.syntax.set.unordered can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.set.unordered.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→17 cxx.syntax.types uses cxx.syntax.map.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.types uses a type in cxx.syntax.map.unordered.
- The types involved
cxx.syntax.types.Types→cxx.syntax.map.unordered.UnorderedMap
- Direction
- cxx.syntax.types uses cxx.syntax.map.unordered, so a change to cxx.syntax.map.unordered can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.map.unordered.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→19 cxx.syntax.types uses cxx_gen.error✕
- Connections
- 1 pair of types, where a type in cxx.syntax.types uses a type in cxx_gen.error.
- The types involved
cxx.syntax.types.Types→cxx_gen.error.IntoIter
- Direction
- cxx.syntax.types uses cxx_gen.error, so a change to cxx_gen.error can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx_gen.error.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→21 cxx.syntax.types uses cxx.syntax.map.ordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.types uses a type in cxx.syntax.map.ordered.
- The types involved
cxx.syntax.types.Types→cxx.syntax.map.ordered.OrderedMap
- Direction
- cxx.syntax.types uses cxx.syntax.map.ordered, so a change to cxx.syntax.map.ordered can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.map.ordered.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→27 cxx.syntax.types uses cxx.syntax.resolve✕
- Connections
- 1 pair of types, where a type in cxx.syntax.types uses a type in cxx.syntax.resolve.
- The types involved
cxx.syntax.types.Types→cxx.syntax.resolve.Resolution
- Direction
- cxx.syntax.types uses cxx.syntax.resolve, so a change to cxx.syntax.resolve can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.resolve.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
31→28 cxx.syntax.types uses cxx.syntax✕
- Connections
- 3 pairs of types, where a type in cxx.syntax.types uses a type in cxx.syntax.
- The types involved
cxx.syntax.types.ConditionalImpl→cxx.syntax.Implcxx.syntax.types.Types→cxx.syntax.Structcxx.syntax.types.Types→cxx.syntax.Type
- Direction
- cxx.syntax.types uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.types, while a change to cxx.syntax.types can't break cxx.syntax.
- Position
- Below the diagonal: cxx.syntax.types uses a module listed above it, which is the healthy direction.
32→7 cxx.bridge.src.out uses cxx.bridge.src.pragma✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.out uses a type in cxx.bridge.src.pragma.
- The types involved
cxx.bridge.src.out.OutFile→cxx.bridge.src.pragma.Pragma
- Direction
- cxx.bridge.src.out uses cxx.bridge.src.pragma, so a change to cxx.bridge.src.pragma can break cxx.bridge.src.out, while a change to cxx.bridge.src.out can't break cxx.bridge.src.pragma.
- Position
- Below the diagonal: cxx.bridge.src.out uses a module listed above it, which is the healthy direction.
32→10 cxx.bridge.src.out uses cxxbridge_cmd✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.out uses a type in cxxbridge_cmd.
- The types involved
cxx.bridge.src.out.OutFile→cxxbridge_cmd.Opt
- Direction
- cxx.bridge.src.out uses cxxbridge_cmd, so a change to cxxbridge_cmd can break cxx.bridge.src.out, while a change to cxx.bridge.src.out can't break cxxbridge_cmd.
- Position
- Below the diagonal: cxx.bridge.src.out uses a module listed above it, which is the healthy direction.
32→11 cxx.bridge.src.out uses cxx.bridge.src.builtin✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.out uses a type in cxx.bridge.src.builtin.
- The types involved
cxx.bridge.src.out.OutFile→cxx.bridge.src.builtin.Builtins
- Direction
- cxx.bridge.src.out uses cxx.bridge.src.builtin, so a change to cxx.bridge.src.builtin can break cxx.bridge.src.out, while a change to cxx.bridge.src.out can't break cxx.bridge.src.builtin.
- Position
- Below the diagonal: cxx.bridge.src.out uses a module listed above it, which is the healthy direction.
32→24 cxx.bridge.src.out uses cxx.syntax.namespace✕
- Connections
- 2 pairs of types, where a type in cxx.bridge.src.out uses a type in cxx.syntax.namespace.
- The types involved
cxx.bridge.src.out.Content→cxx.syntax.namespace.Namespacecxx.bridge.src.out.OutFile→cxx.syntax.namespace.Namespace
- Direction
- cxx.bridge.src.out uses cxx.syntax.namespace, so a change to cxx.syntax.namespace can break cxx.bridge.src.out, while a change to cxx.bridge.src.out can't break cxx.syntax.namespace.
- Position
- Below the diagonal: cxx.bridge.src.out uses a module listed above it, which is the healthy direction.
32→31 cxx.bridge.src.out uses cxx.syntax.types✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.out uses a type in cxx.syntax.types.
- The types involved
cxx.bridge.src.out.OutFile→cxx.syntax.types.Types
- Direction
- cxx.bridge.src.out uses cxx.syntax.types, so a change to cxx.syntax.types can break cxx.bridge.src.out, while a change to cxx.bridge.src.out can't break cxx.syntax.types.
- Position
- Below the diagonal: cxx.bridge.src.out uses a module listed above it, which is the healthy direction.
32→37 cxx.bridge.src.out uses cxx.bridge.src.include part of a loop✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.out uses a type in cxx.bridge.src.include.
- The types involved
cxx.bridge.src.out.OutFile→cxx.bridge.src.include.Includes
- Direction
- cxx.bridge.src.out uses cxx.bridge.src.include, so a change to cxx.bridge.src.include can break cxx.bridge.src.out, while a change to cxx.bridge.src.out can't break cxx.bridge.src.include.
- 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 cxx.syntax.check uses cxx.extern_type✕
- Connections
- 1 pair of types, where a type in cxx.syntax.check uses a type in cxx.extern_type.
- The types involved
cxx.syntax.check.check$module→cxx.extern_type.ExternType
- Direction
- cxx.syntax.check uses cxx.extern_type, so a change to cxx.extern_type can break cxx.syntax.check, while a change to cxx.syntax.check can't break cxx.extern_type.
- Position
- Below the diagonal: cxx.syntax.check uses a module listed above it, which is the healthy direction.
33→9 cxx.syntax.check uses cxx.syntax.report✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.check uses a type in cxx.syntax.report.
- The types involved
cxx.syntax.check.Check→cxx.syntax.report.Errorscxx.syntax.check.check$module→cxx.syntax.report.Errors
- Direction
- cxx.syntax.check uses cxx.syntax.report, so a change to cxx.syntax.report can break cxx.syntax.check, while a change to cxx.syntax.check can't break cxx.syntax.report.
- Position
- Below the diagonal: cxx.syntax.check uses a module listed above it, which is the healthy direction.
33→28 cxx.syntax.check uses cxx.syntax✕
- Connections
- 15 pairs of types, where a type in cxx.syntax.check uses a type in cxx.syntax.
- The types involved
cxx.syntax.check.check$module→cxx.syntax.Arraycxx.syntax.check.check$module→cxx.syntax.Enumcxx.syntax.check.check$module→cxx.syntax.ExternFncxx.syntax.check.check$module→cxx.syntax.Implcxx.syntax.check.check$module→cxx.syntax.Lifetimescxx.syntax.check.check$module→cxx.syntax.NamedTypecxx.syntax.check.check$module→cxx.syntax.Ptrcxx.syntax.check.check$module→cxx.syntax.Receivercxx.syntax.check.check$module→cxx.syntax.Refcxx.syntax.check.check$module→cxx.syntax.Signaturecxx.syntax.check.check$module→cxx.syntax.SliceRefcxx.syntax.check.check$module→cxx.syntax.Structcxx.syntax.check.check$module→cxx.syntax.Ty1cxx.syntax.check.check$module→cxx.syntax.Typecxx.syntax.check.check$module→cxx.syntax.TypeAlias
- Direction
- cxx.syntax.check uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.check, while a change to cxx.syntax.check can't break cxx.syntax.
- Position
- Below the diagonal: cxx.syntax.check uses a module listed above it, which is the healthy direction.
33→31 cxx.syntax.check uses cxx.syntax.types✕
- Connections
- 2 pairs of types, where a type in cxx.syntax.check uses a type in cxx.syntax.types.
- The types involved
cxx.syntax.check.Check→cxx.syntax.types.Typescxx.syntax.check.check$module→cxx.syntax.types.Types
- Direction
- cxx.syntax.check uses cxx.syntax.types, so a change to cxx.syntax.types can break cxx.syntax.check, while a change to cxx.syntax.check can't break cxx.syntax.types.
- Position
- Below the diagonal: cxx.syntax.check uses a module listed above it, which is the healthy direction.
34→4 cxx.syntax.mangle uses cxx.syntax.symbol✕
- Connections
- 1 pair of types, where a type in cxx.syntax.mangle uses a type in cxx.syntax.symbol.
- The types involved
cxx.syntax.mangle.mangle$module→cxx.syntax.symbol.Symbol
- Direction
- cxx.syntax.mangle uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.syntax.mangle, while a change to cxx.syntax.mangle can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.syntax.mangle uses a module listed above it, which is the healthy direction.
34→17 cxx.syntax.mangle uses cxx.syntax.map.unordered✕
- Connections
- 1 pair of types, where a type in cxx.syntax.mangle uses a type in cxx.syntax.map.unordered.
- The types involved
cxx.syntax.mangle.mangle$module→cxx.syntax.map.unordered.UnorderedMap
- Direction
- cxx.syntax.mangle uses cxx.syntax.map.unordered, so a change to cxx.syntax.map.unordered can break cxx.syntax.mangle, while a change to cxx.syntax.mangle can't break cxx.syntax.map.unordered.
- Position
- Below the diagonal: cxx.syntax.mangle uses a module listed above it, which is the healthy direction.
34→28 cxx.syntax.mangle uses cxx.syntax✕
- Connections
- 3 pairs of types, where a type in cxx.syntax.mangle uses a type in cxx.syntax.
- The types involved
cxx.syntax.mangle.mangle$module→cxx.syntax.ExternFncxx.syntax.mangle.mangle$module→cxx.syntax.Paircxx.syntax.mangle.mangle$module→cxx.syntax.Type
- Direction
- cxx.syntax.mangle uses cxx.syntax, so a change to cxx.syntax can break cxx.syntax.mangle, while a change to cxx.syntax.mangle can't break cxx.syntax.
- Position
- Below the diagonal: cxx.syntax.mangle uses a module listed above it, which is the healthy direction.
34→31 cxx.syntax.mangle uses cxx.syntax.types✕
- Connections
- 1 pair of types, where a type in cxx.syntax.mangle uses a type in cxx.syntax.types.
- The types involved
cxx.syntax.mangle.mangle$module→cxx.syntax.types.Types
- Direction
- cxx.syntax.mangle uses cxx.syntax.types, so a change to cxx.syntax.types can break cxx.syntax.mangle, while a change to cxx.syntax.mangle can't break cxx.syntax.types.
- Position
- Below the diagonal: cxx.syntax.mangle uses a module listed above it, which is the healthy direction.
35→1 cxxbridge_macro.expand uses cxx.extern_type✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.expand uses a type in cxx.extern_type.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.extern_type.ExternType
- Direction
- cxxbridge_macro.expand uses cxx.extern_type, so a change to cxx.extern_type can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.extern_type.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→3 cxxbridge_macro.expand uses cxx.syntax.doc✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.doc.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.doc.Doc
- Direction
- cxxbridge_macro.expand uses cxx.syntax.doc, so a change to cxx.syntax.doc can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.doc.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→4 cxxbridge_macro.expand uses cxx.syntax.symbol✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.symbol.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.symbol.Symbol
- Direction
- cxxbridge_macro.expand uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→16 cxxbridge_macro.expand uses cxx.syntax.file✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.file.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.file.Module
- Direction
- cxxbridge_macro.expand uses cxx.syntax.file, so a change to cxx.syntax.file can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.file.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→18 cxxbridge_macro.expand uses cxx.syntax.instantiate✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.instantiate.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.instantiate.NamedImplKey
- Direction
- cxxbridge_macro.expand uses cxx.syntax.instantiate, so a change to cxx.syntax.instantiate can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.instantiate.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→26 cxxbridge_macro.expand uses cxx.syntax.attrs✕
- Connections
- 1 pair of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.attrs.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.attrs.OtherAttrs
- Direction
- cxxbridge_macro.expand uses cxx.syntax.attrs, so a change to cxx.syntax.attrs can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.attrs.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→28 cxxbridge_macro.expand uses cxx.syntax✕
- Connections
- 8 pairs of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.Enumcxxbridge_macro.expand.expand$module→cxx.syntax.ExternFncxxbridge_macro.expand.expand$module→cxx.syntax.Langcxxbridge_macro.expand.expand$module→cxx.syntax.Paircxxbridge_macro.expand.expand$module→cxx.syntax.Signaturecxxbridge_macro.expand.expand$module→cxx.syntax.Structcxxbridge_macro.expand.expand$module→cxx.syntax.Typecxxbridge_macro.expand.expand$module→cxx.syntax.TypeAlias
- Direction
- cxxbridge_macro.expand uses cxx.syntax, so a change to cxx.syntax can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
35→31 cxxbridge_macro.expand uses cxx.syntax.types✕
- Connections
- 2 pairs of types, where a type in cxxbridge_macro.expand uses a type in cxx.syntax.types.
- The types involved
cxxbridge_macro.expand.expand$module→cxx.syntax.types.ConditionalImplcxxbridge_macro.expand.expand$module→cxx.syntax.types.Types
- Direction
- cxxbridge_macro.expand uses cxx.syntax.types, so a change to cxx.syntax.types can break cxxbridge_macro.expand, while a change to cxxbridge_macro.expand can't break cxx.syntax.types.
- Position
- Below the diagonal: cxxbridge_macro.expand uses a module listed above it, which is the healthy direction.
36→4 cxx.bridge.src.guard uses cxx.syntax.symbol✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.guard uses a type in cxx.syntax.symbol.
- The types involved
cxx.bridge.src.guard.Guard→cxx.syntax.symbol.Symbol
- Direction
- cxx.bridge.src.guard uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.bridge.src.guard, while a change to cxx.bridge.src.guard can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.bridge.src.guard uses a module listed above it, which is the healthy direction.
36→28 cxx.bridge.src.guard uses cxx.syntax✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.guard uses a type in cxx.syntax.
- The types involved
cxx.bridge.src.guard.Guard→cxx.syntax.Pair
- Direction
- cxx.bridge.src.guard uses cxx.syntax, so a change to cxx.syntax can break cxx.bridge.src.guard, while a change to cxx.bridge.src.guard can't break cxx.syntax.
- Position
- Below the diagonal: cxx.bridge.src.guard uses a module listed above it, which is the healthy direction.
36→32 cxx.bridge.src.guard uses cxx.bridge.src.out✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.guard uses a type in cxx.bridge.src.out.
- The types involved
cxx.bridge.src.guard.Guard→cxx.bridge.src.out.OutFile
- Direction
- cxx.bridge.src.guard uses cxx.bridge.src.out, so a change to cxx.bridge.src.out can break cxx.bridge.src.guard, while a change to cxx.bridge.src.guard can't break cxx.bridge.src.out.
- Position
- Below the diagonal: cxx.bridge.src.guard uses a module listed above it, which is the healthy direction.
37→6 cxx.bridge.src.include uses cxx✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.include uses a type in cxx.
- The types involved
cxx.bridge.src.include.Includes→cxx.I
- Direction
- cxx.bridge.src.include uses cxx, so a change to cxx can break cxx.bridge.src.include, while a change to cxx.bridge.src.include can't break cxx.
- Position
- Below the diagonal: cxx.bridge.src.include uses a module listed above it, which is the healthy direction.
37→28 cxx.bridge.src.include uses cxx.syntax✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.include uses a type in cxx.syntax.
- The types involved
cxx.bridge.src.include.Include→cxx.syntax.IncludeKind
- Direction
- cxx.bridge.src.include uses cxx.syntax, so a change to cxx.syntax can break cxx.bridge.src.include, while a change to cxx.bridge.src.include can't break cxx.syntax.
- Position
- Below the diagonal: cxx.bridge.src.include uses a module listed above it, which is the healthy direction.
37→32 cxx.bridge.src.include uses cxx.bridge.src.out✕
- Connections
- 2 pairs of types, where a type in cxx.bridge.src.include uses a type in cxx.bridge.src.out.
- The types involved
cxx.bridge.src.include.Includes→cxx.bridge.src.out.Contentcxx.bridge.src.include.include$module→cxx.bridge.src.out.OutFile
- Direction
- cxx.bridge.src.include uses cxx.bridge.src.out, so a change to cxx.bridge.src.out can break cxx.bridge.src.include, while a change to cxx.bridge.src.include can't break cxx.bridge.src.out.
- Position
- Below the diagonal: cxx.bridge.src.include uses a module listed above it, which is the healthy direction.
38→1 cxx.bridge.src.write uses cxx.extern_type✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.extern_type.
- The types involved
cxx.bridge.src.write.write$module→cxx.extern_type.ExternType
- Direction
- cxx.bridge.src.write uses cxx.extern_type, so a change to cxx.extern_type can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.extern_type.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→2 cxx.bridge.src.write uses cxx.syntax.discriminant✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.syntax.discriminant.
- The types involved
cxx.bridge.src.write.write$module→cxx.syntax.discriminant.Discriminant
- Direction
- cxx.bridge.src.write uses cxx.syntax.discriminant, so a change to cxx.syntax.discriminant can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.syntax.discriminant.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→3 cxx.bridge.src.write uses cxx.syntax.doc✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.syntax.doc.
- The types involved
cxx.bridge.src.write.write$module→cxx.syntax.doc.Doc
- Direction
- cxx.bridge.src.write uses cxx.syntax.doc, so a change to cxx.syntax.doc can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.syntax.doc.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→4 cxx.bridge.src.write uses cxx.syntax.symbol✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.syntax.symbol.
- The types involved
cxx.bridge.src.write.write$module→cxx.syntax.symbol.Symbol
- Direction
- cxx.bridge.src.write uses cxx.syntax.symbol, so a change to cxx.syntax.symbol can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.syntax.symbol.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→10 cxx.bridge.src.write uses cxxbridge_cmd✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxxbridge_cmd.
- The types involved
cxx.bridge.src.write.write$module→cxxbridge_cmd.Opt
- Direction
- cxx.bridge.src.write uses cxxbridge_cmd, so a change to cxxbridge_cmd can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxxbridge_cmd.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→18 cxx.bridge.src.write uses cxx.syntax.instantiate✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.syntax.instantiate.
- The types involved
cxx.bridge.src.write.write$module→cxx.syntax.instantiate.NamedImplKey
- Direction
- cxx.bridge.src.write uses cxx.syntax.instantiate, so a change to cxx.syntax.instantiate can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.syntax.instantiate.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→28 cxx.bridge.src.write uses cxx.syntax✕
- Connections
- 9 pairs of types, where a type in cxx.bridge.src.write uses a type in cxx.syntax.
- The types involved
cxx.bridge.src.write.write$module→cxx.syntax.Enumcxx.bridge.src.write.write$module→cxx.syntax.ExternFncxx.bridge.src.write.write$module→cxx.syntax.Langcxx.bridge.src.write.write$module→cxx.syntax.Paircxx.bridge.src.write.write$module→cxx.syntax.Signaturecxx.bridge.src.write.write$module→cxx.syntax.Structcxx.bridge.src.write.write$module→cxx.syntax.Typecxx.bridge.src.write.write$module→cxx.syntax.TypeAliascxx.bridge.src.write.write$module→cxx.syntax.Var
- Direction
- cxx.bridge.src.write uses cxx.syntax, so a change to cxx.syntax can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.syntax.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→31 cxx.bridge.src.write uses cxx.syntax.types✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.syntax.types.
- The types involved
cxx.bridge.src.write.write$module→cxx.syntax.types.Types
- Direction
- cxx.bridge.src.write uses cxx.syntax.types, so a change to cxx.syntax.types can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.syntax.types.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
38→32 cxx.bridge.src.write uses cxx.bridge.src.out✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.write uses a type in cxx.bridge.src.out.
- The types involved
cxx.bridge.src.write.write$module→cxx.bridge.src.out.OutFile
- Direction
- cxx.bridge.src.write uses cxx.bridge.src.out, so a change to cxx.bridge.src.out can break cxx.bridge.src.write, while a change to cxx.bridge.src.write can't break cxx.bridge.src.out.
- Position
- Below the diagonal: cxx.bridge.src.write uses a module listed above it, which is the healthy direction.
39→10 cxx.bridge.src uses cxxbridge_cmd✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src uses a type in cxxbridge_cmd.
- The types involved
cxx.bridge.src.src$module→cxxbridge_cmd.Opt
- Direction
- cxx.bridge.src uses cxxbridge_cmd, so a change to cxxbridge_cmd can break cxx.bridge.src, while a change to cxx.bridge.src can't break cxxbridge_cmd.
- Position
- Below the diagonal: cxx.bridge.src uses a module listed above it, which is the healthy direction.
39→37 cxx.bridge.src uses cxx.bridge.src.include✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src uses a type in cxx.bridge.src.include.
- The types involved
cxx.bridge.src.Opt→cxx.bridge.src.include.Include
- Direction
- cxx.bridge.src uses cxx.bridge.src.include, so a change to cxx.bridge.src.include can break cxx.bridge.src, while a change to cxx.bridge.src can't break cxx.bridge.src.include.
- Position
- Below the diagonal: cxx.bridge.src uses a module listed above it, which is the healthy direction.
40→9 cxx.bridge.src.cfg uses cxx.syntax.report✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.cfg uses a type in cxx.syntax.report.
- The types involved
cxx.bridge.src.cfg.cfg$module→cxx.syntax.report.Errors
- Direction
- cxx.bridge.src.cfg uses cxx.syntax.report, so a change to cxx.syntax.report can break cxx.bridge.src.cfg, while a change to cxx.bridge.src.cfg can't break cxx.syntax.report.
- Position
- Below the diagonal: cxx.bridge.src.cfg uses a module listed above it, which is the healthy direction.
40→12 cxx.bridge.src.cfg uses cxx.syntax.cfg✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.cfg uses a type in cxx.syntax.cfg.
- The types involved
cxx.bridge.src.cfg.cfg$module→cxx.syntax.cfg.CfgExpr
- Direction
- cxx.bridge.src.cfg uses cxx.syntax.cfg, so a change to cxx.syntax.cfg can break cxx.bridge.src.cfg, while a change to cxx.bridge.src.cfg can't break cxx.syntax.cfg.
- Position
- Below the diagonal: cxx.bridge.src.cfg uses a module listed above it, which is the healthy direction.
40→28 cxx.bridge.src.cfg uses cxx.syntax✕
- Connections
- 1 pair of types, where a type in cxx.bridge.src.cfg uses a type in cxx.syntax.
- The types involved
cxx.bridge.src.cfg.cfg$module→cxx.syntax.Api
- Direction
- cxx.bridge.src.cfg uses cxx.syntax, so a change to cxx.syntax can break cxx.bridge.src.cfg, while a change to cxx.bridge.src.cfg can't break cxx.syntax.
- Position
- Below the diagonal: cxx.bridge.src.cfg uses a module listed above it, which is the healthy direction.
40→39 cxx.bridge.src.cfg uses cxx.bridge.src✕
- Connections
- 2 pairs of types, where a type in cxx.bridge.src.cfg uses a type in cxx.bridge.src.
- The types involved
cxx.bridge.src.cfg.UnsupportedCfgEvaluator→cxx.bridge.src.CfgEvaluatorcxx.bridge.src.cfg.UnsupportedCfgEvaluator→cxx.bridge.src.CfgResult
- Direction
- cxx.bridge.src.cfg uses cxx.bridge.src, so a change to cxx.bridge.src can break cxx.bridge.src.cfg, while a change to cxx.bridge.src.cfg can't break cxx.bridge.src.
- Position
- Below the diagonal: cxx.bridge.src.cfg uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 40 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
First, establish a formal process for recording significant design decisions by maintaining a dedicated ADR folder with dated documents for each choice. Second, implement robust observability by adding verbose logging to error paths, ensuring users can provide diagnostic trails when reporting bugs. Third, automate dependency management by enabling tools like Dependabot to track and update libraries, while simultaneously maintaining a clear changelog to document what ships in every release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.6 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. | +7.0 pts | Medium | Architecture documentation |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +6.5 pts | Medium | Observability |
| Enable Dependabot/Renovate or a dependency-review gate. | +3.7 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.9 pts | Medium | Release Hygiene |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.9 pts | Medium | Documentation (README) |
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +0.8 pts | Low | Test Distribution |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +1.2 pts | Medium | Web-Security Posture |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| macro/src/expand.rs | 5.0 | Mixed | Change Coupling: Boundary-crossing change coupling: expand.rs ↔ rust_vec.rs |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| syntax/parse.rs | 5.5 | Mixed | Cyclomatic Complexity: cxx::syntax::parse::parse_type_path (cyclomatic 33) |
| src/shared_ptr.rs | 5.7 | Mixed | Code Duplication: Duplicated block (7 lines × 2) |
| src/unique_ptr.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| bridge/src/write.rs | 7.0 | Mixed | Cyclomatic Complexity: cxx::bridge::src::write::write_cxx_function_shim (cyclomatic 41) |
| syntax/check.rs | 7.0 | Mixed | Cyclomatic Complexity: cxx::syntax::check::check_api_fn (cyclomatic 28) |
| syntax/attrs.rs | 7.1 | Mixed | Cyclomatic Complexity: cxx::syntax::attrs::parse (cyclomatic 38) |
| bridge/src/builtin.rs | 7.1 | Mixed | Cyclomatic Complexity: cxx::bridge::src::builtin::write (cyclomatic 49) |
| syntax/trivial.rs | 7.1 | Mixed | Cyclomatic Complexity: cxx::syntax::trivial::as_what (cyclomatic 26) |
| syntax/types.rs | 7.2 | Mixed | Cyclomatic Complexity: Types::collect (cyclomatic 41) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/rust_slice.rs | 7.3 | Mixed | Explicit Debt: TodoComment |
| bridge/src/include.rs | 7.8 | Mixed | Cyclomatic Complexity: cxx::bridge::src::include::write (cyclomatic 50) |
| syntax/signature.rs | 7.8 | Mixed | Cyclomatic Complexity: Signature::undeclared_lifetimes (cyclomatic 21) |
| bridge/src/cfg.rs | 7.8 | Mixed | Cyclomatic Complexity: cxx::bridge::src::cfg::try_eval (cyclomatic 16) |
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. 59 of 59 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 — 59 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, 184 of 198 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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.
- 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (80 contributor(s) across 4462 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 79 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — 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.
- D31 IaC & Container Security — 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. REDACTED carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 1 of 2 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- 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.
- AXR1 Runtime accessibility — 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. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM dtolnay/devcontainer:latest 2 | -------------------- ERROR: failed to solve: dtolnay/devcontainer:latest: failed to resolve source metadata for docker.io/dtolnay/devcontainer:latest: failed to do request: Head "https://registry-1.docker.io/v2/dtolnay/devcontainer/manifests/latest": Forbidden; runtime evidence skipped.
- 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 this repository's Rust, c, cpp is most of its product and 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 this repository's Rust, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X26 Unsynchronised callback handoff — 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 Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C, 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.
- 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, Cpp, 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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 REDACTED (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.
- 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
27 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was cxxbridge_macro::expand::expand_cxx_function_shim at 56. A further 7 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 cxx::syntax::check::do_typecheck at 21 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: macro/src/derive.rs (cxxbridge_macro::derive::expand_enum at 20), syntax/atom.rs (Atom::from_str at 17), syntax/derive.rs (Derive::from at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 27 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with cxxbridge_macro::expand::expand_cxx_function_shim (cyclomatic 56), cxx::bridge::src::include::write (cyclomatic 50), cxx::bridge::src::builtin::write (cyclomatic 49). — 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 27 together lifts Cyclomatic Complexity from 6.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
35 method(s) exceeded the cognitive complexity threshold of 15; the worst was cxx::syntax::attrs::parse at 90.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with cxx::syntax::attrs::parse (cognitive 90), cxx::syntax::parse::parse_type_path (cognitive 76), cxxbridge_macro::expand::expand_cxx_function_shim (cognitive 72). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 4.5 to about 5.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
16 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 11 FunctionTooLong finding(s) in God Classes — start with expand.rs (4), parse.rs (2), write.rs (2). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with expand.rs, write.rs, parse.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with types.rs. — One of this dimension's main actionable groups (1 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
42 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with expand.rs (3), derive.rs, parse.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with parse.rs (2), expand.rs, check.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with expand.rs (2), attrs.rs, check.rs. — One of this dimension's main actionable groups (4 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
11 production modules (Cargo+npm+Bazel), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 4 of the 11 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 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 35 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with shared_ptr.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
56 test methods: 13 unit, 43 integration, 0 BDD, 0 e2e. The Rust suite contributes 56 `#[test]` function(s) across 14 file(s) declaring at least one; its unit/integration split is Cargo's own — 9 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 14 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 12 of 14 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed Cargo.lock). 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 42 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here. ★ 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
No churn × complexity hotspots in the window.
D17 · Explicit Debt
10 deducted task-comment markers across 19242 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 10 TodoComment finding(s) in Explicit Debt — start with unique_ptr.rs (3), rust_slice.rs (2), deny_missing_docs.rs. — One of this dimension's main actionable groups (10 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. 8 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
1 of 6 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
40 finding(s): 0 critical, 40 high, 0 medium, 0 low. 38 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/cxx_string.rs` (line 19) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 35 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 (35 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 0 medium, 4 low.
What to do
- Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 47 of the 102 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: impls.rs↔parse.rs 71%; parse.rs↔tokens.rs 52%; expand.rs↔rust_vec.rs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with expand.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with impls.rs, parse.rs. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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
- 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 6 project(s) that lack one — worth up to 1.3 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
S1 · Web-Security Posture
- `https://www.googletagmanager.com/gtag/js?id=G-DG41MK6DDN` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — book/theme/head.hbs:1
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
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
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 | 88% | Strong | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 48% | Weak — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
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 — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript 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 — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM dtolnay/devcontainer:latest 2 | -------------------- ERROR: failed to solve: dtolnay/devcontainer:latest: failed to resolve source metadata for docker.io/dtolnay/devcontainer:latest: failed to do request: Head "https://registry-1.docker.io/v2/dtolnay/devcontainer/manifests/latest": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a 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 — ~2887 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; 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 .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.
- 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 (19 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
- M4 Documentation accuracy — Not applicable: the 8 current-state document(s) make no claim of a kind M4 checks.
- 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 JavaScript/TypeScript, 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — 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.
- X26 Unsynchronised callback handoff — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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 — 44 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
- Boundary-crossing change coupling: expand.rs ↔ rust_vec.rs macro/src/expand.rs:1
Serious — 140 finding(s)
- cxx::syntax::attrs::parse (cognitive 90) syntax/attrs.rs:48
- cxx::syntax::parse::parse_type_path (cognitive 76) syntax/parse.rs:1246
- cxx::bridge::src::builtin::write (cognitive 57) bridge/src/builtin.rs:49
- cxx::bridge::src::include::write (cognitive 52) bridge/src/include.rs:65
- cxx::bridge::src::write::write_cxx_function_shim (cognitive 46) bridge/src/write.rs:847
- cxx::bridge::src::write::write_rust_function_shim_impl (cognitive 39) bridge/src/write.rs:1183
- cxx::syntax::check::check_api_fn (cognitive 38) syntax/check.rs:474
- cxx::syntax::trivial::required_trivial_reasons (cognitive 36) syntax/trivial.rs:30
- cxx::syntax::trivial::as_what (cognitive 31) syntax/trivial.rs:117
- cxx::syntax::parse::parse_foreign_mod (cognitive 28) syntax/parse.rs:354
- cxx::bridge::src::write::write_data_structures (cognitive 27) bridge/src/write.rs:97
- cxx::syntax::parse::parse_extern_fn (cognitive 27) syntax/parse.rs:533
- cxx::lossy::debug (cognitive 22) src/lossy.rs:24
- cxx::syntax::parse::parse_struct (cognitive 22) syntax/parse.rs:59
- cxx::bridge::src::pragma::write (cognitive 20) bridge/src/pragma.rs:22
- cxx::syntax::parse::parse_extern_type_bounded (cognitive 20) syntax/parse.rs:936
- cxx::bridge::src::cfg::try_eval (cognitive 19) bridge/src/cfg.rs:70
- cxx::bridge::src::ifndef::write (cognitive 19) bridge/src/ifndef.rs:4
- cxx::bridge::src::write::write_struct (cognitive 19) bridge/src/write.rs:277
- cxx::bridge::src::write::write_rust_function_decl_impl (cognitive 19) bridge/src/write.rs:1057
- cxx::bridge::src::file::parse (cognitive 18) bridge/src/file.rs:19
- cxx::bridge::src::builtin::write_builtin (cognitive 17) bridge/src/builtin.rs:348
- cxx::syntax::parse::parse_impl (cognitive 17) syntax/parse.rs:1031
- cxx::bridge::src::write::write_type_to_generic_writer (cognitive 16) bridge/src/write.rs:1419
- cxx::syntax::parse::extern_type_lifetimes (cognitive 16) syntax/parse.rs:828
- cxx::bridge::src::include::write (cyclomatic 50) bridge/src/include.rs:65
- cxx::bridge::src::builtin::write (cyclomatic 49) bridge/src/builtin.rs:49
- cxx::bridge::src::write::write_cxx_function_shim (cyclomatic 41) bridge/src/write.rs:847
- cxx::syntax::attrs::parse (cyclomatic 38) syntax/attrs.rs:48
- cxx::bridge::src::write::write_rust_function_shim_impl (cyclomatic 35) bridge/src/write.rs:1183
- cxx::bridge::src::builtin::write_builtin (cyclomatic 34) bridge/src/builtin.rs:348
- cxx::syntax::parse::parse_type_path (cyclomatic 33) syntax/parse.rs:1246
- cxx::syntax::check::check_api_fn (cyclomatic 28) syntax/check.rs:474
- cxx::syntax::trivial::as_what (cyclomatic 26) syntax/trivial.rs:117
- cxx::syntax::parse::parse_extern_fn (cyclomatic 23) syntax/parse.rs:533
- cxx::syntax::parse::parse_foreign_mod (cyclomatic 22) syntax/parse.rs:354
- cxx::bridge::src::write::write_type_to_generic_writer (cyclomatic 21) bridge/src/write.rs:1419
- cxx::syntax::check::describe (cyclomatic 21) syntax/check.rs:788
- cxx::syntax::trivial::required_trivial_reasons (cyclomatic 20) syntax/trivial.rs:30
- cxx::bridge::src::write::pick_includes_and_builtins (cyclomatic 19) bridge/src/write.rs:227
- cxx::bridge::src::cfg::try_eval (cyclomatic 16) bridge/src/cfg.rs:70
- cxx::bridge::src::pragma::write (cyclomatic 16) bridge/src/pragma.rs:22
- cxx::bridge::src::write::write_data_structures (cyclomatic 16) bridge/src/write.rs:97
- cxx::syntax::parse::parse_struct (cyclomatic 16) syntax/parse.rs:59
- FunctionTooLong: cxxbridge_macro::expand::expand_cxx_function_shim macro/src/expand.rs:725
- FunctionTooLong: cxx::bridge::src::builtin::write bridge/src/builtin.rs:49
- FunctionTooLong: cxx::syntax::parse::parse_extern_fn syntax/parse.rs:533
- FunctionTooLong: cxxbridge_macro::expand::expand_rust_function_shim_impl macro/src/expand.rs:1179
- FunctionTooLong: cxx::bridge::src::write::write_cxx_function_shim bridge/src/write.rs:847
- FunctionTooLong: cxxbridge_macro::expand::expand_type_alias_verify macro/src/expand.rs:1457
- FunctionTooLong: cxxbridge_macro::expand::expand_cxx_vector macro/src/expand.rs:2115
- FunctionTooLong: cxx::syntax::trivial::as_what syntax/trivial.rs:117
- FunctionTooLong: cxx::bridge::src::write::write_rust_function_shim_impl bridge/src/write.rs:1183
- FunctionTooLong: cxx::syntax::attrs::parse syntax/attrs.rs:48
- FunctionTooLong: cxx::syntax::parse::parse_struct syntax/parse.rs:59
- TodoComment tests/ui/deny_missing_docs.rs:1
- TodoComment syntax/instantiate.rs:29
- TodoComment syntax/names.rs:39
- TodoComment syntax/symbol.rs:94
- TodoComment src/opaque.rs:26
- TodoComment src/rust_slice.rs:39
- TodoComment src/rust_slice.rs:55
- TodoComment src/unique_ptr.rs:280
- TodoComment src/unique_ptr.rs:313
- TodoComment src/unique_ptr.rs:351
- Duplicated block (8 lines × 2) macro/src/derive.rs:172
- Duplicated block (8 lines × 2) macro/src/expand.rs:174
- Duplicated block (8 lines × 2) macro/src/expand.rs:1836
- Duplicated block (8 lines × 2) macro/src/expand.rs:2006
- Duplicated block (8 lines × 2) syntax/parse.rs:73
- Duplicated block (8 lines × 2) src/shared_ptr.rs:61
- cxxbridge_macro::expand::expand_cxx_function_shim (cyclomatic 56) macro/src/expand.rs:725
- cxxbridge_macro::expand::expand_rust_function_shim_impl (cyclomatic 38) macro/src/expand.rs:1179
- cxxbridge_macro::expand::expand_type_alias_verify (cyclomatic 26) macro/src/expand.rs:1457
- cxxbridge_macro::expand::expand (cyclomatic 22) macro/src/expand.rs:57
- cxxbridge_macro::expand::expand_extern_type (cyclomatic 17) macro/src/expand.rs:2315
- cxxbridge_macro::expand::expand_cxx_function_shim (cognitive 72) macro/src/expand.rs:725
- cxxbridge_macro::expand::expand_type_alias_verify (cognitive 42) macro/src/expand.rs:1457
- cxxbridge_macro::expand::expand_rust_function_shim_impl (cognitive 30) macro/src/expand.rs:1179
- cxxbridge_macro::expand::expand_associated_functions (cognitive 19) macro/src/expand.rs:594
- cxxbridge_macro::expand::expand (cognitive 18) macro/src/expand.rs:57
- Duplicated block (10 lines × 2) macro/src/expand.rs:1866
- Duplicated block (10 lines × 2) syntax/check.rs:743
- Duplicated block (10 lines × 2) syntax/parse.rs:65
- Duplicated block (10 lines × 2) syntax/parse.rs:144
- Duplicated block (10 lines × 2) bridge/src/write.rs:1336
- FileTooLong: src/expand.rs macro/src/expand.rs
- FileTooLong: src/write.rs bridge/src/write.rs
- FileTooLong: syntax/parse.rs syntax/parse.rs
- FileTooLong: syntax/check.rs syntax/check.rs
- Duplicated block (12 lines × 2) macro/src/expand.rs:1982
- Duplicated block (12 lines × 2) macro/src/expand.rs:2021
- Duplicated block (12 lines × 2) syntax/attrs.rs:134
- Duplicated block (12 lines × 2) syntax/check.rs:169
- Duplicated block (9 lines × 2) macro/src/expand.rs:1839
- Duplicated block (9 lines × 2) syntax/parse.rs:60
- Duplicated block (9 lines × 2) syntax/parse.rs:484
- Duplicated block (9 lines × 2) syntax/parse.rs:897
- cxx_build::make_this_crate (cognitive 20) bridge/build/src/lib.rs:268
- cxx_build::best_effort_copy_headers (cognitive 18) bridge/build/src/lib.rs:436
- cxx_build::out::best_effort_remove (cognitive 18) bridge/build/src/out.rs:121
- Duplicated block (15 lines × 2) bridge/src/write.rs:324
- Duplicated block (15 lines × 2) syntax/parse.rs:102
- Duplicated block (15 lines × 2) bridge/src/write.rs:1843
- Duplicated block (11 lines × 2) macro/src/expand.rs:1859
- Duplicated block (11 lines × 2) macro/src/expand.rs:2044
- Duplicated block (11 lines × 2) syntax/types.rs:115
- Duplicated block (6 lines × 2) syntax/parse.rs:889
- Duplicated block (6 lines × 2) src/shared_ptr.rs:281
- Duplicated block (6 lines × 2) src/shared_ptr.rs:293
- Change coupling: impls.rs ↔ parse.rs syntax/impls.rs:1
- Change coupling: parse.rs ↔ tokens.rs syntax/parse.rs:1
- Duplicated block (5 lines × 2) syntax/check.rs:99
- Duplicated block (5 lines × 2) bridge/src/write.rs:281
- Off the main sequence: cxxbridge-cmd
- Off the main sequence: cxx-build
- Types::collect (cyclomatic 41) syntax/types.rs:48
- Signature::undeclared_lifetimes (cyclomatic 21) syntax/signature.rs:30
- (anonymous) (cyclomatic 16) book/build.js:41
- Types::collect (cognitive 69) syntax/types.rs:48
- Signature::undeclared_lifetimes (cognitive 19) syntax/signature.rs:30
- MethodTooLong: Types.collect syntax/types.rs:48
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) macro/src/expand.rs:1656
- Members sharing a duplicated core (4 members, 50+ identical tokens) syntax/parse.rs:483
- Duplicated block (19 lines × 2) macro/src/tokens.rs:23
- Duplicated block (17 lines × 2) macro/src/expand.rs:1662
- Duplicated block (11 lines × 3) syntax/attrs.rs:122
- Duplicated block (9 lines × 4) macro/src/expand.rs:1662
- Duplicated block (8 lines × 6) macro/src/expand.rs:1665
- Duplicated block (8 lines × 4) syntax/parse.rs:496
- Duplicated block (7 lines × 2) src/shared_ptr.rs:237
- Duplicated block (6 lines × 3) macro/src/expand.rs:173
- Duplicated block (12 lines × 4) syntax/attrs.rs:83
- Duplicated block (8 lines × 3) syntax/check.rs:123
- Duplicated block (7 lines × 6) syntax/parse.rs:1258
- Duplicated block (5 lines × 6) macro/src/expand.rs:260
- Low cohesion: SharedPtr (LCOM4 5) src/shared_ptr.rs:46
- No structured logging
- Third-party script without Subresource Integrity book/theme/head.hbs:1
Minor — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- No architecture diagram/doc
- No changelog
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-eda3be64dc56449d86c3f3c4090385c5/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-eda3be64dc56449d86c3f3c4090385c5/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 third-party/bazel . | 40 | 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 | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 |