Executive summary
PRQL/prql meets our standard for a preview release. It scores 66 out of 100 and is rated Strong, and all 255 of its critical findings are security problems.
Production Readiness, at 60, is the weakest lens and counts most in the score. The best first step is adding tests for the code no test reaches, worth about 5 points. Recording design decisions comes next, worth about 2 points. Raising Production Readiness to 62 would lift the score to about 67.
189 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Forty-two secrets can leak from the build pipeline, and eleven pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Updating the vulnerable packages would fix the four packages with a known security hole, and the seven pipeline steps that run downloads without checking them need each download checked against a known checksum first.
The product code is 35,384 lines, about €55,000 to rebuild.
If Production Readiness rose from 60 to 62, the lowest score rated Strong, the score would rise from 66 to about 67.
New since the last survey: 38 findings
- Code Duplication · Edited copy of a member (118 corresponding lines) prqlc/prqlc/src/cli/docs_generator.rs
- Code Duplication · Edited copies of one member (6 members, 25+ corresponding lines) prqlc/prqlc/src/sql/dialect.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) prqlc/prqlc-parser/src/lexer/mod.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) prqlc/prqlc-parser/src/parser/expr.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) prqlc/bindings/dotnet/PrqlCompiler/PrqlCompiler.cs
- Code Duplication · Edited copy of a member (12 corresponding lines) prqlc/bindings/prqlc-c/src/lib.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) prqlc/prqlc/src/semantic/module.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) prqlc/prqlc-parser/src/lexer/mod.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) prqlc/prqlc-parser/src/parser/expr.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) prqlc/bindings/java/src/lib.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) prqlc/bindings/prqlc-python/src/lib.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) prqlc/bindings/elixir/native/prql/src/lib.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) prqlc/bindings/elixir/native/prql/src/lib.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) prqlc/bindings/elixir/native/prql/src/lib.rs
- Code Duplication · Duplicated block (32 lines × 2) prqlc/prqlc/src/sql/dialect.rs
- Code Duplication · Duplicated block (16 lines × 2) prqlc/prqlc/src/semantic/lowering.rs
- Code Duplication · Duplicated block (7–8 lines × 2) prqlc/prqlc/src/semantic/resolver/flatten.rs
- Code Duplication · Duplicated block (5 lines × 2) prqlc/prqlc/src/semantic/module.rs
- Code Duplication · Duplicated block (5 lines × 3) prqlc/prqlc/src/sql/dialect.rs
- Code Duplication · Duplicated block (12 lines × 2) prqlc/prqlc/src/sql/dialect.rs
- Churn × Complexity Hotspots · Repeated repair: prqlc/prqlc/src/sql/dialect.rs prqlc/prqlc/src/sql/dialect.rs
- Churn × Complexity Hotspots · Repeated repair: prqlc/prqlc/src/sql/operators.rs prqlc/prqlc/src/sql/operators.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 26 findings
- Code Duplication · Duplicated block (7–8 lines × 2) prqlc/prqlc/src/semantic/resolver/flatten.rs
- Code Duplication · Duplicated block (5 lines × 2) prqlc/prqlc/src/semantic/resolver/static_eval.rs
- Code Duplication · Duplicated block (9 lines × 2) prqlc/prqlc/src/sql/dialect.rs
- Churn × Complexity Hotspots · Hotspot: prqlc/prqlc/src/semantic/resolver/transforms.rs prqlc/prqlc/src/semantic/resolver/transforms.rs
- Churn × Complexity Hotspots · Hotspot: prqlc/prqlc/src/semantic/resolver/expr.rs prqlc/prqlc/src/semantic/resolver/expr.rs
- Churn × Complexity Hotspots · Repeated repair: prqlc/prqlc/src/semantic/resolver/stmt.rs prqlc/prqlc/src/semantic/resolver/stmt.rs
- Churn × Complexity Hotspots · Repeated repair: prqlc/prqlc/src/lib.rs prqlc/prqlc/src/lib.rs
- Churn × Complexity Hotspots · Repeated repair: prqlc/bindings/prqlc-python/src/lib.rs prqlc/bindings/prqlc-python/src/lib.rs
- Static Analysis (SAST) · High: watchdog-privileged-trigger-secret-to-unpinned-action .github/workflows/tend-ci-fix.yaml
- Static Analysis (SAST) · High: REDACTED .github/workflows/tend-ci-fix.yaml
- Static Analysis (SAST) · High: REDACTED .github/workflows/tend-ci-fix.yaml
- Static Analysis (SAST) · High: REDACTED .github/workflows/tend-ci-fix.yaml
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/tend-ci-fix.yaml
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/tend-ci-fix.yaml
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/tend-ci-fix.yaml
- Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] web/playground/package-lock.json
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2026-0381 REDACTED
- Dependency Vulnerabilities · Medium advisory (unmaintained): RUSTSEC-2025-0134 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0235 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0338 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0346 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0346 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
- Supply-chain Provenance & Signing REDACTED .github/workflows/tend-ci-fix.yaml
Rebuild cost: about €55,000 · Estimate
| Cost to rebuild | €18,000 to €92,000, for 306 to 970 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 35,384 lines of product code |
| Comment lines | The estimate prices 35,251 lines. Comment lines count towards the size of 35,384 lines but aren't priced as work. |
| 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 prqlc.ir.rq.ids | 2 prqlc_parser.parser.pr.ident | 3 prqlc.ir.pl.lineage | 4 prqlc_parser.span | 5 prqlc_parser.error | 6 prqlc_parser.generic | 7 prqlc_parser.parser.pr.types | 8 prqlc.ir.generic | 9 prqlc.sql.dialect | 10 prqlc_parser.lexer.lr | 11 prqlc.ir.rq.transform | 12 prqlc_parser.parser | 13 prqlc_parser.parser.pr.expr | 14 prqlc_parser.parser.pr.stmt | 15 prqlc.ir.decl | 16 prqlc.ir.rq | 17 prqlc.ir.rq.fold | 18 prqlc.utils.id_gen | 19 prqlc.sql.pq.context | 20 prqlc.sql.pq.ast | 21 prqlc.sql | 22 prqlc.sql.gen_expr | 23 prqlc.sql.gen_projection | 24 prqlc.sql.pq.gen_query | 25 prqlc.ir.pl.expr | 26 prqlc.ir.pl.extra | 27 prqlc.ir.pl.stmt | 28 prqlc.sql.gen_query | 29 prqlc.sql.operators | 30 prqlc.sql.pq.anchor | 31 prqlc.sql.pq.preprocess | 32 prqlc | 33 prqlc.ir.pl.fold | 34 prqlc.semantic.ast_expand | 35 prqlc.debug.render_html | 36 prqlc.error_message | 37 prqlc.semantic.lowering | 38 prqlc.semantic.reporting | 39 prqlc.semantic.resolver | 40 prqlc.json |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 prqlc.ir.rq.ids | ||||||||||||||||||||||||||||||||||||||||
| 2 prqlc_parser.parser.pr.ident | ||||||||||||||||||||||||||||||||||||||||
| 3 prqlc.ir.pl.lineage | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 4 prqlc_parser.span | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 prqlc_parser.error | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 prqlc_parser.generic | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 prqlc_parser.parser.pr.types | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 prqlc.ir.generic | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 prqlc.sql.dialect | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 prqlc_parser.lexer.lr | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 prqlc.ir.rq.transform | 3 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 prqlc_parser.parser | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 prqlc_parser.parser.pr.expr | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 prqlc_parser.parser.pr.stmt | 1 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 15 prqlc.ir.decl | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 16 prqlc.ir.rq | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 prqlc.ir.rq.fold | 1 | 2 | 1 | 5 | 2 | 9 | 4 | |||||||||||||||||||||||||||||||||
| 18 prqlc.utils.id_gen | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 prqlc.sql.pq.context | 4 | 1 | 2 | 1 | 7 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 20 prqlc.sql.pq.ast | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 prqlc.sql | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 prqlc.sql.gen_expr | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 23 prqlc.sql.gen_projection | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 prqlc.sql.pq.gen_query | 1 | 1 | 1 | 1 | 4 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 25 prqlc.ir.pl.expr | 2 | 1 | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 26 prqlc.ir.pl.extra | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 prqlc.ir.pl.stmt | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 prqlc.sql.gen_query | 1 | 1 | 1 | 1 | 2 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 29 prqlc.sql.operators | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 prqlc.sql.pq.anchor | 5 | 1 | 3 | 2 | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||
| 31 prqlc.sql.pq.preprocess | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 32 prqlc | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 prqlc.ir.pl.fold | 4 | 2 | 3 | 9 | 3 | 7 | ||||||||||||||||||||||||||||||||||
| 34 prqlc.semantic.ast_expand | 1 | 3 | 2 | 3 | 4 | |||||||||||||||||||||||||||||||||||
| 35 prqlc.debug.render_html | 1 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 prqlc.error_message | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 prqlc.semantic.lowering | 1 | 3 | 1 | 1 | 1 | 3 | 1 | 1 | 2 | 1 | 4 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||
| 38 prqlc.semantic.reporting | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 prqlc.semantic.resolver | 1 | 1 | 1 | 2 | 2 | 1 | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||
| 40 prqlc.json | 1 | 1 | 1 | 1 |
3→2 prqlc.ir.pl.lineage uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.lineage uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.ir.pl.lineage.LineageInput→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.ir.pl.lineage uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.ir.pl.lineage, while a change to prqlc.ir.pl.lineage can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.ir.pl.lineage uses a module listed above it, which is the healthy direction.
3→25 prqlc.ir.pl.lineage uses prqlc.ir.pl.expr part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.lineage uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.ir.pl.lineage.Lineage→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.ir.pl.lineage uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.ir.pl.lineage, while a change to prqlc.ir.pl.lineage can't break prqlc.ir.pl.expr.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→6 prqlc_parser.span uses prqlc_parser.generic part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc_parser.span uses a type in prqlc_parser.generic.
- The types involved
prqlc_parser.span.Span→prqlc_parser.generic.Range
- Direction
- prqlc_parser.span uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc_parser.span, while a change to prqlc_parser.span can't break prqlc_parser.generic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→4 prqlc_parser.error uses prqlc_parser.span✕
- Connections
- 2 pairs of types, where a type in prqlc_parser.error uses a type in prqlc_parser.span.
- The types involved
prqlc_parser.error.Error→prqlc_parser.span.Spanprqlc_parser.error.WithErrorInfo→prqlc_parser.span.Span
- Direction
- prqlc_parser.error uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc_parser.error, while a change to prqlc_parser.error can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc_parser.error uses a module listed above it, which is the healthy direction.
6→4 prqlc_parser.generic uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc_parser.generic uses a type in prqlc_parser.span.
- The types involved
prqlc_parser.generic.Range→prqlc_parser.span.Span
- Direction
- prqlc_parser.generic uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc_parser.generic, while a change to prqlc_parser.generic can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc_parser.generic uses a module listed above it, which is the healthy direction.
7→2 prqlc_parser.parser.pr.types uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser.pr.types uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc_parser.parser.pr.types.TyFunc→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc_parser.parser.pr.types uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc_parser.parser.pr.types, while a change to prqlc_parser.parser.pr.types can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc_parser.parser.pr.types uses a module listed above it, which is the healthy direction.
7→4 prqlc_parser.parser.pr.types uses prqlc_parser.span✕
- Connections
- 2 pairs of types, where a type in prqlc_parser.parser.pr.types uses a type in prqlc_parser.span.
- The types involved
prqlc_parser.parser.pr.types.Ty→prqlc_parser.span.Spanprqlc_parser.parser.pr.types.TyKind→prqlc_parser.span.Span
- Direction
- prqlc_parser.parser.pr.types uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc_parser.parser.pr.types, while a change to prqlc_parser.parser.pr.types can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc_parser.parser.pr.types uses a module listed above it, which is the healthy direction.
8→6 prqlc.ir.generic uses prqlc_parser.generic✕
- Connections
- 1 pair of types, where a type in prqlc.ir.generic uses a type in prqlc_parser.generic.
- The types involved
prqlc.ir.generic.WindowFrame→prqlc_parser.generic.Range
- Direction
- prqlc.ir.generic uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.ir.generic, while a change to prqlc.ir.generic can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.ir.generic uses a module listed above it, which is the healthy direction.
9→5 prqlc.sql.dialect uses prqlc_parser.error✕
- Connections
- 1 pair of types, where a type in prqlc.sql.dialect uses a type in prqlc_parser.error.
- The types involved
prqlc.sql.dialect.dialect$module→prqlc_parser.error.Error
- Direction
- prqlc.sql.dialect uses prqlc_parser.error, so a change to prqlc_parser.error can break prqlc.sql.dialect, while a change to prqlc.sql.dialect can't break prqlc_parser.error.
- Position
- Below the diagonal: prqlc.sql.dialect uses a module listed above it, which is the healthy direction.
9→25 prqlc.sql.dialect uses prqlc.ir.pl.expr part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc.sql.dialect uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.sql.dialect.DialectHandler→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.sql.dialect uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.sql.dialect, while a change to prqlc.sql.dialect can't break prqlc.ir.pl.expr.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→6 prqlc_parser.lexer.lr uses prqlc_parser.generic✕
- Connections
- 1 pair of types, where a type in prqlc_parser.lexer.lr uses a type in prqlc_parser.generic.
- The types involved
prqlc_parser.lexer.lr.Token→prqlc_parser.generic.Range
- Direction
- prqlc_parser.lexer.lr uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc_parser.lexer.lr, while a change to prqlc_parser.lexer.lr can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc_parser.lexer.lr uses a module listed above it, which is the healthy direction.
11→1 prqlc.ir.rq.transform uses prqlc.ir.rq.ids✕
- Connections
- 3 pairs of types, where a type in prqlc.ir.rq.transform uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.ir.rq.transform.Compute→prqlc.ir.rq.ids.CIdprqlc.ir.rq.transform.Take→prqlc.ir.rq.ids.CIdprqlc.ir.rq.transform.Window→prqlc.ir.rq.ids.CId
- Direction
- prqlc.ir.rq.transform uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.ir.rq.transform, while a change to prqlc.ir.rq.transform can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.ir.rq.transform uses a module listed above it, which is the healthy direction.
11→6 prqlc.ir.rq.transform uses prqlc_parser.generic✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq.transform uses a type in prqlc_parser.generic.
- The types involved
prqlc.ir.rq.transform.Take→prqlc_parser.generic.Range
- Direction
- prqlc.ir.rq.transform uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.ir.rq.transform, while a change to prqlc.ir.rq.transform can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.ir.rq.transform uses a module listed above it, which is the healthy direction.
11→8 prqlc.ir.rq.transform uses prqlc.ir.generic✕
- Connections
- 3 pairs of types, where a type in prqlc.ir.rq.transform uses a type in prqlc.ir.generic.
- The types involved
prqlc.ir.rq.transform.Take→prqlc.ir.generic.ColumnSortprqlc.ir.rq.transform.Window→prqlc.ir.generic.ColumnSortprqlc.ir.rq.transform.Window→prqlc.ir.generic.WindowFrame
- Direction
- prqlc.ir.rq.transform uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.ir.rq.transform, while a change to prqlc.ir.rq.transform can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.ir.rq.transform uses a module listed above it, which is the healthy direction.
11→25 prqlc.ir.rq.transform uses prqlc.ir.pl.expr part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq.transform uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.ir.rq.transform.Compute→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.ir.rq.transform uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.ir.rq.transform, while a change to prqlc.ir.rq.transform can't break prqlc.ir.pl.expr.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→4 prqlc_parser.parser uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser uses a type in prqlc_parser.span.
- The types involved
prqlc_parser.parser.parser$module→prqlc_parser.span.Span
- Direction
- prqlc_parser.parser uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc_parser.parser, while a change to prqlc_parser.parser can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc_parser.parser uses a module listed above it, which is the healthy direction.
12→10 prqlc_parser.parser uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc_parser.parser.parser$module→prqlc_parser.lexer.lr.Token
- Direction
- prqlc_parser.parser uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc_parser.parser, while a change to prqlc_parser.parser can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc_parser.parser uses a module listed above it, which is the healthy direction.
12→14 prqlc_parser.parser uses prqlc_parser.parser.pr.stmt part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser uses a type in prqlc_parser.parser.pr.stmt.
- The types involved
prqlc_parser.parser.parser$module→prqlc_parser.parser.pr.stmt.Stmt
- Direction
- prqlc_parser.parser uses prqlc_parser.parser.pr.stmt, so a change to prqlc_parser.parser.pr.stmt can break prqlc_parser.parser, while a change to prqlc_parser.parser can't break prqlc_parser.parser.pr.stmt.
- 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→4 prqlc_parser.parser.pr.expr uses prqlc_parser.span✕
- Connections
- 2 pairs of types, where a type in prqlc_parser.parser.pr.expr uses a type in prqlc_parser.span.
- The types involved
prqlc_parser.parser.pr.expr.Expr→prqlc_parser.span.Spanprqlc_parser.parser.pr.expr.ExprKind→prqlc_parser.span.Span
- Direction
- prqlc_parser.parser.pr.expr uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc_parser.parser.pr.expr, while a change to prqlc_parser.parser.pr.expr can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc_parser.parser.pr.expr uses a module listed above it, which is the healthy direction.
13→7 prqlc_parser.parser.pr.expr uses prqlc_parser.parser.pr.types✕
- Connections
- 3 pairs of types, where a type in prqlc_parser.parser.pr.expr uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc_parser.parser.pr.expr.Func→prqlc_parser.parser.pr.types.Typrqlc_parser.parser.pr.expr.FuncParam→prqlc_parser.parser.pr.types.Typrqlc_parser.parser.pr.expr.GenericTypeParam→prqlc_parser.parser.pr.types.Ty
- Direction
- prqlc_parser.parser.pr.expr uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc_parser.parser.pr.expr, while a change to prqlc_parser.parser.pr.expr can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc_parser.parser.pr.expr uses a module listed above it, which is the healthy direction.
13→10 prqlc_parser.parser.pr.expr uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser.pr.expr uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc_parser.parser.pr.expr.ExprKind→prqlc_parser.lexer.lr.Literal
- Direction
- prqlc_parser.parser.pr.expr uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc_parser.parser.pr.expr, while a change to prqlc_parser.parser.pr.expr can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc_parser.parser.pr.expr uses a module listed above it, which is the healthy direction.
13→12 prqlc_parser.parser.pr.expr uses prqlc_parser.parser✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser.pr.expr uses a type in prqlc_parser.parser.
- The types involved
prqlc_parser.parser.pr.expr.Expr→prqlc_parser.parser.SupportsDocComment
- Direction
- prqlc_parser.parser.pr.expr uses prqlc_parser.parser, so a change to prqlc_parser.parser can break prqlc_parser.parser.pr.expr, while a change to prqlc_parser.parser.pr.expr can't break prqlc_parser.parser.
- Position
- Below the diagonal: prqlc_parser.parser.pr.expr uses a module listed above it, which is the healthy direction.
14→2 prqlc_parser.parser.pr.stmt uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser.pr.stmt uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc_parser.parser.pr.stmt.ImportDef→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc_parser.parser.pr.stmt uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc_parser.parser.pr.stmt, while a change to prqlc_parser.parser.pr.stmt can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc_parser.parser.pr.stmt uses a module listed above it, which is the healthy direction.
14→4 prqlc_parser.parser.pr.stmt uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser.pr.stmt uses a type in prqlc_parser.span.
- The types involved
prqlc_parser.parser.pr.stmt.Stmt→prqlc_parser.span.Span
- Direction
- prqlc_parser.parser.pr.stmt uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc_parser.parser.pr.stmt, while a change to prqlc_parser.parser.pr.stmt can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc_parser.parser.pr.stmt uses a module listed above it, which is the healthy direction.
14→7 prqlc_parser.parser.pr.stmt uses prqlc_parser.parser.pr.types✕
- Connections
- 2 pairs of types, where a type in prqlc_parser.parser.pr.stmt uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc_parser.parser.pr.stmt.TypeDef→prqlc_parser.parser.pr.types.Typrqlc_parser.parser.pr.stmt.VarDef→prqlc_parser.parser.pr.types.Ty
- Direction
- prqlc_parser.parser.pr.stmt uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc_parser.parser.pr.stmt, while a change to prqlc_parser.parser.pr.stmt can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc_parser.parser.pr.stmt uses a module listed above it, which is the healthy direction.
14→12 prqlc_parser.parser.pr.stmt uses prqlc_parser.parser✕
- Connections
- 1 pair of types, where a type in prqlc_parser.parser.pr.stmt uses a type in prqlc_parser.parser.
- The types involved
prqlc_parser.parser.pr.stmt.Stmt→prqlc_parser.parser.SupportsDocComment
- Direction
- prqlc_parser.parser.pr.stmt uses prqlc_parser.parser, so a change to prqlc_parser.parser can break prqlc_parser.parser.pr.stmt, while a change to prqlc_parser.parser.pr.stmt can't break prqlc_parser.parser.
- Position
- Below the diagonal: prqlc_parser.parser.pr.stmt uses a module listed above it, which is the healthy direction.
14→13 prqlc_parser.parser.pr.stmt uses prqlc_parser.parser.pr.expr✕
- Connections
- 2 pairs of types, where a type in prqlc_parser.parser.pr.stmt uses a type in prqlc_parser.parser.pr.expr.
- The types involved
prqlc_parser.parser.pr.stmt.Annotation→prqlc_parser.parser.pr.expr.Exprprqlc_parser.parser.pr.stmt.VarDef→prqlc_parser.parser.pr.expr.Expr
- Direction
- prqlc_parser.parser.pr.stmt uses prqlc_parser.parser.pr.expr, so a change to prqlc_parser.parser.pr.expr can break prqlc_parser.parser.pr.stmt, while a change to prqlc_parser.parser.pr.stmt can't break prqlc_parser.parser.pr.expr.
- Position
- Below the diagonal: prqlc_parser.parser.pr.stmt uses a module listed above it, which is the healthy direction.
15→2 prqlc.ir.decl uses prqlc_parser.parser.pr.ident✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.decl uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.ir.decl.Module→prqlc_parser.parser.pr.ident.Identprqlc.ir.decl.RootModule→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.ir.decl uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.ir.decl, while a change to prqlc.ir.decl can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.ir.decl uses a module listed above it, which is the healthy direction.
15→3 prqlc.ir.decl uses prqlc.ir.pl.lineage✕
- Connections
- 1 pair of types, where a type in prqlc.ir.decl uses a type in prqlc.ir.pl.lineage.
- The types involved
prqlc.ir.decl.Module→prqlc.ir.pl.lineage.Lineage
- Direction
- prqlc.ir.decl uses prqlc.ir.pl.lineage, so a change to prqlc.ir.pl.lineage can break prqlc.ir.decl, while a change to prqlc.ir.decl can't break prqlc.ir.pl.lineage.
- Position
- Below the diagonal: prqlc.ir.decl uses a module listed above it, which is the healthy direction.
15→7 prqlc.ir.decl uses prqlc_parser.parser.pr.types✕
- Connections
- 1 pair of types, where a type in prqlc.ir.decl uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc.ir.decl.TableDecl→prqlc_parser.parser.pr.types.Ty
- Direction
- prqlc.ir.decl uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc.ir.decl, while a change to prqlc.ir.decl can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc.ir.decl uses a module listed above it, which is the healthy direction.
15→14 prqlc.ir.decl uses prqlc_parser.parser.pr.stmt✕
- Connections
- 1 pair of types, where a type in prqlc.ir.decl uses a type in prqlc_parser.parser.pr.stmt.
- The types involved
prqlc.ir.decl.RootModule→prqlc_parser.parser.pr.stmt.QueryDef
- Direction
- prqlc.ir.decl uses prqlc_parser.parser.pr.stmt, so a change to prqlc_parser.parser.pr.stmt can break prqlc.ir.decl, while a change to prqlc.ir.decl can't break prqlc_parser.parser.pr.stmt.
- Position
- Below the diagonal: prqlc.ir.decl uses a module listed above it, which is the healthy direction.
15→27 prqlc.ir.decl uses prqlc.ir.pl.stmt part of a loop✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.decl uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.ir.decl.Decl→prqlc.ir.pl.stmt.Annotationprqlc.ir.decl.RootModule→prqlc.ir.pl.stmt.Annotation
- Direction
- prqlc.ir.decl uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.ir.decl, while a change to prqlc.ir.decl can't break prqlc.ir.pl.stmt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 prqlc.ir.rq uses prqlc.ir.rq.ids✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.rq uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.ir.rq.TableDecl→prqlc.ir.rq.ids.TIdprqlc.ir.rq.TableRef→prqlc.ir.rq.ids.TId
- Direction
- prqlc.ir.rq uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.ir.rq, while a change to prqlc.ir.rq can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.ir.rq uses a module listed above it, which is the healthy direction.
16→10 prqlc.ir.rq uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc.ir.rq.RelationLiteral→prqlc_parser.lexer.lr.Literal
- Direction
- prqlc.ir.rq uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc.ir.rq, while a change to prqlc.ir.rq can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc.ir.rq uses a module listed above it, which is the healthy direction.
16→14 prqlc.ir.rq uses prqlc_parser.parser.pr.stmt✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq uses a type in prqlc_parser.parser.pr.stmt.
- The types involved
prqlc.ir.rq.RelationalQuery→prqlc_parser.parser.pr.stmt.QueryDef
- Direction
- prqlc.ir.rq uses prqlc_parser.parser.pr.stmt, so a change to prqlc_parser.parser.pr.stmt can break prqlc.ir.rq, while a change to prqlc.ir.rq can't break prqlc_parser.parser.pr.stmt.
- Position
- Below the diagonal: prqlc.ir.rq uses a module listed above it, which is the healthy direction.
16→15 prqlc.ir.rq uses prqlc.ir.decl✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq uses a type in prqlc.ir.decl.
- The types involved
prqlc.ir.rq.RelationalQuery→prqlc.ir.decl.TableDecl
- Direction
- prqlc.ir.rq uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.ir.rq, while a change to prqlc.ir.rq can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.ir.rq uses a module listed above it, which is the healthy direction.
17→1 prqlc.ir.rq.fold uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq.fold uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.ir.rq.fold.RqFold→prqlc.ir.rq.ids.CId
- Direction
- prqlc.ir.rq.fold uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.ir.rq.fold uses a module listed above it, which is the healthy direction.
17→6 prqlc.ir.rq.fold uses prqlc_parser.generic✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.rq.fold uses a type in prqlc_parser.generic.
- The types involved
prqlc.ir.rq.fold.fold$module→prqlc_parser.generic.InterpolateItemprqlc.ir.rq.fold.fold$module→prqlc_parser.generic.SwitchCase
- Direction
- prqlc.ir.rq.fold uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.ir.rq.fold uses a module listed above it, which is the healthy direction.
17→8 prqlc.ir.rq.fold uses prqlc.ir.generic✕
- Connections
- 1 pair of types, where a type in prqlc.ir.rq.fold uses a type in prqlc.ir.generic.
- The types involved
prqlc.ir.rq.fold.fold$module→prqlc.ir.generic.ColumnSort
- Direction
- prqlc.ir.rq.fold uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.ir.rq.fold uses a module listed above it, which is the healthy direction.
17→11 prqlc.ir.rq.fold uses prqlc.ir.rq.transform✕
- Connections
- 5 pairs of types, where a type in prqlc.ir.rq.fold uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.ir.rq.fold.RqFold→prqlc.ir.rq.transform.Computeprqlc.ir.rq.fold.RqFold→prqlc.ir.rq.transform.Transformprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.transform.Computeprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.transform.Transformprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.transform.Window
- Direction
- prqlc.ir.rq.fold uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.ir.rq.fold uses a module listed above it, which is the healthy direction.
17→15 prqlc.ir.rq.fold uses prqlc.ir.decl✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.rq.fold uses a type in prqlc.ir.decl.
- The types involved
prqlc.ir.rq.fold.RqFold→prqlc.ir.decl.TableDeclprqlc.ir.rq.fold.fold$module→prqlc.ir.decl.TableDecl
- Direction
- prqlc.ir.rq.fold uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.ir.rq.fold uses a module listed above it, which is the healthy direction.
17→16 prqlc.ir.rq.fold uses prqlc.ir.rq✕
- Connections
- 9 pairs of types, where a type in prqlc.ir.rq.fold uses a type in prqlc.ir.rq.
- The types involved
prqlc.ir.rq.fold.RqFold→prqlc.ir.rq.Relationprqlc.ir.rq.fold.RqFold→prqlc.ir.rq.RelationColumnprqlc.ir.rq.fold.RqFold→prqlc.ir.rq.RelationKindprqlc.ir.rq.fold.RqFold→prqlc.ir.rq.RelationalQueryprqlc.ir.rq.fold.RqFold→prqlc.ir.rq.TableRefprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.Relationprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.RelationKindprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.RelationalQueryprqlc.ir.rq.fold.fold$module→prqlc.ir.rq.TableRef
- Direction
- prqlc.ir.rq.fold uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.ir.rq.fold uses a module listed above it, which is the healthy direction.
17→25 prqlc.ir.rq.fold uses prqlc.ir.pl.expr part of a loop✕
- Connections
- 4 pairs of types, where a type in prqlc.ir.rq.fold uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.ir.rq.fold.RqFold→prqlc.ir.pl.expr.Exprprqlc.ir.rq.fold.RqFold→prqlc.ir.pl.expr.ExprKindprqlc.ir.rq.fold.fold$module→prqlc.ir.pl.expr.Exprprqlc.ir.rq.fold.fold$module→prqlc.ir.pl.expr.ExprKind
- Direction
- prqlc.ir.rq.fold uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.ir.rq.fold, while a change to prqlc.ir.rq.fold can't break prqlc.ir.pl.expr.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 prqlc.utils.id_gen uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.utils.id_gen uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.utils.id_gen.IdLoader→prqlc.ir.rq.ids.CId
- Direction
- prqlc.utils.id_gen uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.utils.id_gen, while a change to prqlc.utils.id_gen can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.utils.id_gen uses a module listed above it, which is the healthy direction.
18→15 prqlc.utils.id_gen uses prqlc.ir.decl✕
- Connections
- 1 pair of types, where a type in prqlc.utils.id_gen uses a type in prqlc.ir.decl.
- The types involved
prqlc.utils.id_gen.IdLoader→prqlc.ir.decl.TableDecl
- Direction
- prqlc.utils.id_gen uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.utils.id_gen, while a change to prqlc.utils.id_gen can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.utils.id_gen uses a module listed above it, which is the healthy direction.
18→16 prqlc.utils.id_gen uses prqlc.ir.rq✕
- Connections
- 1 pair of types, where a type in prqlc.utils.id_gen uses a type in prqlc.ir.rq.
- The types involved
prqlc.utils.id_gen.IdGenerator→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc.utils.id_gen uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.utils.id_gen, while a change to prqlc.utils.id_gen can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.utils.id_gen uses a module listed above it, which is the healthy direction.
18→17 prqlc.utils.id_gen uses prqlc.ir.rq.fold✕
- Connections
- 1 pair of types, where a type in prqlc.utils.id_gen uses a type in prqlc.ir.rq.fold.
- The types involved
prqlc.utils.id_gen.IdLoader→prqlc.ir.rq.fold.RqFold
- Direction
- prqlc.utils.id_gen uses prqlc.ir.rq.fold, so a change to prqlc.ir.rq.fold can break prqlc.utils.id_gen, while a change to prqlc.utils.id_gen can't break prqlc.ir.rq.fold.
- Position
- Below the diagonal: prqlc.utils.id_gen uses a module listed above it, which is the healthy direction.
19→1 prqlc.sql.pq.context uses prqlc.ir.rq.ids✕
- Connections
- 4 pairs of types, where a type in prqlc.sql.pq.context uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.sql.pq.context.AnchorContext→prqlc.ir.rq.ids.CIdprqlc.sql.pq.context.AnchorContext→prqlc.ir.rq.ids.TIdprqlc.sql.pq.context.RelationInstance→prqlc.ir.rq.ids.CIdprqlc.sql.pq.context.SqlTableDecl→prqlc.ir.rq.ids.TId
- Direction
- prqlc.sql.pq.context uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→2 prqlc.sql.pq.context uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.context uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.sql.pq.context.SqlTableDecl→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.sql.pq.context uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→11 prqlc.sql.pq.context uses prqlc.ir.rq.transform✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.pq.context uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.sql.pq.context.AnchorContext→prqlc.ir.rq.transform.Computeprqlc.sql.pq.context.QueryLoader→prqlc.ir.rq.transform.Compute
- Direction
- prqlc.sql.pq.context uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→15 prqlc.sql.pq.context uses prqlc.ir.decl✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.context uses a type in prqlc.ir.decl.
- The types involved
prqlc.sql.pq.context.QueryLoader→prqlc.ir.decl.TableDecl
- Direction
- prqlc.sql.pq.context uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→16 prqlc.sql.pq.context uses prqlc.ir.rq✕
- Connections
- 7 pairs of types, where a type in prqlc.sql.pq.context uses a type in prqlc.ir.rq.
- The types involved
prqlc.sql.pq.context.AnchorContext→prqlc.ir.rq.RelationColumnprqlc.sql.pq.context.AnchorContext→prqlc.ir.rq.RelationalQueryprqlc.sql.pq.context.AnchorContext→prqlc.ir.rq.TableRefprqlc.sql.pq.context.QueryLoader→prqlc.ir.rq.RelationalQueryprqlc.sql.pq.context.QueryLoader→prqlc.ir.rq.TableRefprqlc.sql.pq.context.RelationAdapter→prqlc.ir.rq.Relationprqlc.sql.pq.context.RelationInstance→prqlc.ir.rq.TableRef
- Direction
- prqlc.sql.pq.context uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→17 prqlc.sql.pq.context uses prqlc.ir.rq.fold✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.context uses a type in prqlc.ir.rq.fold.
- The types involved
prqlc.sql.pq.context.QueryLoader→prqlc.ir.rq.fold.RqFold
- Direction
- prqlc.sql.pq.context uses prqlc.ir.rq.fold, so a change to prqlc.ir.rq.fold can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.ir.rq.fold.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→18 prqlc.sql.pq.context uses prqlc.utils.id_gen✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.pq.context uses a type in prqlc.utils.id_gen.
- The types involved
prqlc.sql.pq.context.AnchorContext→prqlc.utils.id_gen.IdGeneratorprqlc.sql.pq.context.AnchorContext→prqlc.utils.id_gen.NameGenerator
- Direction
- prqlc.sql.pq.context uses prqlc.utils.id_gen, so a change to prqlc.utils.id_gen can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.utils.id_gen.
- Position
- Below the diagonal: prqlc.sql.pq.context uses a module listed above it, which is the healthy direction.
19→20 prqlc.sql.pq.context uses prqlc.sql.pq.ast part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.context uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.sql.pq.context.RelationAdapter→prqlc.sql.pq.ast.SqlRelation
- Direction
- prqlc.sql.pq.context uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.sql.pq.context, while a change to prqlc.sql.pq.context can't break prqlc.sql.pq.ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 prqlc.sql.pq.ast uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.ast uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.sql.pq.ast.Cte→prqlc.ir.rq.ids.TId
- Direction
- prqlc.sql.pq.ast uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.sql.pq.ast, while a change to prqlc.sql.pq.ast can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.sql.pq.ast uses a module listed above it, which is the healthy direction.
20→17 prqlc.sql.pq.ast uses prqlc.ir.rq.fold✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.ast uses a type in prqlc.ir.rq.fold.
- The types involved
prqlc.sql.pq.ast.PqMapper→prqlc.ir.rq.fold.RqFold
- Direction
- prqlc.sql.pq.ast uses prqlc.ir.rq.fold, so a change to prqlc.ir.rq.fold can break prqlc.sql.pq.ast, while a change to prqlc.sql.pq.ast can't break prqlc.ir.rq.fold.
- Position
- Below the diagonal: prqlc.sql.pq.ast uses a module listed above it, which is the healthy direction.
20→19 prqlc.sql.pq.ast uses prqlc.sql.pq.context✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.ast uses a type in prqlc.sql.pq.context.
- The types involved
prqlc.sql.pq.ast.RelationExpr→prqlc.sql.pq.context.RIId
- Direction
- prqlc.sql.pq.ast uses prqlc.sql.pq.context, so a change to prqlc.sql.pq.context can break prqlc.sql.pq.ast, while a change to prqlc.sql.pq.ast can't break prqlc.sql.pq.context.
- Position
- Below the diagonal: prqlc.sql.pq.ast uses a module listed above it, which is the healthy direction.
21→9 prqlc.sql uses prqlc.sql.dialect✕
- Connections
- 1 pair of types, where a type in prqlc.sql uses a type in prqlc.sql.dialect.
- The types involved
prqlc.sql.Context→prqlc.sql.dialect.Dialect
- Direction
- prqlc.sql uses prqlc.sql.dialect, so a change to prqlc.sql.dialect can break prqlc.sql, while a change to prqlc.sql can't break prqlc.sql.dialect.
- Position
- Below the diagonal: prqlc.sql uses a module listed above it, which is the healthy direction.
21→16 prqlc.sql uses prqlc.ir.rq✕
- Connections
- 1 pair of types, where a type in prqlc.sql uses a type in prqlc.ir.rq.
- The types involved
prqlc.sql.sql$module→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc.sql uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.sql, while a change to prqlc.sql can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.sql uses a module listed above it, which is the healthy direction.
21→19 prqlc.sql uses prqlc.sql.pq.context✕
- Connections
- 1 pair of types, where a type in prqlc.sql uses a type in prqlc.sql.pq.context.
- The types involved
prqlc.sql.Context→prqlc.sql.pq.context.AnchorContext
- Direction
- prqlc.sql uses prqlc.sql.pq.context, so a change to prqlc.sql.pq.context can break prqlc.sql, while a change to prqlc.sql can't break prqlc.sql.pq.context.
- Position
- Below the diagonal: prqlc.sql uses a module listed above it, which is the healthy direction.
21→20 prqlc.sql uses prqlc.sql.pq.ast✕
- Connections
- 1 pair of types, where a type in prqlc.sql uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.sql.Context→prqlc.sql.pq.ast.Cte
- Direction
- prqlc.sql uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.sql, while a change to prqlc.sql can't break prqlc.sql.pq.ast.
- Position
- Below the diagonal: prqlc.sql uses a module listed above it, which is the healthy direction.
21→32 prqlc.sql uses prqlc part of a loop✕
- Connections
- 1 pair of types, where a type in prqlc.sql uses a type in prqlc.
- The types involved
prqlc.sql.sql$module→prqlc.Options
- Direction
- prqlc.sql uses prqlc, so a change to prqlc can break prqlc.sql, while a change to prqlc.sql can't break prqlc.
- 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→1 prqlc.sql.gen_expr uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_expr uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc.ir.rq.ids.CId
- Direction
- prqlc.sql.gen_expr uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→2 prqlc.sql.gen_expr uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_expr uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.sql.gen_expr uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→4 prqlc.sql.gen_expr uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_expr uses a type in prqlc_parser.span.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc_parser.span.Span
- Direction
- prqlc.sql.gen_expr uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→6 prqlc.sql.gen_expr uses prqlc_parser.generic✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.gen_expr uses a type in prqlc_parser.generic.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc_parser.generic.InterpolateItemprqlc.sql.gen_expr.gen_expr$module→prqlc_parser.generic.Range
- Direction
- prqlc.sql.gen_expr uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→8 prqlc.sql.gen_expr uses prqlc.ir.generic✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.gen_expr uses a type in prqlc.ir.generic.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc.ir.generic.ColumnSortprqlc.sql.gen_expr.gen_expr$module→prqlc.ir.generic.WindowFrame
- Direction
- prqlc.sql.gen_expr uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→10 prqlc.sql.gen_expr uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_expr uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc_parser.lexer.lr.Literal
- Direction
- prqlc.sql.gen_expr uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→11 prqlc.sql.gen_expr uses prqlc.ir.rq.transform✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_expr uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc.ir.rq.transform.Window
- Direction
- prqlc.sql.gen_expr uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→21 prqlc.sql.gen_expr uses prqlc.sql✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_expr uses a type in prqlc.sql.
- The types involved
prqlc.sql.gen_expr.gen_expr$module→prqlc.sql.Context
- Direction
- prqlc.sql.gen_expr uses prqlc.sql, so a change to prqlc.sql can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc.sql.
- Position
- Below the diagonal: prqlc.sql.gen_expr uses a module listed above it, which is the healthy direction.
22→25 prqlc.sql.gen_expr uses prqlc.ir.pl.expr part of a loop✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.gen_expr uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.sql.gen_expr.ExprOrSource→prqlc.ir.pl.expr.Exprprqlc.sql.gen_expr.gen_expr$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.sql.gen_expr uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.sql.gen_expr, while a change to prqlc.sql.gen_expr can't break prqlc.ir.pl.expr.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→1 prqlc.sql.gen_projection uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_projection uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.sql.gen_projection.gen_projection$module→prqlc.ir.rq.ids.CId
- Direction
- prqlc.sql.gen_projection uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.sql.gen_projection, while a change to prqlc.sql.gen_projection can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.sql.gen_projection uses a module listed above it, which is the healthy direction.
23→4 prqlc.sql.gen_projection uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_projection uses a type in prqlc_parser.span.
- The types involved
prqlc.sql.gen_projection.gen_projection$module→prqlc_parser.span.Span
- Direction
- prqlc.sql.gen_projection uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.sql.gen_projection, while a change to prqlc.sql.gen_projection can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.sql.gen_projection uses a module listed above it, which is the healthy direction.
23→19 prqlc.sql.gen_projection uses prqlc.sql.pq.context✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_projection uses a type in prqlc.sql.pq.context.
- The types involved
prqlc.sql.gen_projection.gen_projection$module→prqlc.sql.pq.context.AnchorContext
- Direction
- prqlc.sql.gen_projection uses prqlc.sql.pq.context, so a change to prqlc.sql.pq.context can break prqlc.sql.gen_projection, while a change to prqlc.sql.gen_projection can't break prqlc.sql.pq.context.
- Position
- Below the diagonal: prqlc.sql.gen_projection uses a module listed above it, which is the healthy direction.
23→21 prqlc.sql.gen_projection uses prqlc.sql✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_projection uses a type in prqlc.sql.
- The types involved
prqlc.sql.gen_projection.gen_projection$module→prqlc.sql.Context
- Direction
- prqlc.sql.gen_projection uses prqlc.sql, so a change to prqlc.sql can break prqlc.sql.gen_projection, while a change to prqlc.sql.gen_projection can't break prqlc.sql.
- Position
- Below the diagonal: prqlc.sql.gen_projection uses a module listed above it, which is the healthy direction.
24→9 prqlc.sql.pq.gen_query uses prqlc.sql.dialect✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.sql.dialect.
- The types involved
prqlc.sql.pq.gen_query.gen_query$module→prqlc.sql.dialect.Dialect
- Direction
- prqlc.sql.pq.gen_query uses prqlc.sql.dialect, so a change to prqlc.sql.dialect can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.sql.dialect.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
24→11 prqlc.sql.pq.gen_query uses prqlc.ir.rq.transform✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.sql.pq.gen_query.TransformCompiler→prqlc.ir.rq.transform.Transform
- Direction
- prqlc.sql.pq.gen_query uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
24→16 prqlc.sql.pq.gen_query uses prqlc.ir.rq✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.ir.rq.
- The types involved
prqlc.sql.pq.gen_query.gen_query$module→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc.sql.pq.gen_query uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
24→17 prqlc.sql.pq.gen_query uses prqlc.ir.rq.fold✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.ir.rq.fold.
- The types involved
prqlc.sql.pq.gen_query.TransformCompiler→prqlc.ir.rq.fold.RqFold
- Direction
- prqlc.sql.pq.gen_query uses prqlc.ir.rq.fold, so a change to prqlc.ir.rq.fold can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.ir.rq.fold.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
24→19 prqlc.sql.pq.gen_query uses prqlc.sql.pq.context✕
- Connections
- 4 pairs of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.sql.pq.context.
- The types involved
prqlc.sql.pq.gen_query.TransformCompiler→prqlc.sql.pq.context.RIIdprqlc.sql.pq.gen_query.gen_query$module→prqlc.sql.pq.context.AnchorContextprqlc.sql.pq.gen_query.gen_query$module→prqlc.sql.pq.context.RIIdprqlc.sql.pq.gen_query.gen_query$module→prqlc.sql.pq.context.RelationAdapter
- Direction
- prqlc.sql.pq.gen_query uses prqlc.sql.pq.context, so a change to prqlc.sql.pq.context can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.sql.pq.context.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
24→20 prqlc.sql.pq.gen_query uses prqlc.sql.pq.ast✕
- Connections
- 3 pairs of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.sql.pq.gen_query.TransformCompiler→prqlc.sql.pq.ast.PqMapperprqlc.sql.pq.gen_query.TransformCompiler→prqlc.sql.pq.ast.SqlTransformprqlc.sql.pq.gen_query.gen_query$module→prqlc.sql.pq.ast.SqlTransform
- Direction
- prqlc.sql.pq.gen_query uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.sql.pq.ast.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
24→21 prqlc.sql.pq.gen_query uses prqlc.sql✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.pq.gen_query uses a type in prqlc.sql.
- The types involved
prqlc.sql.pq.gen_query.TransformCompiler→prqlc.sql.Contextprqlc.sql.pq.gen_query.gen_query$module→prqlc.sql.Context
- Direction
- prqlc.sql.pq.gen_query uses prqlc.sql, so a change to prqlc.sql can break prqlc.sql.pq.gen_query, while a change to prqlc.sql.pq.gen_query can't break prqlc.sql.
- Position
- Below the diagonal: prqlc.sql.pq.gen_query uses a module listed above it, which is the healthy direction.
25→2 prqlc.ir.pl.expr uses prqlc_parser.parser.pr.ident✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.pl.expr uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.ir.pl.expr.ExprKind→prqlc_parser.parser.pr.ident.Identprqlc.ir.pl.expr.Func→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.ir.pl.expr uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.ir.pl.expr, while a change to prqlc.ir.pl.expr can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.ir.pl.expr uses a module listed above it, which is the healthy direction.
25→3 prqlc.ir.pl.expr uses prqlc.ir.pl.lineage✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.expr uses a type in prqlc.ir.pl.lineage.
- The types involved
prqlc.ir.pl.expr.Expr→prqlc.ir.pl.lineage.Lineage
- Direction
- prqlc.ir.pl.expr uses prqlc.ir.pl.lineage, so a change to prqlc.ir.pl.lineage can break prqlc.ir.pl.expr, while a change to prqlc.ir.pl.expr can't break prqlc.ir.pl.lineage.
- Position
- Below the diagonal: prqlc.ir.pl.expr uses a module listed above it, which is the healthy direction.
25→4 prqlc.ir.pl.expr uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.expr uses a type in prqlc_parser.span.
- The types involved
prqlc.ir.pl.expr.Expr→prqlc_parser.span.Span
- Direction
- prqlc.ir.pl.expr uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.ir.pl.expr, while a change to prqlc.ir.pl.expr can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.ir.pl.expr uses a module listed above it, which is the healthy direction.
25→7 prqlc.ir.pl.expr uses prqlc_parser.parser.pr.types✕
- Connections
- 3 pairs of types, where a type in prqlc.ir.pl.expr uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc.ir.pl.expr.Expr→prqlc_parser.parser.pr.types.Typrqlc.ir.pl.expr.Func→prqlc_parser.parser.pr.types.Typrqlc.ir.pl.expr.FuncParam→prqlc_parser.parser.pr.types.Ty
- Direction
- prqlc.ir.pl.expr uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc.ir.pl.expr, while a change to prqlc.ir.pl.expr can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc.ir.pl.expr uses a module listed above it, which is the healthy direction.
25→10 prqlc.ir.pl.expr uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.expr uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc.ir.pl.expr.ExprKind→prqlc_parser.lexer.lr.Literal
- Direction
- prqlc.ir.pl.expr uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc.ir.pl.expr, while a change to prqlc.ir.pl.expr can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc.ir.pl.expr uses a module listed above it, which is the healthy direction.
25→22 prqlc.ir.pl.expr uses prqlc.sql.gen_expr✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.pl.expr uses a type in prqlc.sql.gen_expr.
- The types involved
prqlc.ir.pl.expr.Expr→prqlc.sql.gen_expr.Associativityprqlc.ir.pl.expr.Expr→prqlc.sql.gen_expr.SQLExpression
- Direction
- prqlc.ir.pl.expr uses prqlc.sql.gen_expr, so a change to prqlc.sql.gen_expr can break prqlc.ir.pl.expr, while a change to prqlc.ir.pl.expr can't break prqlc.sql.gen_expr.
- Position
- Below the diagonal: prqlc.ir.pl.expr uses a module listed above it, which is the healthy direction.
26→8 prqlc.ir.pl.extra uses prqlc.ir.generic✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.pl.extra uses a type in prqlc.ir.generic.
- The types involved
prqlc.ir.pl.extra.TransformCall→prqlc.ir.generic.ColumnSortprqlc.ir.pl.extra.TransformCall→prqlc.ir.generic.WindowFrame
- Direction
- prqlc.ir.pl.extra uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.ir.pl.extra, while a change to prqlc.ir.pl.extra can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.ir.pl.extra uses a module listed above it, which is the healthy direction.
26→25 prqlc.ir.pl.extra uses prqlc.ir.pl.expr✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.extra uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.ir.pl.extra.TransformCall→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.ir.pl.extra uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.ir.pl.extra, while a change to prqlc.ir.pl.extra can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.ir.pl.extra uses a module listed above it, which is the healthy direction.
27→2 prqlc.ir.pl.stmt uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.stmt uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.ir.pl.stmt.ImportDef→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.ir.pl.stmt uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.ir.pl.stmt, while a change to prqlc.ir.pl.stmt can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.ir.pl.stmt uses a module listed above it, which is the healthy direction.
27→4 prqlc.ir.pl.stmt uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.ir.pl.stmt uses a type in prqlc_parser.span.
- The types involved
prqlc.ir.pl.stmt.Stmt→prqlc_parser.span.Span
- Direction
- prqlc.ir.pl.stmt uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.ir.pl.stmt, while a change to prqlc.ir.pl.stmt can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.ir.pl.stmt uses a module listed above it, which is the healthy direction.
27→7 prqlc.ir.pl.stmt uses prqlc_parser.parser.pr.types✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.pl.stmt uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc.ir.pl.stmt.TypeDef→prqlc_parser.parser.pr.types.Typrqlc.ir.pl.stmt.VarDef→prqlc_parser.parser.pr.types.Ty
- Direction
- prqlc.ir.pl.stmt uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc.ir.pl.stmt, while a change to prqlc.ir.pl.stmt can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc.ir.pl.stmt uses a module listed above it, which is the healthy direction.
27→25 prqlc.ir.pl.stmt uses prqlc.ir.pl.expr✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.pl.stmt uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.ir.pl.stmt.Annotation→prqlc.ir.pl.expr.Exprprqlc.ir.pl.stmt.VarDef→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.ir.pl.stmt uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.ir.pl.stmt, while a change to prqlc.ir.pl.stmt can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.ir.pl.stmt uses a module listed above it, which is the healthy direction.
28→2 prqlc.sql.gen_query uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_query uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.sql.gen_query uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→6 prqlc.sql.gen_query uses prqlc_parser.generic✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_query uses a type in prqlc_parser.generic.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc_parser.generic.InterpolateItem
- Direction
- prqlc.sql.gen_query uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→9 prqlc.sql.gen_query uses prqlc.sql.dialect✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_query uses a type in prqlc.sql.dialect.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc.sql.dialect.Dialect
- Direction
- prqlc.sql.gen_query uses prqlc.sql.dialect, so a change to prqlc.sql.dialect can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc.sql.dialect.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→11 prqlc.sql.gen_query uses prqlc.ir.rq.transform✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_query uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc.ir.rq.transform.Transform
- Direction
- prqlc.sql.gen_query uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→16 prqlc.sql.gen_query uses prqlc.ir.rq✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.gen_query uses a type in prqlc.ir.rq.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc.ir.rq.RelationLiteralprqlc.sql.gen_query.gen_query$module→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc.sql.gen_query uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→20 prqlc.sql.gen_query uses prqlc.sql.pq.ast✕
- Connections
- 3 pairs of types, where a type in prqlc.sql.gen_query uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc.sql.pq.ast.Cteprqlc.sql.gen_query.gen_query$module→prqlc.sql.pq.ast.RelationExprprqlc.sql.gen_query.gen_query$module→prqlc.sql.pq.ast.SqlRelation
- Direction
- prqlc.sql.gen_query uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc.sql.pq.ast.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→21 prqlc.sql.gen_query uses prqlc.sql✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_query uses a type in prqlc.sql.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc.sql.Context
- Direction
- prqlc.sql.gen_query uses prqlc.sql, so a change to prqlc.sql can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc.sql.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
28→25 prqlc.sql.gen_query uses prqlc.ir.pl.expr✕
- Connections
- 1 pair of types, where a type in prqlc.sql.gen_query uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.sql.gen_query.gen_query$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.sql.gen_query uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.sql.gen_query, while a change to prqlc.sql.gen_query can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.sql.gen_query uses a module listed above it, which is the healthy direction.
29→5 prqlc.sql.operators uses prqlc_parser.error✕
- Connections
- 1 pair of types, where a type in prqlc.sql.operators uses a type in prqlc_parser.error.
- The types involved
prqlc.sql.operators.operators$module→prqlc_parser.error.Error
- Direction
- prqlc.sql.operators uses prqlc_parser.error, so a change to prqlc_parser.error can break prqlc.sql.operators, while a change to prqlc.sql.operators can't break prqlc_parser.error.
- Position
- Below the diagonal: prqlc.sql.operators uses a module listed above it, which is the healthy direction.
29→9 prqlc.sql.operators uses prqlc.sql.dialect✕
- Connections
- 1 pair of types, where a type in prqlc.sql.operators uses a type in prqlc.sql.dialect.
- The types involved
prqlc.sql.operators.operators$module→prqlc.sql.dialect.Dialect
- Direction
- prqlc.sql.operators uses prqlc.sql.dialect, so a change to prqlc.sql.dialect can break prqlc.sql.operators, while a change to prqlc.sql.operators can't break prqlc.sql.dialect.
- Position
- Below the diagonal: prqlc.sql.operators uses a module listed above it, which is the healthy direction.
29→10 prqlc.sql.operators uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc.sql.operators uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc.sql.operators.operators$module→prqlc_parser.lexer.lr.Literal
- Direction
- prqlc.sql.operators uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc.sql.operators, while a change to prqlc.sql.operators can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc.sql.operators uses a module listed above it, which is the healthy direction.
29→15 prqlc.sql.operators uses prqlc.ir.decl✕
- Connections
- 1 pair of types, where a type in prqlc.sql.operators uses a type in prqlc.ir.decl.
- The types involved
prqlc.sql.operators.operators$module→prqlc.ir.decl.Module
- Direction
- prqlc.sql.operators uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.sql.operators, while a change to prqlc.sql.operators can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.sql.operators uses a module listed above it, which is the healthy direction.
29→21 prqlc.sql.operators uses prqlc.sql✕
- Connections
- 1 pair of types, where a type in prqlc.sql.operators uses a type in prqlc.sql.
- The types involved
prqlc.sql.operators.operators$module→prqlc.sql.Context
- Direction
- prqlc.sql.operators uses prqlc.sql, so a change to prqlc.sql can break prqlc.sql.operators, while a change to prqlc.sql.operators can't break prqlc.sql.
- Position
- Below the diagonal: prqlc.sql.operators uses a module listed above it, which is the healthy direction.
29→25 prqlc.sql.operators uses prqlc.ir.pl.expr✕
- Connections
- 1 pair of types, where a type in prqlc.sql.operators uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.sql.operators.operators$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.sql.operators uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.sql.operators, while a change to prqlc.sql.operators can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.sql.operators uses a module listed above it, which is the healthy direction.
30→1 prqlc.sql.pq.anchor uses prqlc.ir.rq.ids✕
- Connections
- 5 pairs of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.sql.pq.anchor.CidCollector→prqlc.ir.rq.ids.CIdprqlc.sql.pq.anchor.CidRedirector→prqlc.ir.rq.ids.CIdprqlc.sql.pq.anchor.Requirement→prqlc.ir.rq.ids.CIdprqlc.sql.pq.anchor.Requirements→prqlc.ir.rq.ids.CIdprqlc.sql.pq.anchor.anchor$module→prqlc.ir.rq.ids.CId
- Direction
- prqlc.sql.pq.anchor uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
30→8 prqlc.sql.pq.anchor uses prqlc.ir.generic✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.ir.generic.
- The types involved
prqlc.sql.pq.anchor.CidRedirector→prqlc.ir.generic.ColumnSort
- Direction
- prqlc.sql.pq.anchor uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
30→11 prqlc.sql.pq.anchor uses prqlc.ir.rq.transform✕
- Connections
- 3 pairs of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.sql.pq.anchor.CidCollector→prqlc.ir.rq.transform.Transformprqlc.sql.pq.anchor.CidRedirector→prqlc.ir.rq.transform.Transformprqlc.sql.pq.anchor.anchor$module→prqlc.ir.rq.transform.Compute
- Direction
- prqlc.sql.pq.anchor uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
30→17 prqlc.sql.pq.anchor uses prqlc.ir.rq.fold✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.ir.rq.fold.
- The types involved
prqlc.sql.pq.anchor.CidCollector→prqlc.ir.rq.fold.RqFoldprqlc.sql.pq.anchor.CidRedirector→prqlc.ir.rq.fold.RqFold
- Direction
- prqlc.sql.pq.anchor uses prqlc.ir.rq.fold, so a change to prqlc.ir.rq.fold can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.ir.rq.fold.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
30→19 prqlc.sql.pq.anchor uses prqlc.sql.pq.context✕
- Connections
- 3 pairs of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.sql.pq.context.
- The types involved
prqlc.sql.pq.anchor.CidRedirector→prqlc.sql.pq.context.AnchorContextprqlc.sql.pq.anchor.CidRedirector→prqlc.sql.pq.context.RIIdprqlc.sql.pq.anchor.anchor$module→prqlc.sql.pq.context.AnchorContext
- Direction
- prqlc.sql.pq.anchor uses prqlc.sql.pq.context, so a change to prqlc.sql.pq.context can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.sql.pq.context.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
30→20 prqlc.sql.pq.anchor uses prqlc.sql.pq.ast✕
- Connections
- 3 pairs of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.sql.pq.anchor.CidRedirector→prqlc.sql.pq.ast.PqMapperprqlc.sql.pq.anchor.CidRedirector→prqlc.sql.pq.ast.SqlTransformprqlc.sql.pq.anchor.anchor$module→prqlc.sql.pq.ast.SqlTransform
- Direction
- prqlc.sql.pq.anchor uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.sql.pq.ast.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
30→25 prqlc.sql.pq.anchor uses prqlc.ir.pl.expr✕
- Connections
- 3 pairs of types, where a type in prqlc.sql.pq.anchor uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.sql.pq.anchor.CidCollector→prqlc.ir.pl.expr.Exprprqlc.sql.pq.anchor.Requirements→prqlc.ir.pl.expr.Exprprqlc.sql.pq.anchor.anchor$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.sql.pq.anchor uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.sql.pq.anchor, while a change to prqlc.sql.pq.anchor can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.sql.pq.anchor uses a module listed above it, which is the healthy direction.
31→1 prqlc.sql.pq.preprocess uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.sql.pq.preprocess.preprocess$module→prqlc.ir.rq.ids.CId
- Direction
- prqlc.sql.pq.preprocess uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→6 prqlc.sql.pq.preprocess uses prqlc_parser.generic✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc_parser.generic.
- The types involved
prqlc.sql.pq.preprocess.preprocess$module→prqlc_parser.generic.Range
- Direction
- prqlc.sql.pq.preprocess uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→8 prqlc.sql.pq.preprocess uses prqlc.ir.generic✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.ir.generic.
- The types involved
prqlc.sql.pq.preprocess.preprocess$module→prqlc.ir.generic.ColumnSort
- Direction
- prqlc.sql.pq.preprocess uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→11 prqlc.sql.pq.preprocess uses prqlc.ir.rq.transform✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.sql.pq.preprocess.preprocess$module→prqlc.ir.rq.transform.Transform
- Direction
- prqlc.sql.pq.preprocess uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→17 prqlc.sql.pq.preprocess uses prqlc.ir.rq.fold✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.ir.rq.fold.
- The types involved
prqlc.sql.pq.preprocess.Normalizer→prqlc.ir.rq.fold.RqFold
- Direction
- prqlc.sql.pq.preprocess uses prqlc.ir.rq.fold, so a change to prqlc.ir.rq.fold can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.ir.rq.fold.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→20 prqlc.sql.pq.preprocess uses prqlc.sql.pq.ast✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.sql.pq.preprocess.preprocess$module→prqlc.sql.pq.ast.SqlTransform
- Direction
- prqlc.sql.pq.preprocess uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.sql.pq.ast.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→21 prqlc.sql.pq.preprocess uses prqlc.sql✕
- Connections
- 1 pair of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.sql.
- The types involved
prqlc.sql.pq.preprocess.preprocess$module→prqlc.sql.Context
- Direction
- prqlc.sql.pq.preprocess uses prqlc.sql, so a change to prqlc.sql can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.sql.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
31→25 prqlc.sql.pq.preprocess uses prqlc.ir.pl.expr✕
- Connections
- 2 pairs of types, where a type in prqlc.sql.pq.preprocess uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.sql.pq.preprocess.Normalizer→prqlc.ir.pl.expr.Exprprqlc.sql.pq.preprocess.preprocess$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.sql.pq.preprocess uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.sql.pq.preprocess, while a change to prqlc.sql.pq.preprocess can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.sql.pq.preprocess uses a module listed above it, which is the healthy direction.
32→16 prqlc uses prqlc.ir.rq✕
- Connections
- 1 pair of types, where a type in prqlc uses a type in prqlc.ir.rq.
- The types involved
prqlc.prqlc$module→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc, while a change to prqlc can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc uses a module listed above it, which is the healthy direction.
32→27 prqlc uses prqlc.ir.pl.stmt✕
- Connections
- 1 pair of types, where a type in prqlc uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.prqlc$module→prqlc.ir.pl.stmt.ModuleDef
- Direction
- prqlc uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc, while a change to prqlc can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc uses a module listed above it, which is the healthy direction.
33→6 prqlc.ir.pl.fold uses prqlc_parser.generic✕
- Connections
- 4 pairs of types, where a type in prqlc.ir.pl.fold uses a type in prqlc_parser.generic.
- The types involved
prqlc.ir.pl.fold.PlFold→prqlc_parser.generic.InterpolateItemprqlc.ir.pl.fold.fold$module→prqlc_parser.generic.InterpolateItemprqlc.ir.pl.fold.fold$module→prqlc_parser.generic.Rangeprqlc.ir.pl.fold.fold$module→prqlc_parser.generic.SwitchCase
- Direction
- prqlc.ir.pl.fold uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.ir.pl.fold, while a change to prqlc.ir.pl.fold can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.ir.pl.fold uses a module listed above it, which is the healthy direction.
33→7 prqlc.ir.pl.fold uses prqlc_parser.parser.pr.types✕
- Connections
- 2 pairs of types, where a type in prqlc.ir.pl.fold uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc.ir.pl.fold.PlFold→prqlc_parser.parser.pr.types.Typrqlc.ir.pl.fold.fold$module→prqlc_parser.parser.pr.types.Ty
- Direction
- prqlc.ir.pl.fold uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc.ir.pl.fold, while a change to prqlc.ir.pl.fold can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc.ir.pl.fold uses a module listed above it, which is the healthy direction.
33→8 prqlc.ir.pl.fold uses prqlc.ir.generic✕
- Connections
- 3 pairs of types, where a type in prqlc.ir.pl.fold uses a type in prqlc.ir.generic.
- The types involved
prqlc.ir.pl.fold.PlFold→prqlc.ir.generic.WindowFrameprqlc.ir.pl.fold.fold$module→prqlc.ir.generic.ColumnSortprqlc.ir.pl.fold.fold$module→prqlc.ir.generic.WindowFrame
- Direction
- prqlc.ir.pl.fold uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.ir.pl.fold, while a change to prqlc.ir.pl.fold can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.ir.pl.fold uses a module listed above it, which is the healthy direction.
33→25 prqlc.ir.pl.fold uses prqlc.ir.pl.expr✕
- Connections
- 9 pairs of types, where a type in prqlc.ir.pl.fold uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.ir.pl.fold.PlFold→prqlc.ir.pl.expr.Exprprqlc.ir.pl.fold.PlFold→prqlc.ir.pl.expr.ExprKindprqlc.ir.pl.fold.PlFold→prqlc.ir.pl.expr.Funcprqlc.ir.pl.fold.PlFold→prqlc.ir.pl.expr.FuncCallprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.expr.Exprprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.expr.ExprKindprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.expr.Funcprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.expr.FuncCallprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.expr.FuncParam
- Direction
- prqlc.ir.pl.fold uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.ir.pl.fold, while a change to prqlc.ir.pl.fold can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.ir.pl.fold uses a module listed above it, which is the healthy direction.
33→26 prqlc.ir.pl.fold uses prqlc.ir.pl.extra✕
- Connections
- 3 pairs of types, where a type in prqlc.ir.pl.fold uses a type in prqlc.ir.pl.extra.
- The types involved
prqlc.ir.pl.fold.PlFold→prqlc.ir.pl.extra.TransformCallprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.extra.TransformCallprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.extra.TransformKind
- Direction
- prqlc.ir.pl.fold uses prqlc.ir.pl.extra, so a change to prqlc.ir.pl.extra can break prqlc.ir.pl.fold, while a change to prqlc.ir.pl.fold can't break prqlc.ir.pl.extra.
- Position
- Below the diagonal: prqlc.ir.pl.fold uses a module listed above it, which is the healthy direction.
33→27 prqlc.ir.pl.fold uses prqlc.ir.pl.stmt✕
- Connections
- 7 pairs of types, where a type in prqlc.ir.pl.fold uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.ir.pl.fold.PlFold→prqlc.ir.pl.stmt.ModuleDefprqlc.ir.pl.fold.PlFold→prqlc.ir.pl.stmt.Stmtprqlc.ir.pl.fold.PlFold→prqlc.ir.pl.stmt.TypeDefprqlc.ir.pl.fold.PlFold→prqlc.ir.pl.stmt.VarDefprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.stmt.ModuleDefprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.stmt.StmtKindprqlc.ir.pl.fold.fold$module→prqlc.ir.pl.stmt.VarDef
- Direction
- prqlc.ir.pl.fold uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.ir.pl.fold, while a change to prqlc.ir.pl.fold can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc.ir.pl.fold uses a module listed above it, which is the healthy direction.
34→6 prqlc.semantic.ast_expand uses prqlc_parser.generic✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.ast_expand uses a type in prqlc_parser.generic.
- The types involved
prqlc.semantic.ast_expand.ast_expand$module→prqlc_parser.generic.Range
- Direction
- prqlc.semantic.ast_expand uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.semantic.ast_expand, while a change to prqlc.semantic.ast_expand can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.semantic.ast_expand uses a module listed above it, which is the healthy direction.
34→13 prqlc.semantic.ast_expand uses prqlc_parser.parser.pr.expr✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.ast_expand uses a type in prqlc_parser.parser.pr.expr.
- The types involved
prqlc.semantic.ast_expand.ast_expand$module→prqlc_parser.parser.pr.expr.BinaryExprprqlc.semantic.ast_expand.ast_expand$module→prqlc_parser.parser.pr.expr.Pipelineprqlc.semantic.ast_expand.ast_expand$module→prqlc_parser.parser.pr.expr.UnaryExpr
- Direction
- prqlc.semantic.ast_expand uses prqlc_parser.parser.pr.expr, so a change to prqlc_parser.parser.pr.expr can break prqlc.semantic.ast_expand, while a change to prqlc.semantic.ast_expand can't break prqlc_parser.parser.pr.expr.
- Position
- Below the diagonal: prqlc.semantic.ast_expand uses a module listed above it, which is the healthy direction.
34→15 prqlc.semantic.ast_expand uses prqlc.ir.decl✕
- Connections
- 2 pairs of types, where a type in prqlc.semantic.ast_expand uses a type in prqlc.ir.decl.
- The types involved
prqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.decl.Declprqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.decl.Module
- Direction
- prqlc.semantic.ast_expand uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.semantic.ast_expand, while a change to prqlc.semantic.ast_expand can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.semantic.ast_expand uses a module listed above it, which is the healthy direction.
34→25 prqlc.semantic.ast_expand uses prqlc.ir.pl.expr✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.ast_expand uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.expr.Exprprqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.expr.ExprKindprqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.expr.FuncParam
- Direction
- prqlc.semantic.ast_expand uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.semantic.ast_expand, while a change to prqlc.semantic.ast_expand can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.semantic.ast_expand uses a module listed above it, which is the healthy direction.
34→27 prqlc.semantic.ast_expand uses prqlc.ir.pl.stmt✕
- Connections
- 4 pairs of types, where a type in prqlc.semantic.ast_expand uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.stmt.Annotationprqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.stmt.ModuleDefprqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.stmt.Stmtprqlc.semantic.ast_expand.ast_expand$module→prqlc.ir.pl.stmt.StmtKind
- Direction
- prqlc.semantic.ast_expand uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.semantic.ast_expand, while a change to prqlc.semantic.ast_expand can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc.semantic.ast_expand uses a module listed above it, which is the healthy direction.
35→5 prqlc.debug.render_html uses prqlc_parser.error✕
- Connections
- 1 pair of types, where a type in prqlc.debug.render_html uses a type in prqlc_parser.error.
- The types involved
prqlc.debug.render_html.IoWriter→prqlc_parser.error.Error
- Direction
- prqlc.debug.render_html uses prqlc_parser.error, so a change to prqlc_parser.error can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc_parser.error.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
35→10 prqlc.debug.render_html uses prqlc_parser.lexer.lr✕
- Connections
- 1 pair of types, where a type in prqlc.debug.render_html uses a type in prqlc_parser.lexer.lr.
- The types involved
prqlc.debug.render_html.render_html$module→prqlc_parser.lexer.lr.Tokens
- Direction
- prqlc.debug.render_html uses prqlc_parser.lexer.lr, so a change to prqlc_parser.lexer.lr can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc_parser.lexer.lr.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
35→15 prqlc.debug.render_html uses prqlc.ir.decl✕
- Connections
- 2 pairs of types, where a type in prqlc.debug.render_html uses a type in prqlc.ir.decl.
- The types involved
prqlc.debug.render_html.render_html$module→prqlc.ir.decl.Declprqlc.debug.render_html.render_html$module→prqlc.ir.decl.RootModule
- Direction
- prqlc.debug.render_html uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
35→16 prqlc.debug.render_html uses prqlc.ir.rq✕
- Connections
- 1 pair of types, where a type in prqlc.debug.render_html uses a type in prqlc.ir.rq.
- The types involved
prqlc.debug.render_html.render_html$module→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc.debug.render_html uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
35→20 prqlc.debug.render_html uses prqlc.sql.pq.ast✕
- Connections
- 1 pair of types, where a type in prqlc.debug.render_html uses a type in prqlc.sql.pq.ast.
- The types involved
prqlc.debug.render_html.render_html$module→prqlc.sql.pq.ast.SqlQuery
- Direction
- prqlc.debug.render_html uses prqlc.sql.pq.ast, so a change to prqlc.sql.pq.ast can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc.sql.pq.ast.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
35→27 prqlc.debug.render_html uses prqlc.ir.pl.stmt✕
- Connections
- 1 pair of types, where a type in prqlc.debug.render_html uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.debug.render_html.render_html$module→prqlc.ir.pl.stmt.ModuleDef
- Direction
- prqlc.debug.render_html uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
35→32 prqlc.debug.render_html uses prqlc✕
- Connections
- 1 pair of types, where a type in prqlc.debug.render_html uses a type in prqlc.
- The types involved
prqlc.debug.render_html.render_html$module→prqlc.SourceTree
- Direction
- prqlc.debug.render_html uses prqlc, so a change to prqlc can break prqlc.debug.render_html, while a change to prqlc.debug.render_html can't break prqlc.
- Position
- Below the diagonal: prqlc.debug.render_html uses a module listed above it, which is the healthy direction.
36→4 prqlc.error_message uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.error_message uses a type in prqlc_parser.span.
- The types involved
prqlc.error_message.ErrorMessage→prqlc_parser.span.Span
- Direction
- prqlc.error_message uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.error_message, while a change to prqlc.error_message can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.error_message uses a module listed above it, which is the healthy direction.
36→5 prqlc.error_message uses prqlc_parser.error✕
- Connections
- 4 pairs of types, where a type in prqlc.error_message uses a type in prqlc_parser.error.
- The types involved
prqlc.error_message.ErrorMessage→prqlc_parser.error.Errorprqlc.error_message.ErrorMessage→prqlc_parser.error.MessageKindprqlc.error_message.ErrorMessages→prqlc_parser.error.Errorprqlc.error_message.ErrorMessages→prqlc_parser.error.Errors
- Direction
- prqlc.error_message uses prqlc_parser.error, so a change to prqlc_parser.error can break prqlc.error_message, while a change to prqlc.error_message can't break prqlc_parser.error.
- Position
- Below the diagonal: prqlc.error_message uses a module listed above it, which is the healthy direction.
36→32 prqlc.error_message uses prqlc✕
- Connections
- 2 pairs of types, where a type in prqlc.error_message uses a type in prqlc.
- The types involved
prqlc.error_message.ErrorMessages→prqlc.SourceTreeprqlc.error_message.FileTreeCache→prqlc.SourceTree
- Direction
- prqlc.error_message uses prqlc, so a change to prqlc can break prqlc.error_message, while a change to prqlc.error_message can't break prqlc.
- Position
- Below the diagonal: prqlc.error_message uses a module listed above it, which is the healthy direction.
37→1 prqlc.semantic.lowering uses prqlc.ir.rq.ids✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.rq.ids.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.rq.ids.TId
- Direction
- prqlc.semantic.lowering uses prqlc.ir.rq.ids, so a change to prqlc.ir.rq.ids can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.rq.ids.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→2 prqlc.semantic.lowering uses prqlc_parser.parser.pr.ident✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.lowering uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc_parser.parser.pr.ident.Identprqlc.semantic.lowering.TableDepsCollector→prqlc_parser.parser.pr.ident.Identprqlc.semantic.lowering.lowering$module→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.semantic.lowering uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→3 prqlc.semantic.lowering uses prqlc.ir.pl.lineage✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.pl.lineage.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.pl.lineage.Lineage
- Direction
- prqlc.semantic.lowering uses prqlc.ir.pl.lineage, so a change to prqlc.ir.pl.lineage can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.pl.lineage.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→4 prqlc.semantic.lowering uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc_parser.span.
- The types involved
prqlc.semantic.lowering.lowering$module→prqlc_parser.span.Span
- Direction
- prqlc.semantic.lowering uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→5 prqlc.semantic.lowering uses prqlc_parser.error✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc_parser.error.
- The types involved
prqlc.semantic.lowering.lowering$module→prqlc_parser.error.Error
- Direction
- prqlc.semantic.lowering uses prqlc_parser.error, so a change to prqlc_parser.error can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc_parser.error.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→6 prqlc.semantic.lowering uses prqlc_parser.generic✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.lowering uses a type in prqlc_parser.generic.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc_parser.generic.InterpolateItemprqlc.semantic.lowering.Lowerer→prqlc_parser.generic.Rangeprqlc.semantic.lowering.lowering$module→prqlc_parser.generic.Range
- Direction
- prqlc.semantic.lowering uses prqlc_parser.generic, so a change to prqlc_parser.generic can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc_parser.generic.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→7 prqlc.semantic.lowering uses prqlc_parser.parser.pr.types✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc.semantic.lowering.lowering$module→prqlc_parser.parser.pr.types.TyTupleField
- Direction
- prqlc.semantic.lowering uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→8 prqlc.semantic.lowering uses prqlc.ir.generic✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.generic.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.generic.ColumnSort
- Direction
- prqlc.semantic.lowering uses prqlc.ir.generic, so a change to prqlc.ir.generic can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.generic.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→11 prqlc.semantic.lowering uses prqlc.ir.rq.transform✕
- Connections
- 2 pairs of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.rq.transform.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.rq.transform.Transformprqlc.semantic.lowering.Lowerer→prqlc.ir.rq.transform.Window
- Direction
- prqlc.semantic.lowering uses prqlc.ir.rq.transform, so a change to prqlc.ir.rq.transform can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.rq.transform.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→14 prqlc.semantic.lowering uses prqlc_parser.parser.pr.stmt✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc_parser.parser.pr.stmt.
- The types involved
prqlc.semantic.lowering.lowering$module→prqlc_parser.parser.pr.stmt.QueryDef
- Direction
- prqlc.semantic.lowering uses prqlc_parser.parser.pr.stmt, so a change to prqlc_parser.parser.pr.stmt can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc_parser.parser.pr.stmt.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→15 prqlc.semantic.lowering uses prqlc.ir.decl✕
- Connections
- 4 pairs of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.decl.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.decl.RootModuleprqlc.semantic.lowering.Lowerer→prqlc.ir.decl.TableDeclprqlc.semantic.lowering.TableExtractor→prqlc.ir.decl.Moduleprqlc.semantic.lowering.lowering$module→prqlc.ir.decl.RootModule
- Direction
- prqlc.semantic.lowering uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→16 prqlc.semantic.lowering uses prqlc.ir.rq✕
- Connections
- 2 pairs of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.rq.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.rq.TableRefprqlc.semantic.lowering.lowering$module→prqlc.ir.rq.RelationColumn
- Direction
- prqlc.semantic.lowering uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→18 prqlc.semantic.lowering uses prqlc.utils.id_gen✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc.utils.id_gen.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.utils.id_gen.IdGenerator
- Direction
- prqlc.semantic.lowering uses prqlc.utils.id_gen, so a change to prqlc.utils.id_gen can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.utils.id_gen.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→25 prqlc.semantic.lowering uses prqlc.ir.pl.expr✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.semantic.lowering.Lowerer→prqlc.ir.pl.expr.Exprprqlc.semantic.lowering.TableDepsCollector→prqlc.ir.pl.expr.Exprprqlc.semantic.lowering.lowering$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.semantic.lowering uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
37→33 prqlc.semantic.lowering uses prqlc.ir.pl.fold✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.lowering uses a type in prqlc.ir.pl.fold.
- The types involved
prqlc.semantic.lowering.TableDepsCollector→prqlc.ir.pl.fold.PlFold
- Direction
- prqlc.semantic.lowering uses prqlc.ir.pl.fold, so a change to prqlc.ir.pl.fold can break prqlc.semantic.lowering, while a change to prqlc.semantic.lowering can't break prqlc.ir.pl.fold.
- Position
- Below the diagonal: prqlc.semantic.lowering uses a module listed above it, which is the healthy direction.
38→4 prqlc.semantic.reporting uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.reporting uses a type in prqlc_parser.span.
- The types involved
prqlc.semantic.reporting.ExprGraphNode→prqlc_parser.span.Span
- Direction
- prqlc.semantic.reporting uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.semantic.reporting, while a change to prqlc.semantic.reporting can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.semantic.reporting uses a module listed above it, which is the healthy direction.
38→25 prqlc.semantic.reporting uses prqlc.ir.pl.expr✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.reporting uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.semantic.reporting.ExprGraphNode→prqlc.ir.pl.expr.ExprKindprqlc.semantic.reporting.FrameCollector→prqlc.ir.pl.expr.Exprprqlc.semantic.reporting.reporting$module→prqlc.ir.pl.expr.Expr
- Direction
- prqlc.semantic.reporting uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.semantic.reporting, while a change to prqlc.semantic.reporting can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.semantic.reporting uses a module listed above it, which is the healthy direction.
38→27 prqlc.semantic.reporting uses prqlc.ir.pl.stmt✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.reporting uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.semantic.reporting.FrameCollector→prqlc.ir.pl.stmt.ModuleDef
- Direction
- prqlc.semantic.reporting uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.semantic.reporting, while a change to prqlc.semantic.reporting can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc.semantic.reporting uses a module listed above it, which is the healthy direction.
38→33 prqlc.semantic.reporting uses prqlc.ir.pl.fold✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.reporting uses a type in prqlc.ir.pl.fold.
- The types involved
prqlc.semantic.reporting.FrameCollector→prqlc.ir.pl.fold.PlFold
- Direction
- prqlc.semantic.reporting uses prqlc.ir.pl.fold, so a change to prqlc.ir.pl.fold can break prqlc.semantic.reporting, while a change to prqlc.semantic.reporting can't break prqlc.ir.pl.fold.
- Position
- Below the diagonal: prqlc.semantic.reporting uses a module listed above it, which is the healthy direction.
39→2 prqlc.semantic.resolver uses prqlc_parser.parser.pr.ident✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.resolver uses a type in prqlc_parser.parser.pr.ident.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc_parser.parser.pr.ident.Ident
- Direction
- prqlc.semantic.resolver uses prqlc_parser.parser.pr.ident, so a change to prqlc_parser.parser.pr.ident can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc_parser.parser.pr.ident.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→3 prqlc.semantic.resolver uses prqlc.ir.pl.lineage✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.resolver uses a type in prqlc.ir.pl.lineage.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.ir.pl.lineage.Lineage
- Direction
- prqlc.semantic.resolver uses prqlc.ir.pl.lineage, so a change to prqlc.ir.pl.lineage can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.ir.pl.lineage.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→4 prqlc.semantic.resolver uses prqlc_parser.span✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.resolver uses a type in prqlc_parser.span.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc_parser.span.Span
- Direction
- prqlc.semantic.resolver uses prqlc_parser.span, so a change to prqlc_parser.span can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc_parser.span.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→7 prqlc.semantic.resolver uses prqlc_parser.parser.pr.types✕
- Connections
- 2 pairs of types, where a type in prqlc.semantic.resolver uses a type in prqlc_parser.parser.pr.types.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc_parser.parser.pr.types.Typrqlc.semantic.resolver.Resolver→prqlc_parser.parser.pr.types.TyTupleField
- Direction
- prqlc.semantic.resolver uses prqlc_parser.parser.pr.types, so a change to prqlc_parser.parser.pr.types can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc_parser.parser.pr.types.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→15 prqlc.semantic.resolver uses prqlc.ir.decl✕
- Connections
- 2 pairs of types, where a type in prqlc.semantic.resolver uses a type in prqlc.ir.decl.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.ir.decl.Moduleprqlc.semantic.resolver.Resolver→prqlc.ir.decl.RootModule
- Direction
- prqlc.semantic.resolver uses prqlc.ir.decl, so a change to prqlc.ir.decl can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.ir.decl.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→18 prqlc.semantic.resolver uses prqlc.utils.id_gen✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.resolver uses a type in prqlc.utils.id_gen.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.utils.id_gen.IdGenerator
- Direction
- prqlc.semantic.resolver uses prqlc.utils.id_gen, so a change to prqlc.utils.id_gen can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.utils.id_gen.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→25 prqlc.semantic.resolver uses prqlc.ir.pl.expr✕
- Connections
- 3 pairs of types, where a type in prqlc.semantic.resolver uses a type in prqlc.ir.pl.expr.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.ir.pl.expr.Exprprqlc.semantic.resolver.Resolver→prqlc.ir.pl.expr.Funcprqlc.semantic.resolver.Resolver→prqlc.ir.pl.expr.FuncParam
- Direction
- prqlc.semantic.resolver uses prqlc.ir.pl.expr, so a change to prqlc.ir.pl.expr can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.ir.pl.expr.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→26 prqlc.semantic.resolver uses prqlc.ir.pl.extra✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.resolver uses a type in prqlc.ir.pl.extra.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.ir.pl.extra.TransformCall
- Direction
- prqlc.semantic.resolver uses prqlc.ir.pl.extra, so a change to prqlc.ir.pl.extra can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.ir.pl.extra.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→27 prqlc.semantic.resolver uses prqlc.ir.pl.stmt✕
- Connections
- 2 pairs of types, where a type in prqlc.semantic.resolver uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.ir.pl.stmt.Stmtprqlc.semantic.resolver.Resolver→prqlc.ir.pl.stmt.VarDef
- Direction
- prqlc.semantic.resolver uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
39→33 prqlc.semantic.resolver uses prqlc.ir.pl.fold✕
- Connections
- 1 pair of types, where a type in prqlc.semantic.resolver uses a type in prqlc.ir.pl.fold.
- The types involved
prqlc.semantic.resolver.Resolver→prqlc.ir.pl.fold.PlFold
- Direction
- prqlc.semantic.resolver uses prqlc.ir.pl.fold, so a change to prqlc.ir.pl.fold can break prqlc.semantic.resolver, while a change to prqlc.semantic.resolver can't break prqlc.ir.pl.fold.
- Position
- Below the diagonal: prqlc.semantic.resolver uses a module listed above it, which is the healthy direction.
40→5 prqlc.json uses prqlc_parser.error✕
- Connections
- 1 pair of types, where a type in prqlc.json uses a type in prqlc_parser.error.
- The types involved
prqlc.json.json$module→prqlc_parser.error.Error
- Direction
- prqlc.json uses prqlc_parser.error, so a change to prqlc_parser.error can break prqlc.json, while a change to prqlc.json can't break prqlc_parser.error.
- Position
- Below the diagonal: prqlc.json uses a module listed above it, which is the healthy direction.
40→16 prqlc.json uses prqlc.ir.rq✕
- Connections
- 1 pair of types, where a type in prqlc.json uses a type in prqlc.ir.rq.
- The types involved
prqlc.json.json$module→prqlc.ir.rq.RelationalQuery
- Direction
- prqlc.json uses prqlc.ir.rq, so a change to prqlc.ir.rq can break prqlc.json, while a change to prqlc.json can't break prqlc.ir.rq.
- Position
- Below the diagonal: prqlc.json uses a module listed above it, which is the healthy direction.
40→27 prqlc.json uses prqlc.ir.pl.stmt✕
- Connections
- 1 pair of types, where a type in prqlc.json uses a type in prqlc.ir.pl.stmt.
- The types involved
prqlc.json.json$module→prqlc.ir.pl.stmt.ModuleDef
- Direction
- prqlc.json uses prqlc.ir.pl.stmt, so a change to prqlc.ir.pl.stmt can break prqlc.json, while a change to prqlc.json can't break prqlc.ir.pl.stmt.
- Position
- Below the diagonal: prqlc.json uses a module listed above it, which is the healthy direction.
40→36 prqlc.json uses prqlc.error_message✕
- Connections
- 1 pair of types, where a type in prqlc.json uses a type in prqlc.error_message.
- The types involved
prqlc.json.json$module→prqlc.error_message.ErrorMessages
- Direction
- prqlc.json uses prqlc.error_message, so a change to prqlc.error_message can break prqlc.json, while a change to prqlc.json can't break prqlc.error_message.
- Position
- Below the diagonal: prqlc.json uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 263 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 33 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Add tests that import the unreached modules (directly or through their public entry); 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; Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add tests that import the unreached modules (directly or through their public entry). | +5.0 pts | Medium | Test Coverage |
| 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. | +2.4 pts | Medium | Architecture documentation |
| Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes. | +2.4 pts | Medium | Library API & versioning |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals. | +1.8 pts | Medium | Import Boundaries |
| Resolve the 18 Orphaned file finding(s) in Knowledge Freshness — start with fold.rs (2), gen_query.rs, ast.rs. | +1.4 pts | Medium | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.0 pts | Medium | Documentation (README) |
| Dependabot is configured but does not watch `nuget`, `maven`, `composer` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers. | +0.8 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
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 53 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 — 53 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, 448 of 463 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
- D10 Test 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. The 10 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 18 test source file(s) (.rs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability NOT MEASURED: this repository's test suite spans .NET and JavaScript/TypeScript, and the JavaScript/TypeScript half could not be re-run — unit: measured (0 flaky); JavaScript/TypeScript (mocha via `npm install --ignore-scripts` (no lockfile) in grammars/prql-lezer/; mocha via `npm ci --ignore-scripts` in prqlc/bindings/js/): not included — the mocha run in grammars/prql-lezer/ produced no per-test report (Exception during run: Error [ERR_REQUIRE_CYCLE_MODULE]: Cannot require() ES Module grammars/prql-lezer/test/test-highlight.js in a cycle. (from grammars/prql-le…). No partial figure is published as if it were the whole: reliability is excluded from the score rather than counted as a near-zero.
- 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 reliability for the mocha suite in grammars/prql-lezer/ was NOT MEASURED: the mocha run in grammars/prql-lezer/ produced no per-test report (Exception during run: Error [ERR_REQUIRE_CYCLE_MODULE]: Cannot require() ES Module grammars/prql-lezer/test/test-highlight.js in a cycle. (from grammars/prql-le…). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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 reliability for the mocha suite in prqlc/bindings/js/ was NOT MEASURED: the mocha run in prqlc/bindings/js/ produced no per-test report (Exception during run: Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'prqlc/bindings/js/dist/node/prqlc_js.js' imported from prqlc/bindings/js/tests/test_all.…). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .rs (28,097 lines, 94% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 56 task marker(s) (TODO/FIXME/HACK/XXX) across 33 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated 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 — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- X12 Unreachable branch — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
22 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Resolver::resolve_special_func at 59. A further 12 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being TokenKind::fmt at 27 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: prqlc/prqlc-parser/src/lexer/lr.rs (TokenKind::fmt at 27), prqlc/prqlc/src/cli/highlight.rs (prqlc::cli::highlight::highlight_token_kind at 22), prqlc/prqlc/src/sql/dialect.rs (MsSqlDialect::translate_chrono_item at 22), prqlc/prqlc/src/semantic/ast_expand.rs (prqlc::semantic::ast_expand::expand_binary at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with Resolver::resolve_special_func (cyclomatic 59). — Refactoring it lifts Cyclomatic Complexity from 6.8 to about 7.5/10.
D2 · Cognitive Complexity
40 method(s) exceeded the cognitive complexity threshold of 15; the worst was Resolver::resolve_special_func at 67.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Resolver::resolve_special_func (cognitive 67). — Refactoring it lifts Cognitive Complexity from 5.5 to about 5.7/10.
D3 · God Classes
12 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with transforms.rs, gen_expr.rs, lowering.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with transforms.rs, lowering.rs, expr.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with gen_query.rs, docs_generator.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
17 duplicated block group(s) detected. 2.4 % of the production lines (820 of 33,647) are in a reported copy. A further 15 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with module.rs, expr.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with lib.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with lib.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
15 production modules (Maven+Cargo+npm+Composer+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 10 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 32 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 10 tests. Measured on the C# suite only — at least 18 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 148 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 144 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Cargo manifest, 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: prqlc/prqlc/src/codegen/ast.rs (9×24=216); prqlc/prqlc/src/sql/gen_query.rs (5×20=100) Repeated repair below the complexity floor: prqlc/prqlc/src/sql/dialect.rs (4 of 4 changes were fixes); prqlc/prqlc/src/sql/operators.rs (3 of 3 changes were fixes)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with ast.rs, gen_query.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with dialect.rs, operators.rs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
12 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is prqlc/prqlc/src/codegen/ast.rs. Counted over 85 of the 129 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).
D17 · Explicit Debt
0 deducted debt markers + 0 dead symbols across 387 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .rs (94% of production source) was not read, and carries at least 56 uncounted task marker(s) in 33 file(s).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 36 document(s) read across 6 unit(s).
D24 · Comment Value
0 of 32 judged comments only repeat the code they sit on (0.0 %). 3 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 2 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
264 finding(s): 0 critical, 251 high, 13 medium, 0 low. 170 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 8 file(s) — `REDACTED`, `prqlc/bindings/java/java/mvnw` (lines 195–196), `prqlc/prqlc/src/sql/gen_expr.rs` (line 1020), `web/website/themes/prql-theme/layouts/_default/baseof.html` (line 24, line 25), `REDACTED` (lines 1–4, lines 36–37, line 200), … (+3 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 8 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 36 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (36 issue-level).
- Resolve the 19 REDACTED finding(s) charged to Static Analysis (SAST) — the other 170 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (189 issue-level, 19 of them charged here).
- Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
D30 · Dependency Vulnerabilities
15 finding(s): 0 critical, 4 high, 11 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 0 medium, 2 low.
D34 · Knowledge Freshness
18 of 85 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is prqlc/prqlc/src/sql/pq/gen_query.rs. Counted over 85 of the 129 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 18 Orphaned file finding(s) in Knowledge Freshness — start with fold.rs (2), gen_query.rs, ast.rs. — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: decl.rs↔reporting.rs 55%; lib.rs↔mod.rs 54%; gen_query.rs↔context.rs 54%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with decl.rs, lib.rs, gen_query.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 10 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
- No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
- Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `maven`, `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `nuget`, `maven`, `composer` — add those `package-ecosystem` entries to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
- 4 typed · 4 plain JS — the untyped files are grammars/prql-lezer/src/highlight.js, grammars/prql-lezer/test/test-highlight.js, grammars/prql-lezer/test/test-prql.js, prqlc/bindings/js/tests/test_all.mjs.
R10 · Code Duplication
R11 · Import Boundaries
- web/playground/src/output/Output.jsx:6 imports react-syntax-highlighter/dist/esm/languages/hljs/sql, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — web/playground/src/output/Output.jsx:6
- web/playground/src/output/Output.jsx:7 imports react-syntax-highlighter/dist/esm/languages/hljs/yaml, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — web/playground/src/output/Output.jsx:7
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- Sidebar has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/playground/src/sidebar/Sidebar.jsx:4
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×13) — web/playground/src/workbench/Workbench.jsx:1, web/playground/src/output/Output.jsx:1, web/playground/generateBook.cjs:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 4 file(s) (~179 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — grammars/prql-lezer
- 1 file(s) (~159 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — prqlc/bindings/js
- Nothing imports this binding — it is safe to review for removal. (×2) — grammars/prql-lezer/src/highlight.js:45, web/prql-codemirror-demo/src/codemirror.ts:106
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in web/playground/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Cryptographic Hygiene
- `https://www.googletagmanager.com/gtag/js?id=G-LQJDD599T4` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — web/book/theme/head.hbs:2
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 70% | Adequate — gated by R11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by R4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 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 — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- 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 dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test reliability not measured — polyglot suite, one half not re-run
- D12 Dependency Hygiene — Dependency hygiene not measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .c, .cpp, .ex, .exs, .java, .php, .py, .rs, .ts, .zig, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half measured 28.6%; the JavaScript/TypeScript half could not be measured — grammars/prql-lezer/ runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 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
- IC1 Incompleteness & stubs — IC1 reached only 1% of this repository's production lines — rust (32,070 lines), javascript (1,552 lines), php (382 lines), java (286 lines), typescript (286 lines), elixir (194 lines), zig (105 lines), c (62 lines), python (42 lines), cpp (18 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- 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 by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- 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.
- 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.
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — rust (32,070 lines), javascript (1,552 lines), php (382 lines), java (286 lines), typescript (286 lines), elixir (194 lines), zig (105 lines), c (62 lines), python (42 lines), cpp (18 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — rust (32,070 lines), javascript (1,552 lines), php (382 lines), java (286 lines), typescript (286 lines), elixir (194 lines), zig (105 lines), c (62 lines), python (42 lines), cpp (18 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X3 Exception handling — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 255 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 178 finding(s)
- prqlc::cli::docs_generator::generate_html_docs (cognitive 43) prqlc/prqlc/src/cli/docs_generator.rs:13
- prqlc::cli::docs_generator::generate_markdown_docs (cognitive 43) prqlc/prqlc/src/cli/docs_generator.rs:176
- prqlc::sql::gen_query::translate_select_pipeline (cognitive 36) prqlc/prqlc/src/sql/gen_query.rs:73
- prqlc::sql::pq::anchor::split_off_back (cognitive 35) prqlc/prqlc/src/sql/pq/anchor.rs:69
- prqlc::sql::pq::preprocess::except (cognitive 34) prqlc/prqlc/src/sql/pq/preprocess.rs:306
- prqlc::sql::pq::preprocess::intersect (cognitive 30) prqlc/prqlc/src/sql/pq/preprocess.rs:404
- prqlc::semantic::resolver::types::is_super_type_of_kind (cognitive 27) prqlc/prqlc/src/semantic/resolver/types.rs:300
- prqlc::sql::gen_expr::translate_expr (cognitive 26) prqlc/prqlc/src/sql/gen_expr.rs:24
- prqlc::sql::gen_projection::translate_wildcards (cognitive 25) prqlc/prqlc/src/sql/gen_projection.rs:62
- prqlc::semantic::resolver::static_eval::static_eval_rq_operator (cognitive 23) prqlc/prqlc/src/semantic/resolver/static_eval.rs:24
- prqlc::semantic::lowering::try_extract_sql_columns (cognitive 22) prqlc/prqlc/src/semantic/lowering.rs:1055
- prqlc::sql::pq::gen_query::compile_relation_instance (cognitive 22) prqlc/prqlc/src/sql/pq/gen_query.rs:180
- prqlc::debug::render_html::write_json_ast_node (cognitive 17) prqlc/prqlc/src/debug/render_html.rs:393
- prqlc::cli::watch::watch_and_compile (cognitive 16) prqlc/prqlc/src/cli/watch.rs:64
- prqlc::sql::gen_expr::translate_cid (cognitive 16) prqlc/prqlc/src/sql/gen_expr.rs:694
- prqlc::sql::pq::preprocess::distinct (cognitive 16) prqlc/prqlc/src/sql/pq/preprocess.rs:126
- No test reaches this file web/playground/src/workbench/Workbench.jsx:1
- No test reaches this file web/playground/src/output/Output.jsx:1
- No test reaches this file web/playground/generateBook.cjs:1
- No test reaches this file web/playground/src/workbench/prql-syntax.js:1
- No test reaches this file web/prql-codemirror-demo/src/codemirror.ts:1
- No test reaches this file web/playground/src/sidebar/Sidebar.jsx:1
- No test reaches this file web/prql-codemirror-demo/src/lang-prql/complete.ts:1
- No test reaches this file web/playground/src/examples.js:1
- No test reaches this file web/playground/src/app/App.jsx:1
- No test reaches this file web/playground/src/workbench/duckdb.js:1
- No test reaches this file web/prql-codemirror-demo/src/main.ts:1
- No test reaches this file web/prql-codemirror-demo/src/lang-prql/prql.ts:1
- No test reaches this file web/playground/src/main.jsx:1
- prqlc::semantic::resolver::static_eval::static_eval_rq_operator (cyclomatic 20) prqlc/prqlc/src/semantic/resolver/static_eval.rs:24
- prqlc::sql::gen_query::translate_select_pipeline (cyclomatic 20) prqlc/prqlc/src/sql/gen_query.rs:73
- prqlc::cli::docs_generator::generate_html_docs (cyclomatic 19) prqlc/prqlc/src/cli/docs_generator.rs:13
- prqlc::cli::docs_generator::generate_markdown_docs (cyclomatic 19) prqlc/prqlc/src/cli/docs_generator.rs:176
- prqlc::sql::gen_expr::translate_expr (cyclomatic 19) prqlc/prqlc/src/sql/gen_expr.rs:24
- prqlc::semantic::resolver::types::is_super_type_of_kind (cyclomatic 18) prqlc/prqlc/src/semantic/resolver/types.rs:300
- prqlc::sql::pq::anchor::split_off_back (cyclomatic 18) prqlc/prqlc/src/sql/pq/anchor.rs:69
- prqlc::sql::pq::preprocess::except (cyclomatic 18) prqlc/prqlc/src/sql/pq/preprocess.rs:306
- prqlc::sql::pq::anchor::is_split_required (cyclomatic 17) prqlc/prqlc/src/sql/pq/anchor.rs:310
- prqlc::sql::pq::preprocess::intersect (cyclomatic 16) prqlc/prqlc/src/sql/pq/preprocess.rs:404
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Resolver::resolve_special_func (cognitive 67) prqlc/prqlc/src/semantic/resolver/transforms.rs:21
- Resolver::resolve_function_args (cognitive 38) prqlc/prqlc/src/semantic/resolver/functions.rs:217
- Resolver::fold_expr (cognitive 19) prqlc/prqlc/src/semantic/resolver/expr.rs:60
- Resolver::infer_type (cognitive 18) prqlc/prqlc/src/semantic/resolver/types.rs:9
- Resolver::resolve_ident_wildcard (cognitive 17) prqlc/prqlc/src/semantic/resolver/names.rs:235
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Resolver::resolve_special_func (cyclomatic 59) prqlc/prqlc/src/semantic/resolver/transforms.rs:21
- Resolver::infer_type (cyclomatic 23) prqlc/prqlc/src/semantic/resolver/types.rs:9
- Resolver::fold_expr (cyclomatic 20) prqlc/prqlc/src/semantic/resolver/expr.rs:60
- Resolver::resolve_function_args (cyclomatic 16) prqlc/prqlc/src/semantic/resolver/functions.rs:217
- FileTooLong: resolver/transforms.rs prqlc/prqlc/src/semantic/resolver/transforms.rs
- FileTooLong: sql/gen_expr.rs prqlc/prqlc/src/sql/gen_expr.rs
- FileTooLong: semantic/lowering.rs prqlc/prqlc/src/semantic/lowering.rs
- FileTooLong: debug/render_html.rs prqlc/prqlc/src/debug/render_html.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- prqlc_parser::lexer::parse_escape_sequence (cognitive 32) prqlc/prqlc-parser/src/lexer/mod.rs:637
- prqlc_parser::lexer::multi_quoted_string (cognitive 21) prqlc/prqlc-parser/src/lexer/mod.rs:703
- prqlc_parser::parser::perror::rich_error_to_error (cognitive 19) prqlc/prqlc-parser/src/parser/perror.rs:9
- SortingInference::fold_sql_query (cognitive 25) prqlc/prqlc/src/sql/pq/postprocess.rs:187
- SortingInference::alias_last_sorting (cognitive 22) prqlc/prqlc/src/sql/pq/postprocess.rs:59
- SortingInference::fold_sql_transforms (cognitive 22) prqlc/prqlc/src/sql/pq/postprocess.rs:321
- MethodTooLong: Resolver.resolve_special_func prqlc/prqlc/src/semantic/resolver/transforms.rs:21
- MethodTooLong: Lowerer.lower_table_ref prqlc/prqlc/src/semantic/lowering.rs:251
- MethodTooLong: Resolver.fold_expr prqlc/prqlc/src/semantic/resolver/expr.rs:60
- REDACTED
- REDACTED
- REDACTED
- Change coupling: decl.rs ↔ reporting.rs prqlc/prqlc/src/ir/decl.rs:1
- Change coupling: lib.rs ↔ mod.rs prqlc/prqlc-macros/src/lib.rs:1
- Change coupling: gen_query.rs ↔ context.rs prqlc/prqlc/src/sql/gen_query.rs:1
- Hotspot: prqlc/prqlc/src/codegen/ast.rs prqlc/prqlc/src/codegen/ast.rs:103
- Hotspot: prqlc/prqlc/src/sql/gen_query.rs prqlc/prqlc/src/sql/gen_query.rs:73
- Repeated repair: prqlc/prqlc/src/sql/dialect.rs prqlc/prqlc/src/sql/dialect.rs:129
- Repeated repair: prqlc/prqlc/src/sql/operators.rs prqlc/prqlc/src/sql/operators.rs:43
- Lowerer::lower_expr (cognitive 23) prqlc/prqlc/src/semantic/lowering.rs:869
- Lowerer::push_select (cognitive 17) prqlc/prqlc/src/semantic/lowering.rs:668
- REDACTED
- REDACTED
- FunctionTooLong: prqlc::sql::gen_query::translate_select_pipeline prqlc/prqlc/src/sql/gen_query.rs:73
- FunctionTooLong: prqlc::cli::docs_generator::generate_html_docs prqlc/prqlc/src/cli/docs_generator.rs:13
- REDACTED
- REDACTED
- Edited copy of a member (14 corresponding lines) prqlc/prqlc/src/semantic/module.rs:501
- Edited copy of a member (14 corresponding lines) prqlc/prqlc-parser/src/parser/expr.rs:368
- Edited copy of a member (8 corresponding lines) prqlc/bindings/java/src/lib.rs:50
- Edited copy of a member (8 corresponding lines) prqlc/bindings/elixir/native/prql/src/lib.rs:149
- Edited copy of a member (7 corresponding lines) prqlc/bindings/elixir/native/prql/src/lib.rs:160
- Edited copy of a member (7 corresponding lines) prqlc/bindings/elixir/native/prql/src/lib.rs:139
- Duplicated block (8 lines × 2) prqlc/prqlc/src/debug/render_html.rs:343
- Duplicated block (8 lines × 2) prqlc/prqlc/src/cli/docs_generator.rs:67
- Duplicated block (5 lines × 2) prqlc/prqlc/src/semantic/module.rs:506
- Duplicated block (5 lines × 2) prqlc/prqlc/src/semantic/resolver/static_eval.rs:57
- Duplicated block (9 lines × 2) prqlc/prqlc/src/ir/pl/fold.rs:162
- Duplicated block (9 lines × 2) prqlc/prqlc/src/semantic/resolver/transforms.rs:187
- Off the main sequence: prqlc-parser
- Off the main sequence: prqlc (Cargo)
- Boundary violation [package:third-party-deep-import] web/playground/src/output/Output.jsx:6
- Boundary violation [package:third-party-deep-import] web/playground/src/output/Output.jsx:7
- ExprKind::write (cyclomatic 24) prqlc/prqlc/src/codegen/ast.rs:103
- FrameCollector::fold_expr (cyclomatic 22) prqlc/prqlc/src/semantic/reporting.rs:98
- Lineage::apply_assign (cyclomatic 21) prqlc/prqlc/src/semantic/resolver/transforms.rs:1031
- Lowerer::lower_expr (cyclomatic 21) prqlc/prqlc/src/semantic/lowering.rs:869
- prqlc_parser::lexer::parse_escape_sequence (cyclomatic 20) prqlc/prqlc-parser/src/lexer/mod.rs:637
- Environment.getJniLibraryName (cyclomatic 19) prqlc/bindings/java/java/src/main/java/org/prql/prql4j/Environment.java:103
- Stmt::write (cyclomatic 18) prqlc/prqlc/src/codegen/ast.rs:400
- Command::execute (cyclomatic 17) prqlc/prqlc/src/cli/mod.rs:396
- Lineage::apply_assign (cognitive 59) prqlc/prqlc/src/semantic/resolver/transforms.rs:1031
- FrameCollector::fold_expr (cognitive 39) prqlc/prqlc/src/semantic/reporting.rs:98
- Environment.getJniLibraryName (cognitive 29) prqlc/bindings/java/java/src/main/java/org/prql/prql4j/Environment.java:103
- Stmt::write (cognitive 28) prqlc/prqlc/src/codegen/ast.rs:400
- Flattener::fold_expr (cognitive 23) prqlc/prqlc/src/semantic/resolver/flatten.rs:53
- ExprKind::write (cognitive 22) prqlc/prqlc/src/codegen/ast.rs:103
- Module::lookup::lookup_in (cognitive 21) prqlc/prqlc/src/semantic/module.rs:166
- mdbook_prql::replace_examples (cognitive 21) web/book/src/lib.rs:66
- prqlc_c::result_destroy (cognitive 19) prqlc/bindings/prqlc-c/src/lib.rs:206
- NativeLibraryLoader.loadLibraryFromJarToTemp (cognitive 18) prqlc/bindings/java/java/src/main/java/org/prql/prql4j/NativeLibraryLoader.java:67
- Command::execute (cognitive 16) prqlc/prqlc/src/cli/mod.rs:396
- REDACTED
- REDACTED
- REDACTED
- ClassTooLong: Lowerer prqlc/prqlc/src/semantic/lowering.rs:169
- TooManyFunctions: prqlc_parser::lexer prqlc/prqlc-parser/src/lexer/mod.rs:19
- TooManyMethods: Resolver prqlc/prqlc/src/semantic/resolver/mod.rs:15
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) prqlc/prqlc/src/debug/render_html.rs:302
- Edited copy of a member (118 corresponding lines) prqlc/prqlc/src/cli/docs_generator.rs:13
- Edited copies of one member (6 members, 25+ corresponding lines) prqlc/prqlc/src/sql/dialect.rs:368
- Edited copy of a member (20 corresponding lines) prqlc/prqlc-parser/src/lexer/mod.rs:308
- Edited copy of a member (17 corresponding lines) prqlc/prqlc-parser/src/parser/expr.rs:172
- Edited copy of a member (21 corresponding lines) prqlc/bindings/dotnet/PrqlCompiler/PrqlCompiler.cs:42
- Edited copy of a member (12 corresponding lines) prqlc/bindings/prqlc-c/src/lib.rs:29
- Edited copy of a member (16 corresponding lines) prqlc/prqlc-parser/src/lexer/mod.rs:67
- Edited copy of a member (6 corresponding lines) prqlc/bindings/prqlc-python/src/lib.rs:63
- Duplicated block (32 lines × 2) prqlc/prqlc/src/sql/dialect.rs:369
- Duplicated block (8–12 lines × 2) prqlc/prqlc-parser/src/lexer/mod.rs:309
- Duplicated block (16 lines × 2) prqlc/prqlc/src/semantic/lowering.rs:306
- Duplicated block (7–8 lines × 2) prqlc/prqlc/src/semantic/resolver/flatten.rs:86
- Duplicated block (11 lines × 2) prqlc/prqlc/src/cli/docs_generator.rs:54
- Duplicated block (10 lines × 2) prqlc/prqlc/src/semantic/resolver/names.rs:281
- Duplicated block (8 lines × 6) prqlc/prqlc/src/debug/render_html.rs:303
- Duplicated block (7 lines × 2) prqlc/prqlc/src/cli/docs_generator.rs:90
- Duplicated block (6 lines × 2) prqlc/prqlc/src/sql/gen_expr.rs:233
- Duplicated block (5 lines × 3) prqlc/prqlc/src/sql/dialect.rs:50
- Duplicated block (12 lines × 2) prqlc/prqlc/src/sql/dialect.rs:524
- Coverage not measured — JavaScript/TypeScript suite
- Coverage collected but not gated
- Type Safety
- Complex function Sidebar (cyclomatic 11, cognitive 16) web/playground/src/sidebar/Sidebar.jsx:4
- Unused dependency '@testing-library/react'
- Unused dependency '@testing-library/user-event'
- Third-party script without Subresource Integrity web/book/theme/head.hbs:2
- NuGet dependencies are not locked
- JavaScript dependencies are not locked grammars/prql-lezer/package.json:37
Minor — 29 finding(s)
- Orphaned file prqlc/prqlc/src/sql/pq/gen_query.rs:1
- Orphaned file prqlc/prqlc/src/ir/pl/fold.rs:1
- Orphaned file prqlc/prqlc/src/ir/rq/fold.rs:1
- Orphaned file prqlc/prqlc/src/sql/pq/ast.rs:1
- Orphaned file prqlc/bindings/php/src/Compiler.php:1
- Orphaned file prqlc/prqlc/src/semantic/resolver/inference.rs:1
- Orphaned file prqlc/prqlc/src/ir/decl.rs:1
- Orphaned file prqlc/prqlc/src/parser.rs:1
- Orphaned file prqlc/prqlc/src/ir/pl/expr.rs:1
- Orphaned file prqlc/bindings/java/java/src/main/java/org/prql/prql4j/NativeLibraryLoader.java:1
- Orphaned file prqlc/bindings/java/java/src/main/java/org/prql/prql4j/Environment.java:1
- Orphaned file prqlc/prqlc/src/debug/log.rs:1
- Orphaned file prqlc/prqlc/src/ir/pl/mod.rs:1
- Orphaned file prqlc/prqlc/src/utils/toposort.rs:1
- Orphaned file prqlc/prqlc-parser/src/parser/pr/types.rs:1
- Orphaned file prqlc/prqlc/src/ir/pl/extra.rs:1
- Orphaned file prqlc/prqlc/src/utils/id_gen.rs:1
- Orphaned file prqlc/prqlc-parser/src/parser/pr/stmt.rs:1
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No explicit versioning
- Dependabot does not watch nuget/maven/composer REDACTED:2
- Unused export 'prqlHighlight' grammars/prql-lezer/src/highlight.js:45
- Unused export 'minimalSetup' web/prql-codemirror-demo/src/codemirror.ts:106
Minor — 1 finding(s)
- doc comments repeat the names prqlc/bindings/dotnet/PrqlCompiler/PrqlCompiler.cs:15
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-83121039de4f44a3924b8b027f9bc5bd/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-83121039de4f44a3924b8b027f9bc5bd/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude web/website/themes/prql-theme/layouts/_default/_markup . | 264 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list prqlc/bindings/dotnet/prql-net.sln package --vulnerable --include-transitive --format json | 15 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | 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 |