Executive summary
effekt-lang/effekt is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because we found no recorded design decisions and no architecture document or diagram. It scores 54 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Maturity, at 48, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Completing the README is another step, worth about 4 points. Raising Maturity to 62 would lift the score to about 58.
Forty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version and passing outside input through environment variables would close both risks. Updating the vulnerable packages would fix the two packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 32,404 lines, about €40,000 to rebuild.
If Maturity rose from 48 to 62, the lowest score rated Strong, the score would rise from 54 to about 58.
New since the last survey: 26 findings
- Cyclomatic Complexity · Raise.stmt (cyclomatic 30) effekt/shared/src/main/scala/effekt/core/ArityRaising.scala
- Cyclomatic Complexity · LambdaSets.solve (cyclomatic 24) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cyclomatic Complexity · Collector.statement (cyclomatic 24) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cyclomatic Complexity · bodyRewriter.rewrite (cyclomatic 17) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cyclomatic Complexity · LambdaSets.assertMonomorphic (cyclomatic 16) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cognitive Complexity · LambdaSets.solve (cognitive 28) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cognitive Complexity · bodyRewriter.rewrite (cognitive 28) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cognitive Complexity · Specializer.result (cognitive 21) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cognitive Complexity · Deadcode.rewrite (cognitive 21) effekt/shared/src/main/scala/effekt/core/optimizer/Deadcode.scala
- Cognitive Complexity · Specializer.adapter (cognitive 19) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- Cognitive Complexity · Raise.stmt (cognitive 17) effekt/shared/src/main/scala/effekt/core/ArityRaising.scala
- God Classes · FileTooLong: core/LambdaSets.scala effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- God Classes · TooManyMethods: Specializer effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- God Classes · TooManyMethods: Raise effekt/shared/src/main/scala/effekt/core/ArityRaising.scala
- Code Duplication · Duplicated block (5 lines × 3) effekt/shared/src/main/scala/effekt/core/TestRenamer.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/machine/Transformer.scala effekt/shared/src/main/scala/effekt/machine/Transformer.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/core/Tree.scala effekt/shared/src/main/scala/effekt/core/Tree.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/generator/llvm/PrettyPrinter.scala effekt/shared/src/main/scala/effekt/generator/llvm/PrettyPrinter.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/Parser.scala effekt/shared/src/main/scala/effekt/Parser.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/machine/PrettyPrinter.scala effekt/shared/src/main/scala/effekt/machine/PrettyPrinter.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/generator/chez/Transformer.scala effekt/shared/src/main/scala/effekt/generator/chez/Transformer.scala
- Churn × Complexity Hotspots · Hotspot: effekt/shared/src/main/scala/effekt/core/Transformer.scala effekt/shared/src/main/scala/effekt/core/Transformer.scala
- Explicit Debt · TodoComment effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala
- Dependency Vulnerabilities · REDACTED
- Exception handling · Swallowed exception (caught, then discarded) effekt/jvm/src/main/scala/effekt/Runner.scala
- Exception handling · Swallowed exception (caught, then discarded) effekt/jvm/src/main/scala/effekt/Runner.scala
Fixed since the last survey: 6 findings
- Code Duplication · Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala
- Explicit Debt · TodoComment effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala
- Explicit Debt · TodoComment effekt/shared/src/main/scala/effekt/machine/Transformer.scala
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Documentation (README) · README may be stale
- Exception handling · Swallowed exception (caught, then discarded) effekt/jvm/src/main/scala/effekt/Runner.scala
Rebuild cost: about €40,000 · Estimate
| Cost to rebuild | €13,000 to €67,000, for 223 to 706 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 32,404 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 core.Mono.preprocess.DeBruijn | 2 core.Mono.specialize | 3 core.PatternMatchingCompiler | 4 core.Type | 5 core.optimizer.StaticResumptions | 6 core.substitutions | 7 lsp | 8 machine.Transformer | 9 cps | 10 util.messages | 11 generator.chez.Tree | 12 generator.js | 13 machine | 14 symbols.scopes | 15 generator.llvm | 16 source | 17 lexer | 18 typer.ExhaustivityChecker | 19 typer | 20 core.Mono | 21 core.Mono.preprocess | 22 symbols | 23 core.Tree | 24 core.LambdaSets.Specializer | 25 core.LambdaSets | 26 core | 27 core.ArityRaising | 28 namer | 29 context | 30 util | 31 context.Context | 32 core.vm | 33 core.vm.As | 34 Intelligence | 35 Repl | 36 core.Mono.collect | 37 effekt | 38 core.optimizer | 39 generator.chez | 40 source.Tree |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.Mono.preprocess.DeBruijn | 1 | |||||||||||||||||||||||||||||||||||||||
| 2 core.Mono.specialize | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 3 core.PatternMatchingCompiler | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 core.Type | 4 | |||||||||||||||||||||||||||||||||||||||
| 5 core.optimizer.StaticResumptions | 1 | 14 | ||||||||||||||||||||||||||||||||||||||
| 6 core.substitutions | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 lsp | 10 | |||||||||||||||||||||||||||||||||||||||
| 8 machine.Transformer | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 9 cps | 4 | 1 | 1 | 1 | 67 | 3 | ||||||||||||||||||||||||||||||||||
| 10 util.messages | 9 | 2 | 6 | |||||||||||||||||||||||||||||||||||||
| 11 generator.chez.Tree | 2 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||||||
| 12 generator.js | 2 | 1 | 4 | 1 | 24 | 3 | 7 | 3 | ||||||||||||||||||||||||||||||||
| 13 machine | 4 | 2 | 2 | 1 | 2 | 1 | 21 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||
| 14 symbols.scopes | 2 | 1 | 2 | 6 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 15 generator.llvm | 1 | 1 | 5 | 5 | 3 | 6 | 3 | |||||||||||||||||||||||||||||||||
| 16 source | 3 | 2 | 1 | 4 | 1 | 4 | 2 | 60 | 8 | 17 | 3 | |||||||||||||||||||||||||||||
| 17 lexer | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 18 typer.ExhaustivityChecker | 3 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 19 typer | 3 | 3 | 2 | 2 | 1 | 2 | 34 | 2 | 5 | 42 | 2 | 40 | 13 | 9 | 3 | |||||||||||||||||||||||||
| 20 core.Mono | 1 | 1 | 1 | 1 | 3 | 32 | 4 | 1 | 4 | |||||||||||||||||||||||||||||||
| 21 core.Mono.preprocess | 1 | 2 | 1 | 14 | 1 | |||||||||||||||||||||||||||||||||||
| 22 symbols | 2 | 1 | 25 | 1 | 8 | 47 | 3 | 17 | ||||||||||||||||||||||||||||||||
| 23 core.Tree | 3 | 62 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 core.LambdaSets.Specializer | 1 | 4 | 15 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 core.LambdaSets | 1 | 1 | 5 | 30 | 6 | |||||||||||||||||||||||||||||||||||
| 26 core | 4 | 1 | 1 | 3 | 4 | 1 | 6 | 21 | 2 | 6 | 7 | 2 | 31 | 10 | ||||||||||||||||||||||||||
| 27 core.ArityRaising | 2 | 19 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 namer | 1 | 1 | 1 | 1 | 15 | 8 | 15 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||||||
| 29 context | 2 | 2 | 1 | 4 | 2 | 6 | 10 | 1 | 2 | 1 | 9 | 1 | ||||||||||||||||||||||||||||
| 30 util | 2 | 1 | 3 | 5 | 2 | 3 | 12 | 3 | 21 | |||||||||||||||||||||||||||||||
| 31 context.Context | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 core.vm | 1 | 7 | 2 | 2 | 7 | |||||||||||||||||||||||||||||||||||
| 33 core.vm.As | 2 | 10 | ||||||||||||||||||||||||||||||||||||||
| 34 Intelligence | 1 | 2 | 1 | 12 | ||||||||||||||||||||||||||||||||||||
| 35 Repl | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 core.Mono.collect | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 effekt | 9 | 1 | 2 | 2 | 1 | 1 | 5 | 11 | 11 | 28 | 8 | 2 | ||||||||||||||||||||||||||||
| 38 core.optimizer | 3 | 1 | 3 | 2 | 54 | 4 | 6 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||
| 39 generator.chez | 1 | 8 | 5 | 4 | 1 | 8 | 3 | 43 | 2 | 7 | 5 | |||||||||||||||||||||||||||||
| 40 source.Tree | 2 | 2 | 11 | 1 | 8 | 2 | 2 | 1 |
1→26 core.Mono.preprocess.DeBruijn uses core part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono.preprocess.DeBruijn uses a type in core.
- The types involved
effekt.core.Mono.preprocess.DeBruijn.Environment→effekt.core.Id
- Direction
- core.Mono.preprocess.DeBruijn uses core, so a change to core can break core.Mono.preprocess.DeBruijn, while a change to core.Mono.preprocess.DeBruijn can't break core.
- 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.
2→25 core.Mono.specialize uses core.LambdaSets part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono.specialize uses a type in core.LambdaSets.
- The types involved
effekt.core.Mono.specialize.State→effekt.core.LambdaSets.Solution
- Direction
- core.Mono.specialize uses core.LambdaSets, so a change to core.LambdaSets can break core.Mono.specialize, while a change to core.Mono.specialize can't break core.LambdaSets.
- 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.
2→26 core.Mono.specialize uses core part of a loop✕
- Connections
- 2 pairs of types, where a type in core.Mono.specialize uses a type in core.
- The types involved
effekt.core.Mono.specialize.Binders→effekt.core.Ideffekt.core.Mono.specialize.State→effekt.core.Id
- Direction
- core.Mono.specialize uses core, so a change to core can break core.Mono.specialize, while a change to core.Mono.specialize can't break core.
- 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.
2→31 core.Mono.specialize uses context.Context part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono.specialize uses a type in context.Context.
- The types involved
effekt.core.Mono.specialize.State→effekt.context.Context.State
- Direction
- core.Mono.specialize uses context.Context, so a change to context.Context can break core.Mono.specialize, while a change to core.Mono.specialize can't break context.Context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→33 core.Mono.specialize uses core.vm.As part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono.specialize uses a type in core.vm.As.
- The types involved
effekt.core.Mono.specialize.Binders→effekt.core.vm.As.Int
- Direction
- core.Mono.specialize uses core.vm.As, so a change to core.vm.As can break core.Mono.specialize, while a change to core.Mono.specialize can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→26 core.PatternMatchingCompiler uses core part of a loop✕
- Connections
- 1 pair of types, where a type in core.PatternMatchingCompiler uses a type in core.
- The types involved
effekt.core.PatternMatchingCompiler.Clause→effekt.core.ValueType
- Direction
- core.PatternMatchingCompiler uses core, so a change to core can break core.PatternMatchingCompiler, while a change to core.PatternMatchingCompiler can't break core.
- 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→26 core.Type uses core part of a loop✕
- Connections
- 4 pairs of types, where a type in core.Type uses a type in core.
- The types involved
effekt.core.Type.MatchClause→effekt.core.Ideffekt.core.Type.MatchClause→effekt.core.ValueTypeeffekt.core.Type.TState→effekt.core.BlockTypeeffekt.core.Type.TState→effekt.core.ValueType
- Direction
- core.Type uses core, so a change to core can break core.Type, while a change to core.Type can't break core.
- 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→23 core.optimizer.StaticResumptions uses core.Tree part of a loop✕
- Connections
- 1 pair of types, where a type in core.optimizer.StaticResumptions uses a type in core.Tree.
- The types involved
effekt.core.optimizer.StaticResumptions.reduce→effekt.core.Tree.Rewrite
- Direction
- core.optimizer.StaticResumptions uses core.Tree, so a change to core.Tree can break core.optimizer.StaticResumptions, while a change to core.optimizer.StaticResumptions can't break core.Tree.
- 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→26 core.optimizer.StaticResumptions uses core part of a loop✕
- Connections
- 14 pairs of types, where a type in core.optimizer.StaticResumptions uses a type in core.
- The types involved
effekt.core.optimizer.StaticResumptions.Continuation→effekt.core.Stmteffekt.core.optimizer.StaticResumptions.Frame→effekt.core.Freeeffekt.core.optimizer.StaticResumptions.Frame→effekt.core.Ideffekt.core.optimizer.StaticResumptions.Frame→effekt.core.Stmteffekt.core.optimizer.StaticResumptions.Prompt→effekt.core.BlockParameffekt.core.optimizer.StaticResumptions.Prompt→effekt.core.Ideffekt.core.optimizer.StaticResumptions.Prompt→effekt.core.ValueTypeeffekt.core.optimizer.StaticResumptions.Shift→effekt.core.Ideffekt.core.optimizer.StaticResumptions.Shift→effekt.core.Stmteffekt.core.optimizer.StaticResumptions.Shift→effekt.core.ValueTypeeffekt.core.optimizer.StaticResumptions.TailPositions→effekt.core.Freeeffekt.core.optimizer.StaticResumptions.TailPositions→effekt.core.Ideffekt.core.optimizer.StaticResumptions.TailPositions→effekt.core.Stmteffekt.core.optimizer.StaticResumptions.reduce→effekt.core.Stmt
- Direction
- core.optimizer.StaticResumptions uses core, so a change to core can break core.optimizer.StaticResumptions, while a change to core.optimizer.StaticResumptions can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→22 core.substitutions uses symbols part of a loop✕
- Connections
- 1 pair of types, where a type in core.substitutions uses a type in symbols.
- The types involved
effekt.core.substitutions.Substitution→effekt.symbols.Captures
- Direction
- core.substitutions uses symbols, so a change to symbols can break core.substitutions, while a change to core.substitutions can't break symbols.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→26 core.substitutions uses core part of a loop✕
- Connections
- 6 pairs of types, where a type in core.substitutions uses a type in core.
- The types involved
effekt.core.substitutions.Substitution→effekt.core.Blockeffekt.core.substitutions.Substitution→effekt.core.BlockParameffekt.core.substitutions.Substitution→effekt.core.Expreffekt.core.substitutions.Substitution→effekt.core.Ideffekt.core.substitutions.Substitution→effekt.core.ValueParameffekt.core.substitutions.Substitution→effekt.core.ValueType
- Direction
- core.substitutions uses core, so a change to core can break core.substitutions, while a change to core.substitutions can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→30 core.substitutions uses util part of a loop✕
- Connections
- 1 pair of types, where a type in core.substitutions uses a type in util.
- The types involved
effekt.core.substitutions.Substitution→effekt.util.DB
- Direction
- core.substitutions uses util, so a change to util can break core.substitutions, while a change to core.substitutions can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→33 lsp uses core.vm.As part of a loop✕
- Connections
- 10 pairs of types, where a type in lsp uses a type in core.vm.As.
- The types involved
effekt.lsp.CaptureInfo→effekt.core.vm.As.Stringeffekt.lsp.Diagnostic→effekt.core.vm.As.Stringeffekt.lsp.NotificationMessage→effekt.core.vm.As.Stringeffekt.lsp.Position→effekt.core.vm.As.Inteffekt.lsp.RequestMessage→effekt.core.vm.As.Inteffekt.lsp.RequestMessage→effekt.core.vm.As.Stringeffekt.lsp.ResponseError→effekt.core.vm.As.Inteffekt.lsp.ResponseError→effekt.core.vm.As.Stringeffekt.lsp.ResponseMessage→effekt.core.vm.As.Inteffekt.lsp.ResponseMessage→effekt.core.vm.As.String
- Direction
- lsp uses core.vm.As, so a change to core.vm.As can break lsp, while a change to lsp can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→13 machine.Transformer uses machine part of a loop✕
- Connections
- 2 pairs of types, where a type in machine.Transformer uses a type in machine.
- The types involved
effekt.machine.Transformer.Binding→effekt.machine.Statementeffekt.machine.Transformer.BlocksParamsContext→effekt.machine.Label
- Direction
- machine.Transformer uses machine, so a change to machine can break machine.Transformer, while a change to machine.Transformer can't break machine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→15 machine.Transformer uses generator.llvm part of a loop✕
- Connections
- 1 pair of types, where a type in machine.Transformer uses a type in generator.llvm.
- The types involved
effekt.machine.Transformer.BlocksParamsContext→effekt.generator.llvm.Definition
- Direction
- machine.Transformer uses generator.llvm, so a change to generator.llvm can break machine.Transformer, while a change to machine.Transformer can't break generator.llvm.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→22 machine.Transformer uses symbols part of a loop✕
- Connections
- 1 pair of types, where a type in machine.Transformer uses a type in symbols.
- The types involved
effekt.machine.Transformer.BlocksParamsContext→effekt.symbols.Symbol
- Direction
- machine.Transformer uses symbols, so a change to symbols can break machine.Transformer, while a change to machine.Transformer can't break symbols.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→26 machine.Transformer uses core part of a loop✕
- Connections
- 2 pairs of types, where a type in machine.Transformer uses a type in core.
- The types involved
effekt.machine.Transformer.Binding→effekt.core.Bindingeffekt.machine.Transformer.BlocksParamsContext→effekt.core.Id
- Direction
- machine.Transformer uses core, so a change to core can break machine.Transformer, while a change to machine.Transformer can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→30 machine.Transformer uses util part of a loop✕
- Connections
- 1 pair of types, where a type in machine.Transformer uses a type in util.
- The types involved
effekt.machine.Transformer.Binding→effekt.util.Trampoline
- Direction
- machine.Transformer uses util, so a change to util can break machine.Transformer, while a change to machine.Transformer can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 cps uses core.PatternMatchingCompiler✕
- Connections
- 4 pairs of types, where a type in cps uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.cps.Contify→effekt.core.PatternMatchingCompiler.Clauseeffekt.cps.PrettyPrinter→effekt.core.PatternMatchingCompiler.Clauseeffekt.cps.Transformer→effekt.core.PatternMatchingCompiler.Clauseeffekt.cps.substitutions→effekt.core.PatternMatchingCompiler.Clause
- Direction
- cps uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break cps, while a change to cps can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: cps uses a module listed above it, which is the healthy direction.
9→5 cps uses core.optimizer.StaticResumptions✕
- Connections
- 1 pair of types, where a type in cps uses a type in core.optimizer.StaticResumptions.
- The types involved
effekt.cps.Transformer→effekt.core.optimizer.StaticResumptions.Continuation
- Direction
- cps uses core.optimizer.StaticResumptions, so a change to core.optimizer.StaticResumptions can break cps, while a change to cps can't break core.optimizer.StaticResumptions.
- Position
- Below the diagonal: cps uses a module listed above it, which is the healthy direction.
9→6 cps uses core.substitutions✕
- Connections
- 1 pair of types, where a type in cps uses a type in core.substitutions.
- The types involved
effekt.cps.substitutions→effekt.core.substitutions.Substitution
- Direction
- cps uses core.substitutions, so a change to core.substitutions can break cps, while a change to cps can't break core.substitutions.
- Position
- Below the diagonal: cps uses a module listed above it, which is the healthy direction.
9→22 cps uses symbols part of a loop✕
- Connections
- 1 pair of types, where a type in cps uses a type in symbols.
- The types involved
effekt.cps.PrettyPrinter→effekt.symbols.Symbol
- Direction
- cps uses symbols, so a change to symbols can break cps, while a change to cps can't break symbols.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→26 cps uses core part of a loop✕
- Connections
- 67 pairs of types, where a type in cps uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.cps.Block→effekt.core.Treeeffekt.cps.Clause→effekt.core.Ideffekt.cps.Clause→effekt.core.Stmteffekt.cps.Clause→effekt.core.Treeeffekt.cps.Cont→effekt.core.Treeeffekt.cps.Contify→effekt.core.Blockeffekt.cps.Contify→effekt.core.Expreffekt.cps.Contify→effekt.core.Externeffekt.cps.Contify→effekt.core.ExternBodyeffekt.cps.Contify→effekt.core.Ideffekt.cps.Contify→effekt.core.Implementationeffekt.cps.Contify→effekt.core.ModuleDecleffekt.cps.Contify→effekt.core.Operationeffekt.cps.Contify→effekt.core.Stmteffekt.cps.Continuation→effekt.core.Expreffekt.cps.Continuation→effekt.core.Ideffekt.cps.Continuation→effekt.core.Stmteffekt.cps.Continuation→effekt.core.ValueTypeeffekt.cps.Def→effekt.core.Blockeffekt.cps.Def→effekt.core.Ideffekt.cps.Def→effekt.core.Treeeffekt.cps.Expr→effekt.core.Treeeffekt.cps.Extern→effekt.core.Treeeffekt.cps.ExternBody→effekt.core.Treeeffekt.cps.Implementation→effekt.core.Operation
- Direction
- cps uses core, so a change to core can break cps, while a change to cps can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→33 cps uses core.vm.As part of a loop✕
- Connections
- 3 pairs of types, where a type in cps uses a type in core.vm.As.
- The types involved
effekt.cps.ModuleDecl→effekt.core.vm.As.Stringeffekt.cps.PrettyPrinter→effekt.core.vm.As.Stringeffekt.cps.Tree→effekt.core.vm.As.Int
- Direction
- cps uses core.vm.As, so a change to core.vm.As can break cps, while a change to cps can't break core.vm.As.
- 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→7 util.messages uses lsp✕
- Connections
- 9 pairs of types, where a type in util.messages uses a type in lsp.
- The types involved
effekt.util.messages.AmbiguousOverloadError→effekt.lsp.Rangeeffekt.util.messages.EffektMessaging→effekt.lsp.Rangeeffekt.util.messages.ErrorReporter→effekt.lsp.Rangeeffekt.util.messages.FailedOverloadError→effekt.lsp.Rangeeffekt.util.messages.ImplicitInstantiationError→effekt.lsp.Rangeeffekt.util.messages.ImplicitMaxRecursionError→effekt.lsp.Rangeeffekt.util.messages.ParseError→effekt.lsp.Rangeeffekt.util.messages.PlainTextError→effekt.lsp.Rangeeffekt.util.messages.StructuredError→effekt.lsp.Range
- Direction
- util.messages uses lsp, so a change to lsp can break util.messages, while a change to util.messages can't break lsp.
- Position
- Below the diagonal: util.messages uses a module listed above it, which is the healthy direction.
10→26 util.messages uses core part of a loop✕
- Connections
- 2 pairs of types, where a type in util.messages uses a type in core.
- The types involved
effekt.util.messages.ErrorReporter→effekt.core.Treeeffekt.util.messages.ImplicitInstantiationError→effekt.core.Type
- Direction
- util.messages uses core, so a change to core can break util.messages, while a change to util.messages can't break core.
- 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→33 util.messages uses core.vm.As part of a loop✕
- Connections
- 6 pairs of types, where a type in util.messages uses a type in core.vm.As.
- The types involved
effekt.util.messages.DebugMessaging→effekt.core.vm.As.Stringeffekt.util.messages.EffektMessaging→effekt.core.vm.As.Stringeffekt.util.messages.ErrorReporter→effekt.core.vm.As.Stringeffekt.util.messages.ImplicitMaxRecursionError→effekt.core.vm.As.Stringeffekt.util.messages.ParseError→effekt.core.vm.As.Stringeffekt.util.messages.PlainTextError→effekt.core.vm.As.String
- Direction
- util.messages uses core.vm.As, so a change to core.vm.As can break util.messages, while a change to util.messages can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→9 generator.chez.Tree uses cps✕
- Connections
- 2 pairs of types, where a type in generator.chez.Tree uses a type in cps.
- The types involved
effekt.generator.chez.Tree.Query→effekt.cps.Defeffekt.generator.chez.Tree.Rewrite→effekt.cps.Def
- Direction
- generator.chez.Tree uses cps, so a change to cps can break generator.chez.Tree, while a change to generator.chez.Tree can't break cps.
- Position
- Below the diagonal: generator.chez.Tree uses a module listed above it, which is the healthy direction.
11→23 generator.chez.Tree uses core.Tree part of a loop✕
- Connections
- 1 pair of types, where a type in generator.chez.Tree uses a type in core.Tree.
- The types involved
effekt.generator.chez.Tree.Visit→effekt.core.Tree.Query
- Direction
- generator.chez.Tree uses core.Tree, so a change to core.Tree can break generator.chez.Tree, while a change to generator.chez.Tree can't break core.Tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→26 generator.chez.Tree uses core part of a loop✕
- Connections
- 8 pairs of types, where a type in generator.chez.Tree uses a type in core.
- The types involved
effekt.generator.chez.Tree.Query→effekt.core.Bindingeffekt.generator.chez.Tree.Query→effekt.core.Blockeffekt.generator.chez.Tree.Query→effekt.core.Expreffekt.generator.chez.Tree.Query→effekt.core.Operationeffekt.generator.chez.Tree.Rewrite→effekt.core.Bindingeffekt.generator.chez.Tree.Rewrite→effekt.core.Blockeffekt.generator.chez.Tree.Rewrite→effekt.core.Expreffekt.generator.chez.Tree.Rewrite→effekt.core.Operation
- Direction
- generator.chez.Tree uses core, so a change to core can break generator.chez.Tree, while a change to generator.chez.Tree can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→30 generator.chez.Tree uses util part of a loop✕
- Connections
- 2 pairs of types, where a type in generator.chez.Tree uses a type in util.
- The types involved
effekt.generator.chez.Tree.Query→effekt.util.Structuraleffekt.generator.chez.Tree.Rewrite→effekt.util.Structural
- Direction
- generator.chez.Tree uses util, so a change to util can break generator.chez.Tree, while a change to generator.chez.Tree can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 generator.js uses core.PatternMatchingCompiler✕
- Connections
- 2 pairs of types, where a type in generator.js uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.generator.js.PrettyPrinter→effekt.core.PatternMatchingCompiler.Patterneffekt.generator.js.TransformerCps→effekt.core.PatternMatchingCompiler.Clause
- Direction
- generator.js uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break generator.js, while a change to generator.js can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: generator.js uses a module listed above it, which is the healthy direction.
12→6 generator.js uses core.substitutions✕
- Connections
- 1 pair of types, where a type in generator.js uses a type in core.substitutions.
- The types involved
effekt.generator.js.TransformerCps→effekt.core.substitutions.Substitution
- Direction
- generator.js uses core.substitutions, so a change to core.substitutions can break generator.js, while a change to generator.js can't break core.substitutions.
- Position
- Below the diagonal: generator.js uses a module listed above it, which is the healthy direction.
12→9 generator.js uses cps✕
- Connections
- 4 pairs of types, where a type in generator.js uses a type in cps.
- The types involved
effekt.generator.js.TransformerCps→effekt.cps.Conteffekt.generator.js.TransformerCps→effekt.cps.Defeffekt.generator.js.TransformerCps→effekt.cps.MetaConteffekt.generator.js.TransformerCps→effekt.cps.ToplevelDefinition
- Direction
- generator.js uses cps, so a change to cps can break generator.js, while a change to generator.js can't break cps.
- Position
- Below the diagonal: generator.js uses a module listed above it, which is the healthy direction.
12→22 generator.js uses symbols part of a loop✕
- Connections
- 1 pair of types, where a type in generator.js uses a type in symbols.
- The types involved
effekt.generator.js.TransformerCps→effekt.symbols.TermSymbol
- Direction
- generator.js uses symbols, so a change to symbols can break generator.js, while a change to generator.js can't break symbols.
- 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→26 generator.js uses core part of a loop✕
- Connections
- 24 pairs of types, where a type in generator.js uses a type in core.
- The types involved
effekt.generator.js.$effekt→effekt.core.Expreffekt.generator.js.Binding→effekt.core.Bindingeffekt.generator.js.Export→effekt.core.Expreffekt.generator.js.JavaScript→effekt.core.Stmteffekt.generator.js.JavaScriptInterpolator→effekt.core.Expreffekt.generator.js.Module→effekt.core.Stmteffekt.generator.js.PrettyPrinter→effekt.core.Expreffekt.generator.js.PrettyPrinter→effekt.core.Stmteffekt.generator.js.Transformer→effekt.core.Constructoreffekt.generator.js.Transformer→effekt.core.DeclarationContexteffekt.generator.js.Transformer→effekt.core.Expreffekt.generator.js.Transformer→effekt.core.Ideffekt.generator.js.Transformer→effekt.core.Stmteffekt.generator.js.TransformerCps→effekt.core.Bindingeffekt.generator.js.TransformerCps→effekt.core.Blockeffekt.generator.js.TransformerCps→effekt.core.Declarationeffekt.generator.js.TransformerCps→effekt.core.DeclarationContexteffekt.generator.js.TransformerCps→effekt.core.Expreffekt.generator.js.TransformerCps→effekt.core.Externeffekt.generator.js.TransformerCps→effekt.core.Ideffekt.generator.js.TransformerCps→effekt.core.Implementationeffekt.generator.js.TransformerCps→effekt.core.ModuleDecleffekt.generator.js.TransformerCps→effekt.core.Stmteffekt.generator.js.TransformerCps→effekt.core.Transformer
- Direction
- generator.js uses core, so a change to core can break generator.js, while a change to generator.js can't break core.
- 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→29 generator.js uses context part of a loop✕
- Connections
- 3 pairs of types, where a type in generator.js uses a type in context.
- The types involved
effekt.generator.js.JavaScript→effekt.context.Contexteffekt.generator.js.Transformer→effekt.context.Contexteffekt.generator.js.TransformerCps→effekt.context.Context
- Direction
- generator.js uses context, so a change to context can break generator.js, while a change to generator.js can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→33 generator.js uses core.vm.As part of a loop✕
- Connections
- 7 pairs of types, where a type in generator.js uses a type in core.vm.As.
- The types involved
effekt.generator.js.$effekt→effekt.core.vm.As.Stringeffekt.generator.js.JSName→effekt.core.vm.As.Stringeffekt.generator.js.JavaScript→effekt.core.vm.As.Stringeffekt.generator.js.PrettyPrinter→effekt.core.vm.As.Stringeffekt.generator.js.Transformer→effekt.core.vm.As.Inteffekt.generator.js.Transformer→effekt.core.vm.As.Stringeffekt.generator.js.TransformerCps→effekt.core.vm.As.Int
- Direction
- generator.js uses core.vm.As, so a change to core.vm.As can break generator.js, while a change to generator.js can't break core.vm.As.
- 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→37 generator.js uses effekt part of a loop✕
- Connections
- 3 pairs of types, where a type in generator.js uses a type in effekt.
- The types involved
effekt.generator.js.JavaScript→effekt.Compilereffekt.generator.js.JavaScript→effekt.Stageeffekt.generator.js.TransformerCps→effekt.Template
- Direction
- generator.js uses effekt, so a change to effekt can break generator.js, while a change to generator.js can't break effekt.
- 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→1 machine uses core.Mono.preprocess.DeBruijn✕
- Connections
- 4 pairs of types, where a type in machine uses a type in core.Mono.preprocess.DeBruijn.
- The types involved
effekt.machine.Clause→effekt.core.Mono.preprocess.DeBruijn.Environmenteffekt.machine.Label→effekt.core.Mono.preprocess.DeBruijn.Environmenteffekt.machine.PrettyPrinter→effekt.core.Mono.preprocess.DeBruijn.Environmenteffekt.machine.Transformer→effekt.core.Mono.preprocess.DeBruijn.Environment
- Direction
- machine uses core.Mono.preprocess.DeBruijn, so a change to core.Mono.preprocess.DeBruijn can break machine, while a change to machine can't break core.Mono.preprocess.DeBruijn.
- Position
- Below the diagonal: machine uses a module listed above it, which is the healthy direction.
13→3 machine uses core.PatternMatchingCompiler✕
- Connections
- 2 pairs of types, where a type in machine uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.machine.PrettyPrinter→effekt.core.PatternMatchingCompiler.Clauseeffekt.machine.Transformer→effekt.core.PatternMatchingCompiler.Clause
- Direction
- machine uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break machine, while a change to machine can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: machine uses a module listed above it, which is the healthy direction.
13→8 machine uses machine.Transformer✕
- Connections
- 2 pairs of types, where a type in machine uses a type in machine.Transformer.
- The types involved
effekt.machine.Transformer→effekt.machine.Transformer.BlockInfoeffekt.machine.Transformer→effekt.machine.Transformer.BlocksParamsContext
- Direction
- machine uses machine.Transformer, so a change to machine.Transformer can break machine, while a change to machine can't break machine.Transformer.
- Position
- Below the diagonal: machine uses a module listed above it, which is the healthy direction.
13→10 machine uses util.messages✕
- Connections
- 1 pair of types, where a type in machine uses a type in util.messages.
- The types involved
effekt.machine.Transformer→effekt.util.messages.ErrorReporter
- Direction
- machine uses util.messages, so a change to util.messages can break machine, while a change to machine can't break util.messages.
- Position
- Below the diagonal: machine uses a module listed above it, which is the healthy direction.
13→15 machine uses generator.llvm part of a loop✕
- Connections
- 2 pairs of types, where a type in machine uses a type in generator.llvm.
- The types involved
effekt.machine.PrettyPrinter→effekt.generator.llvm.Definitioneffekt.machine.Program→effekt.generator.llvm.Definition
- Direction
- machine uses generator.llvm, so a change to generator.llvm can break machine, while a change to machine can't break generator.llvm.
- 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→22 machine uses symbols part of a loop✕
- Connections
- 1 pair of types, where a type in machine uses a type in symbols.
- The types involved
effekt.machine.Transformer→effekt.symbols.TermSymbol
- Direction
- machine uses symbols, so a change to symbols can break machine, while a change to machine can't break symbols.
- 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→26 machine uses core part of a loop✕
- Connections
- 21 pairs of types, where a type in machine uses a type in core.
- The types involved
effekt.machine.PrettyPrinter→effekt.core.Typeeffekt.machine.Program→effekt.core.Declarationeffekt.machine.Transformer→effekt.core.Bindingeffekt.machine.Transformer→effekt.core.Blockeffekt.machine.Transformer→effekt.core.BlockParameffekt.machine.Transformer→effekt.core.BlockTypeeffekt.machine.Transformer→effekt.core.Declarationeffekt.machine.Transformer→effekt.core.DeclarationContexteffekt.machine.Transformer→effekt.core.Expreffekt.machine.Transformer→effekt.core.Externeffekt.machine.Transformer→effekt.core.ExternBodyeffekt.machine.Transformer→effekt.core.Ideffekt.machine.Transformer→effekt.core.Implementationeffekt.machine.Transformer→effekt.core.ModuleDecleffekt.machine.Transformer→effekt.core.Operationeffekt.machine.Transformer→effekt.core.Stmteffekt.machine.Transformer→effekt.core.Topleveleffekt.machine.Transformer→effekt.core.Typeeffekt.machine.Transformer→effekt.core.ValueParameffekt.machine.Transformer→effekt.core.ValueTypeeffekt.machine.Variable→effekt.core.Type
- Direction
- machine uses core, so a change to core can break machine, while a change to machine can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 machine uses context part of a loop✕
- Connections
- 1 pair of types, where a type in machine uses a type in context.
- The types involved
effekt.machine.Transformer→effekt.context.Context
- Direction
- machine uses context, so a change to context can break machine, while a change to machine can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→30 machine uses util part of a loop✕
- Connections
- 1 pair of types, where a type in machine uses a type in util.
- The types involved
effekt.machine.Transformer→effekt.util.Trampoline
- Direction
- machine uses util, so a change to util can break machine, while a change to machine can't break util.
- 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→33 machine uses core.vm.As part of a loop✕
- Connections
- 4 pairs of types, where a type in machine uses a type in core.vm.As.
- The types involved
effekt.machine.Label→effekt.core.vm.As.Stringeffekt.machine.PrettyPrinter→effekt.core.vm.As.Stringeffekt.machine.Transformer→effekt.core.vm.As.Stringeffekt.machine.Variable→effekt.core.vm.As.String
- Direction
- machine uses core.vm.As, so a change to core.vm.As can break machine, while a change to machine can't break core.vm.As.
- 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→37 machine uses effekt part of a loop✕
- Connections
- 1 pair of types, where a type in machine uses a type in effekt.
- The types involved
effekt.machine.Transformer→effekt.Template
- Direction
- machine uses effekt, so a change to effekt can break machine, while a change to machine can't break effekt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→10 symbols.scopes uses util.messages✕
- Connections
- 2 pairs of types, where a type in symbols.scopes uses a type in util.messages.
- The types involved
effekt.symbols.scopes.Scope→effekt.util.messages.ErrorReportereffekt.symbols.scopes.Scoping→effekt.util.messages.ErrorReporter
- Direction
- symbols.scopes uses util.messages, so a change to util.messages can break symbols.scopes, while a change to symbols.scopes can't break util.messages.
- Position
- Below the diagonal: symbols.scopes uses a module listed above it, which is the healthy direction.
14→16 symbols.scopes uses source part of a loop✕
- Connections
- 1 pair of types, where a type in symbols.scopes uses a type in source.
- The types involved
effekt.symbols.scopes.Scoping→effekt.source.IdRef
- Direction
- symbols.scopes uses source, so a change to source can break symbols.scopes, while a change to symbols.scopes can't break source.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 symbols.scopes uses core.Mono.preprocess part of a loop✕
- Connections
- 2 pairs of types, where a type in symbols.scopes uses a type in core.Mono.preprocess.
- The types involved
effekt.symbols.scopes.Scope→effekt.core.Mono.preprocess.Scopeeffekt.symbols.scopes.Scoping→effekt.core.Mono.preprocess.Scope
- Direction
- symbols.scopes uses core.Mono.preprocess, so a change to core.Mono.preprocess can break symbols.scopes, while a change to symbols.scopes can't break core.Mono.preprocess.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→22 symbols.scopes uses symbols part of a loop✕
- Connections
- 6 pairs of types, where a type in symbols.scopes uses a type in symbols.
- The types involved
effekt.symbols.scopes.Scope→effekt.symbols.Bindingseffekt.symbols.scopes.Scoping→effekt.symbols.Bindingseffekt.symbols.scopes.Scoping→effekt.symbols.Captureeffekt.symbols.scopes.Scoping→effekt.symbols.Symboleffekt.symbols.scopes.Scoping→effekt.symbols.TermSymboleffekt.symbols.scopes.Scoping→effekt.symbols.TypeSymbol
- Direction
- symbols.scopes uses symbols, so a change to symbols can break symbols.scopes, while a change to symbols.scopes can't break symbols.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→25 symbols.scopes uses core.LambdaSets part of a loop✕
- Connections
- 1 pair of types, where a type in symbols.scopes uses a type in core.LambdaSets.
- The types involved
effekt.symbols.scopes.Scoping→effekt.core.LambdaSets.Callable
- Direction
- symbols.scopes uses core.LambdaSets, so a change to core.LambdaSets can break symbols.scopes, while a change to symbols.scopes can't break core.LambdaSets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→26 symbols.scopes uses core part of a loop✕
- Connections
- 2 pairs of types, where a type in symbols.scopes uses a type in core.
- The types involved
effekt.symbols.scopes.Scoping→effekt.core.BlockParameffekt.symbols.scopes.Scoping→effekt.core.Operation
- Direction
- symbols.scopes uses core, so a change to core can break symbols.scopes, while a change to symbols.scopes can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→33 symbols.scopes uses core.vm.As part of a loop✕
- Connections
- 2 pairs of types, where a type in symbols.scopes uses a type in core.vm.As.
- The types involved
effekt.symbols.scopes.Scope→effekt.core.vm.As.Stringeffekt.symbols.scopes.Scoping→effekt.core.vm.As.String
- Direction
- symbols.scopes uses core.vm.As, so a change to core.vm.As can break symbols.scopes, while a change to symbols.scopes can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 generator.llvm uses core.Mono.preprocess.DeBruijn✕
- Connections
- 1 pair of types, where a type in generator.llvm uses a type in core.Mono.preprocess.DeBruijn.
- The types involved
effekt.generator.llvm.Transformer→effekt.core.Mono.preprocess.DeBruijn.Environment
- Direction
- generator.llvm uses core.Mono.preprocess.DeBruijn, so a change to core.Mono.preprocess.DeBruijn can break generator.llvm, while a change to generator.llvm can't break core.Mono.preprocess.DeBruijn.
- Position
- Below the diagonal: generator.llvm uses a module listed above it, which is the healthy direction.
15→10 generator.llvm uses util.messages✕
- Connections
- 1 pair of types, where a type in generator.llvm uses a type in util.messages.
- The types involved
effekt.generator.llvm.Transformer→effekt.util.messages.ErrorReporter
- Direction
- generator.llvm uses util.messages, so a change to util.messages can break generator.llvm, while a change to generator.llvm can't break util.messages.
- Position
- Below the diagonal: generator.llvm uses a module listed above it, which is the healthy direction.
15→13 generator.llvm uses machine✕
- Connections
- 5 pairs of types, where a type in generator.llvm uses a type in machine.
- The types involved
effekt.generator.llvm.Transformer→effekt.machine.CTypeeffekt.generator.llvm.Transformer→effekt.machine.Labeleffekt.generator.llvm.Transformer→effekt.machine.Programeffekt.generator.llvm.Transformer→effekt.machine.Statementeffekt.generator.llvm.Transformer→effekt.machine.Variable
- Direction
- generator.llvm uses machine, so a change to machine can break generator.llvm, while a change to generator.llvm can't break machine.
- Position
- Below the diagonal: generator.llvm uses a module listed above it, which is the healthy direction.
15→26 generator.llvm uses core part of a loop✕
- Connections
- 5 pairs of types, where a type in generator.llvm uses a type in core.
- The types involved
effekt.generator.llvm.Parameter→effekt.core.Typeeffekt.generator.llvm.PrettyPrinter→effekt.core.Typeeffekt.generator.llvm.Transformer→effekt.core.Declarationeffekt.generator.llvm.Transformer→effekt.core.ExternBodyeffekt.generator.llvm.Transformer→effekt.core.Type
- Direction
- generator.llvm uses core, so a change to core can break generator.llvm, while a change to generator.llvm can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 generator.llvm uses context part of a loop✕
- Connections
- 3 pairs of types, where a type in generator.llvm uses a type in context.
- The types involved
effekt.generator.llvm.LLVM→effekt.context.Contexteffekt.generator.llvm.PrettyPrinter→effekt.context.Contexteffekt.generator.llvm.Transformer→effekt.context.Context
- Direction
- generator.llvm uses context, so a change to context can break generator.llvm, while a change to generator.llvm can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→33 generator.llvm uses core.vm.As part of a loop✕
- Connections
- 6 pairs of types, where a type in generator.llvm uses a type in core.vm.As.
- The types involved
effekt.generator.llvm.BasicBlock→effekt.core.vm.As.Stringeffekt.generator.llvm.LLVM→effekt.core.vm.As.Stringeffekt.generator.llvm.Parameter→effekt.core.vm.As.Stringeffekt.generator.llvm.PrettyPrinter→effekt.core.vm.As.Stringeffekt.generator.llvm.Transformer→effekt.core.vm.As.Inteffekt.generator.llvm.Transformer→effekt.core.vm.As.String
- Direction
- generator.llvm uses core.vm.As, so a change to core.vm.As can break generator.llvm, while a change to generator.llvm can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→37 generator.llvm uses effekt part of a loop✕
- Connections
- 3 pairs of types, where a type in generator.llvm uses a type in effekt.
- The types involved
effekt.generator.llvm.LLVM→effekt.Compilereffekt.generator.llvm.LLVM→effekt.Stageeffekt.generator.llvm.Transformer→effekt.Template
- Direction
- generator.llvm uses effekt, so a change to effekt can break generator.llvm, while a change to generator.llvm can't break effekt.
- 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→7 source uses lsp✕
- Connections
- 3 pairs of types, where a type in source uses a type in lsp.
- The types involved
effekt.source.Span→effekt.lsp.Rangeeffekt.source.Spans→effekt.lsp.Positioneffekt.source.Spans→effekt.lsp.Range
- Direction
- source uses lsp, so a change to lsp can break source, while a change to source can't break lsp.
- Position
- Below the diagonal: source uses a module listed above it, which is the healthy direction.
16→9 source uses cps✕
- Connections
- 2 pairs of types, where a type in source uses a type in cps.
- The types involved
effekt.source.ModuleDecl→effekt.cps.Defeffekt.source.ResolveExternDefs→effekt.cps.Def
- Direction
- source uses cps, so a change to cps can break source, while a change to source can't break cps.
- Position
- Below the diagonal: source uses a module listed above it, which is the healthy direction.
16→14 source uses symbols.scopes✕
- Connections
- 1 pair of types, where a type in source uses a type in symbols.scopes.
- The types involved
effekt.source.GenerateImplicitArgs→effekt.symbols.scopes.Scoping
- Direction
- source uses symbols.scopes, so a change to symbols.scopes can break source, while a change to source can't break symbols.scopes.
- Position
- Below the diagonal: source uses a module listed above it, which is the healthy direction.
16→15 source uses generator.llvm✕
- Connections
- 4 pairs of types, where a type in source uses a type in generator.llvm.
- The types involved
effekt.source.Constructor→effekt.generator.llvm.Definitioneffekt.source.Def→effekt.generator.llvm.Definitioneffekt.source.Operation→effekt.generator.llvm.Definitioneffekt.source.Param→effekt.generator.llvm.Definition
- Direction
- source uses generator.llvm, so a change to generator.llvm can break source, while a change to source can't break generator.llvm.
- Position
- Below the diagonal: source uses a module listed above it, which is the healthy direction.
16→21 source uses core.Mono.preprocess part of a loop✕
- Connections
- 1 pair of types, where a type in source uses a type in core.Mono.preprocess.
- The types involved
effekt.source.GenerateImplicitArgs→effekt.core.Mono.preprocess.Scope
- Direction
- source uses core.Mono.preprocess, so a change to core.Mono.preprocess can break source, while a change to source can't break core.Mono.preprocess.
- 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→22 source uses symbols part of a loop✕
- Connections
- 4 pairs of types, where a type in source uses a type in symbols.
- The types involved
effekt.source.AnnotateCaptures→effekt.symbols.BlockSymboleffekt.source.AnnotateCaptures→effekt.symbols.Captureseffekt.source.GenerateImplicitArgs→effekt.symbols.Symboleffekt.source.Id→effekt.symbols.Symbol
- Direction
- source uses symbols, so a change to symbols can break source, while a change to source can't break symbols.
- 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→23 source uses core.Tree part of a loop✕
- Connections
- 2 pairs of types, where a type in source uses a type in core.Tree.
- The types involved
effekt.source.AnnotateCaptures→effekt.core.Tree.Queryeffekt.source.ExplicitCapabilities→effekt.core.Tree.Rewrite
- Direction
- source uses core.Tree, so a change to core.Tree can break source, while a change to source can't break core.Tree.
- 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→26 source uses core part of a loop✕
- Connections
- 60 pairs of types, where a type in source uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.source.AnnotateCaptures→effekt.core.ModuleDecleffekt.source.AnnotateCaptures→effekt.core.Treeeffekt.source.BlockTypeTree→effekt.core.BlockTypeeffekt.source.BlockTypeTree→effekt.core.Typeeffekt.source.BoxedType→effekt.core.BlockTypeeffekt.source.BoxedType→effekt.core.Typeeffekt.source.CallTarget→effekt.core.Treeeffekt.source.CaptureSet→effekt.core.Treeeffekt.source.Comment→effekt.core.Treeeffekt.source.Constructor→effekt.core.Ideffekt.source.Constructor→effekt.core.ValueParameffekt.source.Effectful→effekt.core.Typeeffekt.source.Effectful→effekt.core.ValueTypeeffekt.source.Effects→effekt.core.Treeeffekt.source.ExplicitCapabilities→effekt.core.BlockParameffekt.source.ExplicitCapabilities→effekt.core.ExternBodyeffekt.source.ExplicitCapabilities→effekt.core.Stmteffekt.source.ExternBody→effekt.core.Treeeffekt.source.FeatureFlag→effekt.core.Treeeffekt.source.FunctionType→effekt.core.Ideffekt.source.FunctionType→effekt.core.Typeeffekt.source.FunctionType→effekt.core.ValueTypeeffekt.source.GenerateImplicitArgs→effekt.core.BlockParameffekt.source.GenerateImplicitArgs→effekt.core.BlockTypeeffekt.source.GenerateImplicitArgs→effekt.core.Tree
- Direction
- source uses core, so a change to core can break source, while a change to source can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→29 source uses context part of a loop✕
- Connections
- 8 pairs of types, where a type in source uses a type in context.
- The types involved
effekt.source.AnnotateCaptures→effekt.context.Contexteffekt.source.ExplicitCapabilities→effekt.context.Contexteffekt.source.GenerateImplicitArgs→effekt.context.Contexteffekt.source.Id→effekt.context.Contexteffekt.source.IdDef→effekt.context.Contexteffekt.source.IdRef→effekt.context.Contexteffekt.source.ResolveExternDefs→effekt.context.Contexteffekt.source.Tree→effekt.context.Context
- Direction
- source uses context, so a change to context can break source, while a change to source can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→33 source uses core.vm.As part of a loop✕
- Connections
- 17 pairs of types, where a type in source uses a type in core.vm.As.
- The types involved
effekt.source.FeatureFlag→effekt.core.vm.As.Stringeffekt.source.GenerateImplicitArgs→effekt.core.vm.As.Inteffekt.source.GenerateImplicitArgs→effekt.core.vm.As.Stringeffekt.source.Handler→effekt.core.vm.As.Referenceeffekt.source.Id→effekt.core.vm.As.Stringeffekt.source.IdDef→effekt.core.vm.As.Stringeffekt.source.IdRef→effekt.core.vm.As.Stringeffekt.source.Implementation→effekt.core.vm.As.Referenceeffekt.source.Include→effekt.core.vm.As.Stringeffekt.source.ModuleDecl→effekt.core.vm.As.Stringeffekt.source.OpClause→effekt.core.vm.As.Referenceeffekt.source.ResolveExternDefs→effekt.core.vm.As.Stringeffekt.source.Span→effekt.core.vm.As.Inteffekt.source.Span→effekt.core.vm.As.Stringeffekt.source.Spans→effekt.core.vm.As.Stringeffekt.source.TypeRef→effekt.core.vm.As.Referenceeffekt.source.ValueArg→effekt.core.vm.As.String
- Direction
- source uses core.vm.As, so a change to core.vm.As can break source, while a change to source can't break core.vm.As.
- 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→37 source uses effekt part of a loop✕
- Connections
- 3 pairs of types, where a type in source uses a type in effekt.
- The types involved
effekt.source.AnnotateCaptures→effekt.Phaseeffekt.source.ExplicitCapabilities→effekt.Phaseeffekt.source.ResolveExternDefs→effekt.Phase
- Direction
- source uses effekt, so a change to effekt can break source, while a change to source can't break effekt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→7 lexer uses lsp✕
- Connections
- 2 pairs of types, where a type in lexer uses a type in lsp.
- The types involved
effekt.lexer.Lexer→effekt.lsp.Positioneffekt.lexer.Position→effekt.lsp.Position
- Direction
- lexer uses lsp, so a change to lsp can break lexer, while a change to lexer can't break lsp.
- Position
- Below the diagonal: lexer uses a module listed above it, which is the healthy direction.
17→16 lexer uses source✕
- Connections
- 1 pair of types, where a type in lexer uses a type in source.
- The types involved
effekt.lexer.Token→effekt.source.Span
- Direction
- lexer uses source, so a change to source can break lexer, while a change to lexer can't break source.
- Position
- Below the diagonal: lexer uses a module listed above it, which is the healthy direction.
17→33 lexer uses core.vm.As part of a loop✕
- Connections
- 6 pairs of types, where a type in lexer uses a type in core.vm.As.
- The types involved
effekt.lexer.DepthTracker→effekt.core.vm.As.Inteffekt.lexer.Lexer→effekt.core.vm.As.Inteffekt.lexer.Lexer→effekt.core.vm.As.Stringeffekt.lexer.LexerError→effekt.core.vm.As.Stringeffekt.lexer.Position→effekt.core.vm.As.Inteffekt.lexer.Token→effekt.core.vm.As.Int
- Direction
- lexer uses core.vm.As, so a change to core.vm.As can break lexer, while a change to lexer can't break core.vm.As.
- 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→3 typer.ExhaustivityChecker uses core.PatternMatchingCompiler✕
- Connections
- 3 pairs of types, where a type in typer.ExhaustivityChecker uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.typer.ExhaustivityChecker.Clause→effekt.core.PatternMatchingCompiler.Clauseeffekt.typer.ExhaustivityChecker.Clause→effekt.core.PatternMatchingCompiler.Conditioneffekt.typer.ExhaustivityChecker.Clause→effekt.core.PatternMatchingCompiler.Pattern
- Direction
- typer.ExhaustivityChecker uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break typer.ExhaustivityChecker, while a change to typer.ExhaustivityChecker can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: typer.ExhaustivityChecker uses a module listed above it, which is the healthy direction.
18→4 typer.ExhaustivityChecker uses core.Type✕
- Connections
- 2 pairs of types, where a type in typer.ExhaustivityChecker uses a type in core.Type.
- The types involved
effekt.typer.ExhaustivityChecker.Clause→effekt.core.Type.MatchClauseeffekt.typer.ExhaustivityChecker.Exhaustivity→effekt.core.Type.MatchClause
- Direction
- typer.ExhaustivityChecker uses core.Type, so a change to core.Type can break typer.ExhaustivityChecker, while a change to typer.ExhaustivityChecker can't break core.Type.
- Position
- Below the diagonal: typer.ExhaustivityChecker uses a module listed above it, which is the healthy direction.
18→10 typer.ExhaustivityChecker uses util.messages✕
- Connections
- 1 pair of types, where a type in typer.ExhaustivityChecker uses a type in util.messages.
- The types involved
effekt.typer.ExhaustivityChecker.Exhaustivity→effekt.util.messages.ErrorReporter
- Direction
- typer.ExhaustivityChecker uses util.messages, so a change to util.messages can break typer.ExhaustivityChecker, while a change to typer.ExhaustivityChecker can't break util.messages.
- Position
- Below the diagonal: typer.ExhaustivityChecker uses a module listed above it, which is the healthy direction.
18→16 typer.ExhaustivityChecker uses source✕
- Connections
- 1 pair of types, where a type in typer.ExhaustivityChecker uses a type in source.
- The types involved
effekt.typer.ExhaustivityChecker.Exhaustivity→effekt.source.Term
- Direction
- typer.ExhaustivityChecker uses source, so a change to source can break typer.ExhaustivityChecker, while a change to typer.ExhaustivityChecker can't break source.
- Position
- Below the diagonal: typer.ExhaustivityChecker uses a module listed above it, which is the healthy direction.
18→26 typer.ExhaustivityChecker uses core part of a loop✕
- Connections
- 2 pairs of types, where a type in typer.ExhaustivityChecker uses a type in core.
- The types involved
effekt.typer.ExhaustivityChecker.Exhaustivity→effekt.core.Constructoreffekt.typer.ExhaustivityChecker.Exhaustivity→effekt.core.ValueType
- Direction
- typer.ExhaustivityChecker uses core, so a change to core can break typer.ExhaustivityChecker, while a change to typer.ExhaustivityChecker can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→3 typer uses core.PatternMatchingCompiler✕
- Connections
- 3 pairs of types, where a type in typer uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.typer.ExhaustivityChecker→effekt.core.PatternMatchingCompiler.Clauseeffekt.typer.ExhaustivityChecker→effekt.core.PatternMatchingCompiler.Conditioneffekt.typer.ExhaustivityChecker→effekt.core.PatternMatchingCompiler.Pattern
- Direction
- typer uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break typer, while a change to typer can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→4 typer uses core.Type✕
- Connections
- 3 pairs of types, where a type in typer uses a type in core.Type.
- The types involved
effekt.typer.ExhaustivityChecker→effekt.core.Type.MatchClauseeffekt.typer.UnboxInference→effekt.core.Type.MatchClauseeffekt.typer.Wellformedness→effekt.core.Type.MatchClause
- Direction
- typer uses core.Type, so a change to core.Type can break typer, while a change to typer can't break core.Type.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→9 typer uses cps✕
- Connections
- 2 pairs of types, where a type in typer uses a type in cps.
- The types involved
effekt.typer.Typer→effekt.cps.Defeffekt.typer.UnboxInference→effekt.cps.Def
- Direction
- typer uses cps, so a change to cps can break typer, while a change to typer can't break cps.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→10 typer uses util.messages✕
- Connections
- 2 pairs of types, where a type in typer uses a type in util.messages.
- The types involved
effekt.typer.Unification→effekt.util.messages.ErrorReportereffekt.typer.Wellformedness→effekt.util.messages.ErrorReporter
- Direction
- typer uses util.messages, so a change to util.messages can break typer, while a change to typer can't break util.messages.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→11 typer uses generator.chez.Tree✕
- Connections
- 1 pair of types, where a type in typer uses a type in generator.chez.Tree.
- The types involved
effekt.typer.Wellformedness→effekt.generator.chez.Tree.Visit
- Direction
- typer uses generator.chez.Tree, so a change to generator.chez.Tree can break typer, while a change to typer can't break generator.chez.Tree.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→12 typer uses generator.js✕
- Connections
- 2 pairs of types, where a type in typer uses a type in generator.js.
- The types involved
effekt.typer.Typer→effekt.generator.js.Moduleeffekt.typer.Wellformedness→effekt.generator.js.Module
- Direction
- typer uses generator.js, so a change to generator.js can break typer, while a change to typer can't break generator.js.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→16 typer uses source✕
- Connections
- 34 pairs of types, where a type in typer uses a type in source. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.typer.ConcreteEffects→effekt.source.Effectseffekt.typer.Constraints→effekt.source.CaptureSeteffekt.typer.ExhaustivityChecker→effekt.source.MatchGuardeffekt.typer.ExhaustivityChecker→effekt.source.MatchPatterneffekt.typer.ExhaustivityChecker→effekt.source.Termeffekt.typer.Substitutions→effekt.source.Effectseffekt.typer.Substitutions→effekt.source.FunctionTypeeffekt.typer.TypeInstantiator→effekt.source.Effectseffekt.typer.TypeInstantiator→effekt.source.FunctionTypeeffekt.typer.TypeUnifier→effekt.source.Effectseffekt.typer.TypeUnifier→effekt.source.FunctionTypeeffekt.typer.Typer→effekt.source.FunctionTypeeffekt.typer.Typer→effekt.source.IdRefeffekt.typer.Typer→effekt.source.MatchGuardeffekt.typer.Typer→effekt.source.MatchPatterneffekt.typer.Typer→effekt.source.Parameffekt.typer.Typer→effekt.source.Termeffekt.typer.Typer→effekt.source.ValueArgeffekt.typer.TyperOps→effekt.source.Effectseffekt.typer.TyperOps→effekt.source.FunctionTypeeffekt.typer.TyperOps→effekt.source.IdRefeffekt.typer.TyperOps→effekt.source.Termeffekt.typer.TyperOps→effekt.source.ValueArgeffekt.typer.UnboxInference→effekt.source.CallTargeteffekt.typer.UnboxInference→effekt.source.Handler
- Direction
- typer uses source, so a change to source can break typer, while a change to typer can't break source.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→18 typer uses typer.ExhaustivityChecker✕
- Connections
- 2 pairs of types, where a type in typer uses a type in typer.ExhaustivityChecker.
- The types involved
effekt.typer.ExhaustivityChecker→effekt.typer.ExhaustivityChecker.Exhaustivityeffekt.typer.ExhaustivityChecker→effekt.typer.ExhaustivityChecker.Trace
- Direction
- typer uses typer.ExhaustivityChecker, so a change to typer.ExhaustivityChecker can break typer, while a change to typer can't break typer.ExhaustivityChecker.
- Position
- Below the diagonal: typer uses a module listed above it, which is the healthy direction.
19→21 typer uses core.Mono.preprocess part of a loop✕
- Connections
- 5 pairs of types, where a type in typer uses a type in core.Mono.preprocess.
- The types involved
effekt.typer.GlobalScope→effekt.core.Mono.preprocess.Scopeeffekt.typer.LocalScope→effekt.core.Mono.preprocess.Scopeeffekt.typer.Typer→effekt.core.Mono.preprocess.Scopeeffekt.typer.Unification→effekt.core.Mono.preprocess.Scopeeffekt.typer.UnificationState→effekt.core.Mono.preprocess.Scope
- Direction
- typer uses core.Mono.preprocess, so a change to core.Mono.preprocess can break typer, while a change to typer can't break core.Mono.preprocess.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 typer uses symbols part of a loop✕
- Connections
- 42 pairs of types, where a type in typer uses a type in symbols. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.typer.CaptureNodeData→effekt.symbols.Captureeffekt.typer.Constraints→effekt.symbols.CaptUnificationVareffekt.typer.Constraints→effekt.symbols.Captureeffekt.typer.Constraints→effekt.symbols.Captureseffekt.typer.Constraints→effekt.symbols.TypeVareffekt.typer.DummyUnifier→effekt.symbols.Captureseffekt.typer.Instantiation→effekt.symbols.Captureeffekt.typer.Instantiation→effekt.symbols.Captureseffekt.typer.Instantiation→effekt.symbols.TypeVareffekt.typer.LocalScope→effekt.symbols.CaptUnificationVareffekt.typer.SubstitutionException→effekt.symbols.CaptUnificationVareffekt.typer.SubstitutionException→effekt.symbols.Captureeffekt.typer.SubstitutionException→effekt.symbols.Captureseffekt.typer.Substitutions→effekt.symbols.CaptUnificationVareffekt.typer.Substitutions→effekt.symbols.CaptVareffekt.typer.Substitutions→effekt.symbols.Captureeffekt.typer.Substitutions→effekt.symbols.Captureseffekt.typer.Substitutions→effekt.symbols.TypeVareffekt.typer.TypeInstantiator→effekt.symbols.Captureeffekt.typer.TypeInstantiator→effekt.symbols.Captureseffekt.typer.TypeInstantiator→effekt.symbols.TypeVareffekt.typer.TypeMerger→effekt.symbols.Captureseffekt.typer.TypeUnifier→effekt.symbols.Captureeffekt.typer.TypeUnifier→effekt.symbols.Captureseffekt.typer.Typer→effekt.symbols.BlockSymbol
- Direction
- typer uses symbols, so a change to symbols can break typer, while a change to typer can't break symbols.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→25 typer uses core.LambdaSets part of a loop✕
- Connections
- 2 pairs of types, where a type in typer uses a type in core.LambdaSets.
- The types involved
effekt.typer.Constraints→effekt.core.LambdaSets.Constraintseffekt.typer.UnificationState→effekt.core.LambdaSets.Constraints
- Direction
- typer uses core.LambdaSets, so a change to core.LambdaSets can break typer, while a change to typer can't break core.LambdaSets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→26 typer uses core part of a loop✕
- Connections
- 40 pairs of types, where a type in typer uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.typer.BindAll→effekt.core.BlockParameffekt.typer.BindSome→effekt.core.BlockParameffekt.typer.CapabilityScope→effekt.core.BlockParameffekt.typer.Constraints→effekt.core.ValueTypeeffekt.typer.DummyUnifier→effekt.core.Typeeffekt.typer.DummyUnifier→effekt.core.ValueTypeeffekt.typer.ExhaustivityChecker→effekt.core.ValueTypeeffekt.typer.GlobalCapabilityScope→effekt.core.BlockParameffekt.typer.Instantiation→effekt.core.ValueTypeeffekt.typer.Substitutions→effekt.core.BlockTypeeffekt.typer.Substitutions→effekt.core.ValueTypeeffekt.typer.TypeInstantiator→effekt.core.BlockTypeeffekt.typer.TypeInstantiator→effekt.core.ValueTypeeffekt.typer.TypeMerger→effekt.core.ValueTypeeffekt.typer.TypeUnifier→effekt.core.BlockTypeeffekt.typer.TypeUnifier→effekt.core.Typeeffekt.typer.TypeUnifier→effekt.core.ValueTypeeffekt.typer.Typer→effekt.core.BlockParameffekt.typer.Typer→effekt.core.BlockTypeeffekt.typer.Typer→effekt.core.Implementationeffekt.typer.Typer→effekt.core.Stmteffekt.typer.Typer→effekt.core.Treeeffekt.typer.Typer→effekt.core.ValueParameffekt.typer.Typer→effekt.core.ValueTypeeffekt.typer.TyperOps→effekt.core.BlockParam
- Direction
- typer uses core, so a change to core can break typer, while a change to typer can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→29 typer uses context part of a loop✕
- Connections
- 13 pairs of types, where a type in typer uses a type in context.
- The types involved
effekt.typer.BindAll→effekt.context.Contexteffekt.typer.BindSome→effekt.context.Contexteffekt.typer.CapabilityScope→effekt.context.Contexteffekt.typer.DummyUnifier→effekt.context.Contexteffekt.typer.ExhaustivityChecker→effekt.context.Contexteffekt.typer.GlobalCapabilityScope→effekt.context.Contexteffekt.typer.Typer→effekt.context.Contexteffekt.typer.TyperOps→effekt.context.Annotationseffekt.typer.TyperOps→effekt.context.ContextOpseffekt.typer.TyperState→effekt.context.Annotationseffekt.typer.UnboxInference→effekt.context.Contexteffekt.typer.Unification→effekt.context.Contexteffekt.typer.Wellformedness→effekt.context.Context
- Direction
- typer uses context, so a change to context can break typer, while a change to typer can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→33 typer uses core.vm.As part of a loop✕
- Connections
- 9 pairs of types, where a type in typer uses a type in core.vm.As.
- The types involved
effekt.typer.BindAll→effekt.core.vm.As.Stringeffekt.typer.BindSome→effekt.core.vm.As.Stringeffekt.typer.DummyUnifier→effekt.core.vm.As.Stringeffekt.typer.TypeUnifier→effekt.core.vm.As.Stringeffekt.typer.Typer→effekt.core.vm.As.Inteffekt.typer.Typer→effekt.core.vm.As.Stringeffekt.typer.Unification→effekt.core.vm.As.Stringeffekt.typer.Wellformedness→effekt.core.vm.As.Inteffekt.typer.Wellformedness→effekt.core.vm.As.String
- Direction
- typer uses core.vm.As, so a change to core.vm.As can break typer, while a change to typer can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→37 typer uses effekt part of a loop✕
- Connections
- 3 pairs of types, where a type in typer uses a type in effekt.
- The types involved
effekt.typer.Typer→effekt.Phaseeffekt.typer.UnboxInference→effekt.Phaseeffekt.typer.Wellformedness→effekt.Phase
- Direction
- typer uses effekt, so a change to effekt can break typer, while a change to typer can't break effekt.
- 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 core.Mono uses core.Mono.preprocess.DeBruijn✕
- Connections
- 1 pair of types, where a type in core.Mono uses a type in core.Mono.preprocess.DeBruijn.
- The types involved
effekt.core.Mono.collect→effekt.core.Mono.preprocess.DeBruijn.Environment
- Direction
- core.Mono uses core.Mono.preprocess.DeBruijn, so a change to core.Mono.preprocess.DeBruijn can break core.Mono, while a change to core.Mono can't break core.Mono.preprocess.DeBruijn.
- Position
- Below the diagonal: core.Mono uses a module listed above it, which is the healthy direction.
20→2 core.Mono uses core.Mono.specialize✕
- Connections
- 1 pair of types, where a type in core.Mono uses a type in core.Mono.specialize.
- The types involved
effekt.core.Mono.specialize→effekt.core.Mono.specialize.Binders
- Direction
- core.Mono uses core.Mono.specialize, so a change to core.Mono.specialize can break core.Mono, while a change to core.Mono can't break core.Mono.specialize.
- Position
- Below the diagonal: core.Mono uses a module listed above it, which is the healthy direction.
20→6 core.Mono uses core.substitutions✕
- Connections
- 1 pair of types, where a type in core.Mono uses a type in core.substitutions.
- The types involved
effekt.core.Mono.solve→effekt.core.substitutions.Substitution
- Direction
- core.Mono uses core.substitutions, so a change to core.substitutions can break core.Mono, while a change to core.Mono can't break core.substitutions.
- Position
- Below the diagonal: core.Mono uses a module listed above it, which is the healthy direction.
20→19 core.Mono uses typer✕
- Connections
- 1 pair of types, where a type in core.Mono uses a type in typer.
- The types involved
effekt.core.Mono.solve→effekt.typer.Substitutions
- Direction
- core.Mono uses typer, so a change to typer can break core.Mono, while a change to core.Mono can't break typer.
- Position
- Below the diagonal: core.Mono uses a module listed above it, which is the healthy direction.
20→25 core.Mono uses core.LambdaSets part of a loop✕
- Connections
- 3 pairs of types, where a type in core.Mono uses a type in core.LambdaSets.
- The types involved
effekt.core.Mono.solve→effekt.core.LambdaSets.Projectioneffekt.core.Mono.solve→effekt.core.LambdaSets.Solutioneffekt.core.Mono.specialize→effekt.core.LambdaSets.Solution
- Direction
- core.Mono uses core.LambdaSets, so a change to core.LambdaSets can break core.Mono, while a change to core.Mono can't break core.LambdaSets.
- 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→26 core.Mono uses core part of a loop✕
- Connections
- 32 pairs of types, where a type in core.Mono uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.core.Mono.collect→effekt.core.Blockeffekt.core.Mono.collect→effekt.core.BlockParameffekt.core.Mono.collect→effekt.core.BlockTypeeffekt.core.Mono.collect→effekt.core.Declarationeffekt.core.Mono.collect→effekt.core.Expreffekt.core.Mono.collect→effekt.core.Externeffekt.core.Mono.collect→effekt.core.ExternBodyeffekt.core.Mono.collect→effekt.core.Implementationeffekt.core.Mono.collect→effekt.core.ModuleDecleffekt.core.Mono.collect→effekt.core.Operationeffekt.core.Mono.collect→effekt.core.Stmteffekt.core.Mono.collect→effekt.core.Topleveleffekt.core.Mono.collect→effekt.core.ValueParameffekt.core.Mono.collect→effekt.core.ValueTypeeffekt.core.Mono.preprocess→effekt.core.ModuleDecleffekt.core.Mono.specialize→effekt.core.Blockeffekt.core.Mono.specialize→effekt.core.BlockParameffekt.core.Mono.specialize→effekt.core.BlockTypeeffekt.core.Mono.specialize→effekt.core.Constructoreffekt.core.Mono.specialize→effekt.core.Declarationeffekt.core.Mono.specialize→effekt.core.DeclarationContexteffekt.core.Mono.specialize→effekt.core.Expreffekt.core.Mono.specialize→effekt.core.Fieldeffekt.core.Mono.specialize→effekt.core.Ideffekt.core.Mono.specialize→effekt.core.Implementation
- Direction
- core.Mono uses core, so a change to core can break core.Mono, while a change to core.Mono can't break core.
- 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→29 core.Mono uses context part of a loop✕
- Connections
- 4 pairs of types, where a type in core.Mono uses a type in context.
- The types involved
effekt.core.Mono.collect→effekt.context.Contexteffekt.core.Mono.preprocess→effekt.context.Contexteffekt.core.Mono.solve→effekt.context.Contexteffekt.core.Mono.specialize→effekt.context.Context
- Direction
- core.Mono uses context, so a change to context can break core.Mono, while a change to core.Mono can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→31 core.Mono uses context.Context part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono uses a type in context.Context.
- The types involved
effekt.core.Mono.specialize→effekt.context.Context.State
- Direction
- core.Mono uses context.Context, so a change to context.Context can break core.Mono, while a change to core.Mono can't break context.Context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→33 core.Mono uses core.vm.As part of a loop✕
- Connections
- 4 pairs of types, where a type in core.Mono uses a type in core.vm.As.
- The types involved
effekt.core.Mono.Projection→effekt.core.vm.As.Inteffekt.core.Mono.collect→effekt.core.vm.As.Inteffekt.core.Mono.solve→effekt.core.vm.As.Inteffekt.core.Mono.specialize→effekt.core.vm.As.String
- Direction
- core.Mono uses core.vm.As, so a change to core.vm.As can break core.Mono, while a change to core.Mono can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 core.Mono.preprocess uses core.Mono.preprocess.DeBruijn✕
- Connections
- 1 pair of types, where a type in core.Mono.preprocess uses a type in core.Mono.preprocess.DeBruijn.
- The types involved
effekt.core.Mono.preprocess.DeBruijn→effekt.core.Mono.preprocess.DeBruijn.Environment
- Direction
- core.Mono.preprocess uses core.Mono.preprocess.DeBruijn, so a change to core.Mono.preprocess.DeBruijn can break core.Mono.preprocess, while a change to core.Mono.preprocess can't break core.Mono.preprocess.DeBruijn.
- Position
- Below the diagonal: core.Mono.preprocess uses a module listed above it, which is the healthy direction.
21→20 core.Mono.preprocess uses core.Mono✕
- Connections
- 2 pairs of types, where a type in core.Mono.preprocess uses a type in core.Mono.
- The types involved
effekt.core.Mono.preprocess.DeBruijn→effekt.core.Mono.MonoBlockTypeeffekt.core.Mono.preprocess.State→effekt.core.Mono.MonoBlockType
- Direction
- core.Mono.preprocess uses core.Mono, so a change to core.Mono can break core.Mono.preprocess, while a change to core.Mono.preprocess can't break core.Mono.
- Position
- Below the diagonal: core.Mono.preprocess uses a module listed above it, which is the healthy direction.
21→23 core.Mono.preprocess uses core.Tree part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono.preprocess uses a type in core.Tree.
- The types involved
effekt.core.Mono.preprocess.Elaborator→effekt.core.Tree.RewriteWithContext
- Direction
- core.Mono.preprocess uses core.Tree, so a change to core.Tree can break core.Mono.preprocess, while a change to core.Mono.preprocess can't break core.Tree.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→26 core.Mono.preprocess uses core part of a loop✕
- Connections
- 14 pairs of types, where a type in core.Mono.preprocess uses a type in core.
- The types involved
effekt.core.Mono.preprocess.DeBruijn→effekt.core.BlockTypeeffekt.core.Mono.preprocess.DeBruijn→effekt.core.Ideffekt.core.Mono.preprocess.DeBruijn→effekt.core.ValueTypeeffekt.core.Mono.preprocess.Elaborator→effekt.core.Blockeffekt.core.Mono.preprocess.Elaborator→effekt.core.BlockParameffekt.core.Mono.preprocess.Elaborator→effekt.core.BlockTypeeffekt.core.Mono.preprocess.Elaborator→effekt.core.Declarationeffekt.core.Mono.preprocess.Elaborator→effekt.core.Operationeffekt.core.Mono.preprocess.Elaborator→effekt.core.Stmteffekt.core.Mono.preprocess.Elaborator→effekt.core.ValueTypeeffekt.core.Mono.preprocess.Encoded→effekt.core.Ideffekt.core.Mono.preprocess.Encoded→effekt.core.ValueTypeeffekt.core.Mono.preprocess.Encoding→effekt.core.Ideffekt.core.Mono.preprocess.Scope→effekt.core.Id
- Direction
- core.Mono.preprocess uses core, so a change to core can break core.Mono.preprocess, while a change to core.Mono.preprocess can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→29 core.Mono.preprocess uses context part of a loop✕
- Connections
- 1 pair of types, where a type in core.Mono.preprocess uses a type in context.
- The types involved
effekt.core.Mono.preprocess.DeBruijn→effekt.context.Context
- Direction
- core.Mono.preprocess uses context, so a change to context can break core.Mono.preprocess, while a change to core.Mono.preprocess can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→12 symbols uses generator.js✕
- Connections
- 2 pairs of types, where a type in symbols uses a type in generator.js.
- The types involved
effekt.symbols.Module→effekt.generator.js.Moduleeffekt.symbols.ResumeParam→effekt.generator.js.Module
- Direction
- symbols uses generator.js, so a change to generator.js can break symbols, while a change to symbols can't break generator.js.
- Position
- Below the diagonal: symbols uses a module listed above it, which is the healthy direction.
22→14 symbols uses symbols.scopes✕
- Connections
- 1 pair of types, where a type in symbols uses a type in symbols.scopes.
- The types involved
effekt.symbols.scopes→effekt.symbols.scopes.Scoping
- Direction
- symbols uses symbols.scopes, so a change to symbols.scopes can break symbols, while a change to symbols can't break symbols.scopes.
- Position
- Below the diagonal: symbols uses a module listed above it, which is the healthy direction.
22→16 symbols uses source✕
- Connections
- 25 pairs of types, where a type in symbols uses a type in source.
- The types involved
effekt.symbols.Callable→effekt.source.CaptureSeteffekt.symbols.Callable→effekt.source.Effectseffekt.symbols.Callable→effekt.source.FunctionTypeeffekt.symbols.CanonicalOrdering→effekt.source.FunctionTypeeffekt.symbols.CaptureSet→effekt.source.CaptureSeteffekt.symbols.Constructor→effekt.source.Effectseffekt.symbols.DeclPrinter→effekt.source.Effectseffekt.symbols.EffectAlias→effekt.source.Effectseffekt.symbols.Effects→effekt.source.Effectseffekt.symbols.ExternFunction→effekt.source.CaptureSeteffekt.symbols.ExternFunction→effekt.source.Effectseffekt.symbols.ExternFunction→effekt.source.Termeffekt.symbols.Operation→effekt.source.Effectseffekt.symbols.ResumeParam→effekt.source.Parameffekt.symbols.SignaturePrinter→effekt.source.Effectseffekt.symbols.TrackedParam→effekt.source.Parameffekt.symbols.TypePrinter→effekt.source.Effectseffekt.symbols.TypePrinter→effekt.source.IdDefeffekt.symbols.TypePrinter→effekt.source.IdRefeffekt.symbols.UserFunction→effekt.source.CaptureSeteffekt.symbols.UserFunction→effekt.source.Effectseffekt.symbols.ValueParam→effekt.source.Parameffekt.symbols.builtins→effekt.source.CaptureSeteffekt.symbols.kinds→effekt.source.Effectseffekt.symbols.kinds→effekt.source.FunctionType
- Direction
- symbols uses source, so a change to source can break symbols, while a change to symbols can't break source.
- Position
- Below the diagonal: symbols uses a module listed above it, which is the healthy direction.
22→21 symbols uses core.Mono.preprocess✕
- Connections
- 1 pair of types, where a type in symbols uses a type in core.Mono.preprocess.
- The types involved
effekt.symbols.CallTarget→effekt.core.Mono.preprocess.Scope
- Direction
- symbols uses core.Mono.preprocess, so a change to core.Mono.preprocess can break symbols, while a change to symbols can't break core.Mono.preprocess.
- Position
- Below the diagonal: symbols uses a module listed above it, which is the healthy direction.
22→25 symbols uses core.LambdaSets part of a loop✕
- Connections
- 8 pairs of types, where a type in symbols uses a type in core.LambdaSets.
- The types involved
effekt.symbols.Constructor→effekt.core.LambdaSets.Callableeffekt.symbols.DeclPrinter→effekt.core.LambdaSets.Callableeffekt.symbols.ExternFunction→effekt.core.LambdaSets.Callableeffekt.symbols.Field→effekt.core.LambdaSets.Callableeffekt.symbols.Lambda→effekt.core.LambdaSets.Callableeffekt.symbols.Operation→effekt.core.LambdaSets.Callableeffekt.symbols.SignaturePrinter→effekt.core.LambdaSets.Callableeffekt.symbols.UserFunction→effekt.core.LambdaSets.Callable
- Direction
- symbols uses core.LambdaSets, so a change to core.LambdaSets can break symbols, while a change to symbols can't break core.LambdaSets.
- 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→26 symbols uses core part of a loop✕
- Connections
- 47 pairs of types, where a type in symbols uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.symbols.Binder→effekt.core.Typeeffekt.symbols.BlockType→effekt.core.Typeeffekt.symbols.Callable→effekt.core.BlockParameffekt.symbols.Callable→effekt.core.ValueParameffekt.symbols.Callable→effekt.core.ValueTypeeffekt.symbols.Constructor→effekt.core.BlockParameffekt.symbols.Constructor→effekt.core.Fieldeffekt.symbols.Constructor→effekt.core.Treeeffekt.symbols.Constructor→effekt.core.ValueParameffekt.symbols.Constructor→effekt.core.ValueTypeeffekt.symbols.DeclPrinter→effekt.core.ValueTypeeffekt.symbols.EffectAlias→effekt.core.Treeeffekt.symbols.ExternFunction→effekt.core.BlockParameffekt.symbols.ExternFunction→effekt.core.ExternBodyeffekt.symbols.ExternFunction→effekt.core.Stmteffekt.symbols.ExternFunction→effekt.core.Treeeffekt.symbols.ExternFunction→effekt.core.ValueParameffekt.symbols.ExternFunction→effekt.core.ValueTypeeffekt.symbols.Field→effekt.core.Constructoreffekt.symbols.Field→effekt.core.Treeeffekt.symbols.Field→effekt.core.ValueParameffekt.symbols.Hole→effekt.core.ValueTypeeffekt.symbols.Lambda→effekt.core.BlockParameffekt.symbols.Lambda→effekt.core.Treeeffekt.symbols.Lambda→effekt.core.ValueParam
- Direction
- symbols uses core, so a change to core can break symbols, while a change to symbols can't break core.
- 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→29 symbols uses context part of a loop✕
- Connections
- 3 pairs of types, where a type in symbols uses a type in context.
- The types involved
effekt.symbols.DeclPrinter→effekt.context.Contexteffekt.symbols.SignaturePrinter→effekt.context.Contexteffekt.symbols.kinds→effekt.context.Context
- Direction
- symbols uses context, so a change to context can break symbols, while a change to symbols can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→33 symbols uses core.vm.As part of a loop✕
- Connections
- 17 pairs of types, where a type in symbols uses a type in core.vm.As.
- The types involved
effekt.symbols.Bindings→effekt.core.vm.As.Stringeffekt.symbols.CanonicalOrdering→effekt.core.vm.As.Inteffekt.symbols.DeclPrinter→effekt.core.vm.As.Stringeffekt.symbols.Effects→effekt.core.vm.As.Inteffekt.symbols.ErrorMessageInterpolator→effekt.core.vm.As.Stringeffekt.symbols.LocalName→effekt.core.vm.As.Stringeffekt.symbols.Name→effekt.core.vm.As.Stringeffekt.symbols.NoName→effekt.core.vm.As.Stringeffekt.symbols.QualifiedName→effekt.core.vm.As.Stringeffekt.symbols.SignaturePrinter→effekt.core.vm.As.Stringeffekt.symbols.Symbol→effekt.core.vm.As.Inteffekt.symbols.Symbol→effekt.core.vm.As.Stringeffekt.symbols.TmpBlock→effekt.core.vm.As.Stringeffekt.symbols.TmpValue→effekt.core.vm.As.Stringeffekt.symbols.TypePrinter→effekt.core.vm.As.Stringeffekt.symbols.builtins→effekt.core.vm.As.Stringeffekt.symbols.scopes→effekt.core.vm.As.String
- Direction
- symbols uses core.vm.As, so a change to core.vm.As can break symbols, while a change to symbols can't break core.vm.As.
- 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→22 core.Tree uses symbols✕
- Connections
- 3 pairs of types, where a type in core.Tree uses a type in symbols.
- The types involved
effekt.core.Tree.Rewrite→effekt.symbols.Captureseffekt.core.Tree.RewriteWithContext→effekt.symbols.Captureseffekt.core.Tree.TrampolinedRewrite→effekt.symbols.Captures
- Direction
- core.Tree uses symbols, so a change to symbols can break core.Tree, while a change to core.Tree can't break symbols.
- Position
- Below the diagonal: core.Tree uses a module listed above it, which is the healthy direction.
23→26 core.Tree uses core part of a loop✕
- Connections
- 62 pairs of types, where a type in core.Tree uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.core.Tree.Query→effekt.core.Blockeffekt.core.Tree.Query→effekt.core.Expreffekt.core.Tree.Query→effekt.core.ExternBodyeffekt.core.Tree.Query→effekt.core.Implementationeffekt.core.Tree.Query→effekt.core.ModuleDecleffekt.core.Tree.Query→effekt.core.Operationeffekt.core.Tree.Query→effekt.core.Stmteffekt.core.Tree.Query→effekt.core.Topleveleffekt.core.Tree.Rewrite→effekt.core.Blockeffekt.core.Tree.Rewrite→effekt.core.BlockParameffekt.core.Tree.Rewrite→effekt.core.BlockTypeeffekt.core.Tree.Rewrite→effekt.core.Constructoreffekt.core.Tree.Rewrite→effekt.core.Declarationeffekt.core.Tree.Rewrite→effekt.core.Expreffekt.core.Tree.Rewrite→effekt.core.Externeffekt.core.Tree.Rewrite→effekt.core.ExternBodyeffekt.core.Tree.Rewrite→effekt.core.Fieldeffekt.core.Tree.Rewrite→effekt.core.Ideffekt.core.Tree.Rewrite→effekt.core.Implementationeffekt.core.Tree.Rewrite→effekt.core.ModuleDecleffekt.core.Tree.Rewrite→effekt.core.Operationeffekt.core.Tree.Rewrite→effekt.core.Propertyeffekt.core.Tree.Rewrite→effekt.core.Stmteffekt.core.Tree.Rewrite→effekt.core.Topleveleffekt.core.Tree.Rewrite→effekt.core.ValueParam
- Direction
- core.Tree uses core, so a change to core can break core.Tree, while a change to core.Tree can't break core.
- 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→30 core.Tree uses util part of a loop✕
- Connections
- 2 pairs of types, where a type in core.Tree uses a type in util.
- The types involved
effekt.core.Tree.Query→effekt.util.Structuraleffekt.core.Tree.TrampolinedRewrite→effekt.util.Trampoline
- Direction
- core.Tree uses util, so a change to util can break core.Tree, while a change to core.Tree can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→23 core.LambdaSets.Specializer uses core.Tree✕
- Connections
- 1 pair of types, where a type in core.LambdaSets.Specializer uses a type in core.Tree.
- The types involved
effekt.core.LambdaSets.Specializer.bodyRewriter→effekt.core.Tree.RewriteWithContext
- Direction
- core.LambdaSets.Specializer uses core.Tree, so a change to core.Tree can break core.LambdaSets.Specializer, while a change to core.LambdaSets.Specializer can't break core.Tree.
- Position
- Below the diagonal: core.LambdaSets.Specializer uses a module listed above it, which is the healthy direction.
24→25 core.LambdaSets.Specializer uses core.LambdaSets part of a loop✕
- Connections
- 4 pairs of types, where a type in core.LambdaSets.Specializer uses a type in core.LambdaSets.
- The types involved
effekt.core.LambdaSets.Specializer.CaseLayout→effekt.core.LambdaSets.Selectioneffekt.core.LambdaSets.Specializer.Representation→effekt.core.LambdaSets.LambdaSetIdeffekt.core.LambdaSets.Specializer.SelectedBlock→effekt.core.LambdaSets.LambdaSetIdeffekt.core.LambdaSets.Specializer.bodyRewriter→effekt.core.LambdaSets.Specialization
- Direction
- core.LambdaSets.Specializer uses core.LambdaSets, so a change to core.LambdaSets can break core.LambdaSets.Specializer, while a change to core.LambdaSets.Specializer can't break core.LambdaSets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→26 core.LambdaSets.Specializer uses core part of a loop✕
- Connections
- 15 pairs of types, where a type in core.LambdaSets.Specializer uses a type in core.
- The types involved
effekt.core.LambdaSets.Specializer.CaseLayout→effekt.core.Expreffekt.core.LambdaSets.Specializer.CaseLayout→effekt.core.Fieldeffekt.core.LambdaSets.Specializer.CaseLayout→effekt.core.Ideffekt.core.LambdaSets.Specializer.CaseLayout→effekt.core.ValueParameffekt.core.LambdaSets.Specializer.DispatcherLayout→effekt.core.BlockParameffekt.core.LambdaSets.Specializer.DispatcherLayout→effekt.core.ValueParameffekt.core.LambdaSets.Specializer.OperationDispatcher→effekt.core.Ideffekt.core.LambdaSets.Specializer.Representation→effekt.core.BlockTypeeffekt.core.LambdaSets.Specializer.Representation→effekt.core.Ideffekt.core.LambdaSets.Specializer.SelectedBlock→effekt.core.BlockTypeeffekt.core.LambdaSets.Specializer.SelectedBlock→effekt.core.Ideffekt.core.LambdaSets.Specializer.SelectedBlock→effekt.core.ValueParameffekt.core.LambdaSets.Specializer.bodyRewriter→effekt.core.Blockeffekt.core.LambdaSets.Specializer.bodyRewriter→effekt.core.Expreffekt.core.LambdaSets.Specializer.bodyRewriter→effekt.core.Stmt
- Direction
- core.LambdaSets.Specializer uses core, so a change to core can break core.LambdaSets.Specializer, while a change to core.LambdaSets.Specializer can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→30 core.LambdaSets.Specializer uses util part of a loop✕
- Connections
- 1 pair of types, where a type in core.LambdaSets.Specializer uses a type in util.
- The types involved
effekt.core.LambdaSets.Specializer.CaseLayout→effekt.util.DB
- Direction
- core.LambdaSets.Specializer uses util, so a change to util can break core.LambdaSets.Specializer, while a change to core.LambdaSets.Specializer can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→9 core.LambdaSets uses cps✕
- Connections
- 1 pair of types, where a type in core.LambdaSets uses a type in cps.
- The types involved
effekt.core.LambdaSets.Specializer→effekt.cps.Def
- Direction
- core.LambdaSets uses cps, so a change to cps can break core.LambdaSets, while a change to core.LambdaSets can't break cps.
- Position
- Below the diagonal: core.LambdaSets uses a module listed above it, which is the healthy direction.
25→22 core.LambdaSets uses symbols✕
- Connections
- 1 pair of types, where a type in core.LambdaSets uses a type in symbols.
- The types involved
effekt.core.LambdaSets.Specializer→effekt.symbols.Captures
- Direction
- core.LambdaSets uses symbols, so a change to symbols can break core.LambdaSets, while a change to core.LambdaSets can't break symbols.
- Position
- Below the diagonal: core.LambdaSets uses a module listed above it, which is the healthy direction.
25→24 core.LambdaSets uses core.LambdaSets.Specializer✕
- Connections
- 5 pairs of types, where a type in core.LambdaSets uses a type in core.LambdaSets.Specializer.
- The types involved
effekt.core.LambdaSets.Specializer→effekt.core.LambdaSets.Specializer.CaseLayouteffekt.core.LambdaSets.Specializer→effekt.core.LambdaSets.Specializer.DispatcherLayouteffekt.core.LambdaSets.Specializer→effekt.core.LambdaSets.Specializer.OperationDispatchereffekt.core.LambdaSets.Specializer→effekt.core.LambdaSets.Specializer.Representationeffekt.core.LambdaSets.Specializer→effekt.core.LambdaSets.Specializer.SelectedBlock
- Direction
- core.LambdaSets uses core.LambdaSets.Specializer, so a change to core.LambdaSets.Specializer can break core.LambdaSets, while a change to core.LambdaSets can't break core.LambdaSets.Specializer.
- Position
- Below the diagonal: core.LambdaSets uses a module listed above it, which is the healthy direction.
25→26 core.LambdaSets uses core part of a loop✕
- Connections
- 30 pairs of types, where a type in core.LambdaSets uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.core.LambdaSets.BoxFlow→effekt.core.Ideffekt.core.LambdaSets.CallableInfo→effekt.core.Ideffekt.core.LambdaSets.Collector→effekt.core.Blockeffekt.core.LambdaSets.Collector→effekt.core.Expreffekt.core.LambdaSets.Collector→effekt.core.Freeeffekt.core.LambdaSets.Collector→effekt.core.Ideffekt.core.LambdaSets.Collector→effekt.core.Implementationeffekt.core.LambdaSets.Collector→effekt.core.Stmteffekt.core.LambdaSets.Collector→effekt.core.Topleveleffekt.core.LambdaSets.Collector→effekt.core.ValueParameffekt.core.LambdaSets.Constraints→effekt.core.Blockeffekt.core.LambdaSets.Constraints→effekt.core.Ideffekt.core.LambdaSets.Constraints→effekt.core.Operationeffekt.core.LambdaSets.FunctionDefinition→effekt.core.ValueParameffekt.core.LambdaSets.GraphBuilder→effekt.core.Ideffekt.core.LambdaSets.ImplementationDefinition→effekt.core.Ideffekt.core.LambdaSets.ImplementationDefinition→effekt.core.Implementationeffekt.core.LambdaSets.ImplementationDefinition→effekt.core.ValueParameffekt.core.LambdaSets.LambdaGraph→effekt.core.Ideffekt.core.LambdaSets.Specialization→effekt.core.Ideffekt.core.LambdaSets.Specializer→effekt.core.Blockeffekt.core.LambdaSets.Specializer→effekt.core.BlockTypeeffekt.core.LambdaSets.Specializer→effekt.core.Expreffekt.core.LambdaSets.Specializer→effekt.core.Ideffekt.core.LambdaSets.Specializer→effekt.core.ModuleDecl
- Direction
- core.LambdaSets uses core, so a change to core can break core.LambdaSets, while a change to core.LambdaSets can't break core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→33 core.LambdaSets uses core.vm.As part of a loop✕
- Connections
- 6 pairs of types, where a type in core.LambdaSets uses a type in core.vm.As.
- The types involved
effekt.core.LambdaSets.CallableInfo→effekt.core.vm.As.Inteffekt.core.LambdaSets.Collector→effekt.core.vm.As.Stringeffekt.core.LambdaSets.LambdaSetId→effekt.core.vm.As.Inteffekt.core.LambdaSets.Projection→effekt.core.vm.As.Inteffekt.core.LambdaSets.Specializer→effekt.core.vm.As.Inteffekt.core.LambdaSets.Specializer→effekt.core.vm.As.String
- Direction
- core.LambdaSets uses core.vm.As, so a change to core.vm.As can break core.LambdaSets, while a change to core.LambdaSets can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→3 core uses core.PatternMatchingCompiler✕
- Connections
- 4 pairs of types, where a type in core uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.core.PatternMatchingCompiler→effekt.core.PatternMatchingCompiler.Clauseeffekt.core.PatternMatchingCompiler→effekt.core.PatternMatchingCompiler.Conditioneffekt.core.PatternMatchingCompiler→effekt.core.PatternMatchingCompiler.Patterneffekt.core.Transformer→effekt.core.PatternMatchingCompiler.Clause
- Direction
- core uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break core, while a change to core can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→4 core uses core.Type✕
- Connections
- 1 pair of types, where a type in core uses a type in core.Type.
- The types involved
effekt.core.Transformer→effekt.core.Type.MatchClause
- Direction
- core uses core.Type, so a change to core.Type can break core, while a change to core can't break core.Type.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→6 core uses core.substitutions✕
- Connections
- 1 pair of types, where a type in core uses a type in core.substitutions.
- The types involved
effekt.core.substitutions→effekt.core.substitutions.Substitution
- Direction
- core uses core.substitutions, so a change to core.substitutions can break core, while a change to core can't break core.substitutions.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→9 core uses cps✕
- Connections
- 3 pairs of types, where a type in core uses a type in cps.
- The types involved
effekt.core.DeclarationContext→effekt.cps.Defeffekt.core.Show→effekt.cps.Defeffekt.core.Transformer→effekt.cps.Def
- Direction
- core uses cps, so a change to cps can break core, while a change to core can't break cps.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→10 core uses util.messages✕
- Connections
- 4 pairs of types, where a type in core uses a type in util.messages.
- The types involved
effekt.core.CoreParsers→effekt.util.messages.ErrorReportereffekt.core.DeclarationContext→effekt.util.messages.ErrorReportereffekt.core.ModuleDecl→effekt.util.messages.ErrorReportereffekt.core.Typing→effekt.util.messages.ErrorReporter
- Direction
- core uses util.messages, so a change to util.messages can break core, while a change to core can't break util.messages.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→12 core uses generator.js✕
- Connections
- 1 pair of types, where a type in core uses a type in generator.js.
- The types involved
effekt.core.Transformer→effekt.generator.js.Module
- Direction
- core uses generator.js, so a change to generator.js can break core, while a change to core can't break generator.js.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→16 core uses source✕
- Connections
- 6 pairs of types, where a type in core uses a type in source.
- The types involved
effekt.core.CoreParsers→effekt.source.FeatureFlageffekt.core.PrettyPrinter→effekt.source.FeatureFlageffekt.core.Transformer→effekt.source.CaptureSeteffekt.core.Transformer→effekt.source.MatchGuardeffekt.core.Transformer→effekt.source.Termeffekt.core.Transformer→effekt.source.ValueArg
- Direction
- core uses source, so a change to source can break core, while a change to core can't break source.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→22 core uses symbols✕
- Connections
- 21 pairs of types, where a type in core uses a type in symbols.
- The types involved
effekt.core.Block→effekt.symbols.Captureseffekt.core.BlockParam→effekt.symbols.Captureseffekt.core.CoreParsers→effekt.symbols.Captureseffekt.core.Free→effekt.symbols.Captureseffekt.core.Id→effekt.symbols.Nameeffekt.core.Implementation→effekt.symbols.Captureseffekt.core.Operation→effekt.symbols.Captureseffekt.core.PrettyPrinter→effekt.symbols.Captureseffekt.core.PrettyPrinter→effekt.symbols.Symboleffekt.core.Stmt→effekt.symbols.Captureseffekt.core.Transformer→effekt.symbols.Bindingseffekt.core.Transformer→effekt.symbols.BlockSymboleffekt.core.Transformer→effekt.symbols.Captureseffekt.core.Transformer→effekt.symbols.TermSymboleffekt.core.Transformer→effekt.symbols.TrackedParameffekt.core.Transformer→effekt.symbols.ValueSymboleffekt.core.TransformerOps→effekt.symbols.BlockSymboleffekt.core.TransformerOps→effekt.symbols.Captureeffekt.core.TransformerOps→effekt.symbols.Captureseffekt.core.Typing→effekt.symbols.Captureseffekt.core.substitutions→effekt.symbols.Captures
- Direction
- core uses symbols, so a change to symbols can break core, while a change to core can't break symbols.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→23 core uses core.Tree✕
- Connections
- 2 pairs of types, where a type in core uses a type in core.Tree.
- The types involved
effekt.core.Renamer→effekt.core.Tree.Rewriteeffekt.core.TestRenamer→effekt.core.Tree.Rewrite
- Direction
- core uses core.Tree, so a change to core.Tree can break core, while a change to core can't break core.Tree.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→25 core uses core.LambdaSets✕
- Connections
- 6 pairs of types, where a type in core uses a type in core.LambdaSets.
- The types involved
effekt.core.LambdaSets→effekt.core.LambdaSets.BlockCaseeffekt.core.LambdaSets→effekt.core.LambdaSets.Callableeffekt.core.LambdaSets→effekt.core.LambdaSets.Constraintseffekt.core.LambdaSets→effekt.core.LambdaSets.Solutioneffekt.core.Transformer→effekt.core.LambdaSets.Callableeffekt.core.Typing→effekt.core.LambdaSets.Constraints
- Direction
- core uses core.LambdaSets, so a change to core.LambdaSets can break core, while a change to core can't break core.LambdaSets.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→29 core uses context part of a loop✕
- Connections
- 7 pairs of types, where a type in core uses a type in context.
- The types involved
effekt.core.ArityRaising→effekt.context.Contexteffekt.core.DeadCodeElimination→effekt.context.Contexteffekt.core.LambdaSets→effekt.context.Contexteffekt.core.Mono→effekt.context.Contexteffekt.core.Show→effekt.context.Contexteffekt.core.Transformer→effekt.context.Contexteffekt.core.TransformerOps→effekt.context.ContextOps
- Direction
- core uses context, so a change to context can break core, while a change to core can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→30 core uses util part of a loop✕
- Connections
- 2 pairs of types, where a type in core uses a type in util.
- The types involved
effekt.core.Free→effekt.util.DBeffekt.core.PatternMatchingCompiler→effekt.util.DB
- Direction
- core uses util, so a change to util can break core, while a change to core can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→33 core uses core.vm.As part of a loop✕
- Connections
- 31 pairs of types, where a type in core uses a type in core.vm.As. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.core.ArityRaising→effekt.core.vm.As.Stringeffekt.core.Block→effekt.core.vm.As.Inteffekt.core.Block→effekt.core.vm.As.Stringeffekt.core.CoreParsers→effekt.core.vm.As.Stringeffekt.core.DeadCodeElimination→effekt.core.vm.As.Stringeffekt.core.DeclarationContext→effekt.core.vm.As.Inteffekt.core.DeclarationContext→effekt.core.vm.As.Stringeffekt.core.EffektLexers→effekt.core.vm.As.Stringeffekt.core.Expr→effekt.core.vm.As.Inteffekt.core.Expr→effekt.core.vm.As.Stringeffekt.core.Id→effekt.core.vm.As.Stringeffekt.core.Implementation→effekt.core.vm.As.Inteffekt.core.LambdaSets→effekt.core.vm.As.Inteffekt.core.LambdaSets→effekt.core.vm.As.Stringeffekt.core.ModuleDecl→effekt.core.vm.As.Inteffekt.core.ModuleDecl→effekt.core.vm.As.Stringeffekt.core.Mono→effekt.core.vm.As.Stringeffekt.core.Names→effekt.core.vm.As.Stringeffekt.core.Operation→effekt.core.vm.As.Inteffekt.core.PatternMatchingCompiler→effekt.core.vm.As.Stringeffekt.core.PrettyPrinter→effekt.core.vm.As.Stringeffekt.core.QualifiedSignature→effekt.core.vm.As.Stringeffekt.core.Show→effekt.core.vm.As.Stringeffekt.core.Stmt→effekt.core.vm.As.Inteffekt.core.Stmt→effekt.core.vm.As.String
- Direction
- core uses core.vm.As, so a change to core.vm.As can break core, while a change to core can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→37 core uses effekt part of a loop✕
- Connections
- 10 pairs of types, where a type in core uses a type in effekt.
- The types involved
effekt.core.ArityRaising→effekt.Phaseeffekt.core.CoreParsers→effekt.Templateeffekt.core.DeadCodeElimination→effekt.Phaseeffekt.core.EffektLexers→effekt.Parsereffekt.core.LambdaSets→effekt.Phaseeffekt.core.Mono→effekt.Phaseeffekt.core.PrettyPrinter→effekt.Templateeffekt.core.Show→effekt.Phaseeffekt.core.TestRenamer→effekt.Templateeffekt.core.Transformer→effekt.Phase
- Direction
- core uses effekt, so a change to effekt can break core, while a change to core can't break effekt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→9 core.ArityRaising uses cps✕
- Connections
- 2 pairs of types, where a type in core.ArityRaising uses a type in cps.
- The types involved
effekt.core.ArityRaising.CallSite→effekt.cps.Defeffekt.core.ArityRaising.Raise→effekt.cps.Def
- Direction
- core.ArityRaising uses cps, so a change to cps can break core.ArityRaising, while a change to core.ArityRaising can't break cps.
- Position
- Below the diagonal: core.ArityRaising uses a module listed above it, which is the healthy direction.
27→26 core.ArityRaising uses core✕
- Connections
- 19 pairs of types, where a type in core.ArityRaising uses a type in core.
- The types involved
effekt.core.ArityRaising.CallSite→effekt.core.ValueTypeeffekt.core.ArityRaising.Env→effekt.core.Expreffekt.core.ArityRaising.Env→effekt.core.Ideffekt.core.ArityRaising.Env→effekt.core.ValueParameffekt.core.ArityRaising.Raise→effekt.core.Bindeffekt.core.ArityRaising.Raise→effekt.core.Blockeffekt.core.ArityRaising.Raise→effekt.core.BlockParameffekt.core.ArityRaising.Raise→effekt.core.BlockTypeeffekt.core.ArityRaising.Raise→effekt.core.Constructoreffekt.core.ArityRaising.Raise→effekt.core.Declarationeffekt.core.ArityRaising.Raise→effekt.core.Expreffekt.core.ArityRaising.Raise→effekt.core.Fieldeffekt.core.ArityRaising.Raise→effekt.core.Ideffekt.core.ArityRaising.Raise→effekt.core.ModuleDecleffekt.core.ArityRaising.Raise→effekt.core.Operationeffekt.core.ArityRaising.Raise→effekt.core.Stmteffekt.core.ArityRaising.Raise→effekt.core.Topleveleffekt.core.ArityRaising.Raise→effekt.core.ValueParameffekt.core.ArityRaising.Raise→effekt.core.ValueType
- Direction
- core.ArityRaising uses core, so a change to core can break core.ArityRaising, while a change to core.ArityRaising can't break core.
- Position
- Below the diagonal: core.ArityRaising uses a module listed above it, which is the healthy direction.
27→33 core.ArityRaising uses core.vm.As part of a loop✕
- Connections
- 1 pair of types, where a type in core.ArityRaising uses a type in core.vm.As.
- The types involved
effekt.core.ArityRaising.Raise→effekt.core.vm.As.Int
- Direction
- core.ArityRaising uses core.vm.As, so a change to core.vm.As can break core.ArityRaising, while a change to core.ArityRaising can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→4 namer uses core.Type✕
- Connections
- 1 pair of types, where a type in namer uses a type in core.Type.
- The types involved
effekt.namer.Namer→effekt.core.Type.MatchClause
- Direction
- namer uses core.Type, so a change to core.Type can break namer, while a change to namer can't break core.Type.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→9 namer uses cps✕
- Connections
- 1 pair of types, where a type in namer uses a type in cps.
- The types involved
effekt.namer.Namer→effekt.cps.Def
- Direction
- namer uses cps, so a change to cps can break namer, while a change to namer can't break cps.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→12 namer uses generator.js✕
- Connections
- 1 pair of types, where a type in namer uses a type in generator.js.
- The types involved
effekt.namer.Namer→effekt.generator.js.Module
- Direction
- namer uses generator.js, so a change to generator.js can break namer, while a change to namer can't break generator.js.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→14 namer uses symbols.scopes✕
- Connections
- 1 pair of types, where a type in namer uses a type in symbols.scopes.
- The types involved
effekt.namer.NamerOps→effekt.symbols.scopes.Scoping
- Direction
- namer uses symbols.scopes, so a change to symbols.scopes can break namer, while a change to namer can't break symbols.scopes.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→16 namer uses source✕
- Connections
- 15 pairs of types, where a type in namer uses a type in source.
- The types involved
effekt.namer.Namer→effekt.source.CaptureSeteffekt.namer.Namer→effekt.source.Effectfuleffekt.namer.Namer→effekt.source.Effectseffekt.namer.Namer→effekt.source.FunctionTypeeffekt.namer.Namer→effekt.source.Handlereffekt.namer.Namer→effekt.source.MatchGuardeffekt.namer.Namer→effekt.source.MatchPatterneffekt.namer.Namer→effekt.source.Parameffekt.namer.Namer→effekt.source.Termeffekt.namer.Namer→effekt.source.TypeRefeffekt.namer.Namer→effekt.source.ValueArgeffekt.namer.NamerOps→effekt.source.IdDefeffekt.namer.NamerOps→effekt.source.IdRefeffekt.namer.NamerOps→effekt.source.Manyeffekt.namer.NamerOps→effekt.source.Param
- Direction
- namer uses source, so a change to source can break namer, while a change to namer can't break source.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→22 namer uses symbols✕
- Connections
- 8 pairs of types, where a type in namer uses a type in symbols.
- The types involved
effekt.namer.NamerOps→effekt.symbols.BlockSymboleffekt.namer.NamerOps→effekt.symbols.Captureeffekt.namer.NamerOps→effekt.symbols.Holeeffekt.namer.NamerOps→effekt.symbols.Nameeffekt.namer.NamerOps→effekt.symbols.Symboleffekt.namer.NamerOps→effekt.symbols.TermSymboleffekt.namer.NamerOps→effekt.symbols.TrackedParameffekt.namer.NamerOps→effekt.symbols.TypeSymbol
- Direction
- namer uses symbols, so a change to symbols can break namer, while a change to namer can't break symbols.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→26 namer uses core✕
- Connections
- 15 pairs of types, where a type in namer uses a type in core.
- The types involved
effekt.namer.Namer→effekt.core.BlockParameffekt.namer.Namer→effekt.core.BlockTypeeffekt.namer.Namer→effekt.core.Constructoreffekt.namer.Namer→effekt.core.Fieldeffekt.namer.Namer→effekt.core.Ideffekt.namer.Namer→effekt.core.Implementationeffekt.namer.Namer→effekt.core.ModuleDecleffekt.namer.Namer→effekt.core.Stmteffekt.namer.Namer→effekt.core.Typeeffekt.namer.Namer→effekt.core.ValueParameffekt.namer.Namer→effekt.core.ValueTypeeffekt.namer.NamerOps→effekt.core.BlockParameffekt.namer.NamerOps→effekt.core.Constructoreffekt.namer.NamerOps→effekt.core.Ideffekt.namer.NamerOps→effekt.core.ValueParam
- Direction
- namer uses core, so a change to core can break namer, while a change to namer can't break core.
- Position
- Below the diagonal: namer uses a module listed above it, which is the healthy direction.
28→29 namer uses context part of a loop✕
- Connections
- 2 pairs of types, where a type in namer uses a type in context.
- The types involved
effekt.namer.Namer→effekt.context.Contexteffekt.namer.NamerOps→effekt.context.ContextOps
- Direction
- namer uses context, so a change to context can break namer, while a change to namer can't break context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→30 namer uses util part of a loop✕
- Connections
- 1 pair of types, where a type in namer uses a type in util.
- The types involved
effekt.namer.Namer→effekt.util.RequirementLevel
- Direction
- namer uses util, so a change to util can break namer, while a change to namer can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→33 namer uses core.vm.As part of a loop✕
- Connections
- 3 pairs of types, where a type in namer uses a type in core.vm.As.
- The types involved
effekt.namer.Namer→effekt.core.vm.As.Inteffekt.namer.Namer→effekt.core.vm.As.Stringeffekt.namer.NamerOps→effekt.core.vm.As.String
- Direction
- namer uses core.vm.As, so a change to core.vm.As can break namer, while a change to namer can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→37 namer uses effekt part of a loop✕
- Connections
- 1 pair of types, where a type in namer uses a type in effekt.
- The types involved
effekt.namer.Namer→effekt.Phase
- Direction
- namer uses effekt, so a change to effekt can break namer, while a change to namer can't break effekt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→10 context uses util.messages✕
- Connections
- 2 pairs of types, where a type in context uses a type in util.messages.
- The types involved
effekt.context.Annotations→effekt.util.messages.ErrorReportereffekt.context.ContextOps→effekt.util.messages.ErrorReporter
- Direction
- context uses util.messages, so a change to util.messages can break context, while a change to context can't break util.messages.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→12 context uses generator.js✕
- Connections
- 2 pairs of types, where a type in context uses a type in generator.js.
- The types involved
effekt.context.Context→effekt.generator.js.Moduleeffekt.context.ModuleDB→effekt.generator.js.Module
- Direction
- context uses generator.js, so a change to generator.js can break context, while a change to context can't break generator.js.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→15 context uses generator.llvm✕
- Connections
- 1 pair of types, where a type in context uses a type in generator.llvm.
- The types involved
effekt.context.TreeAnnotations→effekt.generator.llvm.Definition
- Direction
- context uses generator.llvm, so a change to generator.llvm can break context, while a change to context can't break generator.llvm.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→16 context uses source✕
- Connections
- 4 pairs of types, where a type in context uses a type in source.
- The types involved
effekt.context.SymbolAnnotations→effekt.source.FunctionTypeeffekt.context.SymbolAnnotations→effekt.source.IdDefeffekt.context.TreeAnnotations→effekt.source.CaptureSeteffekt.context.TreeAnnotations→effekt.source.Effects
- Direction
- context uses source, so a change to source can break context, while a change to context can't break source.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→19 context uses typer✕
- Connections
- 2 pairs of types, where a type in context uses a type in typer.
- The types involved
effekt.context.Context→effekt.typer.TyperOpseffekt.context.ContextOps→effekt.typer.Unification
- Direction
- context uses typer, so a change to typer can break context, while a change to context can't break typer.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→22 context uses symbols✕
- Connections
- 6 pairs of types, where a type in context uses a type in symbols.
- The types involved
effekt.context.ModuleDB→effekt.symbols.TermSymboleffekt.context.SourceAnnotations→effekt.symbols.Symboleffekt.context.SymbolAnnotations→effekt.symbols.BlockSymboleffekt.context.SymbolAnnotations→effekt.symbols.Captureseffekt.context.SymbolAnnotations→effekt.symbols.Symboleffekt.context.TreeAnnotations→effekt.symbols.Symbol
- Direction
- context uses symbols, so a change to symbols can break context, while a change to context can't break symbols.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→26 context uses core✕
- Connections
- 10 pairs of types, where a type in context uses a type in core.
- The types involved
effekt.context.Context→effekt.core.TransformerOpseffekt.context.Context→effekt.core.Treeeffekt.context.SymbolAnnotations→effekt.core.BlockTypeeffekt.context.SymbolAnnotations→effekt.core.Typeeffekt.context.SymbolAnnotations→effekt.core.ValueTypeeffekt.context.TreeAnnotations→effekt.core.BlockTypeeffekt.context.TreeAnnotations→effekt.core.Ideffekt.context.TreeAnnotations→effekt.core.Treeeffekt.context.TreeAnnotations→effekt.core.Typeeffekt.context.TreeAnnotations→effekt.core.ValueType
- Direction
- context uses core, so a change to core can break context, while a change to context can't break core.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→28 context uses namer✕
- Connections
- 1 pair of types, where a type in context uses a type in namer.
- The types involved
effekt.context.Context→effekt.namer.NamerOps
- Direction
- context uses namer, so a change to namer can break context, while a change to context can't break namer.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
29→30 context uses util part of a loop✕
- Connections
- 2 pairs of types, where a type in context uses a type in util.
- The types involved
effekt.context.Context→effekt.util.Timerseffekt.context.TreeAnnotations→effekt.util.DB
- Direction
- context uses util, so a change to util can break context, while a change to context can't break util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→31 context uses context.Context part of a loop✕
- Connections
- 1 pair of types, where a type in context uses a type in context.Context.
- The types involved
effekt.context.Context→effekt.context.Context.State
- Direction
- context uses context.Context, so a change to context.Context can break context, while a change to context can't break context.Context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→33 context uses core.vm.As part of a loop✕
- Connections
- 9 pairs of types, where a type in context uses a type in core.vm.As.
- The types involved
effekt.context.IOModuleDB→effekt.core.vm.As.Stringeffekt.context.ModuleDB→effekt.core.vm.As.Stringeffekt.context.SourceAnnotation→effekt.core.vm.As.Stringeffekt.context.SymbolAnnotation→effekt.core.vm.As.Stringeffekt.context.SymbolAnnotations→effekt.core.vm.As.Referenceeffekt.context.TreeAnnotation→effekt.core.vm.As.Stringeffekt.context.TreeAnnotations→effekt.core.vm.As.Referenceeffekt.context.VirtualFileSource→effekt.core.vm.As.Stringeffekt.context.VirtualModuleDB→effekt.core.vm.As.String
- Direction
- context uses core.vm.As, so a change to core.vm.As can break context, while a change to context can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→37 context uses effekt part of a loop✕
- Connections
- 1 pair of types, where a type in context uses a type in effekt.
- The types involved
effekt.context.Context→effekt.EffektConfig
- Direction
- context uses effekt, so a change to effekt can break context, while a change to context can't break effekt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→7 util uses lsp✕
- Connections
- 2 pairs of types, where a type in util uses a type in lsp.
- The types involved
effekt.util.ColoredMessaging→effekt.lsp.Positioneffekt.util.PlainMessaging→effekt.lsp.Position
- Direction
- util uses lsp, so a change to lsp can break util, while a change to util can't break lsp.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→9 util uses cps✕
- Connections
- 1 pair of types, where a type in util uses a type in cps.
- The types involved
effekt.util.DocumentationGenerator→effekt.cps.Def
- Direction
- util uses cps, so a change to cps can break util, while a change to util can't break cps.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→10 util uses util.messages✕
- Connections
- 3 pairs of types, where a type in util uses a type in util.messages.
- The types involved
effekt.util.ColoredMessaging→effekt.util.messages.EffektErroreffekt.util.ColoredMessaging→effekt.util.messages.EffektMessagingeffekt.util.PlainMessaging→effekt.util.messages.EffektError
- Direction
- util uses util.messages, so a change to util.messages can break util, while a change to util can't break util.messages.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→16 util uses source✕
- Connections
- 5 pairs of types, where a type in util uses a type in source.
- The types involved
effekt.util.DocumentationGenerator→effekt.source.CaptureSeteffekt.util.DocumentationGenerator→effekt.source.Effectseffekt.util.DocumentationGenerator→effekt.source.Includeeffekt.util.DocumentationGenerator→effekt.source.Spaneffekt.util.StructuralMacro→effekt.source.Term
- Direction
- util uses source, so a change to source can break util, while a change to util can't break source.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→17 util uses lexer✕
- Connections
- 2 pairs of types, where a type in util uses a type in lexer.
- The types involved
effekt.util.AnsiHighlight→effekt.lexer.TokenKindeffekt.util.HtmlHighlight→effekt.lexer.TokenKind
- Direction
- util uses lexer, so a change to lexer can break util, while a change to util can't break lexer.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→22 util uses symbols✕
- Connections
- 3 pairs of types, where a type in util uses a type in symbols.
- The types involved
effekt.util.ColoredMessaging→effekt.symbols.Nameeffekt.util.DocumentationGenerator→effekt.symbols.Symboleffekt.util.StructuralMacro→effekt.symbols.Symbol
- Direction
- util uses symbols, so a change to symbols can break util, while a change to util can't break symbols.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→26 util uses core✕
- Connections
- 12 pairs of types, where a type in util uses a type in core.
- The types involved
effekt.util.DB→effekt.core.Ideffekt.util.DocumentationGenerator→effekt.core.BlockParameffekt.util.DocumentationGenerator→effekt.core.Constructoreffekt.util.DocumentationGenerator→effekt.core.Ideffekt.util.DocumentationGenerator→effekt.core.ModuleDecleffekt.util.DocumentationGenerator→effekt.core.Operationeffekt.util.DocumentationGenerator→effekt.core.Typeeffekt.util.DocumentationGenerator→effekt.core.ValueParameffekt.util.JSONDocumentationGenerator→effekt.core.ModuleDecleffekt.util.StructuralMacro→effekt.core.Expreffekt.util.VirtualSource→effekt.core.ModuleDecleffekt.util.debugMacros→effekt.core.Expr
- Direction
- util uses core, so a change to core can break util, while a change to util can't break core.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→29 util uses context✕
- Connections
- 3 pairs of types, where a type in util uses a type in context.
- The types involved
effekt.util.DocumentationGenerator→effekt.context.Contexteffekt.util.JSONDocumentationGenerator→effekt.context.Contexteffekt.util.Task→effekt.context.Context
- Direction
- util uses context, so a change to context can break util, while a change to util can't break context.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
30→33 util uses core.vm.As part of a loop✕
- Connections
- 21 pairs of types, where a type in util uses a type in core.vm.As.
- The types involved
effekt.util.AnsiColoredMessaging→effekt.core.vm.As.Stringeffekt.util.AnsiHighlight→effekt.core.vm.As.Stringeffekt.util.ColoredMessaging→effekt.core.vm.As.Stringeffekt.util.Docs→effekt.core.vm.As.Inteffekt.util.Docs→effekt.core.vm.As.Stringeffekt.util.DocumentationGenerator→effekt.core.vm.As.Inteffekt.util.DocumentationGenerator→effekt.core.vm.As.Stringeffekt.util.HtmlHighlight→effekt.core.vm.As.Stringeffekt.util.JSONDocumentationGenerator→effekt.core.vm.As.Stringeffekt.util.PathUtils→effekt.core.vm.As.Stringeffekt.util.PlainMessaging→effekt.core.vm.As.Stringeffekt.util.Task→effekt.core.vm.As.Stringeffekt.util.Timed→effekt.core.vm.As.Doubleeffekt.util.Timed→effekt.core.vm.As.Stringeffekt.util.Timers→effekt.core.vm.As.Doubleeffekt.util.Timers→effekt.core.vm.As.Stringeffekt.util.UByte→effekt.core.vm.As.Byteeffekt.util.UByte→effekt.core.vm.As.Inteffekt.util.VirtualSource→effekt.core.vm.As.Inteffekt.util.messages→effekt.core.vm.As.Stringeffekt.util.paths→effekt.core.vm.As.String
- Direction
- util uses core.vm.As, so a change to core.vm.As can break util, while a change to util can't break core.vm.As.
- 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.
31→30 context.Context uses util✕
- Connections
- 1 pair of types, where a type in context.Context uses a type in util.
- The types involved
effekt.context.Context.State→effekt.util.DB
- Direction
- context.Context uses util, so a change to util can break context.Context, while a change to context.Context can't break util.
- Position
- Below the diagonal: context.Context uses a module listed above it, which is the healthy direction.
32→5 core.vm uses core.optimizer.StaticResumptions✕
- Connections
- 1 pair of types, where a type in core.vm uses a type in core.optimizer.StaticResumptions.
- The types involved
effekt.core.vm.Interpreter→effekt.core.optimizer.StaticResumptions.Frame
- Direction
- core.vm uses core.optimizer.StaticResumptions, so a change to core.optimizer.StaticResumptions can break core.vm, while a change to core.vm can't break core.optimizer.StaticResumptions.
- Position
- Below the diagonal: core.vm uses a module listed above it, which is the healthy direction.
32→26 core.vm uses core✕
- Connections
- 7 pairs of types, where a type in core.vm uses a type in core.
- The types involved
effekt.core.vm.Counting→effekt.core.Ideffekt.core.vm.Env→effekt.core.Ideffekt.core.vm.Instrumentation→effekt.core.Ideffekt.core.vm.Interpreter→effekt.core.Blockeffekt.core.vm.Interpreter→effekt.core.Expreffekt.core.vm.Interpreter→effekt.core.Ideffekt.core.vm.Interpreter→effekt.core.ModuleDecl
- Direction
- core.vm uses core, so a change to core can break core.vm, while a change to core.vm can't break core.
- Position
- Below the diagonal: core.vm uses a module listed above it, which is the healthy direction.
32→27 core.vm uses core.ArityRaising✕
- Connections
- 2 pairs of types, where a type in core.vm uses a type in core.ArityRaising.
- The types involved
effekt.core.vm.Env→effekt.core.ArityRaising.Enveffekt.core.vm.Interpreter→effekt.core.ArityRaising.Env
- Direction
- core.vm uses core.ArityRaising, so a change to core.ArityRaising can break core.vm, while a change to core.vm can't break core.ArityRaising.
- Position
- Below the diagonal: core.vm uses a module listed above it, which is the healthy direction.
32→31 core.vm uses context.Context✕
- Connections
- 2 pairs of types, where a type in core.vm uses a type in context.Context.
- The types involved
effekt.core.vm.Instrumentation→effekt.context.Context.Stateeffekt.core.vm.Interpreter→effekt.context.Context.State
- Direction
- core.vm uses context.Context, so a change to context.Context can break core.vm, while a change to core.vm can't break context.Context.
- Position
- Below the diagonal: core.vm uses a module listed above it, which is the healthy direction.
32→33 core.vm uses core.vm.As part of a loop✕
- Connections
- 7 pairs of types, where a type in core.vm uses a type in core.vm.As.
- The types involved
effekt.core.vm.Builtin→effekt.core.vm.As.Stringeffekt.core.vm.BuiltinHistogram→effekt.core.vm.As.Inteffekt.core.vm.BuiltinHistogram→effekt.core.vm.As.Stringeffekt.core.vm.Counting→effekt.core.vm.As.Inteffekt.core.vm.Instrumentation→effekt.core.vm.As.Inteffekt.core.vm.Instrumentation→effekt.core.vm.As.Stringeffekt.core.vm.VMError→effekt.core.vm.As.String
- Direction
- core.vm uses core.vm.As, so a change to core.vm.As can break core.vm, while a change to core.vm can't break core.vm.As.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→30 core.vm.As uses util✕
- Connections
- 2 pairs of types, where a type in core.vm.As uses a type in util.
- The types involved
effekt.core.vm.As.Byte→effekt.util.UByteeffekt.core.vm.As.ByteArray→effekt.util.UByte
- Direction
- core.vm.As uses util, so a change to util can break core.vm.As, while a change to core.vm.As can't break util.
- Position
- Below the diagonal: core.vm.As uses a module listed above it, which is the healthy direction.
33→32 core.vm.As uses core.vm✕
- Connections
- 10 pairs of types, where a type in core.vm.As uses a type in core.vm.
- The types involved
effekt.core.vm.As.Array→effekt.core.vm.Valueeffekt.core.vm.As.Bool→effekt.core.vm.Valueeffekt.core.vm.As.Byte→effekt.core.vm.Valueeffekt.core.vm.As.ByteArray→effekt.core.vm.Valueeffekt.core.vm.As.Double→effekt.core.vm.Valueeffekt.core.vm.As.Int→effekt.core.vm.Valueeffekt.core.vm.As.Reference→effekt.core.vm.Valueeffekt.core.vm.As.Regex→effekt.core.vm.Valueeffekt.core.vm.As.RegexMatch→effekt.core.vm.Valueeffekt.core.vm.As.String→effekt.core.vm.Value
- Direction
- core.vm.As uses core.vm, so a change to core.vm can break core.vm.As, while a change to core.vm.As can't break core.vm.
- Position
- Below the diagonal: core.vm.As uses a module listed above it, which is the healthy direction.
34→7 Intelligence uses lsp✕
- Connections
- 1 pair of types, where a type in Intelligence uses a type in lsp.
- The types involved
effekt.Intelligence.CaptureInfo→effekt.lsp.Position
- Direction
- Intelligence uses lsp, so a change to lsp can break Intelligence, while a change to Intelligence can't break lsp.
- Position
- Below the diagonal: Intelligence uses a module listed above it, which is the healthy direction.
34→16 Intelligence uses source✕
- Connections
- 2 pairs of types, where a type in Intelligence uses a type in source.
- The types involved
effekt.Intelligence.CaptureInfo→effekt.source.CaptureSeteffekt.Intelligence.HoleInfo→effekt.source.Span
- Direction
- Intelligence uses source, so a change to source can break Intelligence, while a change to Intelligence can't break source.
- Position
- Below the diagonal: Intelligence uses a module listed above it, which is the healthy direction.
34→22 Intelligence uses symbols✕
- Connections
- 1 pair of types, where a type in Intelligence uses a type in symbols.
- The types involved
effekt.Intelligence.SymbolInfo→effekt.symbols.Symbol
- Direction
- Intelligence uses symbols, so a change to symbols can break Intelligence, while a change to Intelligence can't break symbols.
- Position
- Below the diagonal: Intelligence uses a module listed above it, which is the healthy direction.
34→33 Intelligence uses core.vm.As✕
- Connections
- 12 pairs of types, where a type in Intelligence uses a type in core.vm.As.
- The types involved
effekt.Intelligence.BindingInfo→effekt.core.vm.As.Stringeffekt.Intelligence.Code→effekt.core.vm.As.Stringeffekt.Intelligence.HoleInfo→effekt.core.vm.As.Stringeffekt.Intelligence.HoleItem→effekt.core.vm.As.Stringeffekt.Intelligence.LSPLocation→effekt.core.vm.As.Stringeffekt.Intelligence.LSPPosition→effekt.core.vm.As.Inteffekt.Intelligence.NaturalLanguage→effekt.core.vm.As.Stringeffekt.Intelligence.ScopeInfo→effekt.core.vm.As.Stringeffekt.Intelligence.ScopeKind→effekt.core.vm.As.Stringeffekt.Intelligence.SymbolInfo→effekt.core.vm.As.Stringeffekt.Intelligence.TermBinding→effekt.core.vm.As.Stringeffekt.Intelligence.TypeBinding→effekt.core.vm.As.String
- Direction
- Intelligence uses core.vm.As, so a change to core.vm.As can break Intelligence, while a change to Intelligence can't break core.vm.As.
- Position
- Below the diagonal: Intelligence uses a module listed above it, which is the healthy direction.
35→9 Repl uses cps✕
- Connections
- 1 pair of types, where a type in Repl uses a type in cps.
- The types involved
effekt.Repl.ReplModule→effekt.cps.Def
- Direction
- Repl uses cps, so a change to cps can break Repl, while a change to Repl can't break cps.
- Position
- Below the diagonal: Repl uses a module listed above it, which is the healthy direction.
35→16 Repl uses source✕
- Connections
- 2 pairs of types, where a type in Repl uses a type in source.
- The types involved
effekt.Repl.ReplModule→effekt.source.Includeeffekt.Repl.ReplModule→effekt.source.Term
- Direction
- Repl uses source, so a change to source can break Repl, while a change to Repl can't break source.
- Position
- Below the diagonal: Repl uses a module listed above it, which is the healthy direction.
35→26 Repl uses core✕
- Connections
- 1 pair of types, where a type in Repl uses a type in core.
- The types involved
effekt.Repl.ReplModule→effekt.core.ModuleDecl
- Direction
- Repl uses core, so a change to core can break Repl, while a change to Repl can't break core.
- Position
- Below the diagonal: Repl uses a module listed above it, which is the healthy direction.
35→33 Repl uses core.vm.As✕
- Connections
- 2 pairs of types, where a type in Repl uses a type in core.vm.As.
- The types involved
effekt.Repl.Command→effekt.core.vm.As.Stringeffekt.Repl.ReplModule→effekt.core.vm.As.String
- Direction
- Repl uses core.vm.As, so a change to core.vm.As can break Repl, while a change to Repl can't break core.vm.As.
- Position
- Below the diagonal: Repl uses a module listed above it, which is the healthy direction.
36→1 core.Mono.collect uses core.Mono.preprocess.DeBruijn✕
- Connections
- 1 pair of types, where a type in core.Mono.collect uses a type in core.Mono.preprocess.DeBruijn.
- The types involved
effekt.core.Mono.collect.Environment→effekt.core.Mono.preprocess.DeBruijn.Environment
- Direction
- core.Mono.collect uses core.Mono.preprocess.DeBruijn, so a change to core.Mono.preprocess.DeBruijn can break core.Mono.collect, while a change to core.Mono.collect can't break core.Mono.preprocess.DeBruijn.
- Position
- Below the diagonal: core.Mono.collect uses a module listed above it, which is the healthy direction.
36→20 core.Mono.collect uses core.Mono✕
- Connections
- 1 pair of types, where a type in core.Mono.collect uses a type in core.Mono.
- The types involved
effekt.core.Mono.collect.Environment→effekt.core.Mono.MonoCapture
- Direction
- core.Mono.collect uses core.Mono, so a change to core.Mono can break core.Mono.collect, while a change to core.Mono.collect can't break core.Mono.
- Position
- Below the diagonal: core.Mono.collect uses a module listed above it, which is the healthy direction.
36→25 core.Mono.collect uses core.LambdaSets✕
- Connections
- 1 pair of types, where a type in core.Mono.collect uses a type in core.LambdaSets.
- The types involved
effekt.core.Mono.collect.Environment→effekt.core.LambdaSets.Projection
- Direction
- core.Mono.collect uses core.LambdaSets, so a change to core.LambdaSets can break core.Mono.collect, while a change to core.Mono.collect can't break core.LambdaSets.
- Position
- Below the diagonal: core.Mono.collect uses a module listed above it, which is the healthy direction.
36→26 core.Mono.collect uses core✕
- Connections
- 1 pair of types, where a type in core.Mono.collect uses a type in core.
- The types involved
effekt.core.Mono.collect.Environment→effekt.core.Id
- Direction
- core.Mono.collect uses core, so a change to core can break core.Mono.collect, while a change to core.Mono.collect can't break core.
- Position
- Below the diagonal: core.Mono.collect uses a module listed above it, which is the healthy direction.
36→29 core.Mono.collect uses context✕
- Connections
- 1 pair of types, where a type in core.Mono.collect uses a type in context.
- The types involved
effekt.core.Mono.collect.Environment→effekt.context.Context
- Direction
- core.Mono.collect uses context, so a change to context can break core.Mono.collect, while a change to core.Mono.collect can't break context.
- Position
- Below the diagonal: core.Mono.collect uses a module listed above it, which is the healthy direction.
36→33 core.Mono.collect uses core.vm.As✕
- Connections
- 1 pair of types, where a type in core.Mono.collect uses a type in core.vm.As.
- The types involved
effekt.core.Mono.collect.Environment→effekt.core.vm.As.Int
- Direction
- core.Mono.collect uses core.vm.As, so a change to core.vm.As can break core.Mono.collect, while a change to core.Mono.collect can't break core.vm.As.
- Position
- Below the diagonal: core.Mono.collect uses a module listed above it, which is the healthy direction.
37→7 effekt uses lsp✕
- Connections
- 9 pairs of types, where a type in effekt uses a type in lsp.
- The types involved
effekt.Intelligence→effekt.lsp.CaptureInfoeffekt.Intelligence→effekt.lsp.Positioneffekt.Intelligence→effekt.lsp.Rangeeffekt.LanguageServer→effekt.lsp.CaptureInfoeffekt.LanguageServer→effekt.lsp.Diagnosticeffekt.LanguageServer→effekt.lsp.DiagnosticSeverityeffekt.LanguageServer→effekt.lsp.Locationeffekt.LanguageServer→effekt.lsp.Positioneffekt.Server→effekt.lsp.Diagnostic
- Direction
- effekt uses lsp, so a change to lsp can break effekt, while a change to effekt can't break lsp.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→10 effekt uses util.messages✕
- Connections
- 1 pair of types, where a type in effekt uses a type in util.messages.
- The types involved
effekt.LanguageServer→effekt.util.messages.EffektError
- Direction
- effekt uses util.messages, so a change to util.messages can break effekt, while a change to effekt can't break util.messages.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→12 effekt uses generator.js✕
- Connections
- 2 pairs of types, where a type in effekt uses a type in generator.js.
- The types involved
effekt.Compiler→effekt.generator.js.Moduleeffekt.Repl→effekt.generator.js.Module
- Direction
- effekt uses generator.js, so a change to generator.js can break effekt, while a change to effekt can't break generator.js.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→16 effekt uses source✕
- Connections
- 2 pairs of types, where a type in effekt uses a type in source.
- The types involved
effekt.Server→effekt.source.Spaneffekt.Spanned→effekt.source.Span
- Direction
- effekt uses source, so a change to source can break effekt, while a change to effekt can't break source.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→17 effekt uses lexer✕
- Connections
- 1 pair of types, where a type in effekt uses a type in lexer.
- The types involved
effekt.PrecedenceTable→effekt.lexer.TokenKind
- Direction
- effekt uses lexer, so a change to lexer can break effekt, while a change to effekt can't break lexer.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→21 effekt uses core.Mono.preprocess✕
- Connections
- 1 pair of types, where a type in effekt uses a type in core.Mono.preprocess.
- The types involved
effekt.Intelligence→effekt.core.Mono.preprocess.Scope
- Direction
- effekt uses core.Mono.preprocess, so a change to core.Mono.preprocess can break effekt, while a change to effekt can't break core.Mono.preprocess.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→22 effekt uses symbols✕
- Connections
- 5 pairs of types, where a type in effekt uses a type in symbols.
- The types involved
effekt.Intelligence→effekt.symbols.Bindingseffekt.Intelligence→effekt.symbols.Holeeffekt.Intelligence→effekt.symbols.Symboleffekt.Server→effekt.symbols.Holeeffekt.Server→effekt.symbols.Symbol
- Direction
- effekt uses symbols, so a change to symbols can break effekt, while a change to effekt can't break symbols.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→26 effekt uses core✕
- Connections
- 11 pairs of types, where a type in effekt uses a type in core.
- The types involved
effekt.Compiler→effekt.core.ModuleDecleffekt.Driver→effekt.core.ModuleDecleffekt.Intelligence→effekt.core.Ideffekt.Intelligence→effekt.core.Stmteffekt.Intelligence→effekt.core.Treeeffekt.Intelligence→effekt.core.ValueTypeeffekt.Repl→effekt.core.ModuleDecleffekt.Repl→effekt.core.Treeeffekt.ScalaListTypeAdapter→effekt.core.Typeeffekt.ScalaOptionTypeAdapter→effekt.core.Typeeffekt.Server→effekt.core.Tree
- Direction
- effekt uses core, so a change to core can break effekt, while a change to effekt can't break core.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→29 effekt uses context✕
- Connections
- 11 pairs of types, where a type in effekt uses a type in context.
- The types involved
effekt.ChezRunner→effekt.context.Contexteffekt.Compiler→effekt.context.Contexteffekt.Driver→effekt.context.Contexteffekt.Intelligence→effekt.context.Contexteffekt.JSNodeRunner→effekt.context.Contexteffekt.JSWebRunner→effekt.context.Contexteffekt.LLVMRunner→effekt.context.Contexteffekt.Parser→effekt.context.Contexteffekt.Phase→effekt.context.Contexteffekt.Runner→effekt.context.Contexteffekt.Server→effekt.context.Context
- Direction
- effekt uses context, so a change to context can break effekt, while a change to effekt can't break context.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→33 effekt uses core.vm.As✕
- Connections
- 28 pairs of types, where a type in effekt uses a type in core.vm.As. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.ChezRunner→effekt.core.vm.As.Inteffekt.ChezRunner→effekt.core.vm.As.Stringeffekt.Compiler→effekt.core.vm.As.Stringeffekt.Driver→effekt.core.vm.As.Stringeffekt.EffektConfig→effekt.core.vm.As.Stringeffekt.EffektHoleInfo→effekt.core.vm.As.Stringeffekt.EffektPublishHolesParams→effekt.core.vm.As.Stringeffekt.EffektPublishIRParams→effekt.core.vm.As.Stringeffekt.Fail→effekt.core.vm.As.Inteffekt.Fail→effekt.core.vm.As.Stringeffekt.Intelligence→effekt.core.vm.As.Arrayeffekt.Intelligence→effekt.core.vm.As.Stringeffekt.JSNodeRunner→effekt.core.vm.As.Stringeffekt.JSWebRunner→effekt.core.vm.As.Stringeffekt.LLVMRunner→effekt.core.vm.As.Stringeffekt.LanguageServer→effekt.core.vm.As.Arrayeffekt.LanguageServer→effekt.core.vm.As.Stringeffekt.Main→effekt.core.vm.As.Arrayeffekt.Main→effekt.core.vm.As.Stringeffekt.Phase→effekt.core.vm.As.Stringeffekt.RecoverableDiagnostic→effekt.core.vm.As.Inteffekt.RecoverableDiagnostic→effekt.core.vm.As.Stringeffekt.Repl→effekt.core.vm.As.Stringeffekt.Runner→effekt.core.vm.As.Stringeffekt.Server→effekt.core.vm.As.String
- Direction
- effekt uses core.vm.As, so a change to core.vm.As can break effekt, while a change to effekt can't break core.vm.As.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→34 effekt uses Intelligence✕
- Connections
- 8 pairs of types, where a type in effekt uses a type in Intelligence.
- The types involved
effekt.EffektHoleInfo→effekt.Intelligence.HoleItemeffekt.EffektHoleInfo→effekt.Intelligence.LSPRangeeffekt.EffektHoleInfo→effekt.Intelligence.ScopeInfoeffekt.Intelligence→effekt.Intelligence.BindingInfoeffekt.Intelligence→effekt.Intelligence.HoleInfoeffekt.Intelligence→effekt.Intelligence.HoleItemeffekt.Intelligence→effekt.Intelligence.ScopeInfoeffekt.Intelligence→effekt.Intelligence.SymbolInfo
- Direction
- effekt uses Intelligence, so a change to Intelligence can break effekt, while a change to effekt can't break Intelligence.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
37→35 effekt uses Repl✕
- Connections
- 2 pairs of types, where a type in effekt uses a type in Repl.
- The types involved
effekt.Repl→effekt.Repl.ReplModuleeffekt.Server→effekt.Repl.Command
- Direction
- effekt uses Repl, so a change to Repl can break effekt, while a change to effekt can't break Repl.
- Position
- Below the diagonal: effekt uses a module listed above it, which is the healthy direction.
38→5 core.optimizer uses core.optimizer.StaticResumptions✕
- Connections
- 3 pairs of types, where a type in core.optimizer uses a type in core.optimizer.StaticResumptions.
- The types involved
effekt.core.optimizer.StaticResumptions→effekt.core.optimizer.StaticResumptions.Continuationeffekt.core.optimizer.StaticResumptions→effekt.core.optimizer.StaticResumptions.Prompteffekt.core.optimizer.StaticResumptions→effekt.core.optimizer.StaticResumptions.TailPositions
- Direction
- core.optimizer uses core.optimizer.StaticResumptions, so a change to core.optimizer.StaticResumptions can break core.optimizer, while a change to core.optimizer can't break core.optimizer.StaticResumptions.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→9 core.optimizer uses cps✕
- Connections
- 1 pair of types, where a type in core.optimizer uses a type in cps.
- The types involved
effekt.core.optimizer.Reachable→effekt.cps.Def
- Direction
- core.optimizer uses cps, so a change to cps can break core.optimizer, while a change to core.optimizer can't break cps.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→22 core.optimizer uses symbols✕
- Connections
- 3 pairs of types, where a type in core.optimizer uses a type in symbols.
- The types involved
effekt.core.optimizer.BindSubexpressions→effekt.symbols.Captureseffekt.core.optimizer.Optimizer→effekt.symbols.Symboleffekt.core.optimizer.StaticResumptions→effekt.symbols.Captures
- Direction
- core.optimizer uses symbols, so a change to symbols can break core.optimizer, while a change to core.optimizer can't break symbols.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→23 core.optimizer uses core.Tree✕
- Connections
- 2 pairs of types, where a type in core.optimizer uses a type in core.Tree.
- The types involved
effekt.core.optimizer.Deadcode→effekt.core.Tree.TrampolinedRewriteeffekt.core.optimizer.DirectStyle→effekt.core.Tree.Rewrite
- Direction
- core.optimizer uses core.Tree, so a change to core.Tree can break core.optimizer, while a change to core.optimizer can't break core.Tree.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→26 core.optimizer uses core✕
- Connections
- 54 pairs of types, where a type in core.optimizer uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.core.optimizer.BindSubexpressions→effekt.core.Bindeffekt.core.optimizer.BindSubexpressions→effekt.core.Blockeffekt.core.optimizer.BindSubexpressions→effekt.core.BlockParameffekt.core.optimizer.BindSubexpressions→effekt.core.BlockTypeeffekt.core.optimizer.BindSubexpressions→effekt.core.Expreffekt.core.optimizer.BindSubexpressions→effekt.core.Ideffekt.core.optimizer.BindSubexpressions→effekt.core.Implementationeffekt.core.optimizer.BindSubexpressions→effekt.core.ModuleDecleffekt.core.optimizer.BindSubexpressions→effekt.core.Stmteffekt.core.optimizer.BindSubexpressions→effekt.core.Topleveleffekt.core.optimizer.BindSubexpressions→effekt.core.ValueParameffekt.core.optimizer.BindSubexpressions→effekt.core.ValueTypeeffekt.core.optimizer.CallSite→effekt.core.Blockeffekt.core.optimizer.CallSite→effekt.core.Expreffekt.core.optimizer.Deadcode→effekt.core.Declarationeffekt.core.optimizer.Deadcode→effekt.core.Ideffekt.core.optimizer.Deadcode→effekt.core.Implementationeffekt.core.optimizer.Deadcode→effekt.core.ModuleDecleffekt.core.optimizer.Deadcode→effekt.core.Stmteffekt.core.optimizer.Default→effekt.core.Expreffekt.core.optimizer.Default→effekt.core.Ideffekt.core.optimizer.Default→effekt.core.Implementationeffekt.core.optimizer.Default→effekt.core.Stmteffekt.core.optimizer.DirectStyle→effekt.core.Stmteffekt.core.optimizer.DirectStyle→effekt.core.ValueType
- Direction
- core.optimizer uses core, so a change to core can break core.optimizer, while a change to core.optimizer can't break core.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→27 core.optimizer uses core.ArityRaising✕
- Connections
- 4 pairs of types, where a type in core.optimizer uses a type in core.ArityRaising.
- The types involved
effekt.core.optimizer.BindSubexpressions→effekt.core.ArityRaising.Enveffekt.core.optimizer.Default→effekt.core.ArityRaising.CallSiteeffekt.core.optimizer.InliningPolicy→effekt.core.ArityRaising.CallSiteeffekt.core.optimizer.Unique→effekt.core.ArityRaising.CallSite
- Direction
- core.optimizer uses core.ArityRaising, so a change to core.ArityRaising can break core.optimizer, while a change to core.optimizer can't break core.ArityRaising.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→29 core.optimizer uses context✕
- Connections
- 6 pairs of types, where a type in core.optimizer uses a type in context.
- The types involved
effekt.core.optimizer.Default→effekt.context.Contexteffekt.core.optimizer.DropBindings→effekt.context.Contexteffekt.core.optimizer.InliningPolicy→effekt.context.Contexteffekt.core.optimizer.Normalizer→effekt.context.Contexteffekt.core.optimizer.Optimizer→effekt.context.Contexteffekt.core.optimizer.Unique→effekt.context.Context
- Direction
- core.optimizer uses context, so a change to context can break core.optimizer, while a change to core.optimizer can't break context.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→30 core.optimizer uses util✕
- Connections
- 1 pair of types, where a type in core.optimizer uses a type in util.
- The types involved
effekt.core.optimizer.Deadcode→effekt.util.Trampoline
- Direction
- core.optimizer uses util, so a change to util can break core.optimizer, while a change to core.optimizer can't break util.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→33 core.optimizer uses core.vm.As✕
- Connections
- 3 pairs of types, where a type in core.optimizer uses a type in core.vm.As.
- The types involved
effekt.core.optimizer.Default→effekt.core.vm.As.Inteffekt.core.optimizer.DropBindings→effekt.core.vm.As.Stringeffekt.core.optimizer.Optimizer→effekt.core.vm.As.String
- Direction
- core.optimizer uses core.vm.As, so a change to core.vm.As can break core.optimizer, while a change to core.optimizer can't break core.vm.As.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
38→37 core.optimizer uses effekt✕
- Connections
- 2 pairs of types, where a type in core.optimizer uses a type in effekt.
- The types involved
effekt.core.optimizer.DropBindings→effekt.Phaseeffekt.core.optimizer.Optimizer→effekt.Phase
- Direction
- core.optimizer uses effekt, so a change to effekt can break core.optimizer, while a change to core.optimizer can't break effekt.
- Position
- Below the diagonal: core.optimizer uses a module listed above it, which is the healthy direction.
39→3 generator.chez uses core.PatternMatchingCompiler✕
- Connections
- 1 pair of types, where a type in generator.chez uses a type in core.PatternMatchingCompiler.
- The types involved
effekt.generator.chez.TransformerCPS→effekt.core.PatternMatchingCompiler.Clause
- Direction
- generator.chez uses core.PatternMatchingCompiler, so a change to core.PatternMatchingCompiler can break generator.chez, while a change to generator.chez can't break core.PatternMatchingCompiler.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→9 generator.chez uses cps✕
- Connections
- 8 pairs of types, where a type in generator.chez uses a type in cps.
- The types involved
effekt.generator.chez.Block→effekt.cps.Defeffekt.generator.chez.ChezScheme→effekt.cps.Defeffekt.generator.chez.PrettyPrinter→effekt.cps.Defeffekt.generator.chez.Transformer→effekt.cps.Defeffekt.generator.chez.TransformerCPS→effekt.cps.Conteffekt.generator.chez.TransformerCPS→effekt.cps.Defeffekt.generator.chez.TransformerCPS→effekt.cps.MetaConteffekt.generator.chez.TransformerCPS→effekt.cps.ToplevelDefinition
- Direction
- generator.chez uses cps, so a change to cps can break generator.chez, while a change to generator.chez can't break cps.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→10 generator.chez uses util.messages✕
- Connections
- 5 pairs of types, where a type in generator.chez uses a type in util.messages.
- The types involved
effekt.generator.chez.ChezScheme→effekt.util.messages.ErrorReportereffekt.generator.chez.ChezSchemeCallCC→effekt.util.messages.ErrorReportereffekt.generator.chez.ChezSchemeMonadic→effekt.util.messages.ErrorReportereffekt.generator.chez.Transformer→effekt.util.messages.ErrorReportereffekt.generator.chez.TransformerCPS→effekt.util.messages.ErrorReporter
- Direction
- generator.chez uses util.messages, so a change to util.messages can break generator.chez, while a change to generator.chez can't break util.messages.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→12 generator.chez uses generator.js✕
- Connections
- 4 pairs of types, where a type in generator.chez uses a type in generator.js.
- The types involved
effekt.generator.chez.ChezScheme→effekt.generator.js.Moduleeffekt.generator.chez.ChezSchemeCallCC→effekt.generator.js.Moduleeffekt.generator.chez.ChezSchemeMonadic→effekt.generator.js.Moduleeffekt.generator.chez.Transformer→effekt.generator.js.Module
- Direction
- generator.chez uses generator.js, so a change to generator.js can break generator.chez, while a change to generator.chez can't break generator.js.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→13 generator.chez uses machine✕
- Connections
- 1 pair of types, where a type in generator.chez uses a type in machine.
- The types involved
effekt.generator.chez.TransformerCPS→effekt.machine.Variable
- Direction
- generator.chez uses machine, so a change to machine can break generator.chez, while a change to generator.chez can't break machine.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→22 generator.chez uses symbols✕
- Connections
- 8 pairs of types, where a type in generator.chez uses a type in symbols.
- The types involved
effekt.generator.chez.ChezScheme→effekt.symbols.Symboleffekt.generator.chez.ChezSchemeCallCC→effekt.symbols.Symboleffekt.generator.chez.ChezSchemeMonadic→effekt.symbols.Symboleffekt.generator.chez.RecordNames→effekt.symbols.Symboleffekt.generator.chez.Transformer→effekt.symbols.Lambdaeffekt.generator.chez.Transformer→effekt.symbols.Symboleffekt.generator.chez.TransformerCPS→effekt.symbols.Symboleffekt.generator.chez.TransformerCPS→effekt.symbols.TermSymbol
- Direction
- generator.chez uses symbols, so a change to symbols can break generator.chez, while a change to generator.chez can't break symbols.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→23 generator.chez uses core.Tree✕
- Connections
- 3 pairs of types, where a type in generator.chez uses a type in core.Tree.
- The types involved
effekt.generator.chez.DeadCodeElimination→effekt.core.Tree.Rewriteeffekt.generator.chez.FreeVariables→effekt.core.Tree.Queryeffekt.generator.chez.LetFusion→effekt.core.Tree.Rewrite
- Direction
- generator.chez uses core.Tree, so a change to core.Tree can break generator.chez, while a change to generator.chez can't break core.Tree.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→26 generator.chez uses core✕
- Connections
- 43 pairs of types, where a type in generator.chez uses a type in core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
effekt.generator.chez.Binding→effekt.core.Expreffekt.generator.chez.Block→effekt.core.Expreffekt.generator.chez.ChezScheme→effekt.core.Blockeffekt.generator.chez.ChezScheme→effekt.core.Expreffekt.generator.chez.ChezScheme→effekt.core.ModuleDecleffekt.generator.chez.ChezSchemeCPS→effekt.core.Expreffekt.generator.chez.ChezSchemeCallCC→effekt.core.Blockeffekt.generator.chez.ChezSchemeCallCC→effekt.core.ModuleDecleffekt.generator.chez.ChezSchemeMonadic→effekt.core.Blockeffekt.generator.chez.ChezSchemeMonadic→effekt.core.ModuleDecleffekt.generator.chez.DeadCodeElimination→effekt.core.Blockeffekt.generator.chez.FreeVariables→effekt.core.Bindingeffekt.generator.chez.FreeVariables→effekt.core.Blockeffekt.generator.chez.FreeVariables→effekt.core.Operationeffekt.generator.chez.Operation→effekt.core.Expreffekt.generator.chez.PrettyPrinter→effekt.core.Bindingeffekt.generator.chez.PrettyPrinter→effekt.core.Blockeffekt.generator.chez.PrettyPrinter→effekt.core.Expreffekt.generator.chez.Transformer→effekt.core.Blockeffekt.generator.chez.Transformer→effekt.core.BlockParameffekt.generator.chez.Transformer→effekt.core.Declarationeffekt.generator.chez.Transformer→effekt.core.Expreffekt.generator.chez.Transformer→effekt.core.Externeffekt.generator.chez.Transformer→effekt.core.Implementationeffekt.generator.chez.Transformer→effekt.core.ModuleDecl
- Direction
- generator.chez uses core, so a change to core can break generator.chez, while a change to generator.chez can't break core.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→29 generator.chez uses context✕
- Connections
- 2 pairs of types, where a type in generator.chez uses a type in context.
- The types involved
effekt.generator.chez.ChezScheme→effekt.context.Contexteffekt.generator.chez.ChezSchemeCPS→effekt.context.Context
- Direction
- generator.chez uses context, so a change to context can break generator.chez, while a change to generator.chez can't break context.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→33 generator.chez uses core.vm.As✕
- Connections
- 7 pairs of types, where a type in generator.chez uses a type in core.vm.As.
- The types involved
effekt.generator.chez.ChezName→effekt.core.vm.As.Stringeffekt.generator.chez.ChezScheme→effekt.core.vm.As.Stringeffekt.generator.chez.ChezSchemeCPS→effekt.core.vm.As.Stringeffekt.generator.chez.ChezSchemeCallCC→effekt.core.vm.As.Stringeffekt.generator.chez.ChezSchemeMonadic→effekt.core.vm.As.Stringeffekt.generator.chez.Transformer→effekt.core.vm.As.Stringeffekt.generator.chez.TransformerCPS→effekt.core.vm.As.Int
- Direction
- generator.chez uses core.vm.As, so a change to core.vm.As can break generator.chez, while a change to generator.chez can't break core.vm.As.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
39→37 generator.chez uses effekt✕
- Connections
- 5 pairs of types, where a type in generator.chez uses a type in effekt.
- The types involved
effekt.generator.chez.ChezScheme→effekt.Compilereffekt.generator.chez.ChezScheme→effekt.Stageeffekt.generator.chez.ChezSchemeCPS→effekt.Compilereffekt.generator.chez.ChezSchemeCPS→effekt.Stageeffekt.generator.chez.Transformer→effekt.Template
- Direction
- generator.chez uses effekt, so a change to effekt can break generator.chez, while a change to generator.chez can't break effekt.
- Position
- Below the diagonal: generator.chez uses a module listed above it, which is the healthy direction.
40→4 source.Tree uses core.Type✕
- Connections
- 2 pairs of types, where a type in source.Tree uses a type in core.Type.
- The types involved
effekt.source.Tree.Query→effekt.core.Type.MatchClauseeffekt.source.Tree.Rewrite→effekt.core.Type.MatchClause
- Direction
- source.Tree uses core.Type, so a change to core.Type can break source.Tree, while a change to source.Tree can't break core.Type.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→9 source.Tree uses cps✕
- Connections
- 2 pairs of types, where a type in source.Tree uses a type in cps.
- The types involved
effekt.source.Tree.Query→effekt.cps.Defeffekt.source.Tree.Rewrite→effekt.cps.Def
- Direction
- source.Tree uses cps, so a change to cps can break source.Tree, while a change to source.Tree can't break cps.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→16 source.Tree uses source✕
- Connections
- 11 pairs of types, where a type in source.Tree uses a type in source.
- The types involved
effekt.source.Tree.Query→effekt.source.Handlereffekt.source.Tree.Query→effekt.source.MatchGuardeffekt.source.Tree.Query→effekt.source.OpClauseeffekt.source.Tree.Query→effekt.source.Termeffekt.source.Tree.Query→effekt.source.ValueArgeffekt.source.Tree.Rewrite→effekt.source.CallTargeteffekt.source.Tree.Rewrite→effekt.source.Handlereffekt.source.Tree.Rewrite→effekt.source.MatchGuardeffekt.source.Tree.Rewrite→effekt.source.OpClauseeffekt.source.Tree.Rewrite→effekt.source.Termeffekt.source.Tree.Rewrite→effekt.source.ValueArg
- Direction
- source.Tree uses source, so a change to source can break source.Tree, while a change to source.Tree can't break source.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→23 source.Tree uses core.Tree✕
- Connections
- 1 pair of types, where a type in source.Tree uses a type in core.Tree.
- The types involved
effekt.source.Tree.Visit→effekt.core.Tree.Query
- Direction
- source.Tree uses core.Tree, so a change to core.Tree can break source.Tree, while a change to source.Tree can't break core.Tree.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→26 source.Tree uses core✕
- Connections
- 8 pairs of types, where a type in source.Tree uses a type in core.
- The types involved
effekt.source.Tree.Query→effekt.core.ExternBodyeffekt.source.Tree.Query→effekt.core.Implementationeffekt.source.Tree.Query→effekt.core.ModuleDecleffekt.source.Tree.Query→effekt.core.Stmteffekt.source.Tree.Rewrite→effekt.core.ExternBodyeffekt.source.Tree.Rewrite→effekt.core.Implementationeffekt.source.Tree.Rewrite→effekt.core.ModuleDecleffekt.source.Tree.Rewrite→effekt.core.Stmt
- Direction
- source.Tree uses core, so a change to core can break source.Tree, while a change to source.Tree can't break core.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→29 source.Tree uses context✕
- Connections
- 2 pairs of types, where a type in source.Tree uses a type in context.
- The types involved
effekt.source.Tree.Query→effekt.context.Contexteffekt.source.Tree.Rewrite→effekt.context.Context
- Direction
- source.Tree uses context, so a change to context can break source.Tree, while a change to source.Tree can't break context.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→30 source.Tree uses util✕
- Connections
- 2 pairs of types, where a type in source.Tree uses a type in util.
- The types involved
effekt.source.Tree.Query→effekt.util.Structuraleffekt.source.Tree.Rewrite→effekt.util.Structural
- Direction
- source.Tree uses util, so a change to util can break source.Tree, while a change to source.Tree can't break util.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
40→37 source.Tree uses effekt✕
- Connections
- 1 pair of types, where a type in source.Tree uses a type in effekt.
- The types involved
effekt.source.Tree.Query→effekt.Template
- Direction
- source.Tree uses effekt, so a change to effekt can break source.Tree, while a change to source.Tree can't break effekt.
- Position
- Below the diagonal: source.Tree uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 45 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Expand the README with getting-started, architecture overview and a project map.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +6.8 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.6 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +4.2 pts | Medium | Documentation (README) |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.2 pts | Medium | Observability |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.9 pts | Medium | Release Hygiene |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.7 pts | Medium | Nullable reference types |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +1.3 pts | Medium | Security & performance tooling |
| Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with Transformer.scala (4), PrettyPrinter.scala (2), Normalizer.scala. | +1.1 pts | High | Churn × Complexity Hotspots |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | 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.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| effekt/jvm/src/main/scala/effekt/Server.scala | 5.7 | Mixed | Cognitive Complexity: Server.inlayHint (cognitive 22) |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| effekt/shared/src/main/scala/effekt/core/Tree.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/Lexer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/core/vm/VM.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/core/optimizer/Normalizer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/machine/Transformer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/Typer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/Namer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/core/PrettyPrinter.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| effekt/shared/src/main/scala/effekt/core/Transformer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 58 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 339 of 355 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 25 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — 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 deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `effekt/jvm/src/main/scala/effekt/Runner.scala`, `effekt/shared/src/main/scala/effekt/Intelligence.scala`, `effekt/shared/src/main/scala/effekt/Parser.scala`, `effekt/shared/src/main/scala/effekt/Precedence.scala`, `effekt/shared/src/main/scala/effekt/core/Mono.scala`, … (+14 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in effekt/shared/src/main/scala/effekt/Namer.scala, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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").
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
35 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TrampolinedRewrite.rewrite at 74. A further 32 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 Parser.opName at 31 — they are counted neither in the figure above nor in this dimension's score. 14 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: effekt/shared/src/main/scala/effekt/generator/llvm/PrettyPrinter.scala (PrettyPrinter.show at 28), effekt/shared/src/main/scala/effekt/cps/Transformer.scala (Transformer.transform at 25), effekt/shared/src/main/scala/effekt/core/Type.scala (Type.typecheck at 24), effekt/shared/src/main/scala/effekt/cps/Contify.scala (Contify.rewrite at 24), effekt/shared/src/main/scala/effekt/core/Show.scala (Show.transform at 23), and 9 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with TrampolinedRewrite.rewrite (cyclomatic 74), Lexer.nextToken (cyclomatic 73). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
38 method(s) exceeded the cognitive complexity threshold of 15; the worst was TrampolinedRewrite.rewrite at 190.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with TrampolinedRewrite.rewrite (cognitive 190), Interpreter.step (cognitive 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
24 god class(es) detected.
What to do
- Resolve the 16 TooManyMethods finding(s) in God Classes — start with Transformer.scala (3), Namer.scala (2), Typer.scala (2). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 8 FileTooLong finding(s) in God Classes — start with Transformer.scala (2), LambdaSets.scala, Parser.scala. — One of this dimension's main actionable groups (8 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
36 duplicated block group(s) detected.
What to do
- Resolve the 13 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Transformer.scala (6), Tree.scala (2), Renamer.scala. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Tree.scala (4), Structural.scala (2), Namer.scala. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Runner.scala, ExplicitCapabilities.scala, Namer.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 production modules (Maven+npm+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
4 of 24 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with Server.scala, LanguageServer.scala, DeclarationContext.scala. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
310 test methods: 310 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 310 test case(s) across 18 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala (8×48=384); effekt/shared/src/main/scala/effekt/core/optimizer/Normalizer.scala (7×54=378); effekt/shared/src/main/scala/effekt/Lexer.scala (3×73=219)
What to do
- Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with Transformer.scala (4), PrettyPrinter.scala (2), Normalizer.scala. — One of this dimension's main actionable groups (11 warning-level).
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is effekt/shared/src/main/scala/effekt/source/GenerateImplicitArgs.scala. Counted over 106 of the 132 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
120 deducted task-comment markers across 32404 LoC (0.3/KLoC) → score 9.3. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 108 TodoComment finding(s) in Explicit Debt — start with Transformer.scala (21), Typer.scala (11), Parser.scala (8). — One of this dimension's main actionable groups (108 warning-level).
- Resolve the 6 HackComment finding(s) in Explicit Debt — start with Typer.scala (3), Parser.scala (2), TestRenamer.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 FixmeComment finding(s) in Explicit Debt — start with ReparseTests.scala (3), Transformer.scala, LSPTests.scala. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
45 finding(s): 0 critical, 45 high, 0 medium, 0 low. 37 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 18 file(s) — `effekt/jvm/src/main/scala/effekt/Runner.scala`, `effekt/shared/src/main/scala/effekt/Intelligence.scala`, `effekt/shared/src/main/scala/effekt/Parser.scala`, `effekt/shared/src/main/scala/effekt/Precedence.scala`, `effekt/shared/src/main/scala/effekt/core/Mono.scala`, … (+13 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) charged to Static Analysis (SAST) — the other 37 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 (41 issue-level, 4 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
2 finding(s): 1 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
3 of 106 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is effekt/shared/src/main/scala/effekt/symbols/SignaturePrinter.scala. Counted over 106 of the 132 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Transformer.scala↔Analysis.scala 78%; ChezScheme.scala↔JavaScript.scala 69%; VirtualModuleDB.scala↔IOModuleDB.scala 64%
What to do
- Resolve the 6 Change coupling finding(s) in Change Coupling — start with AnnotateCaptures.scala (2), Transformer.scala, ChezScheme.scala. — One of this dimension's main actionable groups (6 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — effekt/jvm/src/test/scala/effekt/EffektTests.scala:100
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 96 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `maven`, `gitsubmodule`, 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:5
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Dependabot is configured but does not watch `npm`, `maven`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED 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
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `scala.io.Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(scala.io.Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — effekt/jvm/src/main/scala/effekt/Runner.scala:122
- `new ServerSocket(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and it is held in `serverSocket`, and every later use of `serverSocket` in its block reads a member through it — it is never returned, passed, stored, captured by a lambda, reassigned or released, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(new ServerSocket(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — effekt/jvm/src/main/scala/effekt/Server.scala:636
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
- `withENLocale` changes state that belongs to the whole JVM and changes it back at the end of the same body — the JVM's default `Locale` (changed at line 73, put back at line 75) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: the JVM then keeps the overwritten value for the rest of its life, and every later property lookup, `f"…"` interpolation, date conversion or console write in ANY class reads it. That failure is silent and remote from its cause — the method that breaks is not the method that moved the value. The window is not private while it is open either: system properties, the default `Locale` and `TimeZone` and the standard streams are per-JVM, not per-thread, so a concurrent thread — a `Future`, an actor, a parallel collection — reads the moved value too. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — an explicit `Locale` (`"%.3f".formatLocal(Locale.US, x)`, `String.format(Locale.ROOT, …)`), a `ZoneId` to `java.time`, the setting to the component that reads the property, `Console.withOut(stream) { … }` for captured output, `sys.process.Process(cmd, cwd, env*)` for a child. Where the global genuinely must move, wrap it `try … finally` so the restore runs on every path. — effekt/shared/src/main/scala/effekt/util/Timer.scala:71
What to do
- Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a working directory or an environment variable passed to the operation that needs it (the `cwd` and `env` options of `child_process`, or of `Deno.Command`) is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move, a `try`/`finally` is the least that makes the restore unconditional. In Scala the same holds for a system property (`System.setProperty` or `sys.props`), the default `Locale` or `TimeZone` and `System.out`: pass the value to the operation (`formatLocal(Locale.US, …)`, `Console.withOut`) rather than moving the global.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — effekt/shared/src/main/scala/effekt/Intelligence.scala:219, effekt/shared/src/main/scala/effekt/Intelligence.scala:241
- `case e: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — effekt/shared/src/main/scala/effekt/Intelligence.scala:247
- `case _` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — effekt/jvm/src/main/scala/effekt/Runner.scala:129
- `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — effekt/jvm/src/main/scala/effekt/Runner.scala:311
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 127 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 59% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 48% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 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 — 59 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~8680 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 4 declared JVM dependency coordinate(s) were read from its 1 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 3 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/org/eclipse/lsp4j/org.eclipse.lsp4j/0.12.0/org.eclipse.lsp4j-0.12.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 1 folder(s) declared by REDACTED were not judged for an overview, an example or the map.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .scala source were not judged.
- 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 (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 19 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 195 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Scala code has 38,539 production line(s), 3 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 127 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 47 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
Serious — 287 finding(s)
- TodoComment effekt/shared/src/main/scala/effekt/Compiler.scala:308
- TodoComment effekt/shared/src/main/scala/effekt/Intelligence.scala:246
- TodoComment effekt/shared/src/main/scala/effekt/Lexer.scala:708
- TodoComment effekt/shared/src/main/scala/effekt/Namer.scala:156
- TodoComment effekt/shared/src/main/scala/effekt/Namer.scala:624
- TodoComment effekt/shared/src/main/scala/effekt/Namer.scala:813
- TodoComment effekt/shared/src/main/scala/effekt/Namer.scala:927
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:312
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:548
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:783
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:1013
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:1318
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:1518
- TodoComment effekt/shared/src/main/scala/effekt/Parser.scala:1647
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:439
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:584
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:865
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:891
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1014
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1207
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1240
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1533
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1704
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1710
- TodoComment effekt/shared/src/main/scala/effekt/Typer.scala:1866
- TooManyMethods: Parser effekt/shared/src/main/scala/effekt/Parser.scala:64
- TooManyMethods: Specializer effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:746
- TooManyMethods: Transformer effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:16
- TooManyMethods: PrettyPrinter effekt/shared/src/main/scala/effekt/core/PrettyPrinter.scala:13
- TooManyMethods: Transformer effekt/shared/src/main/scala/effekt/machine/Transformer.scala:20
- TooManyMethods: specialize effekt/shared/src/main/scala/effekt/core/Mono.scala:943
- TooManyMethods: Type effekt/shared/src/main/scala/effekt/core/Type.scala:73
- TooManyMethods: Namer effekt/shared/src/main/scala/effekt/Namer.scala:36
- TooManyMethods: TransformerCps effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:15
- TooManyMethods: Server effekt/jvm/src/main/scala/effekt/Server.scala:43
- TooManyMethods: Typer effekt/shared/src/main/scala/effekt/Typer.scala:52
- TooManyMethods: NamerOps effekt/shared/src/main/scala/effekt/Namer.scala:993
- TooManyMethods: Transformer effekt/shared/src/main/scala/effekt/core/Transformer.scala:15
- TooManyMethods: TyperOps effekt/shared/src/main/scala/effekt/Typer.scala:1763
- TooManyMethods: Unification effekt/shared/src/main/scala/effekt/typer/Unification.scala:42
- TooManyMethods: Raise effekt/shared/src/main/scala/effekt/core/ArityRaising.scala:89
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/core/Renamer.scala:91
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala:535
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/core/Type.scala:361
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:137
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:299
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:665
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/typer/Wellformedness.scala:185
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/util/DocumentationGenerator.scala:164
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/core/Transformer.scala:51
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala:597
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/cps/Transformer.scala:45
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:781
- Duplicated block (5 lines × 2) effekt/shared/src/main/scala/effekt/machine/Transformer.scala:77
- Hotspot: effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:116
- Hotspot: effekt/shared/src/main/scala/effekt/core/optimizer/Normalizer.scala effekt/shared/src/main/scala/effekt/core/optimizer/Normalizer.scala:250
- Hotspot: effekt/shared/src/main/scala/effekt/Lexer.scala effekt/shared/src/main/scala/effekt/Lexer.scala:402
- Hotspot: effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:238
- Hotspot: effekt/shared/src/main/scala/effekt/machine/Transformer.scala effekt/shared/src/main/scala/effekt/machine/Transformer.scala:144
- Hotspot: effekt/shared/src/main/scala/effekt/core/Tree.scala effekt/shared/src/main/scala/effekt/core/Tree.scala:1075
- Hotspot: effekt/shared/src/main/scala/effekt/generator/llvm/PrettyPrinter.scala effekt/shared/src/main/scala/effekt/generator/llvm/PrettyPrinter.scala:65
- Hotspot: effekt/shared/src/main/scala/effekt/Parser.scala effekt/shared/src/main/scala/effekt/Parser.scala:1347
- Hotspot: effekt/shared/src/main/scala/effekt/machine/PrettyPrinter.scala effekt/shared/src/main/scala/effekt/machine/PrettyPrinter.scala:55
- Hotspot: effekt/shared/src/main/scala/effekt/generator/chez/Transformer.scala effekt/shared/src/main/scala/effekt/generator/chez/Transformer.scala:80
- Hotspot: effekt/shared/src/main/scala/effekt/core/Transformer.scala effekt/shared/src/main/scala/effekt/core/Transformer.scala:145
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/Namer.scala:346
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala:490
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala:1502
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/source/GenerateImplicitArgs.scala:170
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/util/AnsiHighlight.scala:60
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/util/DocumentationGenerator.scala:176
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/util/Structural.scala:223
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/util/Structural.scala:252
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/generator/js/Transformer.scala:138
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala:540
- Duplicated block (6 lines × 2) effekt/shared/src/main/scala/effekt/core/Tree.scala:574
- FileTooLong: core/LambdaSets.scala effekt/shared/src/main/scala/effekt/core/LambdaSets.scala
- FileTooLong: effekt/Parser.scala effekt/shared/src/main/scala/effekt/Parser.scala
- FileTooLong: core/Mono.scala effekt/shared/src/main/scala/effekt/core/Mono.scala
- FileTooLong: effekt/Typer.scala effekt/shared/src/main/scala/effekt/Typer.scala
- FileTooLong: core/Tree.scala effekt/shared/src/main/scala/effekt/core/Tree.scala
- FileTooLong: effekt/Namer.scala effekt/shared/src/main/scala/effekt/Namer.scala
- FileTooLong: llvm/Transformer.scala effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala
- FileTooLong: core/Transformer.scala effekt/shared/src/main/scala/effekt/core/Transformer.scala
- HackComment effekt/shared/src/main/scala/effekt/Parser.scala:127
- HackComment effekt/shared/src/main/scala/effekt/Parser.scala:1389
- HackComment effekt/shared/src/main/scala/effekt/Typer.scala:1377
- HackComment effekt/shared/src/main/scala/effekt/Typer.scala:1388
- HackComment effekt/shared/src/main/scala/effekt/Typer.scala:1401
- HackComment effekt/shared/src/main/scala/effekt/core/TestRenamer.scala:46
- FixmeComment effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:44
- FixmeComment effekt/jvm/src/test/scala/effekt/LSPTests.scala:784
- FixmeComment effekt/jvm/src/test/scala/effekt/core/CoreTests.scala:159
- FixmeComment effekt/jvm/src/test/scala/effekt/core/ReparseTests.scala:39
- FixmeComment effekt/jvm/src/test/scala/effekt/core/ReparseTests.scala:41
- FixmeComment effekt/jvm/src/test/scala/effekt/core/ReparseTests.scala:45
- Change coupling: Transformer.scala ↔ Analysis.scala effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:1
- Change coupling: ChezScheme.scala ↔ JavaScript.scala effekt/shared/src/main/scala/effekt/generator/chez/ChezScheme.scala:1
- Change coupling: VirtualModuleDB.scala ↔ IOModuleDB.scala effekt/js/src/main/scala/effekt/context/VirtualModuleDB.scala:1
- Change coupling: Analysis.scala ↔ PrettyPrinter.scala effekt/shared/src/main/scala/effekt/machine/Analysis.scala:1
- Change coupling: AnnotateCaptures.scala ↔ UnboxInference.scala effekt/shared/src/main/scala/effekt/source/AnnotateCaptures.scala:1
- Change coupling: AnnotateCaptures.scala ↔ ExplicitCapabilities.scala effekt/shared/src/main/scala/effekt/source/AnnotateCaptures.scala:1
- Swallowed exception (caught, then discarded) effekt/shared/src/main/scala/effekt/Intelligence.scala:219
- Swallowed exception (caught, then discarded) effekt/shared/src/main/scala/effekt/Intelligence.scala:241
- Swallowed exception (caught, then discarded) effekt/shared/src/main/scala/effekt/Intelligence.scala:247
- Swallowed exception (caught, then discarded) effekt/jvm/src/main/scala/effekt/Runner.scala:129
- Swallowed exception (caught, then discarded) effekt/jvm/src/main/scala/effekt/Runner.scala:311
- Low cohesion: Server (LCOM4 6) effekt/jvm/src/main/scala/effekt/Server.scala:43
- Low cohesion: LanguageServer (LCOM4 5) effekt/js/src/main/scala/effekt/LanguageServer.scala:60
- Low cohesion: DeclarationContext (LCOM4 5) effekt/shared/src/main/scala/effekt/core/DeclarationContext.scala:12
- Low cohesion: Context (LCOM4 4) effekt/shared/src/main/scala/effekt/context/Context.scala:41
- Duplicated block (7 lines × 2) effekt/jvm/src/main/scala/effekt/Runner.scala:323
- Duplicated block (7 lines × 2) effekt/shared/src/main/scala/effekt/source/ExplicitCapabilities.scala:76
- Duplicated block (7 lines × 2) effekt/shared/src/main/scala/effekt/Namer.scala:820
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:487
- Duplicated block (8 lines × 2) effekt/shared/src/main/scala/effekt/util/DocumentationGenerator.scala:110
- Disposable created and abandoned in the function that made it effekt/jvm/src/main/scala/effekt/Runner.scala:122
- Disposable created and abandoned in the function that made it effekt/jvm/src/main/scala/effekt/Server.scala:636
- TrampolinedRewrite.rewrite (cyclomatic 74) effekt/shared/src/main/scala/effekt/core/Tree.scala:669
- Lexer.nextToken (cyclomatic 73) effekt/shared/src/main/scala/effekt/Lexer.scala:402
- Interpreter.step (cyclomatic 60) effekt/shared/src/main/scala/effekt/core/vm/VM.scala:239
- Normalizer.normalize (cyclomatic 54) effekt/shared/src/main/scala/effekt/core/optimizer/Normalizer.scala:250
- Transformer.transform (cyclomatic 53) effekt/shared/src/main/scala/effekt/machine/Transformer.scala:144
- Transformer.transform (cyclomatic 48) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:116
- TransformerCps.toJS (cyclomatic 40) effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:238
- Typer.checkExpr (cyclomatic 39) effekt/shared/src/main/scala/effekt/Typer.scala:133
- TransformerCps.canBeDirect (cyclomatic 39) effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:602
- Namer.resolve (cyclomatic 33) effekt/shared/src/main/scala/effekt/Namer.scala:478
- BindSubexpressions.transform (cyclomatic 31) effekt/shared/src/main/scala/effekt/core/optimizer/BindSubexpressions.scala:38
- Raise.stmt (cyclomatic 30) effekt/shared/src/main/scala/effekt/core/ArityRaising.scala:314
- specialize.monomorphize (cyclomatic 29) effekt/shared/src/main/scala/effekt/core/Mono.scala:1147
- PrettyPrinter.toDocStmts (cyclomatic 29) effekt/shared/src/main/scala/effekt/core/PrettyPrinter.scala:229
- Transformer.preprocess (cyclomatic 28) effekt/shared/src/main/scala/effekt/core/Transformer.scala:638
- PatternMatchingCompiler.compile (cyclomatic 27) effekt/shared/src/main/scala/effekt/core/PatternMatchingCompiler.scala:86
- UnboxInference.rewriteAsExpr (cyclomatic 27) effekt/shared/src/main/scala/effekt/typer/UnboxInference.scala:48
- Namer.resolve (cyclomatic 24) effekt/shared/src/main/scala/effekt/Namer.scala:303
- LambdaSets.solve (cyclomatic 24) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:250
- Collector.statement (cyclomatic 24) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:1997
- ExhaustivityChecker.checkScrutinee (cyclomatic 23) effekt/shared/src/main/scala/effekt/typer/ExhaustivityChecker.scala:225
- Lexer.stringLike (cyclomatic 22) effekt/shared/src/main/scala/effekt/Lexer.scala:611
- SignaturePrinter.toDoc (cyclomatic 22) effekt/shared/src/main/scala/effekt/symbols/SignaturePrinter.scala:17
- ColoredMessaging.formatContent (cyclomatic 22) effekt/shared/src/main/scala/effekt/util/ColoredMessaging.scala:57
- Intelligence.allBindings (cyclomatic 21) effekt/shared/src/main/scala/effekt/Intelligence.scala:189
- Typer.synthDef (cyclomatic 21) effekt/shared/src/main/scala/effekt/Typer.scala:828
- Typer.assertArgsParamsAlign (cyclomatic 21) effekt/shared/src/main/scala/effekt/Typer.scala:1360
- Parser.primExpr (cyclomatic 20) effekt/shared/src/main/scala/effekt/Parser.scala:1347
- Transformer.transformAsStmt (cyclomatic 20) effekt/shared/src/main/scala/effekt/core/Transformer.scala:312
- Default.deadBranches (cyclomatic 20) effekt/shared/src/main/scala/effekt/core/optimizer/InliningPolicy.scala:114
- ErrorContext.explainMismatch (cyclomatic 20) effekt/shared/src/main/scala/effekt/typer/ErrorContext.scala:56
- ResolveExternDefs.rewrite (cyclomatic 18) effekt/shared/src/main/scala/effekt/source/ResolveExternDefs.scala:41
- bodyRewriter.rewrite (cyclomatic 17) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:1567
- Namer.resolveValueType (cyclomatic 16) effekt/shared/src/main/scala/effekt/Namer.scala:786
- LambdaSets.assertMonomorphic (cyclomatic 16) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:200
- TrampolinedRewrite.rewrite (cognitive 190) effekt/shared/src/main/scala/effekt/core/Tree.scala:669
- Interpreter.step (cognitive 80) effekt/shared/src/main/scala/effekt/core/vm/VM.scala:239
- Normalizer.normalize (cognitive 56) effekt/shared/src/main/scala/effekt/core/optimizer/Normalizer.scala:250
- Typer.checkExpr (cognitive 53) effekt/shared/src/main/scala/effekt/Typer.scala:133
- Transformer.transform (cognitive 40) effekt/shared/src/main/scala/effekt/machine/Transformer.scala:144
- TransformerCps.toJS (cognitive 35) effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:238
- Typer.checkImplementation (cognitive 33) effekt/shared/src/main/scala/effekt/Typer.scala:411
- Typer.assertArgsParamsAlign (cognitive 32) effekt/shared/src/main/scala/effekt/Typer.scala:1360
- PatternMatchingCompiler.compile (cognitive 32) effekt/shared/src/main/scala/effekt/core/PatternMatchingCompiler.scala:86
- Namer.resolve (cognitive 30) effekt/shared/src/main/scala/effekt/Namer.scala:478
- TrampolinedRewrite.rewrite (cognitive 29) effekt/shared/src/main/scala/effekt/core/Tree.scala:649
- LambdaSets.solve (cognitive 28) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:250
- bodyRewriter.rewrite (cognitive 28) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:1567
- BindSubexpressions.transform (cognitive 28) effekt/shared/src/main/scala/effekt/core/optimizer/BindSubexpressions.scala:38
- Transformer.transform (cognitive 27) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:116
- Typer.synthDef (cognitive 25) effekt/shared/src/main/scala/effekt/Typer.scala:828
- TypePrinter.toDoc (cognitive 25) effekt/shared/src/main/scala/effekt/symbols/TypePrinter.scala:64
- Namer.resolveValueType (cognitive 24) effekt/shared/src/main/scala/effekt/Namer.scala:786
- ExhaustivityChecker.checkScrutinee (cognitive 23) effekt/shared/src/main/scala/effekt/typer/ExhaustivityChecker.scala:225
- Server.inlayHint (cognitive 22) effekt/jvm/src/main/scala/effekt/Server.scala:397
- Intelligence.allBindings (cognitive 21) effekt/shared/src/main/scala/effekt/Intelligence.scala:189
- Specializer.result (cognitive 21) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:1791
- Deadcode.rewrite (cognitive 21) effekt/shared/src/main/scala/effekt/core/optimizer/Deadcode.scala:22
- Default.deadBranches (cognitive 21) effekt/shared/src/main/scala/effekt/core/optimizer/InliningPolicy.scala:114
- Server.closeHoleAction (cognitive 19) effekt/jvm/src/main/scala/effekt/Server.scala:513
- Intelligence.getInferredCaptures (cognitive 19) effekt/shared/src/main/scala/effekt/Intelligence.scala:315
- Specializer.adapter (cognitive 19) effekt/shared/src/main/scala/effekt/core/LambdaSets.scala:1432
- PrettyPrinter.toDocStmts (cognitive 19) effekt/shared/src/main/scala/effekt/core/PrettyPrinter.scala:229
- Transformer.transform (cognitive 19) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:41
- ResolveExternDefs.rewrite (cognitive 19) effekt/shared/src/main/scala/effekt/source/ResolveExternDefs.scala:41
- effekt_builtins.$effekt.compare (cognitive 19) libraries/js/effekt_builtins.js:36
- Lexer.stringLike (cognitive 18) effekt/shared/src/main/scala/effekt/Lexer.scala:611
- Typer.checkExprAsBlock (cognitive 18) effekt/shared/src/main/scala/effekt/Typer.scala:574
- Transformer.preprocess (cognitive 18) effekt/shared/src/main/scala/effekt/core/Transformer.scala:638
- Raise.stmt (cognitive 17) effekt/shared/src/main/scala/effekt/core/ArityRaising.scala:314
- Server.documentSymbol (cognitive 16) effekt/jvm/src/main/scala/effekt/Server.scala:300
- TransformerCps.canBeDirect (cognitive 16) effekt/shared/src/main/scala/effekt/generator/js/TransformerCps.scala:602
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (40 lines × 2) effekt/shared/src/main/scala/effekt/core/Renamer.scala:48
- Duplicated block (27 lines × 2) effekt/shared/src/main/scala/effekt/util/AnsiHighlight.scala:80
- Duplicated block (21 lines × 2) effekt/shared/src/main/scala/effekt/symbols/DeclPrinter.scala:56
- Duplicated block (12–13 lines × 2) effekt/shared/src/main/scala/effekt/Typer.scala:481
- Duplicated block (3–12 lines × 3) effekt/shared/src/main/scala/effekt/core/Tree.scala:136
- Duplicated block (9 lines × 3) effekt/shared/src/main/scala/effekt/generator/llvm/Transformer.scala:575
- Duplicated block (5 lines × 3) effekt/shared/src/main/scala/effekt/core/TestRenamer.scala:240
- No structured logging
- Process-global state is restored only on the happy path effekt/shared/src/main/scala/effekt/util/Timer.scala:71
Minor — 21 finding(s)
- Orphaned file effekt/shared/src/main/scala/effekt/symbols/SignaturePrinter.scala:1
- Orphaned file effekt/shared/src/main/scala/effekt/util/HtmlHighlight.scala:1
- Orphaned file effekt/jvm/src/main/scala/effekt/GsonUtil.scala:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Disabled test effekt/jvm/src/test/scala/effekt/EffektTests.scala:100
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Dependabot does not watch npm/maven/gitsubmodule REDACTED:5
- No changelog
- Scala's null is not held to the type system everywhere
- Silent fallback default on parse failure effekt/shared/src/main/scala/effekt/Lexer.scala:706
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-cdb2394e4cca49958c98297a6f2d47ac/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-cdb2394e4cca49958c98297a6f2d47ac/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 . | 45 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 2 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 19 file(s) — `effekt/jvm/src/main/scala/effekt/Runner.scala`, `effekt/shared/src/main/scala/effekt/Intelligence.scala`, `effekt/shared/src/main/scala/effekt/Parser.scala`, `effekt/shared/src/main/scala/effekt/Precedence.scala`, `effekt/shared/src/main/scala/effekt/core/Mono.scala`, … (+14 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |