Executive summary
Orange-OpenSource/hurl falls short of our standard for production because it has misused accessibility attributes. It scores 57 out of 100 and is rated Adequate, and 17 of its 21 critical findings are security problems.
Accessibility, at 51, is the weakest lens and counts most in the score. The best first step is correcting the accessibility attributes, worth about 6 points. Structuring the pages comes next, worth about 5 points. Raising Accessibility to 70 would lift the score to about 63.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five passwords or keys are open to anyone who can read the repository, and two settings leave the servers or containers unsafe. Pinning each tool to an exact version, replacing each exposed password or key and correcting the unsafe settings would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The page that doesn't say its language needs its language set.
The product code is 69,965 lines, about €74,000 to rebuild.
If Accessibility rose from 51 to 70, the lowest score rated Strong, the score would rise from 57 to about 63.
New since the last survey: 11 findings
- Cognitive Complexity · update_crates.update_local_crates (cognitive 22) bin/update_crates.py
- Code Duplication · Edited copy of a member (27 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (7 corresponding lines) integration/hurl/tests_ok/add_header/add_header.py
- Code Duplication · Edited copy of a member (7 corresponding lines) integration/hurl/tests_ok/get_large/get_large.py
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
Fixed since the last survey: 11 findings
- Churn × Complexity Hotspots · Hotspot: packages/hurl/src/cli/options/config_file/mod.rs packages/hurl/src/cli/options/config_file/mod.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurl_core/src/parser/option.rs packages/hurl_core/src/parser/option.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurl_core/src/ast/visit.rs packages/hurl_core/src/ast/visit.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurl/src/cli/options/mod.rs packages/hurl/src/cli/options/mod.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurlfmt/src/format/json.rs packages/hurlfmt/src/format/json.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurl_core/src/ast/option.rs packages/hurl_core/src/ast/option.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurl_core/src/parser/error.rs packages/hurl_core/src/parser/error.rs
- Churn × Complexity Hotspots · Hotspot: packages/hurlfmt/src/linter/rewrite.rs packages/hurlfmt/src/linter/rewrite.rs
- IaC & Container Security · Medium IaC: REDACTED REDACTED
- IaC & Container Security · Medium IaC: REDACTED REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €74,000 · Estimate
| Cost to rebuild | €24,000 to €120,000, for 407 to 1,292 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 57. 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: 69,965 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 hurl.util.path | 2 hurl.util.term | 3 hurl_core.input | 4 hurl_core.reader | 5 hurl_core.text.styledstring | 6 hurl_core.types | 7 hurl.pretty.json | 8 hurl_core.ast.json | 9 hurl.http.url | 10 hurl.runner.value | 11 hurl_core.ast.primitive | 12 hurl.http.cookie_store | 13 hurl.http.request_spec | 14 hurl.runner.error | 15 hurl.runner.output | 16 hurl.runner.variable | 17 hurl_core.ast.option | 18 hurl_core.ast.section | 19 hurl.cli.options.env_vars | 20 hurl.runner.runner_options | 21 hurl_core.ast.core | 22 hurl.http.options | 23 hurl_core.ast.visit | 24 hurl.http.curl_cmd | 25 hurl.http.header | 26 hurl.util.logger | 27 hurl.http.request | 28 hurl.cli.options | 29 hurl.cli.options.args | 30 hurl.http.response | 31 hurl.runner.options | 32 hurl.http.call | 33 hurl.http.client | 34 hurl.runner.query | 35 hurl.runner.result | 36 hurl.json.result | 37 hurl.parallel.job | 38 hurl.report.html.testcase | 39 hurl.runner.entry | 40 hurl.runner.hurl_file |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 hurl.util.path | ||||||||||||||||||||||||||||||||||||||||
| 2 hurl.util.term | ||||||||||||||||||||||||||||||||||||||||
| 3 hurl_core.input | ||||||||||||||||||||||||||||||||||||||||
| 4 hurl_core.reader | ||||||||||||||||||||||||||||||||||||||||
| 5 hurl_core.text.styledstring | ||||||||||||||||||||||||||||||||||||||||
| 6 hurl_core.types | ||||||||||||||||||||||||||||||||||||||||
| 7 hurl.pretty.json | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 hurl_core.ast.json | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 hurl.http.url | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 hurl.runner.value | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 hurl_core.ast.primitive | 1 | 30 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 hurl.http.cookie_store | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 hurl.http.request_spec | 2 | 3 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 14 hurl.runner.error | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 hurl.runner.output | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 hurl.runner.variable | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 hurl_core.ast.option | 3 | 5 | ||||||||||||||||||||||||||||||||||||||
| 18 hurl_core.ast.section | 6 | 22 | ||||||||||||||||||||||||||||||||||||||
| 19 hurl.cli.options.env_vars | 2 | 1 | 8 | |||||||||||||||||||||||||||||||||||||
| 20 hurl.runner.runner_options | 2 | 4 | 2 | 2 | 2 | 4 | 4 | |||||||||||||||||||||||||||||||||
| 21 hurl_core.ast.core | 6 | 17 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 hurl.http.options | 2 | 1 | 1 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 23 hurl_core.ast.visit | 4 | 1 | 18 | 18 | 23 | 18 | ||||||||||||||||||||||||||||||||||
| 24 hurl.http.curl_cmd | 2 | 2 | 3 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 25 hurl.http.header | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 hurl.util.logger | 1 | 1 | 1 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||
| 27 hurl.http.request | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 hurl.cli.options | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 hurl.cli.options.args | 1 | 2 | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||
| 30 hurl.http.response | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 hurl.runner.options | 1 | 1 | 1 | 1 | 5 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 32 hurl.http.call | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 hurl.http.client | 1 | 2 | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 34 hurl.runner.query | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 hurl.runner.result | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||
| 36 hurl.json.result | 3 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 4 | |||||||||||||||||||||||||||||||
| 37 hurl.parallel.job | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 hurl.report.html.testcase | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 hurl.runner.entry | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 40 hurl.runner.hurl_file | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 |
7→12 hurl.pretty.json uses hurl.http.cookie_store part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.pretty.json uses a type in hurl.http.cookie_store.
- The types involved
hurl.pretty.json.Formatter→hurl.http.cookie_store.BytePos
- Direction
- hurl.pretty.json uses hurl.http.cookie_store, so a change to hurl.http.cookie_store can break hurl.pretty.json, while a change to hurl.pretty.json can't break hurl.http.cookie_store.
- 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→6 hurl_core.ast.json uses hurl_core.types✕
- Connections
- 6 pairs of types, where a type in hurl_core.ast.json uses a type in hurl_core.types.
- The types involved
hurl_core.ast.json.JsonListElement→hurl_core.types.SourceStringhurl_core.ast.json.JsonListElement→hurl_core.types.ToSourcehurl_core.ast.json.JsonObjectElement→hurl_core.types.SourceStringhurl_core.ast.json.JsonObjectElement→hurl_core.types.ToSourcehurl_core.ast.json.JsonValue→hurl_core.types.SourceStringhurl_core.ast.json.JsonValue→hurl_core.types.ToSource
- Direction
- hurl_core.ast.json uses hurl_core.types, so a change to hurl_core.types can break hurl_core.ast.json, while a change to hurl_core.ast.json can't break hurl_core.types.
- Position
- Below the diagonal: hurl_core.ast.json uses a module listed above it, which is the healthy direction.
8→11 hurl_core.ast.json uses hurl_core.ast.primitive part of a loop✕
- Connections
- 2 pairs of types, where a type in hurl_core.ast.json uses a type in hurl_core.ast.primitive.
- The types involved
hurl_core.ast.json.JsonObjectElement→hurl_core.ast.primitive.Templatehurl_core.ast.json.JsonValue→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl_core.ast.json uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl_core.ast.json, while a change to hurl_core.ast.json can't break hurl_core.ast.primitive.
- 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→7 hurl.http.url uses hurl.pretty.json✕
- Connections
- 1 pair of types, where a type in hurl.http.url uses a type in hurl.pretty.json.
- The types involved
hurl.http.url.Url→hurl.pretty.json.Formatter
- Direction
- hurl.http.url uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.http.url, while a change to hurl.http.url can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.http.url uses a module listed above it, which is the healthy direction.
10→7 hurl.runner.value uses hurl.pretty.json✕
- Connections
- 2 pairs of types, where a type in hurl.runner.value uses a type in hurl.pretty.json.
- The types involved
hurl.runner.value.Value→hurl.pretty.json.Formatterhurl.runner.value.ValueKind→hurl.pretty.json.Formatter
- Direction
- hurl.runner.value uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.runner.value, while a change to hurl.runner.value can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.runner.value uses a module listed above it, which is the healthy direction.
11→4 hurl_core.ast.primitive uses hurl_core.reader✕
- Connections
- 1 pair of types, where a type in hurl_core.ast.primitive uses a type in hurl_core.reader.
- The types involved
hurl_core.ast.primitive.SourceInfo→hurl_core.reader.Pos
- Direction
- hurl_core.ast.primitive uses hurl_core.reader, so a change to hurl_core.reader can break hurl_core.ast.primitive, while a change to hurl_core.ast.primitive can't break hurl_core.reader.
- Position
- Below the diagonal: hurl_core.ast.primitive uses a module listed above it, which is the healthy direction.
11→6 hurl_core.ast.primitive uses hurl_core.types✕
- Connections
- 30 pairs of types, where a type in hurl_core.ast.primitive uses a type in hurl_core.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
hurl_core.ast.primitive.Base64→hurl_core.types.SourceStringhurl_core.ast.primitive.Comment→hurl_core.types.SourceStringhurl_core.ast.primitive.Comment→hurl_core.types.ToSourcehurl_core.ast.primitive.Expr→hurl_core.types.SourceStringhurl_core.ast.primitive.Expr→hurl_core.types.ToSourcehurl_core.ast.primitive.Float→hurl_core.types.SourceStringhurl_core.ast.primitive.Float→hurl_core.types.ToSourcehurl_core.ast.primitive.GraphQl→hurl_core.types.SourceStringhurl_core.ast.primitive.GraphQl→hurl_core.types.ToSourcehurl_core.ast.primitive.GraphQlVariables→hurl_core.types.SourceStringhurl_core.ast.primitive.GraphQlVariables→hurl_core.types.ToSourcehurl_core.ast.primitive.Hex→hurl_core.types.SourceStringhurl_core.ast.primitive.I64→hurl_core.types.SourceStringhurl_core.ast.primitive.I64→hurl_core.types.ToSourcehurl_core.ast.primitive.MultilineString→hurl_core.types.SourceStringhurl_core.ast.primitive.MultilineString→hurl_core.types.ToSourcehurl_core.ast.primitive.MultilineStringKind→hurl_core.types.SourceStringhurl_core.ast.primitive.MultilineStringKind→hurl_core.types.ToSourcehurl_core.ast.primitive.Number→hurl_core.types.SourceStringhurl_core.ast.primitive.Number→hurl_core.types.ToSourcehurl_core.ast.primitive.Placeholder→hurl_core.types.SourceStringhurl_core.ast.primitive.Placeholder→hurl_core.types.ToSourcehurl_core.ast.primitive.Regex→hurl_core.types.SourceStringhurl_core.ast.primitive.Regex→hurl_core.types.ToSourcehurl_core.ast.primitive.Template→hurl_core.types.SourceString
- Direction
- hurl_core.ast.primitive uses hurl_core.types, so a change to hurl_core.types can break hurl_core.ast.primitive, while a change to hurl_core.ast.primitive can't break hurl_core.types.
- Position
- Below the diagonal: hurl_core.ast.primitive uses a module listed above it, which is the healthy direction.
11→8 hurl_core.ast.primitive uses hurl_core.ast.json✕
- Connections
- 1 pair of types, where a type in hurl_core.ast.primitive uses a type in hurl_core.ast.json.
- The types involved
hurl_core.ast.primitive.GraphQlVariables→hurl_core.ast.json.JsonValue
- Direction
- hurl_core.ast.primitive uses hurl_core.ast.json, so a change to hurl_core.ast.json can break hurl_core.ast.primitive, while a change to hurl_core.ast.primitive can't break hurl_core.ast.json.
- Position
- Below the diagonal: hurl_core.ast.primitive uses a module listed above it, which is the healthy direction.
12→7 hurl.http.cookie_store uses hurl.pretty.json✕
- Connections
- 1 pair of types, where a type in hurl.http.cookie_store uses a type in hurl.pretty.json.
- The types involved
hurl.http.cookie_store.Cookie→hurl.pretty.json.Formatter
- Direction
- hurl.http.cookie_store uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.http.cookie_store, while a change to hurl.http.cookie_store can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.http.cookie_store uses a module listed above it, which is the healthy direction.
12→9 hurl.http.cookie_store uses hurl.http.url✕
- Connections
- 1 pair of types, where a type in hurl.http.cookie_store uses a type in hurl.http.url.
- The types involved
hurl.http.cookie_store.Cookie→hurl.http.url.Url
- Direction
- hurl.http.cookie_store uses hurl.http.url, so a change to hurl.http.url can break hurl.http.cookie_store, while a change to hurl.http.cookie_store can't break hurl.http.url.
- Position
- Below the diagonal: hurl.http.cookie_store uses a module listed above it, which is the healthy direction.
13→1 hurl.http.request_spec uses hurl.util.path✕
- Connections
- 2 pairs of types, where a type in hurl.http.request_spec uses a type in hurl.util.path.
- The types involved
hurl.http.request_spec.Body→hurl.util.path.ContextDirhurl.http.request_spec.MultipartParam→hurl.util.path.ContextDir
- Direction
- hurl.http.request_spec uses hurl.util.path, so a change to hurl.util.path can break hurl.http.request_spec, while a change to hurl.http.request_spec can't break hurl.util.path.
- Position
- Below the diagonal: hurl.http.request_spec uses a module listed above it, which is the healthy direction.
13→7 hurl.http.request_spec uses hurl.pretty.json✕
- Connections
- 3 pairs of types, where a type in hurl.http.request_spec uses a type in hurl.pretty.json.
- The types involved
hurl.http.request_spec.FileParam→hurl.pretty.json.Formatterhurl.http.request_spec.Method→hurl.pretty.json.Formatterhurl.http.request_spec.MultipartParam→hurl.pretty.json.Formatter
- Direction
- hurl.http.request_spec uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.http.request_spec, while a change to hurl.http.request_spec can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.http.request_spec uses a module listed above it, which is the healthy direction.
13→9 hurl.http.request_spec uses hurl.http.url✕
- Connections
- 1 pair of types, where a type in hurl.http.request_spec uses a type in hurl.http.url.
- The types involved
hurl.http.request_spec.RequestSpec→hurl.http.url.Url
- Direction
- hurl.http.request_spec uses hurl.http.url, so a change to hurl.http.url can break hurl.http.request_spec, while a change to hurl.http.request_spec can't break hurl.http.url.
- Position
- Below the diagonal: hurl.http.request_spec uses a module listed above it, which is the healthy direction.
13→24 hurl.http.request_spec uses hurl.http.curl_cmd part of a loop✕
- Connections
- 2 pairs of types, where a type in hurl.http.request_spec uses a type in hurl.http.curl_cmd.
- The types involved
hurl.http.request_spec.Body→hurl.http.curl_cmd.Arghurl.http.request_spec.Method→hurl.http.curl_cmd.Arg
- Direction
- hurl.http.request_spec uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.http.request_spec, while a change to hurl.http.request_spec can't break hurl.http.curl_cmd.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→25 hurl.http.request_spec uses hurl.http.header part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.request_spec uses a type in hurl.http.header.
- The types involved
hurl.http.request_spec.RequestSpec→hurl.http.header.HeaderVec
- Direction
- hurl.http.request_spec uses hurl.http.header, so a change to hurl.http.header can break hurl.http.request_spec, while a change to hurl.http.request_spec can't break hurl.http.header.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→27 hurl.http.request_spec uses hurl.http.request part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.request_spec uses a type in hurl.http.request.
- The types involved
hurl.http.request_spec.Method→hurl.http.request.FollowLocation
- Direction
- hurl.http.request_spec uses hurl.http.request, so a change to hurl.http.request can break hurl.http.request_spec, while a change to hurl.http.request_spec can't break hurl.http.request.
- 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→5 hurl.runner.error uses hurl_core.text.styledstring✕
- Connections
- 2 pairs of types, where a type in hurl.runner.error uses a type in hurl_core.text.styledstring.
- The types involved
hurl.runner.error.RunnerError→hurl_core.text.styledstring.StyledStringhurl.runner.error.error$module→hurl_core.text.styledstring.StyledString
- Direction
- hurl.runner.error uses hurl_core.text.styledstring, so a change to hurl_core.text.styledstring can break hurl.runner.error, while a change to hurl.runner.error can't break hurl_core.text.styledstring.
- Position
- Below the diagonal: hurl.runner.error uses a module listed above it, which is the healthy direction.
14→11 hurl.runner.error uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.runner.error uses a type in hurl_core.ast.primitive.
- The types involved
hurl.runner.error.RunnerError→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl.runner.error uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.runner.error, while a change to hurl.runner.error can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.runner.error uses a module listed above it, which is the healthy direction.
15→1 hurl.runner.output uses hurl.util.path✕
- Connections
- 1 pair of types, where a type in hurl.runner.output uses a type in hurl.util.path.
- The types involved
hurl.runner.output.Output→hurl.util.path.ContextDir
- Direction
- hurl.runner.output uses hurl.util.path, so a change to hurl.util.path can break hurl.runner.output, while a change to hurl.runner.output can't break hurl.util.path.
- Position
- Below the diagonal: hurl.runner.output uses a module listed above it, which is the healthy direction.
15→2 hurl.runner.output uses hurl.util.term✕
- Connections
- 1 pair of types, where a type in hurl.runner.output uses a type in hurl.util.term.
- The types involved
hurl.runner.output.Output→hurl.util.term.Stdout
- Direction
- hurl.runner.output uses hurl.util.term, so a change to hurl.util.term can break hurl.runner.output, while a change to hurl.runner.output can't break hurl.util.term.
- Position
- Below the diagonal: hurl.runner.output uses a module listed above it, which is the healthy direction.
15→7 hurl.runner.output uses hurl.pretty.json✕
- Connections
- 1 pair of types, where a type in hurl.runner.output uses a type in hurl.pretty.json.
- The types involved
hurl.runner.output.Output→hurl.pretty.json.Formatter
- Direction
- hurl.runner.output uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.runner.output, while a change to hurl.runner.output can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.runner.output uses a module listed above it, which is the healthy direction.
15→11 hurl.runner.output uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.runner.output uses a type in hurl_core.ast.primitive.
- The types involved
hurl.runner.output.Output→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl.runner.output uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.runner.output, while a change to hurl.runner.output can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.runner.output uses a module listed above it, which is the healthy direction.
16→10 hurl.runner.variable uses hurl.runner.value✕
- Connections
- 2 pairs of types, where a type in hurl.runner.variable uses a type in hurl.runner.value.
- The types involved
hurl.runner.variable.Variable→hurl.runner.value.Valuehurl.runner.variable.VariableSet→hurl.runner.value.Value
- Direction
- hurl.runner.variable uses hurl.runner.value, so a change to hurl.runner.value can break hurl.runner.variable, while a change to hurl.runner.variable can't break hurl.runner.value.
- Position
- Below the diagonal: hurl.runner.variable uses a module listed above it, which is the healthy direction.
17→6 hurl_core.ast.option uses hurl_core.types✕
- Connections
- 3 pairs of types, where a type in hurl_core.ast.option uses a type in hurl_core.types.
- The types involved
hurl_core.ast.option.Duration→hurl_core.types.DurationUnithurl_core.ast.option.VariableValue→hurl_core.types.SourceStringhurl_core.ast.option.VariableValue→hurl_core.types.ToSource
- Direction
- hurl_core.ast.option uses hurl_core.types, so a change to hurl_core.types can break hurl_core.ast.option, while a change to hurl_core.ast.option can't break hurl_core.types.
- Position
- Below the diagonal: hurl_core.ast.option uses a module listed above it, which is the healthy direction.
17→11 hurl_core.ast.option uses hurl_core.ast.primitive✕
- Connections
- 5 pairs of types, where a type in hurl_core.ast.option uses a type in hurl_core.ast.primitive.
- The types involved
hurl_core.ast.option.Duration→hurl_core.ast.primitive.U64hurl_core.ast.option.EntryOption→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.option.EntryOption→hurl_core.ast.primitive.Whitespacehurl_core.ast.option.VariableDefinition→hurl_core.ast.primitive.SourceInfohurl_core.ast.option.VariableDefinition→hurl_core.ast.primitive.Whitespace
- Direction
- hurl_core.ast.option uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl_core.ast.option, while a change to hurl_core.ast.option can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl_core.ast.option uses a module listed above it, which is the healthy direction.
18→6 hurl_core.ast.section uses hurl_core.types✕
- Connections
- 6 pairs of types, where a type in hurl_core.ast.section uses a type in hurl_core.types.
- The types involved
hurl_core.ast.section.CertificateAttributeName→hurl_core.types.SourceStringhurl_core.ast.section.CertificateAttributeName→hurl_core.types.ToSourcehurl_core.ast.section.CookiePath→hurl_core.types.SourceStringhurl_core.ast.section.CookiePath→hurl_core.types.ToSourcehurl_core.ast.section.PredicateFuncValue→hurl_core.types.SourceStringhurl_core.ast.section.PredicateFuncValue→hurl_core.types.ToSource
- Direction
- hurl_core.ast.section uses hurl_core.types, so a change to hurl_core.types can break hurl_core.ast.section, while a change to hurl_core.ast.section can't break hurl_core.types.
- Position
- Below the diagonal: hurl_core.ast.section uses a module listed above it, which is the healthy direction.
18→11 hurl_core.ast.section uses hurl_core.ast.primitive✕
- Connections
- 22 pairs of types, where a type in hurl_core.ast.section uses a type in hurl_core.ast.primitive.
- The types involved
hurl_core.ast.section.Assert→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.section.Assert→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.Capture→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.section.Capture→hurl_core.ast.primitive.Templatehurl_core.ast.section.Capture→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.Cookie→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.section.Cookie→hurl_core.ast.primitive.Templatehurl_core.ast.section.Cookie→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.CookieAttribute→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.CookiePath→hurl_core.ast.primitive.Templatehurl_core.ast.section.FilenameParam→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.section.FilenameParam→hurl_core.ast.primitive.Templatehurl_core.ast.section.FilenameParam→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.FilenameValue→hurl_core.ast.primitive.Templatehurl_core.ast.section.FilenameValue→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.Not→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.Predicate→hurl_core.ast.primitive.Whitespacehurl_core.ast.section.PredicateFunc→hurl_core.ast.primitive.SourceInfohurl_core.ast.section.Query→hurl_core.ast.primitive.SourceInfohurl_core.ast.section.Section→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.section.Section→hurl_core.ast.primitive.SourceInfohurl_core.ast.section.Section→hurl_core.ast.primitive.Whitespace
- Direction
- hurl_core.ast.section uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl_core.ast.section, while a change to hurl_core.ast.section can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl_core.ast.section uses a module listed above it, which is the healthy direction.
19→6 hurl.cli.options.env_vars uses hurl_core.types✕
- Connections
- 2 pairs of types, where a type in hurl.cli.options.env_vars uses a type in hurl_core.types.
- The types involved
hurl.cli.options.env_vars.env_vars$module→hurl_core.types.BytesPerSechurl.cli.options.env_vars.env_vars$module→hurl_core.types.Count
- Direction
- hurl.cli.options.env_vars uses hurl_core.types, so a change to hurl_core.types can break hurl.cli.options.env_vars, while a change to hurl.cli.options.env_vars can't break hurl_core.types.
- Position
- Below the diagonal: hurl.cli.options.env_vars uses a module listed above it, which is the healthy direction.
19→17 hurl.cli.options.env_vars uses hurl_core.ast.option✕
- Connections
- 1 pair of types, where a type in hurl.cli.options.env_vars uses a type in hurl_core.ast.option.
- The types involved
hurl.cli.options.env_vars.env_vars$module→hurl_core.ast.option.Duration
- Direction
- hurl.cli.options.env_vars uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.cli.options.env_vars, while a change to hurl.cli.options.env_vars can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.cli.options.env_vars uses a module listed above it, which is the healthy direction.
19→28 hurl.cli.options.env_vars uses hurl.cli.options part of a loop✕
- Connections
- 8 pairs of types, where a type in hurl.cli.options.env_vars uses a type in hurl.cli.options.
- The types involved
hurl.cli.options.env_vars.env_vars$module→hurl.cli.options.BoolOpthurl.cli.options.env_vars.env_vars$module→hurl.cli.options.CliOptionshurl.cli.options.env_vars.env_vars$module→hurl.cli.options.ErrorFormathurl.cli.options.env_vars.env_vars$module→hurl.cli.options.HttpVersionhurl.cli.options.env_vars.env_vars$module→hurl.cli.options.IpResolvehurl.cli.options.env_vars.env_vars$module→hurl.cli.options.OutputTypehurl.cli.options.env_vars.env_vars$module→hurl.cli.options.TlsVersionhurl.cli.options.env_vars.env_vars$module→hurl.cli.options.Verbosity
- Direction
- hurl.cli.options.env_vars uses hurl.cli.options, so a change to hurl.cli.options can break hurl.cli.options.env_vars, while a change to hurl.cli.options.env_vars can't break hurl.cli.options.
- 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→1 hurl.runner.runner_options uses hurl.util.path✕
- Connections
- 2 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl.util.path.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl.util.path.ContextDirhurl.runner.runner_options.RunnerOptionsBuilder→hurl.util.path.ContextDir
- Direction
- hurl.runner.runner_options uses hurl.util.path, so a change to hurl.util.path can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl.util.path.
- Position
- Below the diagonal: hurl.runner.runner_options uses a module listed above it, which is the healthy direction.
20→6 hurl.runner.runner_options uses hurl_core.types✕
- Connections
- 4 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl_core.types.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl_core.types.BytesPerSechurl.runner.runner_options.RunnerOptions→hurl_core.types.Counthurl.runner.runner_options.RunnerOptionsBuilder→hurl_core.types.BytesPerSechurl.runner.runner_options.RunnerOptionsBuilder→hurl_core.types.Count
- Direction
- hurl.runner.runner_options uses hurl_core.types, so a change to hurl_core.types can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl_core.types.
- Position
- Below the diagonal: hurl.runner.runner_options uses a module listed above it, which is the healthy direction.
20→15 hurl.runner.runner_options uses hurl.runner.output✕
- Connections
- 2 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl.runner.output.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl.runner.output.Outputhurl.runner.runner_options.RunnerOptionsBuilder→hurl.runner.output.Output
- Direction
- hurl.runner.runner_options uses hurl.runner.output, so a change to hurl.runner.output can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.runner.runner_options uses a module listed above it, which is the healthy direction.
20→17 hurl.runner.runner_options uses hurl_core.ast.option✕
- Connections
- 2 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl_core.ast.option.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl_core.ast.option.Durationhurl.runner.runner_options.RunnerOptionsBuilder→hurl_core.ast.option.Duration
- Direction
- hurl.runner.runner_options uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.runner.runner_options uses a module listed above it, which is the healthy direction.
20→25 hurl.runner.runner_options uses hurl.http.header part of a loop✕
- Connections
- 2 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl.http.header.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl.http.header.HeaderVechurl.runner.runner_options.RunnerOptionsBuilder→hurl.http.header.HeaderVec
- Direction
- hurl.runner.runner_options uses hurl.http.header, so a change to hurl.http.header can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl.http.header.
- 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 hurl.runner.runner_options uses hurl.http.request part of a loop✕
- Connections
- 4 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl.http.request.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl.http.request.FollowLocationhurl.runner.runner_options.RunnerOptions→hurl.http.request.RequestedHttpVersionhurl.runner.runner_options.RunnerOptionsBuilder→hurl.http.request.FollowLocationhurl.runner.runner_options.RunnerOptionsBuilder→hurl.http.request.RequestedHttpVersion
- Direction
- hurl.runner.runner_options uses hurl.http.request, so a change to hurl.http.request can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl.http.request.
- 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→28 hurl.runner.runner_options uses hurl.cli.options part of a loop✕
- Connections
- 4 pairs of types, where a type in hurl.runner.runner_options uses a type in hurl.cli.options.
- The types involved
hurl.runner.runner_options.RunnerOptions→hurl.cli.options.IpResolvehurl.runner.runner_options.RunnerOptions→hurl.cli.options.TlsVersionhurl.runner.runner_options.RunnerOptionsBuilder→hurl.cli.options.IpResolvehurl.runner.runner_options.RunnerOptionsBuilder→hurl.cli.options.TlsVersion
- Direction
- hurl.runner.runner_options uses hurl.cli.options, so a change to hurl.cli.options can break hurl.runner.runner_options, while a change to hurl.runner.runner_options can't break hurl.cli.options.
- 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→6 hurl_core.ast.core uses hurl_core.types✕
- Connections
- 6 pairs of types, where a type in hurl_core.ast.core uses a type in hurl_core.types.
- The types involved
hurl_core.ast.core.Method→hurl_core.types.SourceStringhurl_core.ast.core.Method→hurl_core.types.ToSourcehurl_core.ast.core.StatusValue→hurl_core.types.SourceStringhurl_core.ast.core.StatusValue→hurl_core.types.ToSourcehurl_core.ast.core.VersionValue→hurl_core.types.SourceStringhurl_core.ast.core.VersionValue→hurl_core.types.ToSource
- Direction
- hurl_core.ast.core uses hurl_core.types, so a change to hurl_core.types can break hurl_core.ast.core, while a change to hurl_core.ast.core can't break hurl_core.types.
- Position
- Below the diagonal: hurl_core.ast.core uses a module listed above it, which is the healthy direction.
21→11 hurl_core.ast.core uses hurl_core.ast.primitive✕
- Connections
- 17 pairs of types, where a type in hurl_core.ast.core uses a type in hurl_core.ast.primitive.
- The types involved
hurl_core.ast.core.Body→hurl_core.ast.primitive.Byteshurl_core.ast.core.Body→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.core.Body→hurl_core.ast.primitive.Whitespacehurl_core.ast.core.Entry→hurl_core.ast.primitive.SourceInfohurl_core.ast.core.Filter→hurl_core.ast.primitive.SourceInfohurl_core.ast.core.HurlFile→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.core.Request→hurl_core.ast.primitive.KeyValuehurl_core.ast.core.Request→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.core.Request→hurl_core.ast.primitive.SourceInfohurl_core.ast.core.Request→hurl_core.ast.primitive.Templatehurl_core.ast.core.Request→hurl_core.ast.primitive.Whitespacehurl_core.ast.core.Response→hurl_core.ast.primitive.KeyValuehurl_core.ast.core.Response→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.core.Response→hurl_core.ast.primitive.SourceInfohurl_core.ast.core.Response→hurl_core.ast.primitive.Whitespacehurl_core.ast.core.Status→hurl_core.ast.primitive.SourceInfohurl_core.ast.core.Version→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl_core.ast.core uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl_core.ast.core, while a change to hurl_core.ast.core can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl_core.ast.core uses a module listed above it, which is the healthy direction.
21→18 hurl_core.ast.core uses hurl_core.ast.section✕
- Connections
- 2 pairs of types, where a type in hurl_core.ast.core uses a type in hurl_core.ast.section.
- The types involved
hurl_core.ast.core.Request→hurl_core.ast.section.Sectionhurl_core.ast.core.Response→hurl_core.ast.section.Section
- Direction
- hurl_core.ast.core uses hurl_core.ast.section, so a change to hurl_core.ast.section can break hurl_core.ast.core, while a change to hurl_core.ast.core can't break hurl_core.ast.section.
- Position
- Below the diagonal: hurl_core.ast.core uses a module listed above it, which is the healthy direction.
22→6 hurl.http.options uses hurl_core.types✕
- Connections
- 2 pairs of types, where a type in hurl.http.options uses a type in hurl_core.types.
- The types involved
hurl.http.options.ClientOptions→hurl_core.types.BytesPerSechurl.http.options.ClientOptions→hurl_core.types.Count
- Direction
- hurl.http.options uses hurl_core.types, so a change to hurl_core.types can break hurl.http.options, while a change to hurl.http.options can't break hurl_core.types.
- Position
- Below the diagonal: hurl.http.options uses a module listed above it, which is the healthy direction.
22→17 hurl.http.options uses hurl_core.ast.option✕
- Connections
- 1 pair of types, where a type in hurl.http.options uses a type in hurl_core.ast.option.
- The types involved
hurl.http.options.ClientOptions→hurl_core.ast.option.Duration
- Direction
- hurl.http.options uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.http.options, while a change to hurl.http.options can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.http.options uses a module listed above it, which is the healthy direction.
22→20 hurl.http.options uses hurl.runner.runner_options✕
- Connections
- 1 pair of types, where a type in hurl.http.options uses a type in hurl.runner.runner_options.
- The types involved
hurl.http.options.ClientOptions→hurl.runner.runner_options.RunnerOptions
- Direction
- hurl.http.options uses hurl.runner.runner_options, so a change to hurl.runner.runner_options can break hurl.http.options, while a change to hurl.http.options can't break hurl.runner.runner_options.
- Position
- Below the diagonal: hurl.http.options uses a module listed above it, which is the healthy direction.
22→24 hurl.http.options uses hurl.http.curl_cmd part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.options uses a type in hurl.http.curl_cmd.
- The types involved
hurl.http.options.ClientOptions→hurl.http.curl_cmd.Arg
- Direction
- hurl.http.options uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.http.options, while a change to hurl.http.options can't break hurl.http.curl_cmd.
- 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→25 hurl.http.options uses hurl.http.header part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.options uses a type in hurl.http.header.
- The types involved
hurl.http.options.ClientOptions→hurl.http.header.HeaderVec
- Direction
- hurl.http.options uses hurl.http.header, so a change to hurl.http.header can break hurl.http.options, while a change to hurl.http.options can't break hurl.http.header.
- 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 hurl.http.options uses hurl.http.request part of a loop✕
- Connections
- 2 pairs of types, where a type in hurl.http.options uses a type in hurl.http.request.
- The types involved
hurl.http.options.ClientOptions→hurl.http.request.FollowLocationhurl.http.options.ClientOptions→hurl.http.request.RequestedHttpVersion
- Direction
- hurl.http.options uses hurl.http.request, so a change to hurl.http.request can break hurl.http.options, while a change to hurl.http.options can't break hurl.http.request.
- 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→28 hurl.http.options uses hurl.cli.options part of a loop✕
- Connections
- 3 pairs of types, where a type in hurl.http.options uses a type in hurl.cli.options.
- The types involved
hurl.http.options.ClientOptions→hurl.cli.options.IpResolvehurl.http.options.ClientOptions→hurl.cli.options.TlsVersionhurl.http.options.ClientOptions→hurl.cli.options.Verbosity
- Direction
- hurl.http.options uses hurl.cli.options, so a change to hurl.cli.options can break hurl.http.options, while a change to hurl.http.options can't break hurl.cli.options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→6 hurl_core.ast.visit uses hurl_core.types✕
- Connections
- 4 pairs of types, where a type in hurl_core.ast.visit uses a type in hurl_core.types.
- The types involved
hurl_core.ast.visit.Visitor→hurl_core.types.Counthurl_core.ast.visit.Visitor→hurl_core.types.DurationUnithurl_core.ast.visit.Visitor→hurl_core.types.SourceStringhurl_core.ast.visit.visit$module→hurl_core.types.Count
- Direction
- hurl_core.ast.visit uses hurl_core.types, so a change to hurl_core.types can break hurl_core.ast.visit, while a change to hurl_core.ast.visit can't break hurl_core.types.
- Position
- Below the diagonal: hurl_core.ast.visit uses a module listed above it, which is the healthy direction.
23→8 hurl_core.ast.visit uses hurl_core.ast.json✕
- Connections
- 1 pair of types, where a type in hurl_core.ast.visit uses a type in hurl_core.ast.json.
- The types involved
hurl_core.ast.visit.Visitor→hurl_core.ast.json.JsonValue
- Direction
- hurl_core.ast.visit uses hurl_core.ast.json, so a change to hurl_core.ast.json can break hurl_core.ast.visit, while a change to hurl_core.ast.visit can't break hurl_core.ast.json.
- Position
- Below the diagonal: hurl_core.ast.visit uses a module listed above it, which is the healthy direction.
23→11 hurl_core.ast.visit uses hurl_core.ast.primitive✕
- Connections
- 18 pairs of types, where a type in hurl_core.ast.visit uses a type in hurl_core.ast.primitive.
- The types involved
hurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Base64hurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Commenthurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Filehurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Hexhurl_core.ast.visit.Visitor→hurl_core.ast.primitive.KeyValuehurl_core.ast.visit.Visitor→hurl_core.ast.primitive.LineTerminatorhurl_core.ast.visit.Visitor→hurl_core.ast.primitive.MultilineStringhurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Numberhurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Placeholderhurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Regexhurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Templatehurl_core.ast.visit.Visitor→hurl_core.ast.primitive.U64hurl_core.ast.visit.Visitor→hurl_core.ast.primitive.Whitespacehurl_core.ast.visit.visit$module→hurl_core.ast.primitive.Base64hurl_core.ast.visit.visit$module→hurl_core.ast.primitive.Filehurl_core.ast.visit.visit$module→hurl_core.ast.primitive.Hexhurl_core.ast.visit.visit$module→hurl_core.ast.primitive.KeyValuehurl_core.ast.visit.visit$module→hurl_core.ast.primitive.LineTerminator
- Direction
- hurl_core.ast.visit uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl_core.ast.visit, while a change to hurl_core.ast.visit can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl_core.ast.visit uses a module listed above it, which is the healthy direction.
23→17 hurl_core.ast.visit uses hurl_core.ast.option✕
- Connections
- 18 pairs of types, where a type in hurl_core.ast.visit uses a type in hurl_core.ast.option.
- The types involved
hurl_core.ast.visit.Visitor→hurl_core.ast.option.BooleanOptionhurl_core.ast.visit.Visitor→hurl_core.ast.option.CountOptionhurl_core.ast.visit.Visitor→hurl_core.ast.option.Durationhurl_core.ast.visit.Visitor→hurl_core.ast.option.DurationOptionhurl_core.ast.visit.Visitor→hurl_core.ast.option.EntryOptionhurl_core.ast.visit.Visitor→hurl_core.ast.option.NaturalOptionhurl_core.ast.visit.Visitor→hurl_core.ast.option.VariableDefinitionhurl_core.ast.visit.Visitor→hurl_core.ast.option.VariableValuehurl_core.ast.visit.Visitor→hurl_core.ast.option.VerbosityOptionhurl_core.ast.visit.visit$module→hurl_core.ast.option.BooleanOptionhurl_core.ast.visit.visit$module→hurl_core.ast.option.CountOptionhurl_core.ast.visit.visit$module→hurl_core.ast.option.Durationhurl_core.ast.visit.visit$module→hurl_core.ast.option.DurationOptionhurl_core.ast.visit.visit$module→hurl_core.ast.option.EntryOptionhurl_core.ast.visit.visit$module→hurl_core.ast.option.NaturalOptionhurl_core.ast.visit.visit$module→hurl_core.ast.option.VariableDefinitionhurl_core.ast.visit.visit$module→hurl_core.ast.option.VariableValuehurl_core.ast.visit.visit$module→hurl_core.ast.option.VerbosityOption
- Direction
- hurl_core.ast.visit uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl_core.ast.visit, while a change to hurl_core.ast.visit can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl_core.ast.visit uses a module listed above it, which is the healthy direction.
23→18 hurl_core.ast.visit uses hurl_core.ast.section✕
- Connections
- 23 pairs of types, where a type in hurl_core.ast.visit uses a type in hurl_core.ast.section.
- The types involved
hurl_core.ast.visit.Visitor→hurl_core.ast.section.Asserthurl_core.ast.visit.Visitor→hurl_core.ast.section.Capturehurl_core.ast.visit.Visitor→hurl_core.ast.section.Cookiehurl_core.ast.visit.Visitor→hurl_core.ast.section.CookiePathhurl_core.ast.visit.Visitor→hurl_core.ast.section.FilenameParamhurl_core.ast.visit.Visitor→hurl_core.ast.section.FilenameValuehurl_core.ast.visit.Visitor→hurl_core.ast.section.Predicatehurl_core.ast.visit.Visitor→hurl_core.ast.section.PredicateFuncValuehurl_core.ast.visit.Visitor→hurl_core.ast.section.PredicateValuehurl_core.ast.visit.Visitor→hurl_core.ast.section.Queryhurl_core.ast.visit.Visitor→hurl_core.ast.section.QueryValuehurl_core.ast.visit.Visitor→hurl_core.ast.section.Sectionhurl_core.ast.visit.Visitor→hurl_core.ast.section.SectionValuehurl_core.ast.visit.visit$module→hurl_core.ast.section.Asserthurl_core.ast.visit.visit$module→hurl_core.ast.section.Capturehurl_core.ast.visit.visit$module→hurl_core.ast.section.Cookiehurl_core.ast.visit.visit$module→hurl_core.ast.section.FilenameParamhurl_core.ast.visit.visit$module→hurl_core.ast.section.FilenameValuehurl_core.ast.visit.visit$module→hurl_core.ast.section.Predicatehurl_core.ast.visit.visit$module→hurl_core.ast.section.PredicateValuehurl_core.ast.visit.visit$module→hurl_core.ast.section.Queryhurl_core.ast.visit.visit$module→hurl_core.ast.section.Sectionhurl_core.ast.visit.visit$module→hurl_core.ast.section.SectionValue
- Direction
- hurl_core.ast.visit uses hurl_core.ast.section, so a change to hurl_core.ast.section can break hurl_core.ast.visit, while a change to hurl_core.ast.visit can't break hurl_core.ast.section.
- Position
- Below the diagonal: hurl_core.ast.visit uses a module listed above it, which is the healthy direction.
23→21 hurl_core.ast.visit uses hurl_core.ast.core✕
- Connections
- 18 pairs of types, where a type in hurl_core.ast.visit uses a type in hurl_core.ast.core.
- The types involved
hurl_core.ast.visit.Visitor→hurl_core.ast.core.Bodyhurl_core.ast.visit.Visitor→hurl_core.ast.core.Entryhurl_core.ast.visit.Visitor→hurl_core.ast.core.Filterhurl_core.ast.visit.Visitor→hurl_core.ast.core.FilterValuehurl_core.ast.visit.Visitor→hurl_core.ast.core.HurlFilehurl_core.ast.visit.Visitor→hurl_core.ast.core.IntegerValuehurl_core.ast.visit.Visitor→hurl_core.ast.core.Methodhurl_core.ast.visit.Visitor→hurl_core.ast.core.Requesthurl_core.ast.visit.Visitor→hurl_core.ast.core.Responsehurl_core.ast.visit.Visitor→hurl_core.ast.core.StatusValuehurl_core.ast.visit.Visitor→hurl_core.ast.core.VersionValuehurl_core.ast.visit.visit$module→hurl_core.ast.core.Bodyhurl_core.ast.visit.visit$module→hurl_core.ast.core.Entryhurl_core.ast.visit.visit$module→hurl_core.ast.core.Filterhurl_core.ast.visit.visit$module→hurl_core.ast.core.HurlFilehurl_core.ast.visit.visit$module→hurl_core.ast.core.IntegerValuehurl_core.ast.visit.visit$module→hurl_core.ast.core.Requesthurl_core.ast.visit.visit$module→hurl_core.ast.core.Response
- Direction
- hurl_core.ast.visit uses hurl_core.ast.core, so a change to hurl_core.ast.core can break hurl_core.ast.visit, while a change to hurl_core.ast.visit can't break hurl_core.ast.core.
- Position
- Below the diagonal: hurl_core.ast.visit uses a module listed above it, which is the healthy direction.
24→1 hurl.http.curl_cmd uses hurl.util.path✕
- Connections
- 2 pairs of types, where a type in hurl.http.curl_cmd uses a type in hurl.util.path.
- The types involved
hurl.http.curl_cmd.CurlCmd→hurl.util.path.ContextDirhurl.http.curl_cmd.curl_cmd$module→hurl.util.path.ContextDir
- Direction
- hurl.http.curl_cmd uses hurl.util.path, so a change to hurl.util.path can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.util.path.
- Position
- Below the diagonal: hurl.http.curl_cmd uses a module listed above it, which is the healthy direction.
24→12 hurl.http.curl_cmd uses hurl.http.cookie_store✕
- Connections
- 2 pairs of types, where a type in hurl.http.curl_cmd uses a type in hurl.http.cookie_store.
- The types involved
hurl.http.curl_cmd.CurlCmd→hurl.http.cookie_store.CookieStorehurl.http.curl_cmd.curl_cmd$module→hurl.http.cookie_store.CookieStore
- Direction
- hurl.http.curl_cmd uses hurl.http.cookie_store, so a change to hurl.http.cookie_store can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.http.cookie_store.
- Position
- Below the diagonal: hurl.http.curl_cmd uses a module listed above it, which is the healthy direction.
24→13 hurl.http.curl_cmd uses hurl.http.request_spec✕
- Connections
- 3 pairs of types, where a type in hurl.http.curl_cmd uses a type in hurl.http.request_spec.
- The types involved
hurl.http.curl_cmd.CurlCmd→hurl.http.request_spec.RequestSpechurl.http.curl_cmd.curl_cmd$module→hurl.http.request_spec.Bodyhurl.http.curl_cmd.curl_cmd$module→hurl.http.request_spec.RequestSpec
- Direction
- hurl.http.curl_cmd uses hurl.http.request_spec, so a change to hurl.http.request_spec can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.http.request_spec.
- Position
- Below the diagonal: hurl.http.curl_cmd uses a module listed above it, which is the healthy direction.
24→15 hurl.http.curl_cmd uses hurl.runner.output✕
- Connections
- 2 pairs of types, where a type in hurl.http.curl_cmd uses a type in hurl.runner.output.
- The types involved
hurl.http.curl_cmd.CurlCmd→hurl.runner.output.Outputhurl.http.curl_cmd.curl_cmd$module→hurl.runner.output.Output
- Direction
- hurl.http.curl_cmd uses hurl.runner.output, so a change to hurl.runner.output can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.http.curl_cmd uses a module listed above it, which is the healthy direction.
24→22 hurl.http.curl_cmd uses hurl.http.options✕
- Connections
- 2 pairs of types, where a type in hurl.http.curl_cmd uses a type in hurl.http.options.
- The types involved
hurl.http.curl_cmd.CurlCmd→hurl.http.options.ClientOptionshurl.http.curl_cmd.curl_cmd$module→hurl.http.options.ClientOptions
- Direction
- hurl.http.curl_cmd uses hurl.http.options, so a change to hurl.http.options can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.http.options.
- Position
- Below the diagonal: hurl.http.curl_cmd uses a module listed above it, which is the healthy direction.
24→25 hurl.http.curl_cmd uses hurl.http.header part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.curl_cmd uses a type in hurl.http.header.
- The types involved
hurl.http.curl_cmd.curl_cmd$module→hurl.http.header.HeaderVec
- Direction
- hurl.http.curl_cmd uses hurl.http.header, so a change to hurl.http.header can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.http.header.
- 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→27 hurl.http.curl_cmd uses hurl.http.request part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.curl_cmd uses a type in hurl.http.request.
- The types involved
hurl.http.curl_cmd.curl_cmd$module→hurl.http.request.FollowLocation
- Direction
- hurl.http.curl_cmd uses hurl.http.request, so a change to hurl.http.request can break hurl.http.curl_cmd, while a change to hurl.http.curl_cmd can't break hurl.http.request.
- 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.
25→7 hurl.http.header uses hurl.pretty.json✕
- Connections
- 1 pair of types, where a type in hurl.http.header uses a type in hurl.pretty.json.
- The types involved
hurl.http.header.Header→hurl.pretty.json.Formatter
- Direction
- hurl.http.header uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.http.header, while a change to hurl.http.header can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.http.header uses a module listed above it, which is the healthy direction.
25→24 hurl.http.header uses hurl.http.curl_cmd✕
- Connections
- 1 pair of types, where a type in hurl.http.header uses a type in hurl.http.curl_cmd.
- The types involved
hurl.http.header.Header→hurl.http.curl_cmd.Arg
- Direction
- hurl.http.header uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.http.header, while a change to hurl.http.header can't break hurl.http.curl_cmd.
- Position
- Below the diagonal: hurl.http.header uses a module listed above it, which is the healthy direction.
26→2 hurl.util.logger uses hurl.util.term✕
- Connections
- 1 pair of types, where a type in hurl.util.logger uses a type in hurl.util.term.
- The types involved
hurl.util.logger.Logger→hurl.util.term.Stderr
- Direction
- hurl.util.logger uses hurl.util.term, so a change to hurl.util.term can break hurl.util.logger, while a change to hurl.util.logger can't break hurl.util.term.
- Position
- Below the diagonal: hurl.util.logger uses a module listed above it, which is the healthy direction.
26→3 hurl.util.logger uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.util.logger uses a type in hurl_core.input.
- The types involved
hurl.util.logger.Logger→hurl_core.input.Input
- Direction
- hurl.util.logger uses hurl_core.input, so a change to hurl_core.input can break hurl.util.logger, while a change to hurl.util.logger can't break hurl_core.input.
- Position
- Below the diagonal: hurl.util.logger uses a module listed above it, which is the healthy direction.
26→10 hurl.util.logger uses hurl.runner.value✕
- Connections
- 1 pair of types, where a type in hurl.util.logger uses a type in hurl.runner.value.
- The types involved
hurl.util.logger.Logger→hurl.runner.value.Value
- Direction
- hurl.util.logger uses hurl.runner.value, so a change to hurl.runner.value can break hurl.util.logger, while a change to hurl.util.logger can't break hurl.runner.value.
- Position
- Below the diagonal: hurl.util.logger uses a module listed above it, which is the healthy direction.
26→11 hurl.util.logger uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.util.logger uses a type in hurl_core.ast.primitive.
- The types involved
hurl.util.logger.Logger→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl.util.logger uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.util.logger, while a change to hurl.util.logger can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.util.logger uses a module listed above it, which is the healthy direction.
26→24 hurl.util.logger uses hurl.http.curl_cmd✕
- Connections
- 1 pair of types, where a type in hurl.util.logger uses a type in hurl.http.curl_cmd.
- The types involved
hurl.util.logger.Logger→hurl.http.curl_cmd.CurlCmd
- Direction
- hurl.util.logger uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.util.logger, while a change to hurl.util.logger can't break hurl.http.curl_cmd.
- Position
- Below the diagonal: hurl.util.logger uses a module listed above it, which is the healthy direction.
26→28 hurl.util.logger uses hurl.cli.options part of a loop✕
- Connections
- 6 pairs of types, where a type in hurl.util.logger uses a type in hurl.cli.options.
- The types involved
hurl.util.logger.Logger→hurl.cli.options.ErrorFormathurl.util.logger.Logger→hurl.cli.options.Verbosityhurl.util.logger.LoggerOptions→hurl.cli.options.ErrorFormathurl.util.logger.LoggerOptions→hurl.cli.options.Verbosityhurl.util.logger.LoggerOptionsBuilder→hurl.cli.options.ErrorFormathurl.util.logger.LoggerOptionsBuilder→hurl.cli.options.Verbosity
- Direction
- hurl.util.logger uses hurl.cli.options, so a change to hurl.cli.options can break hurl.util.logger, while a change to hurl.util.logger can't break hurl.cli.options.
- 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→7 hurl.http.request uses hurl.pretty.json✕
- Connections
- 2 pairs of types, where a type in hurl.http.request uses a type in hurl.pretty.json.
- The types involved
hurl.http.request.RequestedHttpVersion→hurl.pretty.json.Formatterhurl.http.request.TlsVersion→hurl.pretty.json.Formatter
- Direction
- hurl.http.request uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.http.request, while a change to hurl.http.request can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.http.request uses a module listed above it, which is the healthy direction.
27→9 hurl.http.request uses hurl.http.url✕
- Connections
- 1 pair of types, where a type in hurl.http.request uses a type in hurl.http.url.
- The types involved
hurl.http.request.Request→hurl.http.url.Url
- Direction
- hurl.http.request uses hurl.http.url, so a change to hurl.http.url can break hurl.http.request, while a change to hurl.http.request can't break hurl.http.url.
- Position
- Below the diagonal: hurl.http.request uses a module listed above it, which is the healthy direction.
27→25 hurl.http.request uses hurl.http.header✕
- Connections
- 1 pair of types, where a type in hurl.http.request uses a type in hurl.http.header.
- The types involved
hurl.http.request.Request→hurl.http.header.HeaderVec
- Direction
- hurl.http.request uses hurl.http.header, so a change to hurl.http.header can break hurl.http.request, while a change to hurl.http.request can't break hurl.http.header.
- Position
- Below the diagonal: hurl.http.request uses a module listed above it, which is the healthy direction.
27→28 hurl.http.request uses hurl.cli.options part of a loop✕
- Connections
- 1 pair of types, where a type in hurl.http.request uses a type in hurl.cli.options.
- The types involved
hurl.http.request.RequestedHttpVersion→hurl.cli.options.HttpVersion
- Direction
- hurl.http.request uses hurl.cli.options, so a change to hurl.cli.options can break hurl.http.request, while a change to hurl.http.request can't break hurl.cli.options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→3 hurl.cli.options uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.cli.options uses a type in hurl_core.input.
- The types involved
hurl.cli.options.CliOptions→hurl_core.input.Input
- Direction
- hurl.cli.options uses hurl_core.input, so a change to hurl_core.input can break hurl.cli.options, while a change to hurl.cli.options can't break hurl_core.input.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
28→6 hurl.cli.options uses hurl_core.types✕
- Connections
- 2 pairs of types, where a type in hurl.cli.options uses a type in hurl_core.types.
- The types involved
hurl.cli.options.CliOptions→hurl_core.types.BytesPerSechurl.cli.options.CliOptions→hurl_core.types.Count
- Direction
- hurl.cli.options uses hurl_core.types, so a change to hurl_core.types can break hurl.cli.options, while a change to hurl.cli.options can't break hurl_core.types.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
28→15 hurl.cli.options uses hurl.runner.output✕
- Connections
- 1 pair of types, where a type in hurl.cli.options uses a type in hurl.runner.output.
- The types involved
hurl.cli.options.CliOptions→hurl.runner.output.Output
- Direction
- hurl.cli.options uses hurl.runner.output, so a change to hurl.runner.output can break hurl.cli.options, while a change to hurl.cli.options can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
28→17 hurl.cli.options uses hurl_core.ast.option✕
- Connections
- 1 pair of types, where a type in hurl.cli.options uses a type in hurl_core.ast.option.
- The types involved
hurl.cli.options.CliOptions→hurl_core.ast.option.Duration
- Direction
- hurl.cli.options uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.cli.options, while a change to hurl.cli.options can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
28→19 hurl.cli.options uses hurl.cli.options.env_vars✕
- Connections
- 1 pair of types, where a type in hurl.cli.options uses a type in hurl.cli.options.env_vars.
- The types involved
hurl.cli.options.options$module→hurl.cli.options.env_vars.EnvVars
- Direction
- hurl.cli.options uses hurl.cli.options.env_vars, so a change to hurl.cli.options.env_vars can break hurl.cli.options, while a change to hurl.cli.options can't break hurl.cli.options.env_vars.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
28→26 hurl.cli.options uses hurl.util.logger✕
- Connections
- 1 pair of types, where a type in hurl.cli.options uses a type in hurl.util.logger.
- The types involved
hurl.cli.options.CliOptions→hurl.util.logger.LoggerOptions
- Direction
- hurl.cli.options uses hurl.util.logger, so a change to hurl.util.logger can break hurl.cli.options, while a change to hurl.cli.options can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
28→27 hurl.cli.options uses hurl.http.request✕
- Connections
- 1 pair of types, where a type in hurl.cli.options uses a type in hurl.http.request.
- The types involved
hurl.cli.options.HttpVersion→hurl.http.request.RequestedHttpVersion
- Direction
- hurl.cli.options uses hurl.http.request, so a change to hurl.http.request can break hurl.cli.options, while a change to hurl.cli.options can't break hurl.http.request.
- Position
- Below the diagonal: hurl.cli.options uses a module listed above it, which is the healthy direction.
29→3 hurl.cli.options.args uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.cli.options.args uses a type in hurl_core.input.
- The types involved
hurl.cli.options.args.args$module→hurl_core.input.Input
- Direction
- hurl.cli.options.args uses hurl_core.input, so a change to hurl_core.input can break hurl.cli.options.args, while a change to hurl.cli.options.args can't break hurl_core.input.
- Position
- Below the diagonal: hurl.cli.options.args uses a module listed above it, which is the healthy direction.
29→6 hurl.cli.options.args uses hurl_core.types✕
- Connections
- 2 pairs of types, where a type in hurl.cli.options.args uses a type in hurl_core.types.
- The types involved
hurl.cli.options.args.args$module→hurl_core.types.BytesPerSechurl.cli.options.args.args$module→hurl_core.types.Count
- Direction
- hurl.cli.options.args uses hurl_core.types, so a change to hurl_core.types can break hurl.cli.options.args, while a change to hurl.cli.options.args can't break hurl_core.types.
- Position
- Below the diagonal: hurl.cli.options.args uses a module listed above it, which is the healthy direction.
29→15 hurl.cli.options.args uses hurl.runner.output✕
- Connections
- 1 pair of types, where a type in hurl.cli.options.args uses a type in hurl.runner.output.
- The types involved
hurl.cli.options.args.args$module→hurl.runner.output.Output
- Direction
- hurl.cli.options.args uses hurl.runner.output, so a change to hurl.runner.output can break hurl.cli.options.args, while a change to hurl.cli.options.args can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.cli.options.args uses a module listed above it, which is the healthy direction.
29→17 hurl.cli.options.args uses hurl_core.ast.option✕
- Connections
- 1 pair of types, where a type in hurl.cli.options.args uses a type in hurl_core.ast.option.
- The types involved
hurl.cli.options.args.args$module→hurl_core.ast.option.Duration
- Direction
- hurl.cli.options.args uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.cli.options.args, while a change to hurl.cli.options.args can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.cli.options.args uses a module listed above it, which is the healthy direction.
29→28 hurl.cli.options.args uses hurl.cli.options✕
- Connections
- 8 pairs of types, where a type in hurl.cli.options.args uses a type in hurl.cli.options.
- The types involved
hurl.cli.options.args.args$module→hurl.cli.options.BoolOpthurl.cli.options.args.args$module→hurl.cli.options.CliOptionshurl.cli.options.args.args$module→hurl.cli.options.ErrorFormathurl.cli.options.args.args$module→hurl.cli.options.HttpVersionhurl.cli.options.args.args$module→hurl.cli.options.IpResolvehurl.cli.options.args.args$module→hurl.cli.options.OutputTypehurl.cli.options.args.args$module→hurl.cli.options.TlsVersionhurl.cli.options.args.args$module→hurl.cli.options.Verbosity
- Direction
- hurl.cli.options.args uses hurl.cli.options, so a change to hurl.cli.options can break hurl.cli.options.args, while a change to hurl.cli.options.args can't break hurl.cli.options.
- Position
- Below the diagonal: hurl.cli.options.args uses a module listed above it, which is the healthy direction.
30→7 hurl.http.response uses hurl.pretty.json✕
- Connections
- 1 pair of types, where a type in hurl.http.response uses a type in hurl.pretty.json.
- The types involved
hurl.http.response.HttpVersion→hurl.pretty.json.Formatter
- Direction
- hurl.http.response uses hurl.pretty.json, so a change to hurl.pretty.json can break hurl.http.response, while a change to hurl.http.response can't break hurl.pretty.json.
- Position
- Below the diagonal: hurl.http.response uses a module listed above it, which is the healthy direction.
30→9 hurl.http.response uses hurl.http.url✕
- Connections
- 1 pair of types, where a type in hurl.http.response uses a type in hurl.http.url.
- The types involved
hurl.http.response.Response→hurl.http.url.Url
- Direction
- hurl.http.response uses hurl.http.url, so a change to hurl.http.url can break hurl.http.response, while a change to hurl.http.response can't break hurl.http.url.
- Position
- Below the diagonal: hurl.http.response uses a module listed above it, which is the healthy direction.
30→17 hurl.http.response uses hurl_core.ast.option✕
- Connections
- 1 pair of types, where a type in hurl.http.response uses a type in hurl_core.ast.option.
- The types involved
hurl.http.response.Response→hurl_core.ast.option.Duration
- Direction
- hurl.http.response uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.http.response, while a change to hurl.http.response can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.http.response uses a module listed above it, which is the healthy direction.
30→25 hurl.http.response uses hurl.http.header✕
- Connections
- 1 pair of types, where a type in hurl.http.response uses a type in hurl.http.header.
- The types involved
hurl.http.response.Response→hurl.http.header.HeaderVec
- Direction
- hurl.http.response uses hurl.http.header, so a change to hurl.http.header can break hurl.http.response, while a change to hurl.http.response can't break hurl.http.header.
- Position
- Below the diagonal: hurl.http.response uses a module listed above it, which is the healthy direction.
30→26 hurl.http.response uses hurl.util.logger✕
- Connections
- 1 pair of types, where a type in hurl.http.response uses a type in hurl.util.logger.
- The types involved
hurl.http.response.Response→hurl.util.logger.Logger
- Direction
- hurl.http.response uses hurl.util.logger, so a change to hurl.util.logger can break hurl.http.response, while a change to hurl.http.response can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.http.response uses a module listed above it, which is the healthy direction.
30→28 hurl.http.response uses hurl.cli.options✕
- Connections
- 1 pair of types, where a type in hurl.http.response uses a type in hurl.cli.options.
- The types involved
hurl.http.response.Response→hurl.cli.options.HttpVersion
- Direction
- hurl.http.response uses hurl.cli.options, so a change to hurl.cli.options can break hurl.http.response, while a change to hurl.http.response can't break hurl.cli.options.
- Position
- Below the diagonal: hurl.http.response uses a module listed above it, which is the healthy direction.
31→6 hurl.runner.options uses hurl_core.types✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl_core.types.
- The types involved
hurl.runner.options.options$module→hurl_core.types.DurationUnit
- Direction
- hurl.runner.options uses hurl_core.types, so a change to hurl_core.types can break hurl.runner.options, while a change to hurl.runner.options can't break hurl_core.types.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→10 hurl.runner.options uses hurl.runner.value✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl.runner.value.
- The types involved
hurl.runner.options.options$module→hurl.runner.value.Value
- Direction
- hurl.runner.options uses hurl.runner.value, so a change to hurl.runner.value can break hurl.runner.options, while a change to hurl.runner.options can't break hurl.runner.value.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→11 hurl.runner.options uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl_core.ast.primitive.
- The types involved
hurl.runner.options.options$module→hurl_core.ast.primitive.Template
- Direction
- hurl.runner.options uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.runner.options, while a change to hurl.runner.options can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→16 hurl.runner.options uses hurl.runner.variable✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl.runner.variable.
- The types involved
hurl.runner.options.options$module→hurl.runner.variable.VariableSet
- Direction
- hurl.runner.options uses hurl.runner.variable, so a change to hurl.runner.variable can break hurl.runner.options, while a change to hurl.runner.options can't break hurl.runner.variable.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→17 hurl.runner.options uses hurl_core.ast.option✕
- Connections
- 5 pairs of types, where a type in hurl.runner.options uses a type in hurl_core.ast.option.
- The types involved
hurl.runner.options.options$module→hurl_core.ast.option.BooleanOptionhurl.runner.options.options$module→hurl_core.ast.option.CountOptionhurl.runner.options.options$module→hurl_core.ast.option.DurationOptionhurl.runner.options.options$module→hurl_core.ast.option.NaturalOptionhurl.runner.options.options$module→hurl_core.ast.option.VariableValue
- Direction
- hurl.runner.options uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.runner.options, while a change to hurl.runner.options can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→20 hurl.runner.options uses hurl.runner.runner_options✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl.runner.runner_options.
- The types involved
hurl.runner.options.options$module→hurl.runner.runner_options.RunnerOptions
- Direction
- hurl.runner.options uses hurl.runner.runner_options, so a change to hurl.runner.runner_options can break hurl.runner.options, while a change to hurl.runner.options can't break hurl.runner.runner_options.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→21 hurl.runner.options uses hurl_core.ast.core✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl_core.ast.core.
- The types involved
hurl.runner.options.options$module→hurl_core.ast.core.Entry
- Direction
- hurl.runner.options uses hurl_core.ast.core, so a change to hurl_core.ast.core can break hurl.runner.options, while a change to hurl.runner.options can't break hurl_core.ast.core.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→26 hurl.runner.options uses hurl.util.logger✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl.util.logger.
- The types involved
hurl.runner.options.options$module→hurl.util.logger.Logger
- Direction
- hurl.runner.options uses hurl.util.logger, so a change to hurl.util.logger can break hurl.runner.options, while a change to hurl.runner.options can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
31→28 hurl.runner.options uses hurl.cli.options✕
- Connections
- 1 pair of types, where a type in hurl.runner.options uses a type in hurl.cli.options.
- The types involved
hurl.runner.options.options$module→hurl.cli.options.Verbosity
- Direction
- hurl.runner.options uses hurl.cli.options, so a change to hurl.cli.options can break hurl.runner.options, while a change to hurl.runner.options can't break hurl.cli.options.
- Position
- Below the diagonal: hurl.runner.options uses a module listed above it, which is the healthy direction.
32→27 hurl.http.call uses hurl.http.request✕
- Connections
- 1 pair of types, where a type in hurl.http.call uses a type in hurl.http.request.
- The types involved
hurl.http.call.Call→hurl.http.request.Request
- Direction
- hurl.http.call uses hurl.http.request, so a change to hurl.http.request can break hurl.http.call, while a change to hurl.http.call can't break hurl.http.request.
- Position
- Below the diagonal: hurl.http.call uses a module listed above it, which is the healthy direction.
32→30 hurl.http.call uses hurl.http.response✕
- Connections
- 1 pair of types, where a type in hurl.http.call uses a type in hurl.http.response.
- The types involved
hurl.http.call.Call→hurl.http.response.Response
- Direction
- hurl.http.call uses hurl.http.response, so a change to hurl.http.response can break hurl.http.call, while a change to hurl.http.call can't break hurl.http.response.
- Position
- Below the diagonal: hurl.http.call uses a module listed above it, which is the healthy direction.
33→1 hurl.http.client uses hurl.util.path✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.util.path.
- The types involved
hurl.http.client.Client→hurl.util.path.ContextDir
- Direction
- hurl.http.client uses hurl.util.path, so a change to hurl.util.path can break hurl.http.client, while a change to hurl.http.client can't break hurl.util.path.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→9 hurl.http.client uses hurl.http.url✕
- Connections
- 2 pairs of types, where a type in hurl.http.client uses a type in hurl.http.url.
- The types involved
hurl.http.client.Client→hurl.http.url.Urlhurl.http.client.client$module→hurl.http.url.Url
- Direction
- hurl.http.client uses hurl.http.url, so a change to hurl.http.url can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.url.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→12 hurl.http.client uses hurl.http.cookie_store✕
- Connections
- 2 pairs of types, where a type in hurl.http.client uses a type in hurl.http.cookie_store.
- The types involved
hurl.http.client.Client→hurl.http.cookie_store.Cookiehurl.http.client.Client→hurl.http.cookie_store.CookieStore
- Direction
- hurl.http.client uses hurl.http.cookie_store, so a change to hurl.http.cookie_store can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.cookie_store.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→13 hurl.http.client uses hurl.http.request_spec✕
- Connections
- 3 pairs of types, where a type in hurl.http.client uses a type in hurl.http.request_spec.
- The types involved
hurl.http.client.Client→hurl.http.request_spec.Methodhurl.http.client.Client→hurl.http.request_spec.RequestSpechurl.http.client.client$module→hurl.http.request_spec.Method
- Direction
- hurl.http.client uses hurl.http.request_spec, so a change to hurl.http.request_spec can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.request_spec.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→15 hurl.http.client uses hurl.runner.output✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.runner.output.
- The types involved
hurl.http.client.Client→hurl.runner.output.Output
- Direction
- hurl.http.client uses hurl.runner.output, so a change to hurl.runner.output can break hurl.http.client, while a change to hurl.http.client can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→22 hurl.http.client uses hurl.http.options✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.http.options.
- The types involved
hurl.http.client.Client→hurl.http.options.ClientOptions
- Direction
- hurl.http.client uses hurl.http.options, so a change to hurl.http.options can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.options.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→24 hurl.http.client uses hurl.http.curl_cmd✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.http.curl_cmd.
- The types involved
hurl.http.client.Client→hurl.http.curl_cmd.CurlCmd
- Direction
- hurl.http.client uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.curl_cmd.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→25 hurl.http.client uses hurl.http.header✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.http.header.
- The types involved
hurl.http.client.Client→hurl.http.header.HeaderVec
- Direction
- hurl.http.client uses hurl.http.header, so a change to hurl.http.header can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.header.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→26 hurl.http.client uses hurl.util.logger✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.util.logger.
- The types involved
hurl.http.client.Client→hurl.util.logger.Logger
- Direction
- hurl.http.client uses hurl.util.logger, so a change to hurl.util.logger can break hurl.http.client, while a change to hurl.http.client can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→27 hurl.http.client uses hurl.http.request✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.http.request.
- The types involved
hurl.http.client.client$module→hurl.http.request.FollowLocation
- Direction
- hurl.http.client uses hurl.http.request, so a change to hurl.http.request can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.request.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
33→30 hurl.http.client uses hurl.http.response✕
- Connections
- 1 pair of types, where a type in hurl.http.client uses a type in hurl.http.response.
- The types involved
hurl.http.client.Client→hurl.http.response.Response
- Direction
- hurl.http.client uses hurl.http.response, so a change to hurl.http.response can break hurl.http.client, while a change to hurl.http.client can't break hurl.http.response.
- Position
- Below the diagonal: hurl.http.client uses a module listed above it, which is the healthy direction.
34→11 hurl.runner.query uses hurl_core.ast.primitive✕
- Connections
- 2 pairs of types, where a type in hurl.runner.query uses a type in hurl_core.ast.primitive.
- The types involved
hurl.runner.query.query$module→hurl_core.ast.primitive.SourceInfohurl.runner.query.query$module→hurl_core.ast.primitive.Template
- Direction
- hurl.runner.query uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.runner.query, while a change to hurl.runner.query can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.runner.query uses a module listed above it, which is the healthy direction.
34→16 hurl.runner.query uses hurl.runner.variable✕
- Connections
- 1 pair of types, where a type in hurl.runner.query uses a type in hurl.runner.variable.
- The types involved
hurl.runner.query.query$module→hurl.runner.variable.VariableSet
- Direction
- hurl.runner.query uses hurl.runner.variable, so a change to hurl.runner.variable can break hurl.runner.query, while a change to hurl.runner.query can't break hurl.runner.variable.
- Position
- Below the diagonal: hurl.runner.query uses a module listed above it, which is the healthy direction.
34→18 hurl.runner.query uses hurl_core.ast.section✕
- Connections
- 3 pairs of types, where a type in hurl.runner.query uses a type in hurl_core.ast.section.
- The types involved
hurl.runner.query.query$module→hurl_core.ast.section.CertificateAttributeNamehurl.runner.query.query$module→hurl_core.ast.section.CookieAttributeNamehurl.runner.query.query$module→hurl_core.ast.section.RegexValue
- Direction
- hurl.runner.query uses hurl_core.ast.section, so a change to hurl_core.ast.section can break hurl.runner.query, while a change to hurl.runner.query can't break hurl_core.ast.section.
- Position
- Below the diagonal: hurl.runner.query uses a module listed above it, which is the healthy direction.
34→30 hurl.runner.query uses hurl.http.response✕
- Connections
- 1 pair of types, where a type in hurl.runner.query uses a type in hurl.http.response.
- The types involved
hurl.runner.query.query$module→hurl.http.response.Response
- Direction
- hurl.runner.query uses hurl.http.response, so a change to hurl.http.response can break hurl.runner.query, while a change to hurl.runner.query can't break hurl.http.response.
- Position
- Below the diagonal: hurl.runner.query uses a module listed above it, which is the healthy direction.
35→2 hurl.runner.result uses hurl.util.term✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl.util.term.
- The types involved
hurl.runner.result.EntryResult→hurl.util.term.Stdout
- Direction
- hurl.runner.result uses hurl.util.term, so a change to hurl.util.term can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.util.term.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→3 hurl.runner.result uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl_core.input.
- The types involved
hurl.runner.result.HurlResult→hurl_core.input.Input
- Direction
- hurl.runner.result uses hurl_core.input, so a change to hurl_core.input can break hurl.runner.result, while a change to hurl.runner.result can't break hurl_core.input.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→6 hurl.runner.result uses hurl_core.types✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl_core.types.
- The types involved
hurl.runner.result.EntryResult→hurl_core.types.Index
- Direction
- hurl.runner.result uses hurl_core.types, so a change to hurl_core.types can break hurl.runner.result, while a change to hurl.runner.result can't break hurl_core.types.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→10 hurl.runner.result uses hurl.runner.value✕
- Connections
- 2 pairs of types, where a type in hurl.runner.result uses a type in hurl.runner.value.
- The types involved
hurl.runner.result.CaptureResult→hurl.runner.value.Valuehurl.runner.result.HurlResult→hurl.runner.value.Value
- Direction
- hurl.runner.result uses hurl.runner.value, so a change to hurl.runner.value can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.runner.value.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→11 hurl.runner.result uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl_core.ast.primitive.
- The types involved
hurl.runner.result.EntryResult→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl.runner.result uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.runner.result, while a change to hurl.runner.result can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→12 hurl.runner.result uses hurl.http.cookie_store✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl.http.cookie_store.
- The types involved
hurl.runner.result.HurlResult→hurl.http.cookie_store.CookieStore
- Direction
- hurl.runner.result uses hurl.http.cookie_store, so a change to hurl.http.cookie_store can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.http.cookie_store.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→14 hurl.runner.result uses hurl.runner.error✕
- Connections
- 2 pairs of types, where a type in hurl.runner.result uses a type in hurl.runner.error.
- The types involved
hurl.runner.result.AssertResult→hurl.runner.error.RunnerErrorhurl.runner.result.EntryResult→hurl.runner.error.RunnerError
- Direction
- hurl.runner.result uses hurl.runner.error, so a change to hurl.runner.error can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.runner.error.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→15 hurl.runner.result uses hurl.runner.output✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl.runner.output.
- The types involved
hurl.runner.result.EntryResult→hurl.runner.output.Output
- Direction
- hurl.runner.result uses hurl.runner.output, so a change to hurl.runner.output can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→16 hurl.runner.result uses hurl.runner.variable✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl.runner.variable.
- The types involved
hurl.runner.result.HurlResult→hurl.runner.variable.VariableSet
- Direction
- hurl.runner.result uses hurl.runner.variable, so a change to hurl.runner.variable can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.runner.variable.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→17 hurl.runner.result uses hurl_core.ast.option✕
- Connections
- 2 pairs of types, where a type in hurl.runner.result uses a type in hurl_core.ast.option.
- The types involved
hurl.runner.result.EntryResult→hurl_core.ast.option.Durationhurl.runner.result.HurlResult→hurl_core.ast.option.Duration
- Direction
- hurl.runner.result uses hurl_core.ast.option, so a change to hurl_core.ast.option can break hurl.runner.result, while a change to hurl.runner.result can't break hurl_core.ast.option.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→24 hurl.runner.result uses hurl.http.curl_cmd✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl.http.curl_cmd.
- The types involved
hurl.runner.result.EntryResult→hurl.http.curl_cmd.CurlCmd
- Direction
- hurl.runner.result uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.http.curl_cmd.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
35→32 hurl.runner.result uses hurl.http.call✕
- Connections
- 1 pair of types, where a type in hurl.runner.result uses a type in hurl.http.call.
- The types involved
hurl.runner.result.EntryResult→hurl.http.call.Call
- Direction
- hurl.runner.result uses hurl.http.call, so a change to hurl.http.call can break hurl.runner.result, while a change to hurl.runner.result can't break hurl.http.call.
- Position
- Below the diagonal: hurl.runner.result uses a module listed above it, which is the healthy direction.
36→3 hurl.json.result uses hurl_core.input✕
- Connections
- 3 pairs of types, where a type in hurl.json.result uses a type in hurl_core.input.
- The types involved
hurl.json.result.AssertJson→hurl_core.input.Inputhurl.json.result.EntryResultJson→hurl_core.input.Inputhurl.json.result.HurlResultJson→hurl_core.input.Input
- Direction
- hurl.json.result uses hurl_core.input, so a change to hurl_core.input can break hurl.json.result, while a change to hurl.json.result can't break hurl_core.input.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→10 hurl.json.result uses hurl.runner.value✕
- Connections
- 1 pair of types, where a type in hurl.json.result uses a type in hurl.runner.value.
- The types involved
hurl.json.result.CaptureJson→hurl.runner.value.Value
- Direction
- hurl.json.result uses hurl.runner.value, so a change to hurl.runner.value can break hurl.json.result, while a change to hurl.json.result can't break hurl.runner.value.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→11 hurl.json.result uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.json.result uses a type in hurl_core.ast.primitive.
- The types involved
hurl.json.result.AssertJson→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl.json.result uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.json.result, while a change to hurl.json.result can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→12 hurl.json.result uses hurl.http.cookie_store✕
- Connections
- 1 pair of types, where a type in hurl.json.result uses a type in hurl.http.cookie_store.
- The types involved
hurl.json.result.CookieJson→hurl.http.cookie_store.Cookie
- Direction
- hurl.json.result uses hurl.http.cookie_store, so a change to hurl.http.cookie_store can break hurl.json.result, while a change to hurl.json.result can't break hurl.http.cookie_store.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→25 hurl.json.result uses hurl.http.header✕
- Connections
- 1 pair of types, where a type in hurl.json.result uses a type in hurl.http.header.
- The types involved
hurl.json.result.HeaderJson→hurl.http.header.Header
- Direction
- hurl.json.result uses hurl.http.header, so a change to hurl.http.header can break hurl.json.result, while a change to hurl.json.result can't break hurl.http.header.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→27 hurl.json.result uses hurl.http.request✕
- Connections
- 1 pair of types, where a type in hurl.json.result uses a type in hurl.http.request.
- The types involved
hurl.json.result.RequestJson→hurl.http.request.Request
- Direction
- hurl.json.result uses hurl.http.request, so a change to hurl.http.request can break hurl.json.result, while a change to hurl.json.result can't break hurl.http.request.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→30 hurl.json.result uses hurl.http.response✕
- Connections
- 2 pairs of types, where a type in hurl.json.result uses a type in hurl.http.response.
- The types involved
hurl.json.result.ResponseJson→hurl.http.response.Responsehurl.json.result.result$module→hurl.http.response.Response
- Direction
- hurl.json.result uses hurl.http.response, so a change to hurl.http.response can break hurl.json.result, while a change to hurl.json.result can't break hurl.http.response.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→32 hurl.json.result uses hurl.http.call✕
- Connections
- 1 pair of types, where a type in hurl.json.result uses a type in hurl.http.call.
- The types involved
hurl.json.result.CallJson→hurl.http.call.Call
- Direction
- hurl.json.result uses hurl.http.call, so a change to hurl.http.call can break hurl.json.result, while a change to hurl.json.result can't break hurl.http.call.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
36→35 hurl.json.result uses hurl.runner.result✕
- Connections
- 4 pairs of types, where a type in hurl.json.result uses a type in hurl.runner.result.
- The types involved
hurl.json.result.AssertJson→hurl.runner.result.AssertResulthurl.json.result.CaptureJson→hurl.runner.result.CaptureResulthurl.json.result.EntryResultJson→hurl.runner.result.EntryResulthurl.json.result.HurlResultJson→hurl.runner.result.HurlResult
- Direction
- hurl.json.result uses hurl.runner.result, so a change to hurl.runner.result can break hurl.json.result, while a change to hurl.json.result can't break hurl.runner.result.
- Position
- Below the diagonal: hurl.json.result uses a module listed above it, which is the healthy direction.
37→3 hurl.parallel.job uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.parallel.job uses a type in hurl_core.input.
- The types involved
hurl.parallel.job.Job→hurl_core.input.Input
- Direction
- hurl.parallel.job uses hurl_core.input, so a change to hurl_core.input can break hurl.parallel.job, while a change to hurl.parallel.job can't break hurl_core.input.
- Position
- Below the diagonal: hurl.parallel.job uses a module listed above it, which is the healthy direction.
37→6 hurl.parallel.job uses hurl_core.types✕
- Connections
- 1 pair of types, where a type in hurl.parallel.job uses a type in hurl_core.types.
- The types involved
hurl.parallel.job.JobQueue→hurl_core.types.Count
- Direction
- hurl.parallel.job uses hurl_core.types, so a change to hurl_core.types can break hurl.parallel.job, while a change to hurl.parallel.job can't break hurl_core.types.
- Position
- Below the diagonal: hurl.parallel.job uses a module listed above it, which is the healthy direction.
37→16 hurl.parallel.job uses hurl.runner.variable✕
- Connections
- 1 pair of types, where a type in hurl.parallel.job uses a type in hurl.runner.variable.
- The types involved
hurl.parallel.job.Job→hurl.runner.variable.VariableSet
- Direction
- hurl.parallel.job uses hurl.runner.variable, so a change to hurl.runner.variable can break hurl.parallel.job, while a change to hurl.parallel.job can't break hurl.runner.variable.
- Position
- Below the diagonal: hurl.parallel.job uses a module listed above it, which is the healthy direction.
37→20 hurl.parallel.job uses hurl.runner.runner_options✕
- Connections
- 1 pair of types, where a type in hurl.parallel.job uses a type in hurl.runner.runner_options.
- The types involved
hurl.parallel.job.Job→hurl.runner.runner_options.RunnerOptions
- Direction
- hurl.parallel.job uses hurl.runner.runner_options, so a change to hurl.runner.runner_options can break hurl.parallel.job, while a change to hurl.parallel.job can't break hurl.runner.runner_options.
- Position
- Below the diagonal: hurl.parallel.job uses a module listed above it, which is the healthy direction.
37→26 hurl.parallel.job uses hurl.util.logger✕
- Connections
- 1 pair of types, where a type in hurl.parallel.job uses a type in hurl.util.logger.
- The types involved
hurl.parallel.job.Job→hurl.util.logger.LoggerOptions
- Direction
- hurl.parallel.job uses hurl.util.logger, so a change to hurl.util.logger can break hurl.parallel.job, while a change to hurl.parallel.job can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.parallel.job uses a module listed above it, which is the healthy direction.
37→35 hurl.parallel.job uses hurl.runner.result✕
- Connections
- 1 pair of types, where a type in hurl.parallel.job uses a type in hurl.runner.result.
- The types involved
hurl.parallel.job.JobResult→hurl.runner.result.HurlResult
- Direction
- hurl.parallel.job uses hurl.runner.result, so a change to hurl.runner.result can break hurl.parallel.job, while a change to hurl.parallel.job can't break hurl.runner.result.
- Position
- Below the diagonal: hurl.parallel.job uses a module listed above it, which is the healthy direction.
38→3 hurl.report.html.testcase uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.report.html.testcase uses a type in hurl_core.input.
- The types involved
hurl.report.html.testcase.Testcase→hurl_core.input.Input
- Direction
- hurl.report.html.testcase uses hurl_core.input, so a change to hurl_core.input can break hurl.report.html.testcase, while a change to hurl.report.html.testcase can't break hurl_core.input.
- Position
- Below the diagonal: hurl.report.html.testcase uses a module listed above it, which is the healthy direction.
38→21 hurl.report.html.testcase uses hurl_core.ast.core✕
- Connections
- 1 pair of types, where a type in hurl.report.html.testcase uses a type in hurl_core.ast.core.
- The types involved
hurl.report.html.testcase.Testcase→hurl_core.ast.core.HurlFile
- Direction
- hurl.report.html.testcase uses hurl_core.ast.core, so a change to hurl_core.ast.core can break hurl.report.html.testcase, while a change to hurl.report.html.testcase can't break hurl_core.ast.core.
- Position
- Below the diagonal: hurl.report.html.testcase uses a module listed above it, which is the healthy direction.
38→35 hurl.report.html.testcase uses hurl.runner.result✕
- Connections
- 1 pair of types, where a type in hurl.report.html.testcase uses a type in hurl.runner.result.
- The types involved
hurl.report.html.testcase.Testcase→hurl.runner.result.HurlResult
- Direction
- hurl.report.html.testcase uses hurl.runner.result, so a change to hurl.runner.result can break hurl.report.html.testcase, while a change to hurl.report.html.testcase can't break hurl.runner.result.
- Position
- Below the diagonal: hurl.report.html.testcase uses a module listed above it, which is the healthy direction.
39→6 hurl.runner.entry uses hurl_core.types✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl_core.types.
- The types involved
hurl.runner.entry.entry$module→hurl_core.types.Index
- Direction
- hurl.runner.entry uses hurl_core.types, so a change to hurl_core.types can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl_core.types.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→13 hurl.runner.entry uses hurl.http.request_spec✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.http.request_spec.
- The types involved
hurl.runner.entry.entry$module→hurl.http.request_spec.RequestSpec
- Direction
- hurl.runner.entry uses hurl.http.request_spec, so a change to hurl.http.request_spec can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.http.request_spec.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→14 hurl.runner.entry uses hurl.runner.error✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.runner.error.
- The types involved
hurl.runner.entry.entry$module→hurl.runner.error.RunnerError
- Direction
- hurl.runner.entry uses hurl.runner.error, so a change to hurl.runner.error can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.runner.error.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→16 hurl.runner.entry uses hurl.runner.variable✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.runner.variable.
- The types involved
hurl.runner.entry.entry$module→hurl.runner.variable.VariableSet
- Direction
- hurl.runner.entry uses hurl.runner.variable, so a change to hurl.runner.variable can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.runner.variable.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→18 hurl.runner.entry uses hurl_core.ast.section✕
- Connections
- 2 pairs of types, where a type in hurl.runner.entry uses a type in hurl_core.ast.section.
- The types involved
hurl.runner.entry.entry$module→hurl_core.ast.section.Asserthurl.runner.entry.entry$module→hurl_core.ast.section.Capture
- Direction
- hurl.runner.entry uses hurl_core.ast.section, so a change to hurl_core.ast.section can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl_core.ast.section.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→20 hurl.runner.entry uses hurl.runner.runner_options✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.runner.runner_options.
- The types involved
hurl.runner.entry.entry$module→hurl.runner.runner_options.RunnerOptions
- Direction
- hurl.runner.entry uses hurl.runner.runner_options, so a change to hurl.runner.runner_options can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.runner.runner_options.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→21 hurl.runner.entry uses hurl_core.ast.core✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl_core.ast.core.
- The types involved
hurl.runner.entry.entry$module→hurl_core.ast.core.Entry
- Direction
- hurl.runner.entry uses hurl_core.ast.core, so a change to hurl_core.ast.core can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl_core.ast.core.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→24 hurl.runner.entry uses hurl.http.curl_cmd✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.http.curl_cmd.
- The types involved
hurl.runner.entry.entry$module→hurl.http.curl_cmd.CurlCmd
- Direction
- hurl.runner.entry uses hurl.http.curl_cmd, so a change to hurl.http.curl_cmd can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.http.curl_cmd.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→26 hurl.runner.entry uses hurl.util.logger✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.util.logger.
- The types involved
hurl.runner.entry.entry$module→hurl.util.logger.Logger
- Direction
- hurl.runner.entry uses hurl.util.logger, so a change to hurl.util.logger can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→30 hurl.runner.entry uses hurl.http.response✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.http.response.
- The types involved
hurl.runner.entry.entry$module→hurl.http.response.Response
- Direction
- hurl.runner.entry uses hurl.http.response, so a change to hurl.http.response can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.http.response.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→33 hurl.runner.entry uses hurl.http.client✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.http.client.
- The types involved
hurl.runner.entry.entry$module→hurl.http.client.Client
- Direction
- hurl.runner.entry uses hurl.http.client, so a change to hurl.http.client can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.http.client.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
39→35 hurl.runner.entry uses hurl.runner.result✕
- Connections
- 1 pair of types, where a type in hurl.runner.entry uses a type in hurl.runner.result.
- The types involved
hurl.runner.entry.entry$module→hurl.runner.result.EntryResult
- Direction
- hurl.runner.entry uses hurl.runner.result, so a change to hurl.runner.result can break hurl.runner.entry, while a change to hurl.runner.entry can't break hurl.runner.result.
- Position
- Below the diagonal: hurl.runner.entry uses a module listed above it, which is the healthy direction.
40→2 hurl.runner.hurl_file uses hurl.util.term✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl.util.term.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.util.term.Stdout
- Direction
- hurl.runner.hurl_file uses hurl.util.term, so a change to hurl.util.term can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.util.term.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→3 hurl.runner.hurl_file uses hurl_core.input✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl_core.input.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl_core.input.Input
- Direction
- hurl.runner.hurl_file uses hurl_core.input, so a change to hurl_core.input can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl_core.input.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→6 hurl.runner.hurl_file uses hurl_core.types✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl_core.types.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl_core.types.Index
- Direction
- hurl.runner.hurl_file uses hurl_core.types, so a change to hurl_core.types can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl_core.types.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→11 hurl.runner.hurl_file uses hurl_core.ast.primitive✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl_core.ast.primitive.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl_core.ast.primitive.SourceInfo
- Direction
- hurl.runner.hurl_file uses hurl_core.ast.primitive, so a change to hurl_core.ast.primitive can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl_core.ast.primitive.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→15 hurl.runner.hurl_file uses hurl.runner.output✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl.runner.output.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.runner.output.Output
- Direction
- hurl.runner.hurl_file uses hurl.runner.output, so a change to hurl.runner.output can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.runner.output.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→16 hurl.runner.hurl_file uses hurl.runner.variable✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl.runner.variable.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.runner.variable.VariableSet
- Direction
- hurl.runner.hurl_file uses hurl.runner.variable, so a change to hurl.runner.variable can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.runner.variable.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→20 hurl.runner.hurl_file uses hurl.runner.runner_options✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl.runner.runner_options.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.runner.runner_options.RunnerOptions
- Direction
- hurl.runner.hurl_file uses hurl.runner.runner_options, so a change to hurl.runner.runner_options can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.runner.runner_options.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→21 hurl.runner.hurl_file uses hurl_core.ast.core✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl_core.ast.core.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl_core.ast.core.Entry
- Direction
- hurl.runner.hurl_file uses hurl_core.ast.core, so a change to hurl_core.ast.core can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl_core.ast.core.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→26 hurl.runner.hurl_file uses hurl.util.logger✕
- Connections
- 2 pairs of types, where a type in hurl.runner.hurl_file uses a type in hurl.util.logger.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.util.logger.Loggerhurl.runner.hurl_file.hurl_file$module→hurl.util.logger.LoggerOptions
- Direction
- hurl.runner.hurl_file uses hurl.util.logger, so a change to hurl.util.logger can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.util.logger.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→33 hurl.runner.hurl_file uses hurl.http.client✕
- Connections
- 1 pair of types, where a type in hurl.runner.hurl_file uses a type in hurl.http.client.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.http.client.Client
- Direction
- hurl.runner.hurl_file uses hurl.http.client, so a change to hurl.http.client can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.http.client.
- Position
- Below the diagonal: hurl.runner.hurl_file uses a module listed above it, which is the healthy direction.
40→35 hurl.runner.hurl_file uses hurl.runner.result✕
- Connections
- 2 pairs of types, where a type in hurl.runner.hurl_file uses a type in hurl.runner.result.
- The types involved
hurl.runner.hurl_file.hurl_file$module→hurl.runner.result.EntryResulthurl.runner.hurl_file.hurl_file$module→hurl.runner.result.HurlResult
- Direction
- hurl.runner.hurl_file uses hurl.runner.result, so a change to hurl.runner.result can break hurl.runner.hurl_file, while a change to hurl.runner.hurl_file can't break hurl.runner.result.
- Position
- Below the diagonal: hurl.runner.hurl_file 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 — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 31 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Top priorities: Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element. | +5.8 pts | Medium | ARIA correctness |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +5.0 pts | Medium | Page structure |
| Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED. | +1.5 pts | Low | Secrets (history) |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +1.2 pts | Low | ADR Quality |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +0.8 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.1 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| REDACTED | 7.2 | Mixed | Code Duplication: Edited copy of a member (27 corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| bin/update_crates.py | 7.8 | Mixed | Cognitive Complexity: update_crates.update_local_crates (cognitive 22) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| contrib/sample/src/main.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| bin/docs/markdown.py | 8.5 | Near-clean | Cognitive Complexity: markdown.parse_markdown (cognitive 19) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 58 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 75 of 88 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .py) and this repository declares a Cargo test suite (repository root, 162 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. User interface: 5 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: the service booted and answers HTTP at http://127.0.0.1:5000, but serves no HTML page — nothing for the accessibility crawl.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was update_crates.update_local_crates at 22.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with update_crates.update_local_crates (cognitive 22), LocalCrate.collect_dependencies (cognitive 20), markdown.parse_markdown (cognitive 19). — 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 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
3 duplicated block group(s) detected. 0.3 % of the production lines (195 of 69,965) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 6 of the 6 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with add_header.py, get_large.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (27 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 7) finding(s) in Code Duplication — start with assert_bytearray.py. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
6 production modules (Cargo+npm+source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and — for the source no manifest declares — its top-level source directories, with the imports between them as edges; 0 module(s) off the main sequence, with abstractness counted on 2 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D12 · Dependency Hygiene
2 outdated, 0 yanked direct Cargo dependencies. 24 of 26 direct crates were graded against crates.io (0 not published there, 2 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.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 156 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: packages/hurl/src/runner/options.rs (5×60=300); packages/hurl/src/http/client.rs (8×33=264); packages/hurl/src/http/curl_cmd.rs (6×41=246)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with options.rs, client.rs, curl_cmd.rs. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is integration/hurl/tests_ok/follow_redirect/follow_redirect.py. Counted over 10 of the 176 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 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 69965 LoC (0.0/KLoC) → score 10.0. 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 1 FixmeComment finding(s) in Explicit Debt — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 60 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 build units (Cargo, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
90 % of calls cross a namespace and 0 % go through an interface, but 97 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
31 finding(s): 0 critical, 9 high, 3 medium, 19 low. semgrep hit a parse error in 3 file(s) — `docs/assets/cast/starwars.cast`, `integration/hurl/tests_error_parser/json_max_depth.err`, `integration/hurl/tests_error_parser/json_max_depth.hurl` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 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 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 1 high, 4 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
1 of 10 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is integration/hurl/tests_ok/ntlm/ntlm.py. Counted over 10 of the 176 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 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. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — packages/hurl/src/report/html/resources/report.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — packages/hurl/src/report/html/resources/report.html:2, packages/hurl/src/report/html/resources/run.html:2, packages/hurl/src/report/html/resources/source.html:2, …
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — packages/hurl/src/report/html/resources/report.html:19
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
- "{source_selected}" is not a valid value for aria-selected — allowed: true, false, undefined. — packages/hurl/src/report/html/resources/nav.html:4
- "{timeline_selected}" is not a valid value for aria-selected — allowed: true, false, undefined. — packages/hurl/src/report/html/resources/nav.html:5
- "{run_selected}" is not a valid value for aria-selected — allowed: true, false, undefined. — packages/hurl/src/report/html/resources/nav.html:6
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
AX10 · Code composition
AX2 · Stateful singletons
- `secret` serves requests (Flask routes run on a server thread per request, and every thread shares the one module object) but updates module state with a read-modify-write outside any lock (counter; e.g. `counter` in `dynamic_secret` at line 35). Two requests that interleave between the read and the write lose one update. — integration/hurl/tests_ok/secret/secret.py:35
What to do
- Python: keep request handlers free of module-level counters and accumulators — move the state into a store built for concurrent access (the database, a cache, an atomic counter such as itertools.count) or guard each read-modify-write with a module-level threading.Lock (`with _lock:`).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `contrib/npm/hurl`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:25
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — contrib/npm/check_publish.py:40
What to do
- Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
R1 · Type Safety
- 0 typed · 5 plain JS — the untyped files are contrib/npm/hurl/archive.js, contrib/npm/hurl/bin.js, contrib/npm/hurl/hurl.js, contrib/npm/hurl/hurlfmt.js, contrib/npm/hurl/install.js.
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R5 · Dependency Freshness
R6 · Tooling
- test ✗ · lint ✓ · typecheck ✓ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) as REDACTED scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X21 · Side-effecting pattern guard
X3 · Exception handling
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Exemplary | Strongest area. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 51% | Adequate — gated by AC5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no 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 — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — The runtime tier booted this repository's service, but the service booted and answers HTTP at http://127.0.0.1:5000, but serves no HTML page — nothing for the accessibility crawl. This repository also has a user interface (5 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~1441 lines of test source are present (.rs, .py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (6998 declarations, no unit with a dominant convention).
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 1 of 2 comment blocks were not judged (1 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (53 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 0.27% of this repository's production source and the other 99.73% carries 1,441 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang packages/hurl/src/report/html/resources/report.html:2
- Invalid value "{source_selected}" for aria-selected packages/hurl/src/report/html/resources/nav.html:4
- Invalid value "{timeline_selected}" for aria-selected packages/hurl/src/report/html/resources/nav.html:5
- Invalid value "{run_selected}" for aria-selected packages/hurl/src/report/html/resources/nav.html:6
- REDACTED
- REDACTED
- REDACTED
Serious — 33 finding(s)
- Page without a main landmark packages/hurl/src/report/html/resources/report.html:2
- Page without a main landmark packages/hurl/src/report/html/resources/run.html:2
- Page without a main landmark packages/hurl/src/report/html/resources/source.html:2
- Page without a main landmark packages/hurl/src/report/html/resources/timeline.html:2
- Hotspot: packages/hurl/src/runner/options.rs packages/hurl/src/runner/options.rs:42
- Hotspot: packages/hurl/src/http/client.rs packages/hurl/src/http/client.rs:396
- Hotspot: packages/hurl/src/http/curl_cmd.rs packages/hurl/src/http/curl_cmd.rs:460
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (7 corresponding lines) integration/hurl/tests_ok/add_header/add_header.py:17
- Edited copy of a member (7 corresponding lines) integration/hurl/tests_ok/get_large/get_large.py:9
- Data table has no header cells packages/hurl/src/report/html/resources/report.html:19
- Stateful module: secret integration/hurl/tests_ok/secret/secret.py:35
- FixmeComment contrib/sample/src/main.rs:143
- update_crates.update_local_crates (cognitive 22) bin/update_crates.py:273
- LocalCrate.collect_dependencies (cognitive 20) bin/update_crates.py:191
- markdown.parse_markdown (cognitive 19) bin/docs/markdown.py:238
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (27 corresponding lines) REDACTED:7
- Duplicated block (6 lines × 7) integration/hurl/tests_failed/assert_bytearray/assert_bytearray.py:9
- Duplicated block (6 lines × 3) integration/hurl/tests_failed/runner_errors/runner_errors.py:14
- Duplicated block (9 lines × 6) integration/hurl/tests_ok/compressed/compressed.py:9
- Outbound HTTP without resilience contrib/npm/check_publish.py:40
- Type Safety
- No test script
Minor — 32 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Silent fallback default on Err packages/hurl/src/html/unescape.rs:129
- Silent fallback default on Err packages/hurl_core/src/parser/json.rs:306
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found packages/hurlfmt/src/main.rs:1
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file integration/hurl/tests_ok/ntlm/ntlm.py:1
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No dependency-update automation REDACTED:25
Minor — 2 finding(s)
- Outdated: cc
- Outdated: uuid
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-16ba10b10e45493499b8bbcc9d75ba90/history.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-16ba10b10e45493499b8bbcc9d75ba90/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 5 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |