Executive summary
mstange/samply falls short of our standard for a preview release, in part because we found no access checks on the code's endpoints or handlers. It scores 54 out of 100 and is rated Adequate, and 32 of its 34 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Security and Compliance, at 35, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 14 points. Recording design decisions comes next, worth about 5 points. Raising Security and Compliance to 68 would lift the score to about 68.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps run downloads nobody checks, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, checking each download against a checksum and setting a waiting period for automatic updates would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 64,542 lines, about €67,000 to rebuild.
If Security and Compliance rose from 35 to 68, the lowest score rated Strong, the score would rise from 54 to about 68.
New since the last survey: 20 findings
- Cognitive Complexity · samply::server::symbolication_service (cognitive 19) samply/src/server.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €67,000 · Estimate
| Cost to rebuild | €22,000 to €110,000, for 371 to 1,177 hours of work, about 0.5 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 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 64,542 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 fxprof_processed_profile.writer | 2 samply.shared.prop_types | 3 samply_debugid.codeid | 4 etw_reader.tdh_types | 5 fxprof_processed_profile.library_info | 6 fxprof_processed_profile.markers.types | 7 fxprof_processed_profile.timestamp | 8 samply_symbols.symbol_map_string_interner | 9 etw_reader.schema | 10 fxprof_processed_profile.markers.dynamic_schema | 11 samply.shared.timestamp_converter | 12 samply_symbols.source_file_path | 13 etw_reader.etw_types | 14 fxprof_processed_profile.markers.static_schema | 15 samply_symbols.shared | 16 fxprof_processed_profile.string_table | 17 samply_symbols.symbol_map | 18 wholesym.file_resolver | 19 fxprof_processed_profile.global_lib_table | 20 fxprof_processed_profile.marker_table | 21 samply_symbols.symbol_map_object | 22 fxprof_processed_profile.frame_table | 23 fxprof_processed_profile.thread | 24 fxprof_processed_profile.process | 25 gecko_profile | 26 fxprof_processed_profile.profile | 27 fxprof_processed_profile.category | 28 samply.import.perf | 29 samply.shared.per_cpu | 30 samply.shared.unresolved_samples | 31 samply.shared.jit_category_manager | 32 samply_api | 33 samply.shared.lib_mappings | 34 wholesym.symbol_manager | 35 samply.linux_shared.converter | 36 samply.shared.jitdump_manager | 37 samply.shared.process_sample_data | 38 samply.linux_shared.process | 39 samply.mac.task_profiler | 40 samply.windows.profile_context |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 fxprof_processed_profile.writer | ||||||||||||||||||||||||||||||||||||||||
| 2 samply.shared.prop_types | ||||||||||||||||||||||||||||||||||||||||
| 3 samply_debugid.codeid | ||||||||||||||||||||||||||||||||||||||||
| 4 etw_reader.tdh_types | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 fxprof_processed_profile.library_info | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 fxprof_processed_profile.markers.types | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 fxprof_processed_profile.timestamp | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 samply_symbols.symbol_map_string_interner | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 etw_reader.schema | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 10 fxprof_processed_profile.markers.dynamic_schema | 2 | 6 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 11 samply.shared.timestamp_converter | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 samply_symbols.source_file_path | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 etw_reader.etw_types | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 fxprof_processed_profile.markers.static_schema | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 samply_symbols.shared | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 fxprof_processed_profile.string_table | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 samply_symbols.symbol_map | 4 | 18 | ||||||||||||||||||||||||||||||||||||||
| 18 wholesym.file_resolver | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 19 fxprof_processed_profile.global_lib_table | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 fxprof_processed_profile.marker_table | 2 | 3 | 1 | 1 | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 21 samply_symbols.symbol_map_object | 2 | 2 | 2 | 6 | 4 | |||||||||||||||||||||||||||||||||||
| 22 fxprof_processed_profile.frame_table | 1 | 2 | 3 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 23 fxprof_processed_profile.thread | 1 | 3 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 24 fxprof_processed_profile.process | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 gecko_profile | 2 | 2 | 1 | 8 | 3 | 3 | ||||||||||||||||||||||||||||||||||
| 26 fxprof_processed_profile.profile | 3 | 2 | 4 | 1 | 1 | 4 | 2 | 2 | 2 | 2 | 3 | |||||||||||||||||||||||||||||
| 27 fxprof_processed_profile.category | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 28 samply.import.perf | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 samply.shared.per_cpu | 1 | 1 | 2 | 3 | 1 | 2 | 5 | |||||||||||||||||||||||||||||||||
| 30 samply.shared.unresolved_samples | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 samply.shared.jit_category_manager | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 32 samply_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 samply.shared.lib_mappings | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 wholesym.symbol_manager | 1 | 1 | 2 | 10 | 2 | 4 | 3 | |||||||||||||||||||||||||||||||||
| 35 samply.linux_shared.converter | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||
| 36 samply.shared.jitdump_manager | 1 | 2 | 1 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 37 samply.shared.process_sample_data | 1 | 6 | 6 | 1 | 1 | 7 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||
| 38 samply.linux_shared.process | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||
| 39 samply.mac.task_profiler | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 40 samply.windows.profile_context | 1 | 1 | 1 | 1 | 1 | 1 | 5 | 2 | 4 | 5 | 1 | 1 | 3 | 1 | 2 | 1 |
4→13 etw_reader.tdh_types uses etw_reader.etw_types part of a loop✕
- Connections
- 1 pair of types, where a type in etw_reader.tdh_types uses a type in etw_reader.etw_types.
- The types involved
etw_reader.tdh_types.Property→etw_reader.etw_types.EventPropertyInfo
- Direction
- etw_reader.tdh_types uses etw_reader.etw_types, so a change to etw_reader.etw_types can break etw_reader.tdh_types, while a change to etw_reader.tdh_types can't break etw_reader.etw_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.
5→1 fxprof_processed_profile.library_info uses fxprof_processed_profile.writer✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.library_info uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.library_info.LibraryInfo→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.library_info uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.library_info, while a change to fxprof_processed_profile.library_info can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.library_info uses a module listed above it, which is the healthy direction.
6→1 fxprof_processed_profile.markers.types uses fxprof_processed_profile.writer✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.markers.types uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.markers.types.GraphColor→fxprof_processed_profile.writer.Writerfxprof_processed_profile.markers.types.MarkerFieldPIICategory→fxprof_processed_profile.writer.Writerfxprof_processed_profile.markers.types.MarkerGraphType→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.markers.types uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.markers.types, while a change to fxprof_processed_profile.markers.types can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.markers.types uses a module listed above it, which is the healthy direction.
7→1 fxprof_processed_profile.timestamp uses fxprof_processed_profile.writer✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.timestamp uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.timestamp.Timestamp→fxprof_processed_profile.writer.Writerfxprof_processed_profile.timestamp.timestamp$module→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.timestamp uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.timestamp, while a change to fxprof_processed_profile.timestamp can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.timestamp uses a module listed above it, which is the healthy direction.
8→12 samply_symbols.symbol_map_string_interner uses samply_symbols.source_file_path part of a loop✕
- Connections
- 1 pair of types, where a type in samply_symbols.symbol_map_string_interner uses a type in samply_symbols.source_file_path.
- The types involved
samply_symbols.symbol_map_string_interner.SymbolMapStringHandle→samply_symbols.source_file_path.SourceFilePathHandle
- Direction
- samply_symbols.symbol_map_string_interner uses samply_symbols.source_file_path, so a change to samply_symbols.source_file_path can break samply_symbols.symbol_map_string_interner, while a change to samply_symbols.symbol_map_string_interner can't break samply_symbols.source_file_path.
- 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→15 samply_symbols.symbol_map_string_interner uses samply_symbols.shared part of a loop✕
- Connections
- 2 pairs of types, where a type in samply_symbols.symbol_map_string_interner uses a type in samply_symbols.shared.
- The types involved
samply_symbols.symbol_map_string_interner.SymbolMapStringHandle→samply_symbols.shared.FunctionNameHandlesamply_symbols.symbol_map_string_interner.SymbolMapStringHandle→samply_symbols.shared.SymbolNameHandle
- Direction
- samply_symbols.symbol_map_string_interner uses samply_symbols.shared, so a change to samply_symbols.shared can break samply_symbols.symbol_map_string_interner, while a change to samply_symbols.symbol_map_string_interner can't break samply_symbols.shared.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→4 etw_reader.schema uses etw_reader.tdh_types✕
- Connections
- 2 pairs of types, where a type in etw_reader.schema uses a type in etw_reader.tdh_types.
- The types involved
etw_reader.schema.EventSchema→etw_reader.tdh_types.Propertyetw_reader.schema.TypedEvent→etw_reader.tdh_types.Property
- Direction
- etw_reader.schema uses etw_reader.tdh_types, so a change to etw_reader.tdh_types can break etw_reader.schema, while a change to etw_reader.schema can't break etw_reader.tdh_types.
- Position
- Below the diagonal: etw_reader.schema uses a module listed above it, which is the healthy direction.
9→13 etw_reader.schema uses etw_reader.etw_types part of a loop✕
- Connections
- 5 pairs of types, where a type in etw_reader.schema uses a type in etw_reader.etw_types.
- The types involved
etw_reader.schema.EventSchema→etw_reader.etw_types.DecodingSourceetw_reader.schema.SchemaKey→etw_reader.etw_types.EventRecordetw_reader.schema.SchemaLocator→etw_reader.etw_types.EventRecordetw_reader.schema.TypedEvent→etw_reader.etw_types.DecodingSourceetw_reader.schema.TypedEvent→etw_reader.etw_types.EventRecord
- Direction
- etw_reader.schema uses etw_reader.etw_types, so a change to etw_reader.etw_types can break etw_reader.schema, while a change to etw_reader.schema can't break etw_reader.etw_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.
10→1 fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.writer✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.markers.dynamic_schema uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerFieldFormat→fxprof_processed_profile.writer.Writerfxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerGraph→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.markers.dynamic_schema, while a change to fxprof_processed_profile.markers.dynamic_schema can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.markers.dynamic_schema uses a module listed above it, which is the healthy direction.
10→6 fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.markers.types✕
- Connections
- 6 pairs of types, where a type in fxprof_processed_profile.markers.dynamic_schema uses a type in fxprof_processed_profile.markers.types.
- The types involved
fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarker→fxprof_processed_profile.markers.types.MarkerTypeHandlefxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerField→fxprof_processed_profile.markers.types.MarkerFieldPIICategoryfxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerFieldFormat→fxprof_processed_profile.markers.types.MarkerFieldKindfxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerGraph→fxprof_processed_profile.markers.types.GraphColorfxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerGraph→fxprof_processed_profile.markers.types.MarkerGraphTypefxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerSchema→fxprof_processed_profile.markers.types.MarkerLocations
- Direction
- fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break fxprof_processed_profile.markers.dynamic_schema, while a change to fxprof_processed_profile.markers.dynamic_schema can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: fxprof_processed_profile.markers.dynamic_schema uses a module listed above it, which is the healthy direction.
10→14 fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.markers.static_schema part of a loop✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.markers.dynamic_schema uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerField→fxprof_processed_profile.markers.static_schema.MarkerFieldfxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerGraph→fxprof_processed_profile.markers.static_schema.MarkerGraph
- Direction
- fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break fxprof_processed_profile.markers.dynamic_schema, while a change to fxprof_processed_profile.markers.dynamic_schema can't break fxprof_processed_profile.markers.static_schema.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→16 fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.string_table part of a loop✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.markers.dynamic_schema uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarker→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.markers.dynamic_schema.MarkerFieldValueConsumer→fxprof_processed_profile.string_table.StringHandle
- Direction
- fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.markers.dynamic_schema, while a change to fxprof_processed_profile.markers.dynamic_schema can't break fxprof_processed_profile.string_table.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→26 fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.profile part of a loop✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.markers.dynamic_schema uses a type in fxprof_processed_profile.profile.
- The types involved
fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarker→fxprof_processed_profile.profile.Profile
- Direction
- fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break fxprof_processed_profile.markers.dynamic_schema, while a change to fxprof_processed_profile.markers.dynamic_schema can't break fxprof_processed_profile.profile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.category part of a loop✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.markers.dynamic_schema uses a type in fxprof_processed_profile.category.
- The types involved
fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerSchema→fxprof_processed_profile.category.CategoryHandle
- Direction
- fxprof_processed_profile.markers.dynamic_schema uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break fxprof_processed_profile.markers.dynamic_schema, while a change to fxprof_processed_profile.markers.dynamic_schema can't break fxprof_processed_profile.category.
- 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 samply.shared.timestamp_converter uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in samply.shared.timestamp_converter uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.shared.timestamp_converter.TimestampConverter→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.shared.timestamp_converter uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.shared.timestamp_converter, while a change to samply.shared.timestamp_converter can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.shared.timestamp_converter uses a module listed above it, which is the healthy direction.
12→8 samply_symbols.source_file_path uses samply_symbols.symbol_map_string_interner✕
- Connections
- 1 pair of types, where a type in samply_symbols.source_file_path uses a type in samply_symbols.symbol_map_string_interner.
- The types involved
samply_symbols.source_file_path.SourceFilePathHandle→samply_symbols.symbol_map_string_interner.SymbolMapStringHandle
- Direction
- samply_symbols.source_file_path uses samply_symbols.symbol_map_string_interner, so a change to samply_symbols.symbol_map_string_interner can break samply_symbols.source_file_path, while a change to samply_symbols.source_file_path can't break samply_symbols.symbol_map_string_interner.
- Position
- Below the diagonal: samply_symbols.source_file_path uses a module listed above it, which is the healthy direction.
13→4 etw_reader.etw_types uses etw_reader.tdh_types✕
- Connections
- 2 pairs of types, where a type in etw_reader.etw_types uses a type in etw_reader.tdh_types.
- The types involved
etw_reader.etw_types.TraceEventInfoRaw→etw_reader.tdh_types.Propertyetw_reader.etw_types.TraceEventInfoRaw→etw_reader.tdh_types.PropertyMapInfo
- Direction
- etw_reader.etw_types uses etw_reader.tdh_types, so a change to etw_reader.tdh_types can break etw_reader.etw_types, while a change to etw_reader.etw_types can't break etw_reader.tdh_types.
- Position
- Below the diagonal: etw_reader.etw_types uses a module listed above it, which is the healthy direction.
13→9 etw_reader.etw_types uses etw_reader.schema✕
- Connections
- 1 pair of types, where a type in etw_reader.etw_types uses a type in etw_reader.schema.
- The types involved
etw_reader.etw_types.TraceEventInfoRaw→etw_reader.schema.EventSchema
- Direction
- etw_reader.etw_types uses etw_reader.schema, so a change to etw_reader.schema can break etw_reader.etw_types, while a change to etw_reader.etw_types can't break etw_reader.schema.
- Position
- Below the diagonal: etw_reader.etw_types uses a module listed above it, which is the healthy direction.
14→6 fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.markers.types✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.markers.static_schema uses a type in fxprof_processed_profile.markers.types.
- The types involved
fxprof_processed_profile.markers.static_schema.MarkerGraph→fxprof_processed_profile.markers.types.GraphColorfxprof_processed_profile.markers.static_schema.MarkerGraph→fxprof_processed_profile.markers.types.MarkerGraphType
- Direction
- fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break fxprof_processed_profile.markers.static_schema, while a change to fxprof_processed_profile.markers.static_schema can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: fxprof_processed_profile.markers.static_schema uses a module listed above it, which is the healthy direction.
14→9 fxprof_processed_profile.markers.static_schema uses etw_reader.schema✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.markers.static_schema uses a type in etw_reader.schema.
- The types involved
fxprof_processed_profile.markers.static_schema.MarkerFieldsTrait→etw_reader.schema.Schemafxprof_processed_profile.markers.static_schema.Schema→etw_reader.schema.Schema
- Direction
- fxprof_processed_profile.markers.static_schema uses etw_reader.schema, so a change to etw_reader.schema can break fxprof_processed_profile.markers.static_schema, while a change to fxprof_processed_profile.markers.static_schema can't break etw_reader.schema.
- Position
- Below the diagonal: fxprof_processed_profile.markers.static_schema uses a module listed above it, which is the healthy direction.
14→10 fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.markers.dynamic_schema✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.markers.static_schema uses a type in fxprof_processed_profile.markers.dynamic_schema.
- The types involved
fxprof_processed_profile.markers.static_schema.MarkerFieldsTrait→fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerField
- Direction
- fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.markers.dynamic_schema, so a change to fxprof_processed_profile.markers.dynamic_schema can break fxprof_processed_profile.markers.static_schema, while a change to fxprof_processed_profile.markers.static_schema can't break fxprof_processed_profile.markers.dynamic_schema.
- Position
- Below the diagonal: fxprof_processed_profile.markers.static_schema uses a module listed above it, which is the healthy direction.
14→16 fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.string_table part of a loop✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.markers.static_schema uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.markers.static_schema.Marker→fxprof_processed_profile.string_table.StringHandle
- Direction
- fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.markers.static_schema, while a change to fxprof_processed_profile.markers.static_schema can't break fxprof_processed_profile.string_table.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→26 fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.profile part of a loop✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.markers.static_schema uses a type in fxprof_processed_profile.profile.
- The types involved
fxprof_processed_profile.markers.static_schema.Marker→fxprof_processed_profile.profile.Profile
- Direction
- fxprof_processed_profile.markers.static_schema uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break fxprof_processed_profile.markers.static_schema, while a change to fxprof_processed_profile.markers.static_schema can't break fxprof_processed_profile.profile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→3 samply_symbols.shared uses samply_debugid.codeid✕
- Connections
- 1 pair of types, where a type in samply_symbols.shared uses a type in samply_debugid.codeid.
- The types involved
samply_symbols.shared.LibraryInfo→samply_debugid.codeid.CodeId
- Direction
- samply_symbols.shared uses samply_debugid.codeid, so a change to samply_debugid.codeid can break samply_symbols.shared, while a change to samply_symbols.shared can't break samply_debugid.codeid.
- Position
- Below the diagonal: samply_symbols.shared uses a module listed above it, which is the healthy direction.
15→5 samply_symbols.shared uses fxprof_processed_profile.library_info✕
- Connections
- 1 pair of types, where a type in samply_symbols.shared uses a type in fxprof_processed_profile.library_info.
- The types involved
samply_symbols.shared.LibraryInfo→fxprof_processed_profile.library_info.LibraryInfo
- Direction
- samply_symbols.shared uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break samply_symbols.shared, while a change to samply_symbols.shared can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: samply_symbols.shared uses a module listed above it, which is the healthy direction.
15→8 samply_symbols.shared uses samply_symbols.symbol_map_string_interner✕
- Connections
- 2 pairs of types, where a type in samply_symbols.shared uses a type in samply_symbols.symbol_map_string_interner.
- The types involved
samply_symbols.shared.FunctionNameHandle→samply_symbols.symbol_map_string_interner.SymbolMapStringHandlesamply_symbols.shared.SymbolNameHandle→samply_symbols.symbol_map_string_interner.SymbolMapStringHandle
- Direction
- samply_symbols.shared uses samply_symbols.symbol_map_string_interner, so a change to samply_symbols.symbol_map_string_interner can break samply_symbols.shared, while a change to samply_symbols.shared can't break samply_symbols.symbol_map_string_interner.
- Position
- Below the diagonal: samply_symbols.shared uses a module listed above it, which is the healthy direction.
15→12 samply_symbols.shared uses samply_symbols.source_file_path✕
- Connections
- 1 pair of types, where a type in samply_symbols.shared uses a type in samply_symbols.source_file_path.
- The types involved
samply_symbols.shared.FrameDebugInfo→samply_symbols.source_file_path.SourceFilePathHandle
- Direction
- samply_symbols.shared uses samply_symbols.source_file_path, so a change to samply_symbols.source_file_path can break samply_symbols.shared, while a change to samply_symbols.shared can't break samply_symbols.source_file_path.
- Position
- Below the diagonal: samply_symbols.shared uses a module listed above it, which is the healthy direction.
16→1 fxprof_processed_profile.string_table uses fxprof_processed_profile.writer✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.string_table uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.string_table.ProfileStringTable→fxprof_processed_profile.writer.SplitOutObjectBodyfxprof_processed_profile.string_table.ProfileStringTable→fxprof_processed_profile.writer.Writerfxprof_processed_profile.string_table.StringHandle→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.string_table uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.string_table, while a change to fxprof_processed_profile.string_table can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.string_table uses a module listed above it, which is the healthy direction.
16→14 fxprof_processed_profile.string_table uses fxprof_processed_profile.markers.static_schema✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.string_table uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
fxprof_processed_profile.string_table.StringHandle→fxprof_processed_profile.markers.static_schema.MarkerFieldValueType
- Direction
- fxprof_processed_profile.string_table uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break fxprof_processed_profile.string_table, while a change to fxprof_processed_profile.string_table can't break fxprof_processed_profile.markers.static_schema.
- Position
- Below the diagonal: fxprof_processed_profile.string_table uses a module listed above it, which is the healthy direction.
17→12 samply_symbols.symbol_map uses samply_symbols.source_file_path✕
- Connections
- 4 pairs of types, where a type in samply_symbols.symbol_map uses a type in samply_symbols.source_file_path.
- The types involved
samply_symbols.symbol_map.SymbolMap→samply_symbols.source_file_path.SourceFilePathsamply_symbols.symbol_map.SymbolMap→samply_symbols.source_file_path.SourceFilePathHandlesamply_symbols.symbol_map.SymbolMapTrait→samply_symbols.source_file_path.SourceFilePathsamply_symbols.symbol_map.SymbolMapTrait→samply_symbols.source_file_path.SourceFilePathHandle
- Direction
- samply_symbols.symbol_map uses samply_symbols.source_file_path, so a change to samply_symbols.source_file_path can break samply_symbols.symbol_map, while a change to samply_symbols.symbol_map can't break samply_symbols.source_file_path.
- Position
- Below the diagonal: samply_symbols.symbol_map uses a module listed above it, which is the healthy direction.
17→15 samply_symbols.symbol_map uses samply_symbols.shared✕
- Connections
- 18 pairs of types, where a type in samply_symbols.symbol_map uses a type in samply_symbols.shared.
- The types involved
samply_symbols.symbol_map.LoadSymbolMap→samply_symbols.shared.FileContentsWrappersamply_symbols.symbol_map.LoadSymbolMap→samply_symbols.shared.MultiArchDisambiguatorsamply_symbols.symbol_map.LookupQuery→samply_symbols.shared.ExternalFileAddressRefsamply_symbols.symbol_map.LookupQuery→samply_symbols.shared.FramesLookupResultsamply_symbols.symbol_map.LookupQuery→samply_symbols.shared.LookupAddresssamply_symbols.symbol_map.SymbolMap→samply_symbols.shared.ExternalFileAddressRefsamply_symbols.symbol_map.SymbolMap→samply_symbols.shared.FramesLookupResultsamply_symbols.symbol_map.SymbolMap→samply_symbols.shared.FunctionNameHandlesamply_symbols.symbol_map.SymbolMap→samply_symbols.shared.LookupAddresssamply_symbols.symbol_map.SymbolMap→samply_symbols.shared.SymbolNameHandlesamply_symbols.symbol_map.SymbolMap→samply_symbols.shared.SyncAddressInfosamply_symbols.symbol_map.SymbolMapTrait→samply_symbols.shared.FunctionNameHandlesamply_symbols.symbol_map.SymbolMapTrait→samply_symbols.shared.LookupAddresssamply_symbols.symbol_map.SymbolMapTrait→samply_symbols.shared.SymbolNameHandlesamply_symbols.symbol_map.SymbolMapTrait→samply_symbols.shared.SyncAddressInfosamply_symbols.symbol_map.SymbolMapTraitWithExternalFileSupport→samply_symbols.shared.ExternalFileAddressRefsamply_symbols.symbol_map.SymbolMapTraitWithExternalFileSupport→samply_symbols.shared.FramesLookupResultsamply_symbols.symbol_map.symbol_map$module→samply_symbols.shared.FrameDebugInfo
- Direction
- samply_symbols.symbol_map uses samply_symbols.shared, so a change to samply_symbols.shared can break samply_symbols.symbol_map, while a change to samply_symbols.symbol_map can't break samply_symbols.shared.
- Position
- Below the diagonal: samply_symbols.symbol_map uses a module listed above it, which is the healthy direction.
18→3 wholesym.file_resolver uses samply_debugid.codeid✕
- Connections
- 1 pair of types, where a type in wholesym.file_resolver uses a type in samply_debugid.codeid.
- The types involved
wholesym.file_resolver.FileResolver→samply_debugid.codeid.ElfBuildId
- Direction
- wholesym.file_resolver uses samply_debugid.codeid, so a change to samply_debugid.codeid can break wholesym.file_resolver, while a change to wholesym.file_resolver can't break samply_debugid.codeid.
- Position
- Below the diagonal: wholesym.file_resolver uses a module listed above it, which is the healthy direction.
18→5 wholesym.file_resolver uses fxprof_processed_profile.library_info✕
- Connections
- 2 pairs of types, where a type in wholesym.file_resolver uses a type in fxprof_processed_profile.library_info.
- The types involved
wholesym.file_resolver.FileResolver→fxprof_processed_profile.library_info.LibraryInfowholesym.file_resolver.file_resolver$module→fxprof_processed_profile.library_info.LibraryInfo
- Direction
- wholesym.file_resolver uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break wholesym.file_resolver, while a change to wholesym.file_resolver can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: wholesym.file_resolver uses a module listed above it, which is the healthy direction.
18→15 wholesym.file_resolver uses samply_symbols.shared✕
- Connections
- 2 pairs of types, where a type in wholesym.file_resolver uses a type in samply_symbols.shared.
- The types involved
wholesym.file_resolver.WholesymFileLocation→samply_symbols.shared.FileLocationwholesym.file_resolver.WholesymFileTypes→samply_symbols.shared.FileTypes
- Direction
- wholesym.file_resolver uses samply_symbols.shared, so a change to samply_symbols.shared can break wholesym.file_resolver, while a change to wholesym.file_resolver can't break samply_symbols.shared.
- Position
- Below the diagonal: wholesym.file_resolver uses a module listed above it, which is the healthy direction.
19→1 fxprof_processed_profile.global_lib_table uses fxprof_processed_profile.writer✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.global_lib_table uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.global_lib_table.GlobalLibTable→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.global_lib_table uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.global_lib_table, while a change to fxprof_processed_profile.global_lib_table can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.global_lib_table uses a module listed above it, which is the healthy direction.
19→5 fxprof_processed_profile.global_lib_table uses fxprof_processed_profile.library_info✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.global_lib_table uses a type in fxprof_processed_profile.library_info.
- The types involved
fxprof_processed_profile.global_lib_table.GlobalLibTable→fxprof_processed_profile.library_info.LibraryInfofxprof_processed_profile.global_lib_table.GlobalLibTable→fxprof_processed_profile.library_info.SymbolTable
- Direction
- fxprof_processed_profile.global_lib_table uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break fxprof_processed_profile.global_lib_table, while a change to fxprof_processed_profile.global_lib_table can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: fxprof_processed_profile.global_lib_table uses a module listed above it, which is the healthy direction.
19→16 fxprof_processed_profile.global_lib_table uses fxprof_processed_profile.string_table✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.global_lib_table uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.global_lib_table.GlobalLibIndex→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.global_lib_table.GlobalLibTable→fxprof_processed_profile.string_table.ProfileStringTable
- Direction
- fxprof_processed_profile.global_lib_table uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.global_lib_table, while a change to fxprof_processed_profile.global_lib_table can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: fxprof_processed_profile.global_lib_table uses a module listed above it, which is the healthy direction.
20→1 fxprof_processed_profile.marker_table uses fxprof_processed_profile.writer✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.writer.Writerfxprof_processed_profile.marker_table.marker_table$module→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.marker_table uses a module listed above it, which is the healthy direction.
20→6 fxprof_processed_profile.marker_table uses fxprof_processed_profile.markers.types✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.markers.types.
- The types involved
fxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.markers.types.MarkerHandlefxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.markers.types.MarkerTimingfxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.markers.types.MarkerTypeHandle
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: fxprof_processed_profile.marker_table uses a module listed above it, which is the healthy direction.
20→7 fxprof_processed_profile.marker_table uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.timestamp.
- The types involved
fxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.timestamp.Timestamp
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: fxprof_processed_profile.marker_table uses a module listed above it, which is the healthy direction.
20→10 fxprof_processed_profile.marker_table uses fxprof_processed_profile.markers.dynamic_schema✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.markers.dynamic_schema.
- The types involved
fxprof_processed_profile.marker_table.MarkerTableFieldValueConsumer→fxprof_processed_profile.markers.dynamic_schema.MarkerFieldValueConsumer
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.markers.dynamic_schema, so a change to fxprof_processed_profile.markers.dynamic_schema can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.markers.dynamic_schema.
- Position
- Below the diagonal: fxprof_processed_profile.marker_table uses a module listed above it, which is the healthy direction.
20→16 fxprof_processed_profile.marker_table uses fxprof_processed_profile.string_table✕
- Connections
- 5 pairs of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.string_table.ProfileStringTablefxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.marker_table.MarkerTableFieldValueConsumer→fxprof_processed_profile.string_table.ProfileStringTablefxprof_processed_profile.marker_table.MarkerTableFieldValueConsumer→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.marker_table.marker_table$module→fxprof_processed_profile.string_table.ProfileStringTable
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: fxprof_processed_profile.marker_table uses a module listed above it, which is the healthy direction.
20→26 fxprof_processed_profile.marker_table uses fxprof_processed_profile.profile part of a loop✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.profile.
- The types involved
fxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.profile.StackHandlefxprof_processed_profile.marker_table.marker_table$module→fxprof_processed_profile.profile.StackHandle
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.profile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→27 fxprof_processed_profile.marker_table uses fxprof_processed_profile.category part of a loop✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.marker_table uses a type in fxprof_processed_profile.category.
- The types involved
fxprof_processed_profile.marker_table.MarkerTable→fxprof_processed_profile.category.CategoryHandle
- Direction
- fxprof_processed_profile.marker_table uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break fxprof_processed_profile.marker_table, while a change to fxprof_processed_profile.marker_table can't break fxprof_processed_profile.category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→5 samply_symbols.symbol_map_object uses fxprof_processed_profile.library_info✕
- Connections
- 2 pairs of types, where a type in samply_symbols.symbol_map_object uses a type in fxprof_processed_profile.library_info.
- The types involved
samply_symbols.symbol_map_object.SymbolList→fxprof_processed_profile.library_info.Symbolsamply_symbols.symbol_map_object.symbol_map_object$module→fxprof_processed_profile.library_info.SymbolTable
- Direction
- samply_symbols.symbol_map_object uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break samply_symbols.symbol_map_object, while a change to samply_symbols.symbol_map_object can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: samply_symbols.symbol_map_object uses a module listed above it, which is the healthy direction.
21→8 samply_symbols.symbol_map_object uses samply_symbols.symbol_map_string_interner✕
- Connections
- 2 pairs of types, where a type in samply_symbols.symbol_map_object uses a type in samply_symbols.symbol_map_string_interner.
- The types involved
samply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.symbol_map_string_interner.SymbolMapStringInternersamply_symbols.symbol_map_object.symbol_map_object$module→samply_symbols.symbol_map_string_interner.SymbolMapStringInterner
- Direction
- samply_symbols.symbol_map_object uses samply_symbols.symbol_map_string_interner, so a change to samply_symbols.symbol_map_string_interner can break samply_symbols.symbol_map_object, while a change to samply_symbols.symbol_map_object can't break samply_symbols.symbol_map_string_interner.
- Position
- Below the diagonal: samply_symbols.symbol_map_object uses a module listed above it, which is the healthy direction.
21→12 samply_symbols.symbol_map_object uses samply_symbols.source_file_path✕
- Connections
- 2 pairs of types, where a type in samply_symbols.symbol_map_object uses a type in samply_symbols.source_file_path.
- The types involved
samply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.source_file_path.SourceFilePathsamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.source_file_path.SourceFilePathHandle
- Direction
- samply_symbols.symbol_map_object uses samply_symbols.source_file_path, so a change to samply_symbols.source_file_path can break samply_symbols.symbol_map_object, while a change to samply_symbols.symbol_map_object can't break samply_symbols.source_file_path.
- Position
- Below the diagonal: samply_symbols.symbol_map_object uses a module listed above it, which is the healthy direction.
21→15 samply_symbols.symbol_map_object uses samply_symbols.shared✕
- Connections
- 6 pairs of types, where a type in samply_symbols.symbol_map_object uses a type in samply_symbols.shared.
- The types involved
samply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.shared.ExternalFileAddressRefsamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.shared.FramesLookupResultsamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.shared.FunctionNameHandlesamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.shared.LookupAddresssamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.shared.SymbolNameHandlesamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.shared.SyncAddressInfo
- Direction
- samply_symbols.symbol_map_object uses samply_symbols.shared, so a change to samply_symbols.shared can break samply_symbols.symbol_map_object, while a change to samply_symbols.symbol_map_object can't break samply_symbols.shared.
- Position
- Below the diagonal: samply_symbols.symbol_map_object uses a module listed above it, which is the healthy direction.
21→17 samply_symbols.symbol_map_object uses samply_symbols.symbol_map✕
- Connections
- 4 pairs of types, where a type in samply_symbols.symbol_map_object uses a type in samply_symbols.symbol_map.
- The types involved
samply_symbols.symbol_map_object.ObjectSymbolMap→samply_symbols.symbol_map.GetInnerSymbolMapsamply_symbols.symbol_map_object.ObjectSymbolMap→samply_symbols.symbol_map.GetInnerSymbolMapWithLookupFramesExtsamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.symbol_map.SymbolMapTraitsamply_symbols.symbol_map_object.ObjectSymbolMapInner→samply_symbols.symbol_map.SymbolMapTraitWithExternalFileSupport
- Direction
- samply_symbols.symbol_map_object uses samply_symbols.symbol_map, so a change to samply_symbols.symbol_map can break samply_symbols.symbol_map_object, while a change to samply_symbols.symbol_map_object can't break samply_symbols.symbol_map.
- Position
- Below the diagonal: samply_symbols.symbol_map_object uses a module listed above it, which is the healthy direction.
22→1 fxprof_processed_profile.frame_table uses fxprof_processed_profile.writer✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.frame_table uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.frame_table.FrameTable→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.frame_table uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.frame_table, while a change to fxprof_processed_profile.frame_table can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.frame_table uses a module listed above it, which is the healthy direction.
22→16 fxprof_processed_profile.frame_table uses fxprof_processed_profile.string_table✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.frame_table uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.frame_table.FrameTemplate→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.frame_table.InternalFrame→fxprof_processed_profile.string_table.StringHandle
- Direction
- fxprof_processed_profile.frame_table uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.frame_table, while a change to fxprof_processed_profile.frame_table can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: fxprof_processed_profile.frame_table uses a module listed above it, which is the healthy direction.
22→19 fxprof_processed_profile.frame_table uses fxprof_processed_profile.global_lib_table✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.frame_table uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
fxprof_processed_profile.frame_table.FrameInterner→fxprof_processed_profile.global_lib_table.UsedLibraryAddressesCollectorfxprof_processed_profile.frame_table.NativeFrameData→fxprof_processed_profile.global_lib_table.GlobalLibIndexfxprof_processed_profile.frame_table.NativeTemplateData→fxprof_processed_profile.global_lib_table.GlobalLibIndex
- Direction
- fxprof_processed_profile.frame_table uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break fxprof_processed_profile.frame_table, while a change to fxprof_processed_profile.frame_table can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: fxprof_processed_profile.frame_table uses a module listed above it, which is the healthy direction.
22→26 fxprof_processed_profile.frame_table uses fxprof_processed_profile.profile part of a loop✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.frame_table uses a type in fxprof_processed_profile.profile.
- The types involved
fxprof_processed_profile.frame_table.FrameInterner→fxprof_processed_profile.profile.FrameHandlefxprof_processed_profile.frame_table.FrameTemplate→fxprof_processed_profile.profile.SourceLocationfxprof_processed_profile.frame_table.InternalFrame→fxprof_processed_profile.profile.SourceLocation
- Direction
- fxprof_processed_profile.frame_table uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break fxprof_processed_profile.frame_table, while a change to fxprof_processed_profile.frame_table can't break fxprof_processed_profile.profile.
- 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→27 fxprof_processed_profile.frame_table uses fxprof_processed_profile.category part of a loop✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.frame_table uses a type in fxprof_processed_profile.category.
- The types involved
fxprof_processed_profile.frame_table.FrameTemplate→fxprof_processed_profile.category.SubcategoryHandlefxprof_processed_profile.frame_table.InternalFrame→fxprof_processed_profile.category.SubcategoryHandle
- Direction
- fxprof_processed_profile.frame_table uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break fxprof_processed_profile.frame_table, while a change to fxprof_processed_profile.frame_table can't break fxprof_processed_profile.category.
- 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→1 fxprof_processed_profile.thread uses fxprof_processed_profile.writer✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.thread uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.thread.Thread→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.thread uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.thread, while a change to fxprof_processed_profile.thread can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.thread uses a module listed above it, which is the healthy direction.
23→6 fxprof_processed_profile.thread uses fxprof_processed_profile.markers.types✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.thread uses a type in fxprof_processed_profile.markers.types.
- The types involved
fxprof_processed_profile.thread.Thread→fxprof_processed_profile.markers.types.MarkerHandlefxprof_processed_profile.thread.Thread→fxprof_processed_profile.markers.types.MarkerTimingfxprof_processed_profile.thread.Thread→fxprof_processed_profile.markers.types.MarkerTypeHandle
- Direction
- fxprof_processed_profile.thread uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break fxprof_processed_profile.thread, while a change to fxprof_processed_profile.thread can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: fxprof_processed_profile.thread uses a module listed above it, which is the healthy direction.
23→7 fxprof_processed_profile.thread uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.thread uses a type in fxprof_processed_profile.timestamp.
- The types involved
fxprof_processed_profile.thread.Thread→fxprof_processed_profile.timestamp.Timestamp
- Direction
- fxprof_processed_profile.thread uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break fxprof_processed_profile.thread, while a change to fxprof_processed_profile.thread can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: fxprof_processed_profile.thread uses a module listed above it, which is the healthy direction.
23→16 fxprof_processed_profile.thread uses fxprof_processed_profile.string_table✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.thread uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.thread.Thread→fxprof_processed_profile.string_table.ProfileStringTablefxprof_processed_profile.thread.Thread→fxprof_processed_profile.string_table.StringHandle
- Direction
- fxprof_processed_profile.thread uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.thread, while a change to fxprof_processed_profile.thread can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: fxprof_processed_profile.thread uses a module listed above it, which is the healthy direction.
23→20 fxprof_processed_profile.thread uses fxprof_processed_profile.marker_table✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.thread uses a type in fxprof_processed_profile.marker_table.
- The types involved
fxprof_processed_profile.thread.Thread→fxprof_processed_profile.marker_table.MarkerTable
- Direction
- fxprof_processed_profile.thread uses fxprof_processed_profile.marker_table, so a change to fxprof_processed_profile.marker_table can break fxprof_processed_profile.thread, while a change to fxprof_processed_profile.thread can't break fxprof_processed_profile.marker_table.
- Position
- Below the diagonal: fxprof_processed_profile.thread uses a module listed above it, which is the healthy direction.
23→26 fxprof_processed_profile.thread uses fxprof_processed_profile.profile part of a loop✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.thread uses a type in fxprof_processed_profile.profile.
- The types involved
fxprof_processed_profile.thread.Thread→fxprof_processed_profile.profile.StackHandle
- Direction
- fxprof_processed_profile.thread uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break fxprof_processed_profile.thread, while a change to fxprof_processed_profile.thread can't break fxprof_processed_profile.profile.
- 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.
24→7 fxprof_processed_profile.process uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.process uses a type in fxprof_processed_profile.timestamp.
- The types involved
fxprof_processed_profile.process.Process→fxprof_processed_profile.timestamp.Timestamp
- Direction
- fxprof_processed_profile.process uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break fxprof_processed_profile.process, while a change to fxprof_processed_profile.process can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: fxprof_processed_profile.process uses a module listed above it, which is the healthy direction.
24→16 fxprof_processed_profile.process uses fxprof_processed_profile.string_table✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.process uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.process.Process→fxprof_processed_profile.string_table.ProfileStringTable
- Direction
- fxprof_processed_profile.process uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.process, while a change to fxprof_processed_profile.process can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: fxprof_processed_profile.process uses a module listed above it, which is the healthy direction.
24→19 fxprof_processed_profile.process uses fxprof_processed_profile.global_lib_table✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.process uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
fxprof_processed_profile.process.Process→fxprof_processed_profile.global_lib_table.GlobalLibTablefxprof_processed_profile.process.Process→fxprof_processed_profile.global_lib_table.LibraryHandle
- Direction
- fxprof_processed_profile.process uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break fxprof_processed_profile.process, while a change to fxprof_processed_profile.process can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: fxprof_processed_profile.process uses a module listed above it, which is the healthy direction.
24→22 fxprof_processed_profile.process uses fxprof_processed_profile.frame_table✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.process uses a type in fxprof_processed_profile.frame_table.
- The types involved
fxprof_processed_profile.process.Process→fxprof_processed_profile.frame_table.InternalFrameAddress
- Direction
- fxprof_processed_profile.process uses fxprof_processed_profile.frame_table, so a change to fxprof_processed_profile.frame_table can break fxprof_processed_profile.process, while a change to fxprof_processed_profile.process can't break fxprof_processed_profile.frame_table.
- Position
- Below the diagonal: fxprof_processed_profile.process uses a module listed above it, which is the healthy direction.
25→3 gecko_profile uses samply_debugid.codeid✕
- Connections
- 2 pairs of types, where a type in gecko_profile uses a type in samply_debugid.codeid.
- The types involved
gecko_profile.Lib→samply_debugid.codeid.CodeIdgecko_profile.ProfileBuilder→samply_debugid.codeid.CodeId
- Direction
- gecko_profile uses samply_debugid.codeid, so a change to samply_debugid.codeid can break gecko_profile, while a change to gecko_profile can't break samply_debugid.codeid.
- Position
- Below the diagonal: gecko_profile uses a module listed above it, which is the healthy direction.
25→6 gecko_profile uses fxprof_processed_profile.markers.types✕
- Connections
- 2 pairs of types, where a type in gecko_profile uses a type in fxprof_processed_profile.markers.types.
- The types involved
gecko_profile.Marker→fxprof_processed_profile.markers.types.MarkerTiminggecko_profile.ThreadBuilder→fxprof_processed_profile.markers.types.MarkerTiming
- Direction
- gecko_profile uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break gecko_profile, while a change to gecko_profile can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: gecko_profile uses a module listed above it, which is the healthy direction.
25→14 gecko_profile uses fxprof_processed_profile.markers.static_schema✕
- Connections
- 1 pair of types, where a type in gecko_profile uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
gecko_profile.MarkerTable→fxprof_processed_profile.markers.static_schema.Marker
- Direction
- gecko_profile uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break gecko_profile, while a change to gecko_profile can't break fxprof_processed_profile.markers.static_schema.
- Position
- Below the diagonal: gecko_profile uses a module listed above it, which is the healthy direction.
25→16 gecko_profile uses fxprof_processed_profile.string_table✕
- Connections
- 8 pairs of types, where a type in gecko_profile uses a type in fxprof_processed_profile.string_table.
- The types involved
gecko_profile.FrameTable→fxprof_processed_profile.string_table.StringIndexgecko_profile.FrameTable→fxprof_processed_profile.string_table.StringTablegecko_profile.Marker→fxprof_processed_profile.string_table.StringIndexgecko_profile.SerializableFrameTableDataValue→fxprof_processed_profile.string_table.StringIndexgecko_profile.SerializableMarkerTableDataValue→fxprof_processed_profile.string_table.StringIndexgecko_profile.StringTable→fxprof_processed_profile.string_table.StringIndexgecko_profile.ThreadBuilder→fxprof_processed_profile.string_table.StringIndexgecko_profile.ThreadBuilder→fxprof_processed_profile.string_table.StringTable
- Direction
- gecko_profile uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break gecko_profile, while a change to gecko_profile can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: gecko_profile uses a module listed above it, which is the healthy direction.
25→20 gecko_profile uses fxprof_processed_profile.marker_table✕
- Connections
- 3 pairs of types, where a type in gecko_profile uses a type in fxprof_processed_profile.marker_table.
- The types involved
gecko_profile.SerializableMarkerTable→fxprof_processed_profile.marker_table.MarkerTablegecko_profile.SerializableMarkerTableData→fxprof_processed_profile.marker_table.MarkerTablegecko_profile.ThreadBuilder→fxprof_processed_profile.marker_table.MarkerTable
- Direction
- gecko_profile uses fxprof_processed_profile.marker_table, so a change to fxprof_processed_profile.marker_table can break gecko_profile, while a change to gecko_profile can't break fxprof_processed_profile.marker_table.
- Position
- Below the diagonal: gecko_profile uses a module listed above it, which is the healthy direction.
25→22 gecko_profile uses fxprof_processed_profile.frame_table✕
- Connections
- 3 pairs of types, where a type in gecko_profile uses a type in fxprof_processed_profile.frame_table.
- The types involved
gecko_profile.FrameTable→fxprof_processed_profile.frame_table.FrameTablegecko_profile.SerializableFrameTableData→fxprof_processed_profile.frame_table.FrameTablegecko_profile.ThreadBuilder→fxprof_processed_profile.frame_table.FrameTable
- Direction
- gecko_profile uses fxprof_processed_profile.frame_table, so a change to fxprof_processed_profile.frame_table can break gecko_profile, while a change to gecko_profile can't break fxprof_processed_profile.frame_table.
- Position
- Below the diagonal: gecko_profile uses a module listed above it, which is the healthy direction.
26→1 fxprof_processed_profile.profile uses fxprof_processed_profile.writer✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.writer.Writerfxprof_processed_profile.profile.ThreadsArrayBody→fxprof_processed_profile.writer.SplitOutObjectBodyfxprof_processed_profile.profile.ThreadsArrayBody→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→5 fxprof_processed_profile.profile uses fxprof_processed_profile.library_info✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.library_info.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.library_info.LibraryInfofxprof_processed_profile.profile.Profile→fxprof_processed_profile.library_info.SymbolTable
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→6 fxprof_processed_profile.profile uses fxprof_processed_profile.markers.types✕
- Connections
- 4 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.markers.types.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.markers.types.GraphColorfxprof_processed_profile.profile.Profile→fxprof_processed_profile.markers.types.MarkerHandlefxprof_processed_profile.profile.Profile→fxprof_processed_profile.markers.types.MarkerTimingfxprof_processed_profile.profile.Profile→fxprof_processed_profile.markers.types.MarkerTypeHandle
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→7 fxprof_processed_profile.profile uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.timestamp.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.timestamp.Timestamp
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→10 fxprof_processed_profile.profile uses fxprof_processed_profile.markers.dynamic_schema✕
- Connections
- 1 pair of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.markers.dynamic_schema.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.markers.dynamic_schema.DynamicSchemaMarkerSchema
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.markers.dynamic_schema, so a change to fxprof_processed_profile.markers.dynamic_schema can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.markers.dynamic_schema.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→16 fxprof_processed_profile.profile uses fxprof_processed_profile.string_table✕
- Connections
- 4 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.string_table.
- The types involved
fxprof_processed_profile.profile.FrameSymbolInfo→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.profile.Profile→fxprof_processed_profile.string_table.ProfileStringTablefxprof_processed_profile.profile.Profile→fxprof_processed_profile.string_table.StringHandlefxprof_processed_profile.profile.SourceLocation→fxprof_processed_profile.string_table.StringHandle
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→19 fxprof_processed_profile.profile uses fxprof_processed_profile.global_lib_table✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.global_lib_table.GlobalLibTablefxprof_processed_profile.profile.Profile→fxprof_processed_profile.global_lib_table.LibraryHandle
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→22 fxprof_processed_profile.profile uses fxprof_processed_profile.frame_table✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.frame_table.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.frame_table.FrameInternerTablesfxprof_processed_profile.profile.Profile→fxprof_processed_profile.frame_table.InternalFrameAddress
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.frame_table, so a change to fxprof_processed_profile.frame_table can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.frame_table.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→23 fxprof_processed_profile.profile uses fxprof_processed_profile.thread✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.thread.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.thread.ProcessHandlefxprof_processed_profile.profile.Profile→fxprof_processed_profile.thread.Thread
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.thread, so a change to fxprof_processed_profile.thread can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.thread.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→24 fxprof_processed_profile.profile uses fxprof_processed_profile.process✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.process.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.process.Processfxprof_processed_profile.profile.Profile→fxprof_processed_profile.process.ThreadHandle
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: fxprof_processed_profile.profile uses a module listed above it, which is the healthy direction.
26→27 fxprof_processed_profile.profile uses fxprof_processed_profile.category part of a loop✕
- Connections
- 3 pairs of types, where a type in fxprof_processed_profile.profile uses a type in fxprof_processed_profile.category.
- The types involved
fxprof_processed_profile.profile.Profile→fxprof_processed_profile.category.Categoryfxprof_processed_profile.profile.Profile→fxprof_processed_profile.category.CategoryHandlefxprof_processed_profile.profile.Profile→fxprof_processed_profile.category.SubcategoryHandle
- Direction
- fxprof_processed_profile.profile uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break fxprof_processed_profile.profile, while a change to fxprof_processed_profile.profile can't break fxprof_processed_profile.category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→1 fxprof_processed_profile.category uses fxprof_processed_profile.writer✕
- Connections
- 2 pairs of types, where a type in fxprof_processed_profile.category uses a type in fxprof_processed_profile.writer.
- The types involved
fxprof_processed_profile.category.CategoryHandle→fxprof_processed_profile.writer.Writerfxprof_processed_profile.category.InternalCategory→fxprof_processed_profile.writer.Writer
- Direction
- fxprof_processed_profile.category uses fxprof_processed_profile.writer, so a change to fxprof_processed_profile.writer can break fxprof_processed_profile.category, while a change to fxprof_processed_profile.category can't break fxprof_processed_profile.writer.
- Position
- Below the diagonal: fxprof_processed_profile.category uses a module listed above it, which is the healthy direction.
27→26 fxprof_processed_profile.category uses fxprof_processed_profile.profile✕
- Connections
- 5 pairs of types, where a type in fxprof_processed_profile.category uses a type in fxprof_processed_profile.profile.
- The types involved
fxprof_processed_profile.category.Category→fxprof_processed_profile.profile.Profilefxprof_processed_profile.category.CategoryHandle→fxprof_processed_profile.profile.Profilefxprof_processed_profile.category.IntoSubcategoryHandle→fxprof_processed_profile.profile.Profilefxprof_processed_profile.category.Subcategory→fxprof_processed_profile.profile.Profilefxprof_processed_profile.category.SubcategoryHandle→fxprof_processed_profile.profile.Profile
- Direction
- fxprof_processed_profile.category uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break fxprof_processed_profile.category, while a change to fxprof_processed_profile.category can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: fxprof_processed_profile.category uses a module listed above it, which is the healthy direction.
28→2 samply.import.perf uses samply.shared.prop_types✕
- Connections
- 1 pair of types, where a type in samply.import.perf uses a type in samply.shared.prop_types.
- The types involved
samply.import.perf.perf$module→samply.shared.prop_types.ProfileCreationProps
- Direction
- samply.import.perf uses samply.shared.prop_types, so a change to samply.shared.prop_types can break samply.import.perf, while a change to samply.import.perf can't break samply.shared.prop_types.
- Position
- Below the diagonal: samply.import.perf uses a module listed above it, which is the healthy direction.
28→26 samply.import.perf uses fxprof_processed_profile.profile✕
- Connections
- 1 pair of types, where a type in samply.import.perf uses a type in fxprof_processed_profile.profile.
- The types involved
samply.import.perf.perf$module→fxprof_processed_profile.profile.Profile
- Direction
- samply.import.perf uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.import.perf, while a change to samply.import.perf can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.import.perf uses a module listed above it, which is the healthy direction.
29→7 samply.shared.per_cpu uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in samply.shared.per_cpu uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.shared.per_cpu.Cpus→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.shared.per_cpu uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
29→11 samply.shared.per_cpu uses samply.shared.timestamp_converter✕
- Connections
- 1 pair of types, where a type in samply.shared.per_cpu uses a type in samply.shared.timestamp_converter.
- The types involved
samply.shared.per_cpu.Cpu→samply.shared.timestamp_converter.TimestampConverter
- Direction
- samply.shared.per_cpu uses samply.shared.timestamp_converter, so a change to samply.shared.timestamp_converter can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break samply.shared.timestamp_converter.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
29→14 samply.shared.per_cpu uses fxprof_processed_profile.markers.static_schema✕
- Connections
- 2 pairs of types, where a type in samply.shared.per_cpu uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
samply.shared.per_cpu.OnCpuMarkerForThreadTrack→fxprof_processed_profile.markers.static_schema.Markersamply.shared.per_cpu.ThreadNameMarkerForCpuTrack→fxprof_processed_profile.markers.static_schema.Marker
- Direction
- samply.shared.per_cpu uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break fxprof_processed_profile.markers.static_schema.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
29→16 samply.shared.per_cpu uses fxprof_processed_profile.string_table✕
- Connections
- 3 pairs of types, where a type in samply.shared.per_cpu uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.shared.per_cpu.Cpu→fxprof_processed_profile.string_table.StringHandlesamply.shared.per_cpu.OnCpuMarkerForThreadTrack→fxprof_processed_profile.string_table.StringHandlesamply.shared.per_cpu.ThreadNameMarkerForCpuTrack→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.shared.per_cpu uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
29→23 samply.shared.per_cpu uses fxprof_processed_profile.thread✕
- Connections
- 1 pair of types, where a type in samply.shared.per_cpu uses a type in fxprof_processed_profile.thread.
- The types involved
samply.shared.per_cpu.Cpus→fxprof_processed_profile.thread.ProcessHandle
- Direction
- samply.shared.per_cpu uses fxprof_processed_profile.thread, so a change to fxprof_processed_profile.thread can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break fxprof_processed_profile.thread.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
29→24 samply.shared.per_cpu uses fxprof_processed_profile.process✕
- Connections
- 2 pairs of types, where a type in samply.shared.per_cpu uses a type in fxprof_processed_profile.process.
- The types involved
samply.shared.per_cpu.Cpu→fxprof_processed_profile.process.ThreadHandlesamply.shared.per_cpu.Cpus→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.shared.per_cpu uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
29→26 samply.shared.per_cpu uses fxprof_processed_profile.profile✕
- Connections
- 5 pairs of types, where a type in samply.shared.per_cpu uses a type in fxprof_processed_profile.profile.
- The types involved
samply.shared.per_cpu.Cpu→fxprof_processed_profile.profile.FrameHandlesamply.shared.per_cpu.Cpu→fxprof_processed_profile.profile.Profilesamply.shared.per_cpu.Cpus→fxprof_processed_profile.profile.Profilesamply.shared.per_cpu.OnCpuMarkerForThreadTrack→fxprof_processed_profile.profile.Profilesamply.shared.per_cpu.ThreadNameMarkerForCpuTrack→fxprof_processed_profile.profile.Profile
- Direction
- samply.shared.per_cpu uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.shared.per_cpu, while a change to samply.shared.per_cpu can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.shared.per_cpu uses a module listed above it, which is the healthy direction.
30→6 samply.shared.unresolved_samples uses fxprof_processed_profile.markers.types✕
- Connections
- 1 pair of types, where a type in samply.shared.unresolved_samples uses a type in fxprof_processed_profile.markers.types.
- The types involved
samply.shared.unresolved_samples.UnresolvedSamples→fxprof_processed_profile.markers.types.MarkerHandle
- Direction
- samply.shared.unresolved_samples uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break samply.shared.unresolved_samples, while a change to samply.shared.unresolved_samples can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: samply.shared.unresolved_samples uses a module listed above it, which is the healthy direction.
30→7 samply.shared.unresolved_samples uses fxprof_processed_profile.timestamp✕
- Connections
- 2 pairs of types, where a type in samply.shared.unresolved_samples uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.shared.unresolved_samples.UnresolvedSampleOrMarker→fxprof_processed_profile.timestamp.Timestampsamply.shared.unresolved_samples.UnresolvedSamples→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.shared.unresolved_samples uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.shared.unresolved_samples, while a change to samply.shared.unresolved_samples can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.shared.unresolved_samples uses a module listed above it, which is the healthy direction.
30→24 samply.shared.unresolved_samples uses fxprof_processed_profile.process✕
- Connections
- 2 pairs of types, where a type in samply.shared.unresolved_samples uses a type in fxprof_processed_profile.process.
- The types involved
samply.shared.unresolved_samples.UnresolvedSampleOrMarker→fxprof_processed_profile.process.ThreadHandlesamply.shared.unresolved_samples.UnresolvedSamples→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.shared.unresolved_samples uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.shared.unresolved_samples, while a change to samply.shared.unresolved_samples can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.shared.unresolved_samples uses a module listed above it, which is the healthy direction.
30→26 samply.shared.unresolved_samples uses fxprof_processed_profile.profile✕
- Connections
- 2 pairs of types, where a type in samply.shared.unresolved_samples uses a type in fxprof_processed_profile.profile.
- The types involved
samply.shared.unresolved_samples.UnresolvedSampleOrMarker→fxprof_processed_profile.profile.FrameHandlesamply.shared.unresolved_samples.UnresolvedSamples→fxprof_processed_profile.profile.FrameHandle
- Direction
- samply.shared.unresolved_samples uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.shared.unresolved_samples, while a change to samply.shared.unresolved_samples can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.shared.unresolved_samples uses a module listed above it, which is the healthy direction.
31→26 samply.shared.jit_category_manager uses fxprof_processed_profile.profile✕
- Connections
- 4 pairs of types, where a type in samply.shared.jit_category_manager uses a type in fxprof_processed_profile.profile.
- The types involved
samply.shared.jit_category_manager.JitCategoryManager→fxprof_processed_profile.profile.Profilesamply.shared.jit_category_manager.JsScriptSource→fxprof_processed_profile.profile.Profilesamply.shared.jit_category_manager.JsScriptSource→fxprof_processed_profile.profile.SourceLocationsamply.shared.jit_category_manager.LazilyCreatedCategory→fxprof_processed_profile.profile.Profile
- Direction
- samply.shared.jit_category_manager uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.shared.jit_category_manager, while a change to samply.shared.jit_category_manager can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.shared.jit_category_manager uses a module listed above it, which is the healthy direction.
31→27 samply.shared.jit_category_manager uses fxprof_processed_profile.category✕
- Connections
- 3 pairs of types, where a type in samply.shared.jit_category_manager uses a type in fxprof_processed_profile.category.
- The types involved
samply.shared.jit_category_manager.JitCategoryManager→fxprof_processed_profile.category.CategoryHandlesamply.shared.jit_category_manager.LazilyCreatedCategory→fxprof_processed_profile.category.Categorysamply.shared.jit_category_manager.LazilyCreatedCategory→fxprof_processed_profile.category.CategoryHandle
- Direction
- samply.shared.jit_category_manager uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break samply.shared.jit_category_manager, while a change to samply.shared.jit_category_manager can't break fxprof_processed_profile.category.
- Position
- Below the diagonal: samply.shared.jit_category_manager uses a module listed above it, which is the healthy direction.
32→28 samply_api uses samply.import.perf✕
- Connections
- 1 pair of types, where a type in samply_api uses a type in samply.import.perf.
- The types involved
samply_api.QueryApiJsonResult→samply.import.perf.Error
- Direction
- samply_api uses samply.import.perf, so a change to samply.import.perf can break samply_api, while a change to samply_api can't break samply.import.perf.
- Position
- Below the diagonal: samply_api uses a module listed above it, which is the healthy direction.
33→16 samply.shared.lib_mappings uses fxprof_processed_profile.string_table✕
- Connections
- 1 pair of types, where a type in samply.shared.lib_mappings uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.shared.lib_mappings.JitSymbolInfo→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.shared.lib_mappings uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.shared.lib_mappings, while a change to samply.shared.lib_mappings can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.shared.lib_mappings uses a module listed above it, which is the healthy direction.
33→19 samply.shared.lib_mappings uses fxprof_processed_profile.global_lib_table✕
- Connections
- 2 pairs of types, where a type in samply.shared.lib_mappings uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
samply.shared.lib_mappings.JitSymbolInfo→fxprof_processed_profile.global_lib_table.LibraryHandlesamply.shared.lib_mappings.LibMappingInfo→fxprof_processed_profile.global_lib_table.LibraryHandle
- Direction
- samply.shared.lib_mappings uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break samply.shared.lib_mappings, while a change to samply.shared.lib_mappings can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: samply.shared.lib_mappings uses a module listed above it, which is the healthy direction.
33→26 samply.shared.lib_mappings uses fxprof_processed_profile.profile✕
- Connections
- 1 pair of types, where a type in samply.shared.lib_mappings uses a type in fxprof_processed_profile.profile.
- The types involved
samply.shared.lib_mappings.JitSymbolInfo→fxprof_processed_profile.profile.SourceLocation
- Direction
- samply.shared.lib_mappings uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.shared.lib_mappings, while a change to samply.shared.lib_mappings can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.shared.lib_mappings uses a module listed above it, which is the healthy direction.
33→27 samply.shared.lib_mappings uses fxprof_processed_profile.category✕
- Connections
- 1 pair of types, where a type in samply.shared.lib_mappings uses a type in fxprof_processed_profile.category.
- The types involved
samply.shared.lib_mappings.LibMappingInfo→fxprof_processed_profile.category.SubcategoryHandle
- Direction
- samply.shared.lib_mappings uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break samply.shared.lib_mappings, while a change to samply.shared.lib_mappings can't break fxprof_processed_profile.category.
- Position
- Below the diagonal: samply.shared.lib_mappings uses a module listed above it, which is the healthy direction.
33→31 samply.shared.lib_mappings uses samply.shared.jit_category_manager✕
- Connections
- 1 pair of types, where a type in samply.shared.lib_mappings uses a type in samply.shared.jit_category_manager.
- The types involved
samply.shared.lib_mappings.LibMappingInfo→samply.shared.jit_category_manager.JsFrame
- Direction
- samply.shared.lib_mappings uses samply.shared.jit_category_manager, so a change to samply.shared.jit_category_manager can break samply.shared.lib_mappings, while a change to samply.shared.lib_mappings can't break samply.shared.jit_category_manager.
- Position
- Below the diagonal: samply.shared.lib_mappings uses a module listed above it, which is the healthy direction.
34→5 wholesym.symbol_manager uses fxprof_processed_profile.library_info✕
- Connections
- 1 pair of types, where a type in wholesym.symbol_manager uses a type in fxprof_processed_profile.library_info.
- The types involved
wholesym.symbol_manager.SymbolManager→fxprof_processed_profile.library_info.LibraryInfo
- Direction
- wholesym.symbol_manager uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
34→8 wholesym.symbol_manager uses samply_symbols.symbol_map_string_interner✕
- Connections
- 1 pair of types, where a type in wholesym.symbol_manager uses a type in samply_symbols.symbol_map_string_interner.
- The types involved
wholesym.symbol_manager.ExternalFileSymbolMap→samply_symbols.symbol_map_string_interner.SymbolMapStringInterner
- Direction
- wholesym.symbol_manager uses samply_symbols.symbol_map_string_interner, so a change to samply_symbols.symbol_map_string_interner can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break samply_symbols.symbol_map_string_interner.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
34→12 wholesym.symbol_manager uses samply_symbols.source_file_path✕
- Connections
- 2 pairs of types, where a type in wholesym.symbol_manager uses a type in samply_symbols.source_file_path.
- The types involved
wholesym.symbol_manager.SymbolMap→samply_symbols.source_file_path.SourceFilePathwholesym.symbol_manager.SymbolMap→samply_symbols.source_file_path.SourceFilePathHandle
- Direction
- wholesym.symbol_manager uses samply_symbols.source_file_path, so a change to samply_symbols.source_file_path can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break samply_symbols.source_file_path.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
34→15 wholesym.symbol_manager uses samply_symbols.shared✕
- Connections
- 10 pairs of types, where a type in wholesym.symbol_manager uses a type in samply_symbols.shared.
- The types involved
wholesym.symbol_manager.ExternalFileSymbolMap→samply_symbols.shared.ExternalFileAddressInFileRefwholesym.symbol_manager.ExternalFileSymbolMap→samply_symbols.shared.FrameDebugInfowholesym.symbol_manager.SymbolManager→samply_symbols.shared.MultiArchDisambiguatorwholesym.symbol_manager.SymbolMap→samply_symbols.shared.ExternalFileAddressRefwholesym.symbol_manager.SymbolMap→samply_symbols.shared.FrameDebugInfowholesym.symbol_manager.SymbolMap→samply_symbols.shared.FunctionNameHandlewholesym.symbol_manager.SymbolMap→samply_symbols.shared.LookupAddresswholesym.symbol_manager.SymbolMap→samply_symbols.shared.SymbolNameHandlewholesym.symbol_manager.SymbolMap→samply_symbols.shared.SyncAddressInfowholesym.symbol_manager.symbol_manager$module→samply_symbols.shared.MultiArchDisambiguator
- Direction
- wholesym.symbol_manager uses samply_symbols.shared, so a change to samply_symbols.shared can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break samply_symbols.shared.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
34→17 wholesym.symbol_manager uses samply_symbols.symbol_map✕
- Connections
- 2 pairs of types, where a type in wholesym.symbol_manager uses a type in samply_symbols.symbol_map.
- The types involved
wholesym.symbol_manager.SymbolMap→samply_symbols.symbol_map.AccessPatternHintwholesym.symbol_manager.SymbolMap→samply_symbols.symbol_map.SymbolMap
- Direction
- wholesym.symbol_manager uses samply_symbols.symbol_map, so a change to samply_symbols.symbol_map can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break samply_symbols.symbol_map.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
34→18 wholesym.symbol_manager uses wholesym.file_resolver✕
- Connections
- 4 pairs of types, where a type in wholesym.symbol_manager uses a type in wholesym.file_resolver.
- The types involved
wholesym.symbol_manager.SymbolFileOrigin→wholesym.file_resolver.WholesymFileLocationwholesym.symbol_manager.SymbolManager→wholesym.file_resolver.FileResolverwholesym.symbol_manager.SymbolMap→wholesym.file_resolver.FileResolverwholesym.symbol_manager.symbol_manager$module→wholesym.file_resolver.LocalFileFetcher
- Direction
- wholesym.symbol_manager uses wholesym.file_resolver, so a change to wholesym.file_resolver can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break wholesym.file_resolver.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
34→32 wholesym.symbol_manager uses samply_api✕
- Connections
- 3 pairs of types, where a type in wholesym.symbol_manager uses a type in samply_api.
- The types involved
wholesym.symbol_manager.QueryApiJsonResult→samply_api.QueryApiJsonResultwholesym.symbol_manager.QueryApiJsonResult→samply_api.SymbolicateStatswholesym.symbol_manager.SymbolManager→samply_api.QueryApiJsonResult
- Direction
- wholesym.symbol_manager uses samply_api, so a change to samply_api can break wholesym.symbol_manager, while a change to wholesym.symbol_manager can't break samply_api.
- Position
- Below the diagonal: wholesym.symbol_manager uses a module listed above it, which is the healthy direction.
35→2 samply.linux_shared.converter uses samply.shared.prop_types✕
- Connections
- 2 pairs of types, where a type in samply.linux_shared.converter uses a type in samply.shared.prop_types.
- The types involved
samply.linux_shared.converter.Converter→samply.shared.prop_types.ProfileCreationPropssamply.linux_shared.converter.SimpleperfConverterData→samply.shared.prop_types.ProfileCreationProps
- Direction
- samply.linux_shared.converter uses samply.shared.prop_types, so a change to samply.shared.prop_types can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply.shared.prop_types.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→3 samply.linux_shared.converter uses samply_debugid.codeid✕
- Connections
- 2 pairs of types, where a type in samply.linux_shared.converter uses a type in samply_debugid.codeid.
- The types involved
samply.linux_shared.converter.Converter→samply_debugid.codeid.CodeIdsamply.linux_shared.converter.MappingInfo→samply_debugid.codeid.CodeId
- Direction
- samply.linux_shared.converter uses samply_debugid.codeid, so a change to samply_debugid.codeid can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply_debugid.codeid.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→5 samply.linux_shared.converter uses fxprof_processed_profile.library_info✕
- Connections
- 2 pairs of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.library_info.
- The types involved
samply.linux_shared.converter.Converter→fxprof_processed_profile.library_info.LibraryInfosamply.linux_shared.converter.SymbolTableFromSimpleperf→fxprof_processed_profile.library_info.SymbolTable
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→11 samply.linux_shared.converter uses samply.shared.timestamp_converter✕
- Connections
- 2 pairs of types, where a type in samply.linux_shared.converter uses a type in samply.shared.timestamp_converter.
- The types involved
samply.linux_shared.converter.Converter→samply.shared.timestamp_converter.TimestampConvertersamply.linux_shared.converter.converter$module→samply.shared.timestamp_converter.TimestampConverter
- Direction
- samply.linux_shared.converter uses samply.shared.timestamp_converter, so a change to samply.shared.timestamp_converter can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply.shared.timestamp_converter.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→14 samply.linux_shared.converter uses fxprof_processed_profile.markers.static_schema✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
samply.linux_shared.converter.MmapMarker→fxprof_processed_profile.markers.static_schema.Marker
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.markers.static_schema.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→16 samply.linux_shared.converter uses fxprof_processed_profile.string_table✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.linux_shared.converter.MmapMarker→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→19 samply.linux_shared.converter uses fxprof_processed_profile.global_lib_table✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
samply.linux_shared.converter.KernelImageMapping→fxprof_processed_profile.global_lib_table.LibraryHandle
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→24 samply.linux_shared.converter uses fxprof_processed_profile.process✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.process.
- The types involved
samply.linux_shared.converter.converter$module→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→26 samply.linux_shared.converter uses fxprof_processed_profile.profile✕
- Connections
- 4 pairs of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.profile.
- The types involved
samply.linux_shared.converter.Converter→fxprof_processed_profile.profile.Profilesamply.linux_shared.converter.MmapMarker→fxprof_processed_profile.profile.Profilesamply.linux_shared.converter.SimpleperfConverterData→fxprof_processed_profile.profile.Profilesamply.linux_shared.converter.SimpleperfSymbolTables→fxprof_processed_profile.profile.Profile
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→27 samply.linux_shared.converter uses fxprof_processed_profile.category✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in fxprof_processed_profile.category.
- The types involved
samply.linux_shared.converter.SymbolTableFromSimpleperf→fxprof_processed_profile.category.SubcategoryHandle
- Direction
- samply.linux_shared.converter uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break fxprof_processed_profile.category.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→29 samply.linux_shared.converter uses samply.shared.per_cpu✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in samply.shared.per_cpu.
- The types involved
samply.linux_shared.converter.Converter→samply.shared.per_cpu.Cpus
- Direction
- samply.linux_shared.converter uses samply.shared.per_cpu, so a change to samply.shared.per_cpu can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply.shared.per_cpu.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→30 samply.linux_shared.converter uses samply.shared.unresolved_samples✕
- Connections
- 3 pairs of types, where a type in samply.linux_shared.converter uses a type in samply.shared.unresolved_samples.
- The types involved
samply.linux_shared.converter.Converter→samply.shared.unresolved_samples.UnresolvedStackssamply.linux_shared.converter.converter$module→samply.shared.unresolved_samples.UnresolvedSamplessamply.linux_shared.converter.converter$module→samply.shared.unresolved_samples.UnresolvedStackHandle
- Direction
- samply.linux_shared.converter uses samply.shared.unresolved_samples, so a change to samply.shared.unresolved_samples can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply.shared.unresolved_samples.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→31 samply.linux_shared.converter uses samply.shared.jit_category_manager✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in samply.shared.jit_category_manager.
- The types involved
samply.linux_shared.converter.Converter→samply.shared.jit_category_manager.JitCategoryManager
- Direction
- samply.linux_shared.converter uses samply.shared.jit_category_manager, so a change to samply.shared.jit_category_manager can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply.shared.jit_category_manager.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
35→33 samply.linux_shared.converter uses samply.shared.lib_mappings✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.converter uses a type in samply.shared.lib_mappings.
- The types involved
samply.linux_shared.converter.SymbolTableFromSimpleperf→samply.shared.lib_mappings.AndroidArtInfo
- Direction
- samply.linux_shared.converter uses samply.shared.lib_mappings, so a change to samply.shared.lib_mappings can break samply.linux_shared.converter, while a change to samply.linux_shared.converter can't break samply.shared.lib_mappings.
- Position
- Below the diagonal: samply.linux_shared.converter uses a module listed above it, which is the healthy direction.
36→5 samply.shared.jitdump_manager uses fxprof_processed_profile.library_info✕
- Connections
- 1 pair of types, where a type in samply.shared.jitdump_manager uses a type in fxprof_processed_profile.library_info.
- The types involved
samply.shared.jitdump_manager.SingleJitDumpProcessor→fxprof_processed_profile.library_info.Symbol
- Direction
- samply.shared.jitdump_manager uses fxprof_processed_profile.library_info, so a change to fxprof_processed_profile.library_info can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break fxprof_processed_profile.library_info.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
36→11 samply.shared.jitdump_manager uses samply.shared.timestamp_converter✕
- Connections
- 2 pairs of types, where a type in samply.shared.jitdump_manager uses a type in samply.shared.timestamp_converter.
- The types involved
samply.shared.jitdump_manager.JitDumpManager→samply.shared.timestamp_converter.TimestampConvertersamply.shared.jitdump_manager.SingleJitDumpProcessor→samply.shared.timestamp_converter.TimestampConverter
- Direction
- samply.shared.jitdump_manager uses samply.shared.timestamp_converter, so a change to samply.shared.timestamp_converter can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break samply.shared.timestamp_converter.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
36→19 samply.shared.jitdump_manager uses fxprof_processed_profile.global_lib_table✕
- Connections
- 1 pair of types, where a type in samply.shared.jitdump_manager uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
samply.shared.jitdump_manager.SingleJitDumpProcessor→fxprof_processed_profile.global_lib_table.LibraryHandle
- Direction
- samply.shared.jitdump_manager uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
36→24 samply.shared.jitdump_manager uses fxprof_processed_profile.process✕
- Connections
- 2 pairs of types, where a type in samply.shared.jitdump_manager uses a type in fxprof_processed_profile.process.
- The types involved
samply.shared.jitdump_manager.JitDumpManager→fxprof_processed_profile.process.ThreadHandlesamply.shared.jitdump_manager.SingleJitDumpProcessor→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.shared.jitdump_manager uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
36→26 samply.shared.jitdump_manager uses fxprof_processed_profile.profile✕
- Connections
- 2 pairs of types, where a type in samply.shared.jitdump_manager uses a type in fxprof_processed_profile.profile.
- The types involved
samply.shared.jitdump_manager.JitDumpManager→fxprof_processed_profile.profile.Profilesamply.shared.jitdump_manager.SingleJitDumpProcessor→fxprof_processed_profile.profile.Profile
- Direction
- samply.shared.jitdump_manager uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
36→31 samply.shared.jitdump_manager uses samply.shared.jit_category_manager✕
- Connections
- 2 pairs of types, where a type in samply.shared.jitdump_manager uses a type in samply.shared.jit_category_manager.
- The types involved
samply.shared.jitdump_manager.JitDumpManager→samply.shared.jit_category_manager.JitCategoryManagersamply.shared.jitdump_manager.SingleJitDumpProcessor→samply.shared.jit_category_manager.JitCategoryManager
- Direction
- samply.shared.jitdump_manager uses samply.shared.jit_category_manager, so a change to samply.shared.jit_category_manager can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break samply.shared.jit_category_manager.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
36→33 samply.shared.jitdump_manager uses samply.shared.lib_mappings✕
- Connections
- 2 pairs of types, where a type in samply.shared.jitdump_manager uses a type in samply.shared.lib_mappings.
- The types involved
samply.shared.jitdump_manager.JitDumpManager→samply.shared.lib_mappings.LibMappingOpQueuesamply.shared.jitdump_manager.SingleJitDumpProcessor→samply.shared.lib_mappings.LibMappingOpQueue
- Direction
- samply.shared.jitdump_manager uses samply.shared.lib_mappings, so a change to samply.shared.lib_mappings can break samply.shared.jitdump_manager, while a change to samply.shared.jitdump_manager can't break samply.shared.lib_mappings.
- Position
- Below the diagonal: samply.shared.jitdump_manager uses a module listed above it, which is the healthy direction.
37→7 samply.shared.process_sample_data uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.shared.process_sample_data.MarkerSpanOnThread→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→14 samply.shared.process_sample_data uses fxprof_processed_profile.markers.static_schema✕
- Connections
- 6 pairs of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
samply.shared.process_sample_data.OtherEventMarker→fxprof_processed_profile.markers.static_schema.Markersamply.shared.process_sample_data.RssStatMarker→fxprof_processed_profile.markers.static_schema.Markersamply.shared.process_sample_data.SchedSwitchMarkerOnCpuTrack→fxprof_processed_profile.markers.static_schema.Markersamply.shared.process_sample_data.SchedSwitchMarkerOnThreadTrack→fxprof_processed_profile.markers.static_schema.Markersamply.shared.process_sample_data.SimpleMarker→fxprof_processed_profile.markers.static_schema.Markersamply.shared.process_sample_data.UserTimingMarker→fxprof_processed_profile.markers.static_schema.Marker
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.markers.static_schema.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→16 samply.shared.process_sample_data uses fxprof_processed_profile.string_table✕
- Connections
- 6 pairs of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.shared.process_sample_data.OtherEventMarker→fxprof_processed_profile.string_table.StringHandlesamply.shared.process_sample_data.RssStatMarker→fxprof_processed_profile.string_table.StringHandlesamply.shared.process_sample_data.SchedSwitchMarkerOnCpuTrack→fxprof_processed_profile.string_table.StringHandlesamply.shared.process_sample_data.SchedSwitchMarkerOnThreadTrack→fxprof_processed_profile.string_table.StringHandlesamply.shared.process_sample_data.SimpleMarker→fxprof_processed_profile.string_table.StringHandlesamply.shared.process_sample_data.UserTimingMarker→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→23 samply.shared.process_sample_data uses fxprof_processed_profile.thread✕
- Connections
- 1 pair of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.thread.
- The types involved
samply.shared.process_sample_data.ProcessSampleData→fxprof_processed_profile.thread.ProcessHandle
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.thread, so a change to fxprof_processed_profile.thread can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.thread.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→24 samply.shared.process_sample_data uses fxprof_processed_profile.process✕
- Connections
- 1 pair of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.process.
- The types involved
samply.shared.process_sample_data.MarkerSpanOnThread→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→26 samply.shared.process_sample_data uses fxprof_processed_profile.profile✕
- Connections
- 7 pairs of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.profile.
- The types involved
samply.shared.process_sample_data.OtherEventMarker→fxprof_processed_profile.profile.Profilesamply.shared.process_sample_data.ProcessSampleData→fxprof_processed_profile.profile.Profilesamply.shared.process_sample_data.RssStatMarker→fxprof_processed_profile.profile.Profilesamply.shared.process_sample_data.SchedSwitchMarkerOnCpuTrack→fxprof_processed_profile.profile.Profilesamply.shared.process_sample_data.SchedSwitchMarkerOnThreadTrack→fxprof_processed_profile.profile.Profilesamply.shared.process_sample_data.SimpleMarker→fxprof_processed_profile.profile.Profilesamply.shared.process_sample_data.UserTimingMarker→fxprof_processed_profile.profile.Profile
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→27 samply.shared.process_sample_data uses fxprof_processed_profile.category✕
- Connections
- 1 pair of types, where a type in samply.shared.process_sample_data uses a type in fxprof_processed_profile.category.
- The types involved
samply.shared.process_sample_data.ProcessSampleData→fxprof_processed_profile.category.SubcategoryHandle
- Direction
- samply.shared.process_sample_data uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break fxprof_processed_profile.category.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→30 samply.shared.process_sample_data uses samply.shared.unresolved_samples✕
- Connections
- 2 pairs of types, where a type in samply.shared.process_sample_data uses a type in samply.shared.unresolved_samples.
- The types involved
samply.shared.process_sample_data.ProcessSampleData→samply.shared.unresolved_samples.UnresolvedSamplessamply.shared.process_sample_data.ProcessSampleData→samply.shared.unresolved_samples.UnresolvedStacks
- Direction
- samply.shared.process_sample_data uses samply.shared.unresolved_samples, so a change to samply.shared.unresolved_samples can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break samply.shared.unresolved_samples.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
37→33 samply.shared.process_sample_data uses samply.shared.lib_mappings✕
- Connections
- 1 pair of types, where a type in samply.shared.process_sample_data uses a type in samply.shared.lib_mappings.
- The types involved
samply.shared.process_sample_data.ProcessSampleData→samply.shared.lib_mappings.LibMappingOpQueue
- Direction
- samply.shared.process_sample_data uses samply.shared.lib_mappings, so a change to samply.shared.lib_mappings can break samply.shared.process_sample_data, while a change to samply.shared.process_sample_data can't break samply.shared.lib_mappings.
- Position
- Below the diagonal: samply.shared.process_sample_data uses a module listed above it, which is the healthy direction.
38→7 samply.linux_shared.process uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.linux_shared.process.Process→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.linux_shared.process uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→11 samply.linux_shared.process uses samply.shared.timestamp_converter✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in samply.shared.timestamp_converter.
- The types involved
samply.linux_shared.process.Process→samply.shared.timestamp_converter.TimestampConverter
- Direction
- samply.linux_shared.process uses samply.shared.timestamp_converter, so a change to samply.shared.timestamp_converter can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break samply.shared.timestamp_converter.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→16 samply.linux_shared.process uses fxprof_processed_profile.string_table✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.linux_shared.process.Process→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.linux_shared.process uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→19 samply.linux_shared.process uses fxprof_processed_profile.global_lib_table✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in fxprof_processed_profile.global_lib_table.
- The types involved
samply.linux_shared.process.Process→fxprof_processed_profile.global_lib_table.LibraryHandle
- Direction
- samply.linux_shared.process uses fxprof_processed_profile.global_lib_table, so a change to fxprof_processed_profile.global_lib_table can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break fxprof_processed_profile.global_lib_table.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→23 samply.linux_shared.process uses fxprof_processed_profile.thread✕
- Connections
- 2 pairs of types, where a type in samply.linux_shared.process uses a type in fxprof_processed_profile.thread.
- The types involved
samply.linux_shared.process.Process→fxprof_processed_profile.thread.ProcessHandlesamply.linux_shared.process.Process→fxprof_processed_profile.thread.Thread
- Direction
- samply.linux_shared.process uses fxprof_processed_profile.thread, so a change to fxprof_processed_profile.thread can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break fxprof_processed_profile.thread.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→24 samply.linux_shared.process uses fxprof_processed_profile.process✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in fxprof_processed_profile.process.
- The types involved
samply.linux_shared.process.Process→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.linux_shared.process uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→26 samply.linux_shared.process uses fxprof_processed_profile.profile✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in fxprof_processed_profile.profile.
- The types involved
samply.linux_shared.process.Process→fxprof_processed_profile.profile.Profile
- Direction
- samply.linux_shared.process uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→30 samply.linux_shared.process uses samply.shared.unresolved_samples✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in samply.shared.unresolved_samples.
- The types involved
samply.linux_shared.process.Process→samply.shared.unresolved_samples.UnresolvedSamples
- Direction
- samply.linux_shared.process uses samply.shared.unresolved_samples, so a change to samply.shared.unresolved_samples can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break samply.shared.unresolved_samples.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→31 samply.linux_shared.process uses samply.shared.jit_category_manager✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in samply.shared.jit_category_manager.
- The types involved
samply.linux_shared.process.Process→samply.shared.jit_category_manager.JitCategoryManager
- Direction
- samply.linux_shared.process uses samply.shared.jit_category_manager, so a change to samply.shared.jit_category_manager can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break samply.shared.jit_category_manager.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→33 samply.linux_shared.process uses samply.shared.lib_mappings✕
- Connections
- 3 pairs of types, where a type in samply.linux_shared.process uses a type in samply.shared.lib_mappings.
- The types involved
samply.linux_shared.process.Process→samply.shared.lib_mappings.LibMappingInfosamply.linux_shared.process.Process→samply.shared.lib_mappings.LibMappingOpQueuesamply.linux_shared.process.ProcessForkData→samply.shared.lib_mappings.LibMappingOpQueue
- Direction
- samply.linux_shared.process uses samply.shared.lib_mappings, so a change to samply.shared.lib_mappings can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break samply.shared.lib_mappings.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
38→36 samply.linux_shared.process uses samply.shared.jitdump_manager✕
- Connections
- 1 pair of types, where a type in samply.linux_shared.process uses a type in samply.shared.jitdump_manager.
- The types involved
samply.linux_shared.process.Process→samply.shared.jitdump_manager.JitDumpManager
- Direction
- samply.linux_shared.process uses samply.shared.jitdump_manager, so a change to samply.shared.jitdump_manager can break samply.linux_shared.process, while a change to samply.linux_shared.process can't break samply.shared.jitdump_manager.
- Position
- Below the diagonal: samply.linux_shared.process uses a module listed above it, which is the healthy direction.
39→2 samply.mac.task_profiler uses samply.shared.prop_types✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in samply.shared.prop_types.
- The types involved
samply.mac.task_profiler.TaskProfiler→samply.shared.prop_types.ProfileCreationProps
- Direction
- samply.mac.task_profiler uses samply.shared.prop_types, so a change to samply.shared.prop_types can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break samply.shared.prop_types.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→7 samply.mac.task_profiler uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.mac.task_profiler.TaskProfiler→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.mac.task_profiler uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→11 samply.mac.task_profiler uses samply.shared.timestamp_converter✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in samply.shared.timestamp_converter.
- The types involved
samply.mac.task_profiler.TaskProfiler→samply.shared.timestamp_converter.TimestampConverter
- Direction
- samply.mac.task_profiler uses samply.shared.timestamp_converter, so a change to samply.shared.timestamp_converter can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break samply.shared.timestamp_converter.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→16 samply.mac.task_profiler uses fxprof_processed_profile.string_table✕
- Connections
- 2 pairs of types, where a type in samply.mac.task_profiler uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.mac.task_profiler.TaskProfiler→fxprof_processed_profile.string_table.StringHandlesamply.mac.task_profiler.task_profiler$module→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.mac.task_profiler uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→23 samply.mac.task_profiler uses fxprof_processed_profile.thread✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in fxprof_processed_profile.thread.
- The types involved
samply.mac.task_profiler.TaskProfiler→fxprof_processed_profile.thread.ProcessHandle
- Direction
- samply.mac.task_profiler uses fxprof_processed_profile.thread, so a change to fxprof_processed_profile.thread can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break fxprof_processed_profile.thread.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→24 samply.mac.task_profiler uses fxprof_processed_profile.process✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in fxprof_processed_profile.process.
- The types involved
samply.mac.task_profiler.TaskProfiler→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.mac.task_profiler uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→26 samply.mac.task_profiler uses fxprof_processed_profile.profile✕
- Connections
- 2 pairs of types, where a type in samply.mac.task_profiler uses a type in fxprof_processed_profile.profile.
- The types involved
samply.mac.task_profiler.TaskProfiler→fxprof_processed_profile.profile.Profilesamply.mac.task_profiler.task_profiler$module→fxprof_processed_profile.profile.Profile
- Direction
- samply.mac.task_profiler uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→30 samply.mac.task_profiler uses samply.shared.unresolved_samples✕
- Connections
- 2 pairs of types, where a type in samply.mac.task_profiler uses a type in samply.shared.unresolved_samples.
- The types involved
samply.mac.task_profiler.TaskProfiler→samply.shared.unresolved_samples.UnresolvedSamplessamply.mac.task_profiler.TaskProfiler→samply.shared.unresolved_samples.UnresolvedStacks
- Direction
- samply.mac.task_profiler uses samply.shared.unresolved_samples, so a change to samply.shared.unresolved_samples can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break samply.shared.unresolved_samples.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→31 samply.mac.task_profiler uses samply.shared.jit_category_manager✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in samply.shared.jit_category_manager.
- The types involved
samply.mac.task_profiler.TaskProfiler→samply.shared.jit_category_manager.JitCategoryManager
- Direction
- samply.mac.task_profiler uses samply.shared.jit_category_manager, so a change to samply.shared.jit_category_manager can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break samply.shared.jit_category_manager.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→33 samply.mac.task_profiler uses samply.shared.lib_mappings✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in samply.shared.lib_mappings.
- The types involved
samply.mac.task_profiler.TaskProfiler→samply.shared.lib_mappings.LibMappingOpQueue
- Direction
- samply.mac.task_profiler uses samply.shared.lib_mappings, so a change to samply.shared.lib_mappings can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break samply.shared.lib_mappings.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
39→36 samply.mac.task_profiler uses samply.shared.jitdump_manager✕
- Connections
- 1 pair of types, where a type in samply.mac.task_profiler uses a type in samply.shared.jitdump_manager.
- The types involved
samply.mac.task_profiler.TaskProfiler→samply.shared.jitdump_manager.JitDumpManager
- Direction
- samply.mac.task_profiler uses samply.shared.jitdump_manager, so a change to samply.shared.jitdump_manager can break samply.mac.task_profiler, while a change to samply.mac.task_profiler can't break samply.shared.jitdump_manager.
- Position
- Below the diagonal: samply.mac.task_profiler uses a module listed above it, which is the healthy direction.
40→2 samply.windows.profile_context uses samply.shared.prop_types✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in samply.shared.prop_types.
- The types involved
samply.windows.profile_context.ProfileContext→samply.shared.prop_types.ProfileCreationProps
- Direction
- samply.windows.profile_context uses samply.shared.prop_types, so a change to samply.shared.prop_types can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.prop_types.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→3 samply.windows.profile_context uses samply_debugid.codeid✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in samply_debugid.codeid.
- The types involved
samply.windows.profile_context.PeInfo→samply_debugid.codeid.CodeId
- Direction
- samply.windows.profile_context uses samply_debugid.codeid, so a change to samply_debugid.codeid can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply_debugid.codeid.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→6 samply.windows.profile_context uses fxprof_processed_profile.markers.types✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.markers.types.
- The types involved
samply.windows.profile_context.ProfileContext→fxprof_processed_profile.markers.types.MarkerHandle
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.markers.types, so a change to fxprof_processed_profile.markers.types can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.markers.types.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→7 samply.windows.profile_context uses fxprof_processed_profile.timestamp✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.timestamp.
- The types involved
samply.windows.profile_context.PendingMarker→fxprof_processed_profile.timestamp.Timestamp
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.timestamp, so a change to fxprof_processed_profile.timestamp can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.timestamp.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→11 samply.windows.profile_context uses samply.shared.timestamp_converter✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in samply.shared.timestamp_converter.
- The types involved
samply.windows.profile_context.ProfileContext→samply.shared.timestamp_converter.TimestampConverter
- Direction
- samply.windows.profile_context uses samply.shared.timestamp_converter, so a change to samply.shared.timestamp_converter can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.timestamp_converter.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→14 samply.windows.profile_context uses fxprof_processed_profile.markers.static_schema✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.markers.static_schema.
- The types involved
samply.windows.profile_context.FreeformMarker→fxprof_processed_profile.markers.static_schema.Marker
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.markers.static_schema, so a change to fxprof_processed_profile.markers.static_schema can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.markers.static_schema.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→16 samply.windows.profile_context uses fxprof_processed_profile.string_table✕
- Connections
- 5 pairs of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.string_table.
- The types involved
samply.windows.profile_context.FreeformMarker→fxprof_processed_profile.string_table.StringHandlesamply.windows.profile_context.Process→fxprof_processed_profile.string_table.StringHandlesamply.windows.profile_context.ProfileContext→fxprof_processed_profile.string_table.StringHandlesamply.windows.profile_context.Thread→fxprof_processed_profile.string_table.StringHandlesamply.windows.profile_context.profile_context$module→fxprof_processed_profile.string_table.StringHandle
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.string_table, so a change to fxprof_processed_profile.string_table can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.string_table.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→23 samply.windows.profile_context uses fxprof_processed_profile.thread✕
- Connections
- 2 pairs of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.thread.
- The types involved
samply.windows.profile_context.Process→fxprof_processed_profile.thread.ProcessHandlesamply.windows.profile_context.Threads→fxprof_processed_profile.thread.Thread
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.thread, so a change to fxprof_processed_profile.thread can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.thread.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→24 samply.windows.profile_context uses fxprof_processed_profile.process✕
- Connections
- 4 pairs of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.process.
- The types involved
samply.windows.profile_context.Process→fxprof_processed_profile.process.ThreadHandlesamply.windows.profile_context.Processes→fxprof_processed_profile.process.Processsamply.windows.profile_context.ProfileContext→fxprof_processed_profile.process.ThreadHandlesamply.windows.profile_context.Thread→fxprof_processed_profile.process.ThreadHandle
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.process, so a change to fxprof_processed_profile.process can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.process.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→26 samply.windows.profile_context uses fxprof_processed_profile.profile✕
- Connections
- 5 pairs of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.profile.
- The types involved
samply.windows.profile_context.FreeformMarker→fxprof_processed_profile.profile.Profilesamply.windows.profile_context.KnownCategories→fxprof_processed_profile.profile.Profilesamply.windows.profile_context.Process→fxprof_processed_profile.profile.Profilesamply.windows.profile_context.ProfileContext→fxprof_processed_profile.profile.Profilesamply.windows.profile_context.profile_context$module→fxprof_processed_profile.profile.Profile
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.profile, so a change to fxprof_processed_profile.profile can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.profile.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→27 samply.windows.profile_context uses fxprof_processed_profile.category✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in fxprof_processed_profile.category.
- The types involved
samply.windows.profile_context.KnownCategories→fxprof_processed_profile.category.CategoryHandle
- Direction
- samply.windows.profile_context uses fxprof_processed_profile.category, so a change to fxprof_processed_profile.category can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break fxprof_processed_profile.category.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→29 samply.windows.profile_context uses samply.shared.per_cpu✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in samply.shared.per_cpu.
- The types involved
samply.windows.profile_context.ProfileContext→samply.shared.per_cpu.Cpus
- Direction
- samply.windows.profile_context uses samply.shared.per_cpu, so a change to samply.shared.per_cpu can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.per_cpu.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→30 samply.windows.profile_context uses samply.shared.unresolved_samples✕
- Connections
- 3 pairs of types, where a type in samply.windows.profile_context uses a type in samply.shared.unresolved_samples.
- The types involved
samply.windows.profile_context.Process→samply.shared.unresolved_samples.UnresolvedSamplessamply.windows.profile_context.ProfileContext→samply.shared.unresolved_samples.UnresolvedStackHandlesamply.windows.profile_context.ProfileContext→samply.shared.unresolved_samples.UnresolvedStacks
- Direction
- samply.windows.profile_context uses samply.shared.unresolved_samples, so a change to samply.shared.unresolved_samples can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.unresolved_samples.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→31 samply.windows.profile_context uses samply.shared.jit_category_manager✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in samply.shared.jit_category_manager.
- The types involved
samply.windows.profile_context.ProfileContext→samply.shared.jit_category_manager.JitCategoryManager
- Direction
- samply.windows.profile_context uses samply.shared.jit_category_manager, so a change to samply.shared.jit_category_manager can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.jit_category_manager.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→33 samply.windows.profile_context uses samply.shared.lib_mappings✕
- Connections
- 2 pairs of types, where a type in samply.windows.profile_context uses a type in samply.shared.lib_mappings.
- The types involved
samply.windows.profile_context.Process→samply.shared.lib_mappings.LibMappingInfosamply.windows.profile_context.Process→samply.shared.lib_mappings.LibMappingOpQueue
- Direction
- samply.windows.profile_context uses samply.shared.lib_mappings, so a change to samply.shared.lib_mappings can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.lib_mappings.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
40→37 samply.windows.profile_context uses samply.shared.process_sample_data✕
- Connections
- 1 pair of types, where a type in samply.windows.profile_context uses a type in samply.shared.process_sample_data.
- The types involved
samply.windows.profile_context.Processes→samply.shared.process_sample_data.ProcessSampleData
- Direction
- samply.windows.profile_context uses samply.shared.process_sample_data, so a change to samply.shared.process_sample_data can break samply.windows.profile_context, while a change to samply.windows.profile_context can't break samply.shared.process_sample_data.
- Position
- Below the diagonal: samply.windows.profile_context uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 32 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 28 | Medium |
Roadmap
First, implement a global authentication guard with explicit public opt-outs and named role rules to protect all endpoints by default. Second, secure the server's transport by enforcing TLS and sending Strict-Transport-Security headers, or by verifying the X-Forwarded-Proto header if using a terminating proxy. Third, resolve the static analysis findings in the release pipeline to eliminate shell injection risks. Finally, establish a documentation practice by recording significant design decisions in a dedicated ADR folder to ensure architectural clarity.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +14.3 pts | Medium | Access Controls |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.7 pts | Low | ADR Quality |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +2.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +2.3 pts | Low | Supply-chain Provenance & Signing |
| Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only. | +4.6 pts | Medium | Web-Security Posture |
| 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. | +4.4 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.9 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with custom_schemas.rs. | +1.7 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| samply-symbols/src/elf.rs | 4.9 | Mixed | Cognitive Complexity: samply_symbols::elf::compute_function_addresses_elf (cognitive 29) |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| samply/src/windows/coreclr.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| wholesym/src/file_resolver.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/import/perf.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| etw-reader/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/windows/etw_reader/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/linux/profiler.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/linux_shared/converter.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/mac/profiler.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| etw-reader/src/parser.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/windows/etw_reader/parser.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/mac/task_profiler.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| etw-reader/src/etw_types.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/shared/jitdump_manager.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| samply/src/windows/profile_context.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| fxprof-processed-profile/src/profile.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
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. 48 of 48 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 — 48 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, 413 of 455 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- 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 (49 contributor(s) across 2768 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 48 hold 0.4% 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.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's 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.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — 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, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's 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.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 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.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
18 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was samply::windows::etw_gecko::process_trace at 72. A further 6 function(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 KernelError::from at 89 — they are counted neither in the figure above nor in this dimension's score. 5 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: samply/src/mac/kernel_error.rs (KernelError::from at 89), samply/src/mac/mach_ipc.rs (Error::from at 49), samply-symbols/src/error.rs (Error::enum_as_string at 48), samply-mac-preload/src/mach_ipc.rs (MachError::from at 40), samply-symbols/src/macho.rs (samply_symbols::macho::macho_arch_name_for_cpu_type at 21). 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 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with samply::windows::etw_gecko::process_trace (cyclomatic 72). — Refactoring it lifts Cyclomatic Complexity from 6.9 to about 7.1/10.
- 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
49 function(s) exceeded the cognitive complexity threshold of 15; the worst was wholesym_addr2line::main at 99.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with wholesym_addr2line::main (cognitive 99), samply::windows::etw_gecko::process_trace (cognitive 93), FileResolver::get_candidate_paths_for_debug_file (cognitive 66). — 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 3 together lifts Cognitive Complexity from 6.0 to about 6.5/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
39 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 15 FileTooLong finding(s) in God Classes — start with custom_schemas.rs (2), mach_sys.rs, profile_context.rs. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 7 TooManyFields finding(s) in God Classes — start with mach_sys.rs (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with converter.rs, task_profiler.rs, sampler.rs. — One of this dimension's main actionable groups (7 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
114 duplicated block group(s) detected. A further 9 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 10 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with etw_types.rs (2), string_table.rs, mod.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 8 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with parser.rs (3), lib.rs (2), etw_types.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 8 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with lib.rs (2), file_resolver.rs (2), mach_ipc.rs. — One of this dimension's main actionable groups (8 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
14 production modules (Cargo), 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 12 of the 14 (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 215 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with config.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
172 test methods: 122 unit, 50 integration, 0 BDD, 0 e2e. The Rust suite contributes 172 `#[test]` function(s) across 47 file(s) declaring at least one; its unit/integration split is Cargo's own — 5 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, 47 test files): measured (0 flaky).
D12 · Dependency Hygiene
26 outdated, 0 yanked direct Cargo dependencies. 101 of 104 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed REDACTED). 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 REDACTED 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 406 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
Top hotspots: samply-symbols/src/symbol_map_object.rs (6×16=96)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with symbol_map_object.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
93 deducted task-comment markers across 64542 LoC (0.1/KLoC) → score 9.7. 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 85 TodoComment finding(s) in Explicit Debt — start with parser.rs (16), profiler.rs (8), coreclr.rs (7). — One of this dimension's main actionable groups (85 warning-level).
- Resolve the 4 XxxComment finding(s) in Explicit Debt — start with custom_schemas.rs (2), mod.rs, lib.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with mod.rs, lib.rs, mach_ipc.rs. — One of this dimension's main actionable groups (3 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. 14 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
3 of 14 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)
32 finding(s): 0 critical, 32 high, 0 medium, 0 low. 28 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 28 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 (28 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 0 high, 20 medium, 0 low.
What to do
- Resolve the 11 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
9 of 164 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is etw-reader/src/custom_schemas.rs. Counted over 164 of the 231 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with custom_schemas.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with winutils.rs, tdh_types.rs, codeid.rs. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: jit_function_add_marker.rs↔process_sample_data.rs 80%; jit_function_add_marker.rs↔per_cpu.rs 80%; converter.rs↔jit_function_add_marker.rs 80%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with server.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 8 Change coupling finding(s) in Change Coupling — start with jit_function_add_marker.rs (2), elf.rs (2), mod.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with converter.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — a server (.serve_connection) (samply/src/server.rs:240) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — samply/src/server.rs:240
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
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 3 of 15 project(s) that lack one — worth up to 0.4 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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `wholesym-addr2line`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
What to do
- Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `.serve_connection(` (samply/src/server.rs:240).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (samply/src/server.rs:240).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `msg_len` is read from the bytes being parsed at line 75 (`u32::from_be_bytes`), then used to size a `.resize` at line 77 — and nowhere in its scope is `msg_len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `msg_len` against the bytes actually remaining and a maximum the format allows before allocating. — samply/src/windows/utility_process/file_channel.rs:77
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 89% | Exemplary | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 66% | Strong | Solid. |
| Security | 35% | Weak — gated by D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- 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 — ~3275 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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- 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 (116 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
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not 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
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's 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.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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.
- 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 — 34 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
- Orphaned knowledge etw-reader/src/custom_schemas.rs:1
- Boundary-crossing change coupling: server.rs ↔ config.rs samply/src/server.rs:1
Serious — 363 finding(s)
- TodoComment wholesym/src/config.rs:150
- TodoComment wholesym/src/config.rs:161
- TodoComment wholesym/src/debuginfod.rs:88
- TodoComment wholesym/src/debuginfod.rs:92
- TodoComment samply-symbols/tests/integration_tests/main.rs:181
- TodoComment samply-symbols/src/windows.rs:276
- TodoComment samply-api/tests/integration_tests/main.rs:353
- TodoComment samply/src/windows/coreclr.rs:667
- TodoComment samply/src/windows/coreclr.rs:670
- TodoComment samply/src/mac/thread_profiler.rs:220
- TodoComment wholesym/src/downloader.rs:243
- TodoComment wholesym/src/file_resolver.rs:141
- TodoComment samply-symbols/src/shared.rs:187
- TodoComment samply-symbols/src/windows.rs:271
- TodoComment samply-api/src/asm/mod.rs:41
- TodoComment samply-api/src/asm/mod.rs:457
- TodoComment samply-api/src/asm/mod.rs:550
- TodoComment samply/src/cli.rs:397
- TodoComment samply/src/windows/coreclr.rs:384
- TodoComment samply/src/windows/coreclr.rs:422
- TodoComment samply/src/windows/coreclr.rs:529
- TodoComment samply/src/windows/coreclr.rs:631
- TodoComment samply/src/windows/coreclr.rs:673
- TodoComment samply/src/windows/import.rs:20
- TodoComment samply/src/windows/profile_context.rs:483
- FileTooLong: src/mach_sys.rs samply-mac-preload/src/mach_sys.rs
- FileTooLong: windows/profile_context.rs samply/src/windows/profile_context.rs
- FileTooLong: linux_shared/converter.rs samply/src/linux_shared/converter.rs
- FileTooLong: src/profile.rs fxprof-processed-profile/src/profile.rs
- FileTooLong: breakpad/index.rs samply-symbols/src/breakpad/index.rs
- FileTooLong: src/file_resolver.rs wholesym/src/file_resolver.rs
- FileTooLong: mac/mach_ipc.rs samply/src/mac/mach_ipc.rs
- FileTooLong: src/symbol_map_object.rs samply-symbols/src/symbol_map_object.rs
- FileTooLong: src/elf.rs samply-symbols/src/elf.rs
- FileTooLong: mac/proc_maps.rs samply/src/mac/proc_maps.rs
- FileTooLong: mac/task_profiler.rs samply/src/mac/task_profiler.rs
- FileTooLong: src/lib.rs gecko_profile/src/lib.rs
- FileTooLong: src/custom_schemas.rs etw-reader/src/custom_schemas.rs
- FileTooLong: etw_reader/custom_schemas.rs samply/src/windows/etw_reader/custom_schemas.rs
- FileTooLong: src/macho.rs samply-symbols/src/macho.rs
- samply::windows::etw_gecko::process_trace (cognitive 93) samply/src/windows/etw_gecko.rs:69
- samply::import::perf::convert_impl (cognitive 57) samply/src/import/perf.rs:71
- samply::windows::coreclr::handle_coreclr_event (cognitive 45) samply/src/windows/coreclr.rs:353
- samply::linux::profiler::run_profiler (cognitive 38) samply/src/linux/profiler.rs:530
- samply::mac::profiler::run (cognitive 37) samply/src/mac/profiler.rs:20
- samply::windows::etw_reader::write_property (cognitive 37) samply/src/windows/etw_reader/mod.rs:337
- samply::linux::profiler::init_profiler (cognitive 31) samply/src/linux/profiler.rs:370
- samply::linux::profiler::run (cognitive 21) samply/src/linux/profiler.rs:36
- samply::server::symbolication_service (cognitive 19) samply/src/server.rs:259
- samply::windows::etw_reader::enumerate_trace_guids_ex (cognitive 18) samply/src/windows/etw_reader/mod.rs:530
- samply::profile_store::sanitize_profile_name (cognitive 17) samply/src/profile_store.rs:205
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) etw-reader/src/etw_types.rs:150
- Duplicated block (10 lines × 2) fxprof-processed-profile/src/string_table.rs:23
- Duplicated block (10 lines × 2) samply-api/src/source/mod.rs:128
- Duplicated block (10 lines × 2) samply-mac-preload/src/mach_sys.rs:1869
- Duplicated block (10 lines × 2) etw-reader/src/etw_types.rs:304
- Duplicated block (10 lines × 2) etw-reader/src/parser.rs:131
- Duplicated block (10 lines × 2) etw-reader/src/schema.rs:235
- Duplicated block (10 lines × 2) samply/src/linux_shared/vdso.rs:21
- Duplicated block (10 lines × 2) samply/src/windows/coreclr.rs:595
- Duplicated block (10 lines × 2) etw-reader/src/lib.rs:492
- samply::windows::etw_gecko::process_trace (cyclomatic 72) samply/src/windows/etw_gecko.rs:69
- samply::windows::coreclr::handle_coreclr_event (cyclomatic 37) samply/src/windows/coreclr.rs:353
- samply::import::perf::convert_impl (cyclomatic 34) samply/src/import/perf.rs:71
- samply::windows::etw_reader::write_property (cyclomatic 32) samply/src/windows/etw_reader/mod.rs:337
- samply::linux::profiler::run_profiler (cyclomatic 30) samply/src/linux/profiler.rs:530
- samply::mac::profiler::run (cyclomatic 21) samply/src/mac/profiler.rs:20
- samply::linux::profiler::run (cyclomatic 18) samply/src/linux/profiler.rs:36
- samply::linux::profiler::init_profiler (cyclomatic 16) samply/src/linux/profiler.rs:370
- Change coupling: jit_function_add_marker.rs ↔ process_sample_data.rs samply/src/shared/jit_function_add_marker.rs:1
- Change coupling: jit_function_add_marker.rs ↔ per_cpu.rs samply/src/shared/jit_function_add_marker.rs:1
- Change coupling: elf.rs ↔ macho.rs samply-symbols/src/elf.rs:1
- Change coupling: mod.rs ↔ mod.rs samply-api/src/source/mod.rs:1
- Change coupling: lib.rs ↔ lib.rs tools/dump_table/src/lib.rs:1
- Change coupling: import.rs ↔ profiler.rs samply/src/windows/import.rs:1
- Change coupling: elf.rs ↔ windows.rs samply-symbols/src/elf.rs:1
- Change coupling: profiler.rs ↔ xperf.rs samply/src/windows/profiler.rs:1
- Duplicated block (13 lines × 2) etw-reader/src/etw_types.rs:269
- Duplicated block (13 lines × 2) etw-reader/src/lib.rs:298
- Duplicated block (13 lines × 2) etw-reader/src/lib.rs:540
- Duplicated block (13 lines × 2) etw-reader/src/parser.rs:351
- Duplicated block (13 lines × 2) etw-reader/src/parser.rs:368
- Duplicated block (13 lines × 2) etw-reader/src/parser.rs:442
- Duplicated block (13 lines × 2) samply/src/linux_shared/process_threads.rs:119
- Duplicated block (13 lines × 2) samply-mac-preload/src/mach_ipc.rs:297
- Duplicated block (12 lines × 2) etw-reader/src/lib.rs:156
- Duplicated block (12 lines × 2) etw-reader/src/lib.rs:390
- Duplicated block (12 lines × 2) samply-mac-preload/src/mach_ipc.rs:500
- Duplicated block (12 lines × 2) samply-quota-manager/src/quota_manager.rs:276
- Duplicated block (12 lines × 2) samply-symbols/src/breakpad/index.rs:945
- Duplicated block (12 lines × 2) samply/src/import/perf.rs:250
- Duplicated block (12 lines × 2) wholesym/src/file_resolver.rs:1021
- Duplicated block (12 lines × 2) wholesym/src/file_resolver.rs:1177
- Duplicated block (6 lines × 2) etw-reader/src/lib.rs:76
- Duplicated block (6 lines × 2) samply-symbols/src/symbol_map_string_interner.rs:109
- Duplicated block (6 lines × 2) samply/src/linux_shared/vdso.rs:13
- Duplicated block (6 lines × 2) etw-reader/src/etw_types.rs:25
- Duplicated block (6 lines × 2) etw-reader/src/parser.rs:632
- Duplicated block (6 lines × 2) etw-reader/src/utils.rs:58
- Duplicated block (6 lines × 2) samply-mac-preload/src/mach_ipc.rs:113
- Duplicated block (6 lines × 2) fxprof-processed-profile/src/native_symbols.rs:179
- TooManyFields: __darwin_x86_avx512_state64 samply-mac-preload/src/mach_sys.rs:2670
- TooManyFields: __darwin_i386_avx512_state samply-mac-preload/src/mach_sys.rs:2263
- TooManyFields: __darwin_x86_avx_state64 samply-mac-preload/src/mach_sys.rs:2608
- TooManyFields: task_vm_info samply-mac-preload/src/mach_sys.rs:3345
- TooManyFields: __darwin_i386_avx_state samply-mac-preload/src/mach_sys.rs:2217
- TooManyFields: __darwin_x86_float_state64 samply-mac-preload/src/mach_sys.rs:2563
- TooManyFields: __darwin_i386_float_state samply-mac-preload/src/mach_sys.rs:2180
- MethodTooLong: Converter.add_module_to_process samply/src/linux_shared/converter.rs:1317
- MethodTooLong: TaskProfiler.new samply/src/mac/task_profiler.rs:123
- MethodTooLong: Sampler.run samply/src/mac/sampler.rs:61
- MethodTooLong: ElfLoad.provide samply-symbols/src/elf.rs:628
- MethodTooLong: FileResolver.get_candidate_paths_for_debug_file wholesym/src/file_resolver.rs:481
- MethodTooLong: PerfBuilder.open samply/src/linux/perf_event.rs:230
- MethodTooLong: Error.from samply/src/mac/mach_ipc.rs:938
- Duplicated block (9 lines × 2) etw-reader/src/schema.rs:160
- Duplicated block (9 lines × 2) samply-mac-preload/src/lib.rs:122
- Duplicated block (9 lines × 2) samply-mac-preload/src/mach_sys.rs:1895
- Duplicated block (9 lines × 2) samply/src/windows/etw_reader/utils.rs:70
- Duplicated block (9 lines × 2) etw-reader/src/etw_types.rs:83
- Duplicated block (9 lines × 2) samply-symbols/src/symbol_map_object.rs:476
- Duplicated block (9 lines × 2) samply-symbols/src/symbol_map_object.rs:486
- Duplicated block (5 lines × 2) etw-reader/src/etw_types.rs:298
- Duplicated block (5 lines × 2) etw-reader/src/lib.rs:435
- Duplicated block (5 lines × 2) etw-reader/src/parser.rs:617
- Duplicated block (5 lines × 2) samply-symbols/src/symbol_map_object.rs:534
- Duplicated block (5 lines × 2) samply-symbols/src/breakpad/symbol_map.rs:81
- Duplicated block (5 lines × 2) samply-mac-preload/src/lib.rs:132
- Duplicated block (5 lines × 2) samply-mac-preload/src/mach_ipc.rs:367
- Parser::find_property_size (cognitive 19) etw-reader/src/parser.rs:175
- Parser::try_parse (cognitive 19) etw-reader/src/parser.rs:321
- Parser::find_property_size (cognitive 19) samply/src/windows/etw_reader/parser.rs:175
- Parser::try_parse (cognitive 19) samply/src/windows/etw_reader/parser.rs:321
- Parser::try_parse (cognitive 16) etw-reader/src/parser.rs:384
- Parser::try_parse (cognitive 16) samply/src/windows/etw_reader/parser.rs:384
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) etw-reader/src/etw_types.rs:289
- Duplicated block (8 lines × 2) etw-reader/src/lib.rs:87
- Duplicated block (8 lines × 2) samply/src/linux_shared/process_threads.rs:149
- Duplicated block (8 lines × 2) wholesym/src/breakpad.rs:191
- Duplicated block (8 lines × 2) etw-reader/src/lib.rs:113
- Duplicated block (7 lines × 2) etw-reader/src/lib.rs:531
- Duplicated block (7 lines × 2) etw-reader/src/parser.rs:622
- Duplicated block (7 lines × 2) etw-reader/src/utils.rs:66
- Duplicated block (7 lines × 2) samply-symbols/src/breakpad/index.rs:98
- Duplicated block (7 lines × 2) samply-symbols/src/breakpad/index.rs:1027
- XxxComment samply/src/windows/etw_reader/custom_schemas.rs:704
- XxxComment etw-reader/src/custom_schemas.rs:704
- XxxComment samply/src/windows/etw_reader/mod.rs:409
- XxxComment etw-reader/src/lib.rs:409
- Converter::add_module_to_process (cognitive 42) samply/src/linux_shared/converter.rs:1317
- Converter::get_sample_stack (cognitive 29) samply/src/linux_shared/converter.rs:616
- Converter::handle_context_switch (cognitive 17) samply/src/linux_shared/converter.rs:850
- Converter::add_kernel_module (cognitive 17) samply/src/linux_shared/converter.rs:1154
- FunctionTooLong: samply::windows::etw_gecko::process_trace samply/src/windows/etw_gecko.rs:69
- FunctionTooLong: samply::windows::coreclr::handle_coreclr_event samply/src/windows/coreclr.rs:353
- FunctionTooLong: wholesym_addr2line::main wholesym-addr2line/src/main.rs:67
- FunctionTooLong: samply::mac::profiler::run samply/src/mac/profiler.rs:20
- ClassTooLong: Converter samply/src/linux_shared/converter.rs:64
- ClassTooLong: ProfileContext samply/src/windows/profile_context.rs:440
- ClassTooLong: Profile fxprof-processed-profile/src/profile.rs:211
- ClassTooLong: TaskProfiler samply/src/mac/task_profiler.rs:100
- Duplicated block (25 lines × 2) etw-reader/src/lib.rs:504
- Duplicated block (25 lines × 2) etw-reader/src/parser.rs:322
- Duplicated block (25 lines × 2) etw-reader/src/parser.rs:547
- Duplicated block (25 lines × 2) etw-reader/src/schema.rs:191
- Duplicated block (15 lines × 2) etw-reader/src/lib.rs:321
- Duplicated block (15 lines × 2) etw-reader/src/parser.rs:528
- Duplicated block (15 lines × 2) samply/src/linux_shared/converter.rs:1390
- Duplicated block (15 lines × 2) samply/src/windows/profile_context.rs:909
- FixmeComment samply/src/windows/etw_reader/mod.rs:284
- FixmeComment etw-reader/src/lib.rs:284
- FixmeComment samply/src/mac/mach_ipc.rs:236
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2) etw-reader/src/lib.rs:403
- Duplicated block (18 lines × 2) etw-reader/src/parser.rs:420
- Duplicated block (18 lines × 2) samply/src/linux/profiler.rs:637
- Duplicated block (11 lines × 2) samply-mac-preload/src/mach_ipc.rs:264
- Duplicated block (11 lines × 2) samply-mac-preload/src/mach_ipc.rs:397
- Duplicated block (11 lines × 2) samply/src/linux_shared/process.rs:336
- Converter::add_module_to_process (cyclomatic 24) samply/src/linux_shared/converter.rs:1317
- Converter::get_sample_stack (cyclomatic 17) samply/src/linux_shared/converter.rs:616
- Parser::find_property_size (cyclomatic 16) etw-reader/src/parser.rs:175
- Parser::find_property_size (cyclomatic 16) samply/src/windows/etw_reader/parser.rs:175
- FileResolver::get_candidate_paths_for_debug_file (cognitive 66) wholesym/src/file_resolver.rs:481
- FileResolver::get_candidate_paths_for_binary (cognitive 20) wholesym/src/file_resolver.rs:735
- etw_reader::write_property (cognitive 37) etw-reader/src/lib.rs:337
- etw_reader::enumerate_trace_guids_ex (cognitive 18) etw-reader/src/lib.rs:530
- TaskProfiler::sample_impl (cognitive 29) samply/src/mac/task_profiler.rs:348
- TaskProfiler::new (cognitive 26) samply/src/mac/task_profiler.rs:123
- samply_symbols::elf::compute_function_addresses_elf (cognitive 29) samply-symbols/src/elf.rs:393
- samply_symbols::demangle_ocaml::demangle (cognitive 16) samply-symbols/src/demangle_ocaml.rs:1
- ObjectSymbolMapInner::try_lookup_external_impl (cognitive 28) samply-symbols/src/symbol_map_object.rs:685
- ObjectSymbolMapInner::lookup_sync (cognitive 18) samply-symbols/src/symbol_map_object.rs:825
- TraceEventInfoRaw::property_map_info (cognitive 19) etw-reader/src/etw_types.rs:146
- TraceEventInfoRaw::property_map_info (cognitive 19) samply/src/windows/etw_reader/etw_types.rs:146
- wholesym::load_helpers::load_binary_for_library_info (cognitive 18) wholesym/src/load_helpers.rs:83
- wholesym::downloader::consume_stream_and_write_to_file (cognitive 16) wholesym/src/downloader.rs:504
- TooManyMethods: Profile fxprof-processed-profile/src/profile.rs:211
- TooManyMethods: ProfileContext samply/src/windows/profile_context.rs:440
- REDACTED
- REDACTED
- Members sharing a duplicated core (14 members, 50+ identical tokens) etw-reader/src/custom_schemas.rs:173
- Members sharing a duplicated core (14 members, 50+ identical tokens) samply-mac-preload/src/mach_sys.rs:400
- Members sharing a duplicated core (4 members, 50+ identical tokens) etw-reader/src/custom_schemas.rs:86
- Members sharing a duplicated core (4 members, 50+ identical tokens) samply/src/linux_shared/converter.rs:247
- Duplicated block (24 lines × 2) etw-reader/src/parser.rs:293
- Duplicated block (24 lines × 2) samply/src/windows/profile_context.rs:884
- Duplicated block (22 lines × 2) etw-reader/src/lib.rs:459
- Duplicated block (22 lines × 2) etw-reader/src/tdh.rs:25
- Duplicated block (20 lines × 2) etw-reader/src/sddl.rs:34
- Duplicated block (20 lines × 2) etw-reader/src/tdh.rs:49
- Duplicated block (19 lines × 2) etw-reader/src/parser.rs:506
- Duplicated block (19 lines × 2) etw-reader/src/utils.rs:14
- Duplicated block (16 lines × 2) etw-reader/src/etw_types.rs:214
- Duplicated block (16 lines × 2) etw-reader/src/lib.rs:130
- Off the main sequence: samply-quota-manager
- Off the main sequence: fxprof-processed-profile
- No authorization samply/src/server.rs:240
- FileResolver::get_candidate_paths_for_debug_file (cyclomatic 37) wholesym/src/file_resolver.rs:481
- etw_reader::write_property (cyclomatic 32) etw-reader/src/lib.rs:337
- wholesym_addr2line::main (cyclomatic 28) wholesym-addr2line/src/main.rs:67
- Sampler::run (cyclomatic 20) samply/src/mac/sampler.rs:61
- PerfBuilder::open (cyclomatic 18) samply/src/linux/perf_event.rs:230
- SymbolList::new (cyclomatic 16) samply-symbols/src/symbol_map_object.rs:194
- Hotspot: samply-symbols/src/symbol_map_object.rs samply-symbols/src/symbol_map_object.rs:194
- HackComment samply/src/windows/xperf.rs:92
- wholesym_addr2line::main (cognitive 99) wholesym-addr2line/src/main.rs:67
- Sampler::run (cognitive 42) samply/src/mac/sampler.rs:61
- JitCategoryManager::classify_jit_symbol (cognitive 23) samply/src/shared/jit_category_manager.rs:284
- PerfGroup::consume_events (cognitive 22) samply/src/linux/perf_group.rs:224
- ResponseFrame::serialize (cognitive 21) samply-api/src/symbolicate/response_json.rs:205
- ElfLoad::provide (cognitive 20) samply-symbols/src/elf.rs:628
- SingleJitDumpProcessor::process_pending_records (cognitive 19) samply/src/shared/jitdump_manager.rs:143
- FatArchiveMember::match_score_for_disambiguator (cognitive 19) samply-symbols/src/macho.rs:134
- PerfBuilder::open (cognitive 18) samply/src/linux/perf_event.rs:230
- ProfileContext::handle_cswitch (cognitive 18) samply/src/windows/profile_context.rs:1569
- QuotaManager::list_existing_files_sync (cognitive 17) samply-quota-manager/src/quota_manager.rs:149
- AsyncGzipDecoder::poll_read (cognitive 17) wholesym/src/async_gzip_decoder.rs:53
- FrameInterner::create_tables (cognitive 16) fxprof-processed-profile/src/frame_table.rs:102
- SimpleperfSymbolTables::new (cognitive 16) samply/src/linux_shared/converter.rs:1736
- REDACTED
- Change-coupling hub: converter.rs → process.rs, jit_function_add_marker.rs, stack_converter.rs samply/src/linux_shared/converter.rs
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (103 shared lines) etw-reader/src/lib.rs:342
- Near-duplicate member pair (67 shared lines) etw-reader/src/lib.rs:234
- Near-duplicate member pair (53 shared lines) etw-reader/src/lib.rs:530
- Edited copy of a member (36 corresponding lines) samply-mac-preload/src/mach_sys.rs:1868
- Edited copy of a member (38 corresponding lines) etw-reader/src/parser.rs:505
- Duplicated block (58 lines × 2) etw-reader/src/tdh.rs:71
- Duplicated block (51 lines × 2) etw-reader/src/parser.rs:176
- Duplicated block (46 lines × 2) etw-reader/src/lib.rs:343
- Duplicated block (40–44 lines × 2) samply/src/shared/context_switch.rs:91
- Duplicated block (43 lines × 2) samply-mac-preload/src/mach_ipc.rs:561
- Duplicated block (42 lines × 2) etw-reader/src/tdh_types.rs:74
- Duplicated block (37 lines × 2) etw-reader/src/lib.rs:260
- Duplicated block (34 lines × 2) etw-reader/src/schema.rs:69
- Duplicated block (33 lines × 2) etw-reader/src/lib.rs:554
- Duplicated block (31 lines × 2) etw-reader/src/parser.rs:385
- Duplicated block (29 lines × 2) etw-reader/src/parser.rs:234
- Duplicated block (23 lines × 2) etw-reader/src/lib.rs:589
- Duplicated block (21 lines × 2) etw-reader/src/parser.rs:481
- Duplicated block (19–20 lines × 2) samply/src/windows/profile_context.rs:754
- Duplicated block (17 lines × 2) etw-reader/src/lib.rs:236
- Duplicated block (13–16 lines × 2) samply/src/linux_shared/converter.rs:393
- Duplicated block (15 lines × 4) samply/src/linux_shared/converter.rs:262
- Duplicated block (14 lines × 2) etw-reader/src/property.rs:38
- Duplicated block (13–14 lines × 2) samply/src/linux_shared/converter.rs:886
- Duplicated block (12–14 lines × 2) samply/src/main.rs:193
- Duplicated block (12 lines × 14) etw-reader/src/custom_schemas.rs:175
- Duplicated block (12 lines × 4) etw-reader/src/custom_schemas.rs:88
- Duplicated block (11–12 lines × 2) samply/src/shared/per_cpu.rs:46
- Duplicated block (11 lines × 3) wholesym/src/file_resolver.rs:1220
- Duplicated block (9–10 lines × 14) samply-mac-preload/src/mach_sys.rs:401
- Duplicated block (9–10 lines × 2) wholesym/src/file_resolver.rs:651
- Duplicated block (9 lines × 14) samply-mac-preload/src/mach_sys.rs:407
- Duplicated block (8–9 lines × 2) samply/src/mac/task_profiler.rs:432
- Duplicated block (8 lines × 3) wholesym/src/file_resolver.rs:1064
- Duplicated block (5 lines × 4) samply-symbols/src/symbol_map_object.rs:911
- Duplicated block (7 lines × 3) samply/src/linux_shared/process_threads.rs:210
- Duplicated block (5 lines × 3) samply/src/mac/process_launcher.rs:207
- Low cohesion: SymbolManagerConfig (LCOM4 13) wholesym/src/config.rs:11
- Coverage collected but not gated
- Length read from the parsed input is spent without ever being bounded samply/src/windows/utility_process/file_channel.rs:77
Minor — 32 finding(s)
- Duplicated predicate etw-reader/src/parser.rs:372
- Duplicated predicate etw-reader/src/parser.rs:355
- Duplicated predicate etw-reader/src/parser.rs:332
- Duplicated predicate etw-reader/src/parser.rs:402
- Duplicated predicate etw-reader/src/parser.rs:391
- Duplicated predicate etw-reader/src/parser.rs:550
- Duplicated predicate etw-reader/src/etw_types.rs:197
- Duplicated predicate wholesym/src/file_resolver.rs:670
- Duplicated predicate etw-reader/src/parser.rs:186
- Duplicated predicate etw-reader/src/schema.rs:472
- Orphaned file samply/src/windows/winutils.rs:1
- Orphaned file etw-reader/src/tdh_types.rs:1
- Orphaned file samply-debugid/src/codeid.rs:1
- Orphaned file etw-reader/src/tdh.rs:1
- Orphaned file samply-object/src/lib.rs:1
- Orphaned file samply/src/linux/sorter.rs:1
- Orphaned file samply-debugid/src/debugid.rs:1
- Orphaned file etw-reader/src/utils.rs:1
- Silent fallback default on Err samply/src/profile_store.rs:196
- Silent fallback default on Err wholesym/src/file_resolver.rs:711
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No release approval gate
- No app-layer HTTPS enforcement detected
- No security response headers detected
Minor — 26 finding(s)
- Outdated: cfg-if
- Outdated: clap
- Outdated: crc32fast
- Outdated: hyper
- Outdated: hyper-util
- Outdated: jiff
- Outdated: lazy_static
- Outdated: libc
- Outdated: memmap2
- Outdated: mio
- Outdated: plist
- Outdated: rand
- Outdated: rusqlite_migration
- Outdated: rustls
- Outdated: serde_json
- Outdated: thiserror
- Outdated: tokio
- Outdated: tokio-util
- Outdated: toml
- Outdated: uuid
- Outdated: yaxpeax-arch
- Outdated: yoke
- Outdated: yoke-derive
- Outdated: zerocopy
- Outdated: zerocopy-derive
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-e352782170af4102bfbb9bbda04adccb/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-e352782170af4102bfbb9bbda04adccb/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 . | 32 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 20 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |