Executive summary
epfl-lara/stainless falls short of our standard for a preview release, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 51 out of 100 and is rated Adequate, and 22 of its 28 critical findings are security problems in the build pipeline and in its servers and containers.
Accessibility, at 47, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is recording design decisions, worth about 2 points. Fixing focus, motion and contrast would lift Accessibility itself, worth about 3 points.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six pipeline steps run downloads nobody checks, and six parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, checking each download against a checksum and having someone learn the forgotten files would close these risks. The three unsafe settings in infrastructure or container files need changing to safe values.
The product code is 98,107 lines, about €98,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 29 findings
- Cyclomatic Complexity · S2IRImpl.rec (cyclomatic 97) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala
- Cyclomatic Complexity · CPrinter.pp (cyclomatic 34) core/src/main/scala/stainless/genc/CPrinter.scala
- Cyclomatic Complexity · IR2CImpl.checkGlobalInit (cyclomatic 19) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala
- Cyclomatic Complexity · CustomPrinter.ppBody (cyclomatic 17) core/src/main/scala/stainless/testgen/ScalaTestGen.scala
- Cyclomatic Complexity · S2IRImpl.rec (cyclomatic 16) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala
- Cognitive Complexity · IR2CImpl.checkGlobalInit (cognitive 17) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala
- Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) core/src/main/scala/stainless/ast/Deconstructors.scala
- Churn × Complexity Hotspots · Hotspot: core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala
- Churn × Complexity Hotspots · Hotspot: core/src/main/scala/stainless/genc/phases/IR2CPhase.scala core/src/main/scala/stainless/genc/phases/IR2CPhase.scala
- Churn × Complexity Hotspots · Hotspot: core/src/main/scala/stainless/genc/CPrinter.scala core/src/main/scala/stainless/genc/CPrinter.scala
- Churn × Complexity Hotspots · Hotspot: core/src/main/scala/stainless/verification/AssertionInjector.scala core/src/main/scala/stainless/verification/AssertionInjector.scala
- Static Analysis (SAST) · REDACTED
- Knowledge Freshness · Orphaned knowledge core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala
- Knowledge Freshness · Orphaned knowledge core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala
- Knowledge Freshness · Orphaned knowledge frontends/library/stainless/math/package.scala
- Knowledge Freshness · Orphaned knowledge core/src/main/scala/stainless/extraction/innerclasses/InnerClasses.scala
- Knowledge Freshness · Orphaned knowledge core/src/main/scala/stainless/extraction/imperative/ReturnElimination.scala
- Knowledge Freshness · Orphaned knowledge core/src/main/scala/stainless/equivchk/EquivalenceCheckingComponent.scala
- Visual & motion safety · Low contrast colour pair in CSS (2.4:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (2.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
- Visual & motion safety · Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css
Fixed since the last survey: 33 findings
- God Classes · FileTooLong: math/BitVectors.scala frontends/library/stainless/math/BitVectors.scala
- Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) core/src/main/scala/stainless/ast/Deconstructors.scala
- Code Duplication · Duplicated block (9 lines × 2) core/src/main/scala/stainless/extraction/imperative/GhostChecker.scala
- Code Duplication · Duplicated block (5–6 lines × 2) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala
- Explicit Debt · TodoComment frontends/library/stainless/math/BitVectors.scala
- Static Analysis (SAST) · High: REDACTED .github/workflows/stainless-CI-jdk25.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/stainless-CI-jdk25.yml
- Static Analysis (SAST) · High: watchdog-unverified-download-in-run .github/workflows/stainless-CI-jdk25.yml
- Static Analysis (SAST) · High: watchdog-unverified-download-in-run REDACTED
- Static Analysis (SAST) · High: REDACTED .github/workflows/stainless-explicit-fastmachines.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/stainless-explicit-fastmachines.yml
- Static Analysis (SAST) · High: watchdog-unverified-download-in-run .github/workflows/stainless-explicit-fastmachines.yml
- Static Analysis (SAST) · High: watchdog-unverified-shell-installer-download REDACTED
- IaC & Container Security · High IaC: WD-DOCKER-0013 REDACTED
- Supply-chain Provenance & Signing · REDACTED .github/workflows/stainless-CI-jdk25.yml
- Supply-chain Provenance & Signing · REDACTED .github/workflows/stainless-explicit-fastmachines.yml
- Incompleteness & stubs · Skeleton type — most members are unfinished frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Skeleton type — most members are unfinished frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
- Incompleteness & stubs · Unfinished stub — body is ??? / NotImplementedError frontends/library/stainless/math/BitVectors.scala
Rebuild cost: about €98,000 · Estimate
| Cost to rebuild | €33,000 to €160,000, for 543 to 1,721 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| 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 51. 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: 98,107 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: which parts of the code depend on which
| uses → | 1 algebra.ops | 2 extraction.imperative.EffectElaboration | 3 extraction.oo.Trees | 4 lang | 5 genc.ir.IR | 6 genc.CAST | 7 ast.Definitions | 8 extraction.imperative.RefTransform.RefTransformContext.funRefTransformer | 9 extraction.innerclasses.Definitions | 10 genc | 11 extraction.innerfuns.Definitions | 12 genc.ir | 13 extraction.imperative.EffectsAnalyzer | 14 extraction.imperative | 15 extraction.innerclasses | 16 extraction.oo.TypeEncoding | 17 extraction | 18 transformers | 19 extraction.oo | 20 extraction.imperative.trees | 21 extraction.oo.Definitions | 22 genc.phases.IR2CImpl | 23 codegen.runtime | 24 ast.Expressions | 25 ast.ExprOps | 26 transformers.lattices.Core | 27 ast | 28 transformers.lattices | 29 utils | 30 frontend | 31 stainless | 32 extraction.innerfuns | 33 extraction.methods | 34 extraction.xlang | 35 genc.phases | 36 termination | 37 verification | 38 codegen | 39 equivchk | 40 frontends.dotc |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 algebra.ops | ||||||||||||||||||||||||||||||||||||||||
| 2 extraction.imperative.EffectElaboration | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 extraction.oo.Trees | 4 | 17 | 2 | 7 | 5 | 2 | ||||||||||||||||||||||||||||||||||
| 4 lang | 2 | 6 | ||||||||||||||||||||||||||||||||||||||
| 5 genc.ir.IR | 2 | 1 | 55 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 6 genc.CAST | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 7 ast.Definitions | 3 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 8 extraction.imperative.RefTransform.RefTransformContext.funRefTransformer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 extraction.innerclasses.Definitions | 3 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 10 genc | 1 | 1 | 10 | 5 | 2 | 3 | 3 | 1 | 10 | |||||||||||||||||||||||||||||||
| 11 extraction.innerfuns.Definitions | 6 | 9 | 1 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 12 genc.ir | 1 | 1 | 21 | 26 | 6 | 5 | 2 | 6 | ||||||||||||||||||||||||||||||||
| 13 extraction.imperative.EffectsAnalyzer | 10 | 11 | 2 | 2 | 3 | 7 | ||||||||||||||||||||||||||||||||||
| 14 extraction.imperative | 3 | 1 | 13 | 17 | 1 | 1 | 6 | 23 | 11 | 9 | 7 | 4 | 1 | 27 | 4 | |||||||||||||||||||||||||
| 15 extraction.innerclasses | 1 | 5 | 7 | 2 | 11 | 1 | 1 | 5 | 4 | 2 | 3 | 3 | 22 | 1 | ||||||||||||||||||||||||||
| 16 extraction.oo.TypeEncoding | 1 | 3 | 4 | 2 | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||
| 17 extraction | 5 | 7 | 3 | 1 | 7 | 1 | 1 | 10 | 11 | |||||||||||||||||||||||||||||||
| 18 transformers | 2 | 7 | 9 | 5 | 1 | 8 | 3 | 8 | 6 | 1 | ||||||||||||||||||||||||||||||
| 19 extraction.oo | 1 | 7 | 1 | 1 | 6 | 14 | 1 | 1 | 1 | 8 | 1 | 27 | 1 | 12 | 24 | 5 | 4 | 29 | 3 | |||||||||||||||||||||
| 20 extraction.imperative.trees | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 extraction.oo.Definitions | 3 | 1 | 2 | 8 | 1 | 5 | 2 | 4 | ||||||||||||||||||||||||||||||||
| 22 genc.phases.IR2CImpl | 1 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 codegen.runtime | 3 | 10 | ||||||||||||||||||||||||||||||||||||||
| 24 ast.Expressions | 8 | 40 | 19 | 4 | ||||||||||||||||||||||||||||||||||||
| 25 ast.ExprOps | 1 | 6 | 6 | 6 | 10 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 26 transformers.lattices.Core | 3 | 1 | 4 | 10 | 13 | 1 | ||||||||||||||||||||||||||||||||||
| 27 ast | 1 | 1 | 3 | 14 | 2 | 1 | 3 | 4 | 10 | 2 | ||||||||||||||||||||||||||||||
| 28 transformers.lattices | 2 | 3 | 4 | 1 | 3 | 1 | 17 | 2 | ||||||||||||||||||||||||||||||||
| 29 utils | 2 | 6 | 3 | 1 | 1 | 1 | 6 | 4 | 1 | 6 | 8 | 4 | ||||||||||||||||||||||||||||
| 30 frontend | 1 | 6 | 3 | 1 | 2 | 5 | 12 | 7 | 2 | 11 | ||||||||||||||||||||||||||||||
| 31 stainless | 1 | 1 | 1 | 1 | 3 | 4 | 7 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||
| 32 extraction.innerfuns | 3 | 6 | 1 | 1 | 2 | 2 | 4 | 2 | 2 | 19 | 1 | |||||||||||||||||||||||||||||
| 33 extraction.methods | 7 | 11 | 5 | 1 | 1 | 28 | 12 | 10 | 12 | 2 | 1 | 28 | 8 | |||||||||||||||||||||||||||
| 34 extraction.xlang | 2 | 2 | 1 | 1 | 9 | 6 | 4 | 3 | 1 | 12 | 3 | |||||||||||||||||||||||||||||
| 35 genc.phases | 1 | 1 | 1 | 8 | 26 | 2 | 11 | 3 | 1 | 2 | 3 | 2 | 8 | 5 | 4 | 1 | 1 | 15 | ||||||||||||||||||||||
| 36 termination | 2 | 1 | 9 | 13 | 13 | 1 | 6 | 1 | 5 | 1 | 9 | 2 | 8 | |||||||||||||||||||||||||||
| 37 verification | 1 | 5 | 10 | 1 | 6 | 1 | 4 | 7 | 2 | 3 | 15 | |||||||||||||||||||||||||||||
| 38 codegen | 2 | 3 | 4 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 equivchk | 3 | 1 | 3 | 3 | 7 | 2 | 1 | 8 | 4 | |||||||||||||||||||||||||||||||
| 40 frontends.dotc | 6 | 3 | 8 | 3 | 3 | 1 | 6 | 3 | 1 |
2→20 extraction.imperative.EffectElaboration uses extraction.imperative.trees part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.imperative.EffectElaboration uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.imperative.EffectElaboration.TransformerContext→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.imperative.EffectElaboration uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.imperative.EffectElaboration, while a change to extraction.imperative.EffectElaboration can't break extraction.imperative.trees.
- 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→5 extraction.oo.Trees uses genc.ir.IR part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.oo.Trees uses a type in genc.ir.IR.
- The types involved
stainless.extraction.oo.Trees.ClassPattern→stainless.genc.ir.IR.ValDefstainless.extraction.oo.Trees.ClassSelector→stainless.genc.ir.IR.ValDefstainless.extraction.oo.Trees.ClassType→stainless.genc.ir.IR.ValDefstainless.extraction.oo.Trees.InstanceOfPattern→stainless.genc.ir.IR.ValDef
- Direction
- extraction.oo.Trees uses genc.ir.IR, so a change to genc.ir.IR can break extraction.oo.Trees, while a change to extraction.oo.Trees can't break genc.ir.IR.
- 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→6 extraction.oo.Trees uses genc.CAST part of a loop✕
- Connections
- 17 pairs of types, where a type in extraction.oo.Trees uses a type in genc.CAST.
- The types involved
stainless.extraction.oo.Trees.AnyType→stainless.genc.CAST.Typestainless.extraction.oo.Trees.AsInstanceOf→stainless.genc.CAST.Exprstainless.extraction.oo.Trees.AsInstanceOf→stainless.genc.CAST.Typestainless.extraction.oo.Trees.ClassConstructor→stainless.genc.CAST.Exprstainless.extraction.oo.Trees.ClassConstructor→stainless.genc.CAST.Typestainless.extraction.oo.Trees.ClassSelector→stainless.genc.CAST.Exprstainless.extraction.oo.Trees.ClassSelector→stainless.genc.CAST.Typestainless.extraction.oo.Trees.ClassType→stainless.genc.CAST.Typestainless.extraction.oo.Trees.InstanceOfPattern→stainless.genc.CAST.Typestainless.extraction.oo.Trees.IsInstanceOf→stainless.genc.CAST.Exprstainless.extraction.oo.Trees.IsInstanceOf→stainless.genc.CAST.Typestainless.extraction.oo.Trees.NothingType→stainless.genc.CAST.Typestainless.extraction.oo.Trees.TypeApply→stainless.genc.CAST.Typestainless.extraction.oo.Trees.TypeBounds→stainless.genc.CAST.Typestainless.extraction.oo.Trees.TypeSelect→stainless.genc.CAST.Exprstainless.extraction.oo.Trees.TypeSelect→stainless.genc.CAST.Typestainless.extraction.oo.Trees.UnknownType→stainless.genc.CAST.Type
- Direction
- extraction.oo.Trees uses genc.CAST, so a change to genc.CAST can break extraction.oo.Trees, while a change to extraction.oo.Trees can't break genc.CAST.
- 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→15 extraction.oo.Trees uses extraction.innerclasses part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.oo.Trees uses a type in extraction.innerclasses.
- The types involved
stainless.extraction.oo.Trees.OOSelfTreeTransformer→stainless.extraction.innerclasses.TreeTransformerstainless.extraction.oo.Trees.OOSelfTreeTraverser→stainless.extraction.innerclasses.TreeTraverser
- Direction
- extraction.oo.Trees uses extraction.innerclasses, so a change to extraction.innerclasses can break extraction.oo.Trees, while a change to extraction.oo.Trees can't break extraction.innerclasses.
- 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→20 extraction.oo.Trees uses extraction.imperative.trees part of a loop✕
- Connections
- 7 pairs of types, where a type in extraction.oo.Trees uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.oo.Trees.AsInstanceOf→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees.ClassConstructor→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees.ClassSelector→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees.ClassType→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees.IsInstanceOf→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees.TypeApply→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees.TypeSelect→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.oo.Trees uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.oo.Trees, while a change to extraction.oo.Trees can't break extraction.imperative.trees.
- 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→21 extraction.oo.Trees uses extraction.oo.Definitions part of a loop✕
- Connections
- 5 pairs of types, where a type in extraction.oo.Trees uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.oo.Trees.ClassType→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.Trees.ClassType→stainless.extraction.oo.Definitions.TypedClassDefstainless.extraction.oo.Trees.TypeApply→stainless.extraction.oo.Definitions.AppliedTypeDefstainless.extraction.oo.Trees.TypeApply→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.Trees.TypeSelect→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.oo.Trees uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.oo.Trees, while a change to extraction.oo.Trees can't break extraction.oo.Definitions.
- 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→24 extraction.oo.Trees uses ast.Expressions part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.oo.Trees uses a type in ast.Expressions.
- The types involved
stainless.extraction.oo.Trees.ClassPattern→stainless.ast.Expressions.Patternstainless.extraction.oo.Trees.InstanceOfPattern→stainless.ast.Expressions.Pattern
- Direction
- extraction.oo.Trees uses ast.Expressions, so a change to ast.Expressions can break extraction.oo.Trees, while a change to extraction.oo.Trees can't break ast.Expressions.
- 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→1 lang uses algebra.ops✕
- Connections
- 2 pairs of types, where a type in lang uses a type in algebra.ops.
- The types involved
stainless.lang.Either→stainless.algebra.ops.Liststainless.lang.Map→stainless.algebra.ops.List
- Direction
- lang uses algebra.ops, so a change to algebra.ops can break lang, while a change to lang can't break algebra.ops.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
4→23 lang uses codegen.runtime part of a loop✕
- Connections
- 6 pairs of types, where a type in lang uses a type in codegen.runtime.
- The types involved
stainless.lang.Map→stainless.codegen.runtime.Mapstainless.lang.Option→stainless.codegen.runtime.Setstainless.lang.Rational→stainless.codegen.runtime.BigIntstainless.lang.Rational→stainless.codegen.runtime.Rationalstainless.lang.Set→stainless.codegen.runtime.Setstainless.lang.StrOps→stainless.codegen.runtime.BigInt
- Direction
- lang uses codegen.runtime, so a change to codegen.runtime can break lang, while a change to lang can't break codegen.runtime.
- 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→3 genc.ir.IR uses extraction.oo.Trees✕
- Connections
- 2 pairs of types, where a type in genc.ir.IR uses a type in extraction.oo.Trees.
- The types involved
stainless.genc.ir.IR.AsA→stainless.extraction.oo.Trees.ClassTypestainless.genc.ir.IR.IsA→stainless.extraction.oo.Trees.ClassType
- Direction
- genc.ir.IR uses extraction.oo.Trees, so a change to extraction.oo.Trees can break genc.ir.IR, while a change to genc.ir.IR can't break extraction.oo.Trees.
- Position
- Below the diagonal: genc.ir.IR uses a module listed above it, which is the healthy direction.
5→4 genc.ir.IR uses lang✕
- Connections
- 1 pair of types, where a type in genc.ir.IR uses a type in lang.
- The types involved
stainless.genc.ir.IR.ArrayAllocStatic→stainless.lang.Either
- Direction
- genc.ir.IR uses lang, so a change to lang can break genc.ir.IR, while a change to genc.ir.IR can't break lang.
- Position
- Below the diagonal: genc.ir.IR uses a module listed above it, which is the healthy direction.
5→6 genc.ir.IR uses genc.CAST part of a loop✕
- Connections
- 55 pairs of types, where a type in genc.ir.IR uses a type in genc.CAST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.genc.ir.IR.App→stainless.genc.CAST.Exprstainless.genc.ir.IR.ArrayAccess→stainless.genc.CAST.Exprstainless.genc.ir.IR.ArrayAlloc→stainless.genc.CAST.Treestainless.genc.ir.IR.ArrayAllocStatic→stainless.genc.CAST.Exprstainless.genc.ir.IR.ArrayAllocVLA→stainless.genc.CAST.Exprstainless.genc.ir.IR.ArrayInit→stainless.genc.CAST.Exprstainless.genc.ir.IR.ArrayLength→stainless.genc.CAST.Exprstainless.genc.ir.IR.ArrayType→stainless.genc.CAST.Typestainless.genc.ir.IR.AsA→stainless.genc.CAST.Exprstainless.genc.ir.IR.Assert→stainless.genc.CAST.Exprstainless.genc.ir.IR.Assign→stainless.genc.CAST.Exprstainless.genc.ir.IR.BinOp→stainless.genc.CAST.Exprstainless.genc.ir.IR.Binding→stainless.genc.CAST.Exprstainless.genc.ir.IR.Block→stainless.genc.CAST.Exprstainless.genc.ir.IR.Break→stainless.genc.CAST.Exprstainless.genc.ir.IR.Callable→stainless.genc.CAST.Exprstainless.genc.ir.IR.Callable→stainless.genc.CAST.FunTypestainless.genc.ir.IR.ClassDef→stainless.genc.CAST.Defstainless.genc.ir.IR.ClassDef→stainless.genc.CAST.Typestainless.genc.ir.IR.ClassType→stainless.genc.CAST.Typestainless.genc.ir.IR.Construct→stainless.genc.CAST.Exprstainless.genc.ir.IR.Decl→stainless.genc.CAST.Exprstainless.genc.ir.IR.Def→stainless.genc.CAST.Treestainless.genc.ir.IR.Deref→stainless.genc.CAST.Exprstainless.genc.ir.IR.DroppedType→stainless.genc.CAST.Type
- Direction
- genc.ir.IR uses genc.CAST, so a change to genc.CAST can break genc.ir.IR, while a change to genc.ir.IR can't break genc.CAST.
- 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→21 genc.ir.IR uses extraction.oo.Definitions part of a loop✕
- Connections
- 4 pairs of types, where a type in genc.ir.IR uses a type in extraction.oo.Definitions.
- The types involved
stainless.genc.ir.IR.ClassDef→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.IR.ClassType→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.IR.Construct→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.IR.Prog→stainless.extraction.oo.Definitions.ClassDef
- Direction
- genc.ir.IR uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break genc.ir.IR, while a change to genc.ir.IR can't break extraction.oo.Definitions.
- 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 genc.ir.IR uses codegen.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in genc.ir.IR uses a type in codegen.runtime.
- The types involved
stainless.genc.ir.IR.ClassDef→stainless.codegen.runtime.Set
- Direction
- genc.ir.IR uses codegen.runtime, so a change to codegen.runtime can break genc.ir.IR, while a change to genc.ir.IR can't break codegen.runtime.
- 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→31 genc.ir.IR uses stainless part of a loop✕
- Connections
- 1 pair of types, where a type in genc.ir.IR uses a type in stainless.
- The types involved
stainless.genc.ir.IR.Prog→stainless.Context
- Direction
- genc.ir.IR uses stainless, so a change to stainless can break genc.ir.IR, while a change to genc.ir.IR can't break stainless.
- 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→4 genc.CAST uses lang✕
- Connections
- 1 pair of types, where a type in genc.CAST uses a type in lang.
- The types involved
stainless.genc.CAST.Fun→stainless.lang.Either
- Direction
- genc.CAST uses lang, so a change to lang can break genc.CAST, while a change to genc.CAST can't break lang.
- Position
- Below the diagonal: genc.CAST uses a module listed above it, which is the healthy direction.
6→5 genc.CAST uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in genc.CAST uses a type in genc.ir.IR.
- The types involved
stainless.genc.CAST.Primitive→stainless.genc.ir.IR.PrimitiveType
- Direction
- genc.CAST uses genc.ir.IR, so a change to genc.ir.IR can break genc.CAST, while a change to genc.CAST can't break genc.ir.IR.
- Position
- Below the diagonal: genc.CAST uses a module listed above it, which is the healthy direction.
6→21 genc.CAST uses extraction.oo.Definitions part of a loop✕
- Connections
- 1 pair of types, where a type in genc.CAST uses a type in extraction.oo.Definitions.
- The types involved
stainless.genc.CAST.Prog→stainless.extraction.oo.Definitions.TypeDef
- Direction
- genc.CAST uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break genc.CAST, while a change to genc.CAST can't break extraction.oo.Definitions.
- 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→23 genc.CAST uses codegen.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in genc.CAST uses a type in codegen.runtime.
- The types involved
stainless.genc.CAST.Prog→stainless.codegen.runtime.Set
- Direction
- genc.CAST uses codegen.runtime, so a change to codegen.runtime can break genc.CAST, while a change to genc.CAST can't break codegen.runtime.
- 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→31 genc.CAST uses stainless part of a loop✕
- Connections
- 1 pair of types, where a type in genc.CAST uses a type in stainless.
- The types involved
stainless.genc.CAST.Tree→stainless.Context
- Direction
- genc.CAST uses stainless, so a change to stainless can break genc.CAST, while a change to genc.CAST can't break stainless.
- 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→6 ast.Definitions uses genc.CAST✕
- Connections
- 3 pairs of types, where a type in ast.Definitions uses a type in genc.CAST.
- The types involved
stainless.ast.Definitions.IndexedAt→stainless.genc.CAST.Exprstainless.ast.Definitions.StainlessAbstractSymbols→stainless.genc.CAST.Exprstainless.ast.Definitions.StainlessAbstractSymbols→stainless.genc.CAST.Type
- Direction
- ast.Definitions uses genc.CAST, so a change to genc.CAST can break ast.Definitions, while a change to ast.Definitions can't break genc.CAST.
- Position
- Below the diagonal: ast.Definitions uses a module listed above it, which is the healthy direction.
7→23 ast.Definitions uses codegen.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in ast.Definitions uses a type in codegen.runtime.
- The types involved
stainless.ast.Definitions.StainlessAbstractSymbols→stainless.codegen.runtime.Set
- Direction
- ast.Definitions uses codegen.runtime, so a change to codegen.runtime can break ast.Definitions, while a change to ast.Definitions can't break codegen.runtime.
- 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→27 ast.Definitions uses ast part of a loop✕
- Connections
- 4 pairs of types, where a type in ast.Definitions uses a type in ast.
- The types involved
stainless.ast.Definitions.StainlessAbstractSymbols→stainless.ast.CallGraphstainless.ast.Definitions.StainlessAbstractSymbols→stainless.ast.DependencyGraphstainless.ast.Definitions.StainlessAbstractSymbols→stainless.ast.SymbolOpsstainless.ast.Definitions.StainlessAbstractSymbols→stainless.ast.TypeOps
- Direction
- ast.Definitions uses ast, so a change to ast can break ast.Definitions, while a change to ast.Definitions can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→31 ast.Definitions uses stainless part of a loop✕
- Connections
- 1 pair of types, where a type in ast.Definitions uses a type in stainless.
- The types involved
stainless.ast.Definitions.StainlessAbstractSymbols→stainless.Context
- Direction
- ast.Definitions uses stainless, so a change to stainless can break ast.Definitions, while a change to ast.Definitions can't break stainless.
- 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→5 extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses a type in genc.ir.IR.
- The types involved
stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env→stainless.genc.ir.IR.ValDef
- Direction
- extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses genc.ir.IR, so a change to genc.ir.IR can break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, while a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses a module listed above it, which is the healthy direction.
8→6 extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses genc.CAST✕
- Connections
- 1 pair of types, where a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses a type in genc.CAST.
- The types involved
stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env→stainless.genc.CAST.Expr
- Direction
- extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses genc.CAST, so a change to genc.CAST can break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, while a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can't break genc.CAST.
- Position
- Below the diagonal: extraction.imperative.RefTransform.RefTransformContext.funRefTransformer uses a module listed above it, which is the healthy direction.
9→5 extraction.innerclasses.Definitions uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in extraction.innerclasses.Definitions uses a type in genc.ir.IR.
- The types involved
stainless.extraction.innerclasses.Definitions.LocalClassDef→stainless.genc.ir.IR.ValDefstainless.extraction.innerclasses.Definitions.LocalMethodDef→stainless.genc.ir.IR.FunDefstainless.extraction.innerclasses.Definitions.LocalMethodDef→stainless.genc.ir.IR.ValDef
- Direction
- extraction.innerclasses.Definitions uses genc.ir.IR, so a change to genc.ir.IR can break extraction.innerclasses.Definitions, while a change to extraction.innerclasses.Definitions can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.innerclasses.Definitions uses a module listed above it, which is the healthy direction.
9→6 extraction.innerclasses.Definitions uses genc.CAST✕
- Connections
- 4 pairs of types, where a type in extraction.innerclasses.Definitions uses a type in genc.CAST.
- The types involved
stainless.extraction.innerclasses.Definitions.LocalClassDef→stainless.genc.CAST.Typestainless.extraction.innerclasses.Definitions.LocalMethodDef→stainless.genc.CAST.Exprstainless.extraction.innerclasses.Definitions.LocalMethodDef→stainless.genc.CAST.Typestainless.extraction.innerclasses.Definitions.LocalTypeDef→stainless.genc.CAST.Type
- Direction
- extraction.innerclasses.Definitions uses genc.CAST, so a change to genc.CAST can break extraction.innerclasses.Definitions, while a change to extraction.innerclasses.Definitions can't break genc.CAST.
- Position
- Below the diagonal: extraction.innerclasses.Definitions uses a module listed above it, which is the healthy direction.
9→20 extraction.innerclasses.Definitions uses extraction.imperative.trees part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.innerclasses.Definitions uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.innerclasses.Definitions.LocalClassDef→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.innerclasses.Definitions uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.innerclasses.Definitions, while a change to extraction.innerclasses.Definitions can't break extraction.imperative.trees.
- 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→21 extraction.innerclasses.Definitions uses extraction.oo.Definitions part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.innerclasses.Definitions uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.innerclasses.Definitions.LocalClassDef→stainless.extraction.oo.Definitions.TypedClassDefstainless.extraction.innerclasses.Definitions.LocalTypeDef→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.innerclasses.Definitions uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.innerclasses.Definitions, while a change to extraction.innerclasses.Definitions can't break extraction.oo.Definitions.
- 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→2 genc uses extraction.imperative.EffectElaboration✕
- Connections
- 1 pair of types, where a type in genc uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.genc.LeonInlining→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- genc uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break genc, while a change to genc can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: genc uses a module listed above it, which is the healthy direction.
10→5 genc uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in genc uses a type in genc.ir.IR.
- The types involved
stainless.genc.LeonInlining→stainless.genc.ir.IR.FunDef
- Direction
- genc uses genc.ir.IR, so a change to genc.ir.IR can break genc, while a change to genc can't break genc.ir.IR.
- Position
- Below the diagonal: genc uses a module listed above it, which is the healthy direction.
10→6 genc uses genc.CAST✕
- Connections
- 10 pairs of types, where a type in genc uses a type in genc.CAST.
- The types involved
stainless.genc.CAST→stainless.genc.CAST.Exprstainless.genc.CASTDependencies→stainless.genc.CAST.Progstainless.genc.CASTDependencies→stainless.genc.CAST.Typestainless.genc.CASTTraverser→stainless.genc.CAST.Treestainless.genc.CFileOutputPhase→stainless.genc.CAST.Progstainless.genc.CPrinter→stainless.genc.CAST.Includestainless.genc.CPrinter→stainless.genc.CAST.Treestainless.genc.ExtraOps→stainless.genc.CAST.Typestainless.genc.GenerateC→stainless.genc.CAST.Progstainless.genc.PrinterContext→stainless.genc.CAST.Tree
- Direction
- genc uses genc.CAST, so a change to genc.CAST can break genc, while a change to genc can't break genc.CAST.
- Position
- Below the diagonal: genc uses a module listed above it, which is the healthy direction.
10→17 genc uses extraction part of a loop✕
- Connections
- 5 pairs of types, where a type in genc uses a type in extraction.
- The types involved
stainless.genc.GenCAnalysis→stainless.extraction.ExtractionSummarystainless.genc.GenCRun→stainless.extraction.ExtractionPipelinestainless.genc.LeonInlining→stainless.extraction.CachingPhasestainless.genc.LeonInlining→stainless.extraction.IdentitySortsstainless.genc.LeonInlining→stainless.extraction.NoSummaryPhase
- Direction
- genc uses extraction, so a change to extraction can break genc, while a change to genc can't break extraction.
- 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→19 genc uses extraction.oo part of a loop✕
- Connections
- 2 pairs of types, where a type in genc uses a type in extraction.oo.
- The types involved
stainless.genc.LeonInlining→stainless.extraction.oo.IdentityClassesstainless.genc.LeonInlining→stainless.extraction.oo.IdentityTypeDefs
- Direction
- genc uses extraction.oo, so a change to extraction.oo can break genc, while a change to genc can't break extraction.oo.
- 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→20 genc uses extraction.imperative.trees part of a loop✕
- Connections
- 3 pairs of types, where a type in genc uses a type in extraction.imperative.trees.
- The types involved
stainless.genc.ExtraOps→stainless.extraction.imperative.trees.Symbolsstainless.genc.GenerateC→stainless.extraction.imperative.trees.Symbolsstainless.genc.LeonInlining→stainless.extraction.imperative.trees.Symbols
- Direction
- genc uses extraction.imperative.trees, so a change to extraction.imperative.trees can break genc, while a change to genc can't break extraction.imperative.trees.
- 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→23 genc uses codegen.runtime part of a loop✕
- Connections
- 3 pairs of types, where a type in genc uses a type in codegen.runtime.
- The types involved
stainless.genc.CASTDependencies→stainless.codegen.runtime.Setstainless.genc.CPrinter→stainless.codegen.runtime.Setstainless.genc.GenCAnalysis→stainless.codegen.runtime.Set
- Direction
- genc uses codegen.runtime, so a change to codegen.runtime can break genc, while a change to genc can't break codegen.runtime.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 genc uses ast part of a loop✕
- Connections
- 1 pair of types, where a type in genc uses a type in ast.
- The types involved
stainless.genc.LeonInlining→stainless.ast.Trees
- Direction
- genc uses ast, so a change to ast can break genc, while a change to genc can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→31 genc uses stainless part of a loop✕
- Connections
- 10 pairs of types, where a type in genc uses a type in stainless.
- The types involved
stainless.genc.CASTDependencies→stainless.Contextstainless.genc.CFileOutputPhase→stainless.Contextstainless.genc.GenCAnalysis→stainless.AbstractAnalysisstainless.genc.GenCComponent→stainless.Componentstainless.genc.GenCComponent→stainless.Contextstainless.genc.GenCRun→stainless.Contextstainless.genc.GenerateC→stainless.Contextstainless.genc.LeonInlining→stainless.Contextstainless.genc.LeonPipeline→stainless.Contextstainless.genc.NoopPhase→stainless.Context
- Direction
- genc uses stainless, so a change to stainless can break genc, while a change to genc can't break stainless.
- 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→5 extraction.innerfuns.Definitions uses genc.ir.IR✕
- Connections
- 6 pairs of types, where a type in extraction.innerfuns.Definitions uses a type in genc.ir.IR.
- The types involved
stainless.extraction.innerfuns.Definitions.FunAbstraction→stainless.genc.ir.IR.FunDefstainless.extraction.innerfuns.Definitions.FunAbstraction→stainless.genc.ir.IR.ValDefstainless.extraction.innerfuns.Definitions.Inner→stainless.genc.ir.IR.ValDefstainless.extraction.innerfuns.Definitions.LocalFunDef→stainless.genc.ir.IR.ValDefstainless.extraction.innerfuns.Definitions.Outer→stainless.genc.ir.IR.FunDefstainless.extraction.innerfuns.Definitions.Outer→stainless.genc.ir.IR.ValDef
- Direction
- extraction.innerfuns.Definitions uses genc.ir.IR, so a change to genc.ir.IR can break extraction.innerfuns.Definitions, while a change to extraction.innerfuns.Definitions can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.innerfuns.Definitions uses a module listed above it, which is the healthy direction.
11→6 extraction.innerfuns.Definitions uses genc.CAST✕
- Connections
- 9 pairs of types, where a type in extraction.innerfuns.Definitions uses a type in genc.CAST.
- The types involved
stainless.extraction.innerfuns.Definitions.FunAbstraction→stainless.genc.CAST.Exprstainless.extraction.innerfuns.Definitions.FunAbstraction→stainless.genc.CAST.Treestainless.extraction.innerfuns.Definitions.FunAbstraction→stainless.genc.CAST.Typestainless.extraction.innerfuns.Definitions.Inner→stainless.genc.CAST.Exprstainless.extraction.innerfuns.Definitions.Inner→stainless.genc.CAST.Typestainless.extraction.innerfuns.Definitions.LocalFunDef→stainless.genc.CAST.Exprstainless.extraction.innerfuns.Definitions.LocalFunDef→stainless.genc.CAST.Typestainless.extraction.innerfuns.Definitions.Outer→stainless.genc.CAST.Exprstainless.extraction.innerfuns.Definitions.Outer→stainless.genc.CAST.Type
- Direction
- extraction.innerfuns.Definitions uses genc.CAST, so a change to genc.CAST can break extraction.innerfuns.Definitions, while a change to extraction.innerfuns.Definitions can't break genc.CAST.
- Position
- Below the diagonal: extraction.innerfuns.Definitions uses a module listed above it, which is the healthy direction.
11→7 extraction.innerfuns.Definitions uses ast.Definitions✕
- Connections
- 1 pair of types, where a type in extraction.innerfuns.Definitions uses a type in ast.Definitions.
- The types involved
stainless.extraction.innerfuns.Definitions.InnerFunsAbstractSymbols→stainless.ast.Definitions.StainlessAbstractSymbols
- Direction
- extraction.innerfuns.Definitions uses ast.Definitions, so a change to ast.Definitions can break extraction.innerfuns.Definitions, while a change to extraction.innerfuns.Definitions can't break ast.Definitions.
- Position
- Below the diagonal: extraction.innerfuns.Definitions uses a module listed above it, which is the healthy direction.
11→20 extraction.innerfuns.Definitions uses extraction.imperative.trees part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.innerfuns.Definitions uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.innerfuns.Definitions.LocalFunDef→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.innerfuns.Definitions uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.innerfuns.Definitions, while a change to extraction.innerfuns.Definitions can't break extraction.imperative.trees.
- 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→23 extraction.innerfuns.Definitions uses codegen.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.innerfuns.Definitions uses a type in codegen.runtime.
- The types involved
stainless.extraction.innerfuns.Definitions.LocalFunDef→stainless.codegen.runtime.Set
- Direction
- extraction.innerfuns.Definitions uses codegen.runtime, so a change to codegen.runtime can break extraction.innerfuns.Definitions, while a change to extraction.innerfuns.Definitions can't break codegen.runtime.
- 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→27 extraction.innerfuns.Definitions uses ast part of a loop✕
- Connections
- 5 pairs of types, where a type in extraction.innerfuns.Definitions uses a type in ast.
- The types involved
stainless.extraction.innerfuns.Definitions.FunAbstraction→stainless.ast.Treesstainless.extraction.innerfuns.Definitions.Inner→stainless.ast.Treesstainless.extraction.innerfuns.Definitions.InnerFunsAbstractSymbols→stainless.ast.SymbolOpsstainless.extraction.innerfuns.Definitions.InnerFunsAbstractSymbols→stainless.ast.TypeOpsstainless.extraction.innerfuns.Definitions.Outer→stainless.ast.Trees
- Direction
- extraction.innerfuns.Definitions uses ast, so a change to ast can break extraction.innerfuns.Definitions, while a change to extraction.innerfuns.Definitions can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 genc.ir uses algebra.ops✕
- Connections
- 1 pair of types, where a type in genc.ir uses a type in algebra.ops.
- The types involved
stainless.genc.ir.TailRecTransformer→stainless.algebra.ops.List
- Direction
- genc.ir uses algebra.ops, so a change to algebra.ops can break genc.ir, while a change to genc.ir can't break algebra.ops.
- Position
- Below the diagonal: genc.ir uses a module listed above it, which is the healthy direction.
12→3 genc.ir uses extraction.oo.Trees✕
- Connections
- 1 pair of types, where a type in genc.ir uses a type in extraction.oo.Trees.
- The types involved
stainless.genc.ir.Normaliser→stainless.extraction.oo.Trees.ClassType
- Direction
- genc.ir uses extraction.oo.Trees, so a change to extraction.oo.Trees can break genc.ir, while a change to genc.ir can't break extraction.oo.Trees.
- Position
- Below the diagonal: genc.ir uses a module listed above it, which is the healthy direction.
12→5 genc.ir uses genc.ir.IR✕
- Connections
- 21 pairs of types, where a type in genc.ir uses a type in genc.ir.IR.
- The types involved
stainless.genc.ir.ClassLifter→stainless.genc.ir.IR.FunDefstainless.genc.ir.ClassLifter→stainless.genc.ir.IR.ValDefstainless.genc.ir.DependencyFinder→stainless.genc.ir.IR.FunDefstainless.genc.ir.IRPrinter→stainless.genc.ir.IR.ArrayAllocstainless.genc.ir.IRPrinter→stainless.genc.ir.IR.FunBodystainless.genc.ir.IRPrinter→stainless.genc.ir.IR.FunDefstainless.genc.ir.IRPrinter→stainless.genc.ir.IR.ValDefstainless.genc.ir.Normaliser→stainless.genc.ir.IR.FunDefstainless.genc.ir.Referentiator→stainless.genc.ir.IR.FunDefstainless.genc.ir.Referentiator→stainless.genc.ir.IR.ValDefstainless.genc.ir.TailRecTransformer→stainless.genc.ir.IR.FunDefstainless.genc.ir.TailRecTransformer→stainless.genc.ir.IR.ValDefstainless.genc.ir.Transformer→stainless.genc.ir.IR.ArrayAllocstainless.genc.ir.Transformer→stainless.genc.ir.IR.Callablestainless.genc.ir.Transformer→stainless.genc.ir.IR.FunBodystainless.genc.ir.Transformer→stainless.genc.ir.IR.FunDefstainless.genc.ir.Transformer→stainless.genc.ir.IR.ValDefstainless.genc.ir.Visitor→stainless.genc.ir.IR.ArrayAllocstainless.genc.ir.Visitor→stainless.genc.ir.IR.FunBodystainless.genc.ir.Visitor→stainless.genc.ir.IR.FunDefstainless.genc.ir.Visitor→stainless.genc.ir.IR.ValDef
- Direction
- genc.ir uses genc.ir.IR, so a change to genc.ir.IR can break genc.ir, while a change to genc.ir can't break genc.ir.IR.
- Position
- Below the diagonal: genc.ir uses a module listed above it, which is the healthy direction.
12→6 genc.ir uses genc.CAST✕
- Connections
- 26 pairs of types, where a type in genc.ir uses a type in genc.CAST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.genc.ir.ClassLifter→stainless.genc.CAST.Exprstainless.genc.ir.ClassLifter→stainless.genc.CAST.Typestainless.genc.ir.IR→stainless.genc.CAST.Exprstainless.genc.ir.IR→stainless.genc.CAST.Typestainless.genc.ir.IRPrinter→stainless.genc.CAST.Exprstainless.genc.ir.IRPrinter→stainless.genc.CAST.Progstainless.genc.ir.IRPrinter→stainless.genc.CAST.Treestainless.genc.ir.IRPrinter→stainless.genc.CAST.Typestainless.genc.ir.Normaliser→stainless.genc.CAST.Bindingstainless.genc.ir.Normaliser→stainless.genc.CAST.Exprstainless.genc.ir.Normaliser→stainless.genc.CAST.Typestainless.genc.ir.Referentiator→stainless.genc.CAST.Exprstainless.genc.ir.Referentiator→stainless.genc.CAST.Progstainless.genc.ir.Referentiator→stainless.genc.CAST.Typestainless.genc.ir.StructInliner→stainless.genc.CAST.Exprstainless.genc.ir.StructInliner→stainless.genc.CAST.Progstainless.genc.ir.StructInliner→stainless.genc.CAST.Typestainless.genc.ir.TailRecSimpTransformer→stainless.genc.CAST.Exprstainless.genc.ir.TailRecTransformer→stainless.genc.CAST.Exprstainless.genc.ir.TailRecTransformer→stainless.genc.CAST.Progstainless.genc.ir.Transformer→stainless.genc.CAST.Exprstainless.genc.ir.Transformer→stainless.genc.CAST.Progstainless.genc.ir.Transformer→stainless.genc.CAST.Typestainless.genc.ir.Visitor→stainless.genc.CAST.Exprstainless.genc.ir.Visitor→stainless.genc.CAST.Prog
- Direction
- genc.ir uses genc.CAST, so a change to genc.CAST can break genc.ir, while a change to genc.ir can't break genc.CAST.
- Position
- Below the diagonal: genc.ir uses a module listed above it, which is the healthy direction.
12→8 genc.ir uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 6 pairs of types, where a type in genc.ir uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.genc.ir.ClassLifter→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.genc.ir.Normaliser→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.genc.ir.Referentiator→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.genc.ir.StructInliner→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.genc.ir.TailRecSimpTransformer→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.genc.ir.Transformer→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- genc.ir uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break genc.ir, while a change to genc.ir can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: genc.ir uses a module listed above it, which is the healthy direction.
12→21 genc.ir uses extraction.oo.Definitions part of a loop✕
- Connections
- 5 pairs of types, where a type in genc.ir uses a type in extraction.oo.Definitions.
- The types involved
stainless.genc.ir.ClassLifter→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.DependencyFinder→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.IRPrinter→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.Transformer→stainless.extraction.oo.Definitions.ClassDefstainless.genc.ir.Visitor→stainless.extraction.oo.Definitions.ClassDef
- Direction
- genc.ir uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break genc.ir, while a change to genc.ir can't break extraction.oo.Definitions.
- 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→23 genc.ir uses codegen.runtime part of a loop✕
- Connections
- 2 pairs of types, where a type in genc.ir uses a type in codegen.runtime.
- The types involved
stainless.genc.ir.DependencyFinder→stainless.codegen.runtime.Setstainless.genc.ir.TailRecTransformer→stainless.codegen.runtime.Map
- Direction
- genc.ir uses codegen.runtime, so a change to codegen.runtime can break genc.ir, while a change to genc.ir can't break codegen.runtime.
- 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→31 genc.ir uses stainless part of a loop✕
- Connections
- 6 pairs of types, where a type in genc.ir uses a type in stainless.
- The types involved
stainless.genc.ir.ClassLifter→stainless.Contextstainless.genc.ir.IRPrinter→stainless.Contextstainless.genc.ir.Normaliser→stainless.Contextstainless.genc.ir.Referentiator→stainless.Contextstainless.genc.ir.StructInliner→stainless.Contextstainless.genc.ir.TailRecTransformer→stainless.Context
- Direction
- genc.ir uses stainless, so a change to stainless can break genc.ir, while a change to genc.ir can't break stainless.
- 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→5 extraction.imperative.EffectsAnalyzer uses genc.ir.IR✕
- Connections
- 10 pairs of types, where a type in extraction.imperative.EffectsAnalyzer uses a type in genc.ir.IR.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer.ADTFieldAccessor→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.Accessor→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.ArrayAccessor→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.ClassFieldAccessor→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.MutableMapAccessor→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.Path→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.TupleFieldAccessor→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsAnalyzer.UnknownArrayAccessor→stainless.genc.ir.IR.ValDef
- Direction
- extraction.imperative.EffectsAnalyzer uses genc.ir.IR, so a change to genc.ir.IR can break extraction.imperative.EffectsAnalyzer, while a change to extraction.imperative.EffectsAnalyzer can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.imperative.EffectsAnalyzer uses a module listed above it, which is the healthy direction.
13→6 extraction.imperative.EffectsAnalyzer uses genc.CAST✕
- Connections
- 11 pairs of types, where a type in extraction.imperative.EffectsAnalyzer uses a type in genc.CAST.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer.ADTFieldAccessor→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.Accessor→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.ArrayAccessor→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.ClassFieldAccessor→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.genc.CAST.Typestainless.extraction.imperative.EffectsAnalyzer.MutableMapAccessor→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.Path→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.Target→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.TupleFieldAccessor→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer.UnknownArrayAccessor→stainless.genc.CAST.Expr
- Direction
- extraction.imperative.EffectsAnalyzer uses genc.CAST, so a change to genc.CAST can break extraction.imperative.EffectsAnalyzer, while a change to extraction.imperative.EffectsAnalyzer can't break genc.CAST.
- Position
- Below the diagonal: extraction.imperative.EffectsAnalyzer uses a module listed above it, which is the healthy direction.
13→11 extraction.imperative.EffectsAnalyzer uses extraction.innerfuns.Definitions✕
- Connections
- 2 pairs of types, where a type in extraction.imperative.EffectsAnalyzer uses a type in extraction.innerfuns.Definitions.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.extraction.innerfuns.Definitions.FunAbstractionstainless.extraction.imperative.EffectsAnalyzer.Result→stainless.extraction.innerfuns.Definitions.FunAbstraction
- Direction
- extraction.imperative.EffectsAnalyzer uses extraction.innerfuns.Definitions, so a change to extraction.innerfuns.Definitions can break extraction.imperative.EffectsAnalyzer, while a change to extraction.imperative.EffectsAnalyzer can't break extraction.innerfuns.Definitions.
- Position
- Below the diagonal: extraction.imperative.EffectsAnalyzer uses a module listed above it, which is the healthy direction.
13→20 extraction.imperative.EffectsAnalyzer uses extraction.imperative.trees part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.imperative.EffectsAnalyzer uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.EffectsAnalyzer.Path→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.imperative.EffectsAnalyzer uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.imperative.EffectsAnalyzer, while a change to extraction.imperative.EffectsAnalyzer can't break extraction.imperative.trees.
- 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→23 extraction.imperative.EffectsAnalyzer uses codegen.runtime part of a loop✕
- Connections
- 3 pairs of types, where a type in extraction.imperative.EffectsAnalyzer uses a type in codegen.runtime.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis→stainless.codegen.runtime.Setstainless.extraction.imperative.EffectsAnalyzer.Result→stainless.codegen.runtime.Mapstainless.extraction.imperative.EffectsAnalyzer.Result→stainless.codegen.runtime.Set
- Direction
- extraction.imperative.EffectsAnalyzer uses codegen.runtime, so a change to codegen.runtime can break extraction.imperative.EffectsAnalyzer, while a change to extraction.imperative.EffectsAnalyzer can't break codegen.runtime.
- 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→31 extraction.imperative.EffectsAnalyzer uses stainless part of a loop✕
- Connections
- 7 pairs of types, where a type in extraction.imperative.EffectsAnalyzer uses a type in stainless.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer.ADTFieldAccessor→stainless.Contextstainless.extraction.imperative.EffectsAnalyzer.Accessor→stainless.Contextstainless.extraction.imperative.EffectsAnalyzer.ArrayAccessor→stainless.Contextstainless.extraction.imperative.EffectsAnalyzer.ClassFieldAccessor→stainless.Contextstainless.extraction.imperative.EffectsAnalyzer.MutableMapAccessor→stainless.Contextstainless.extraction.imperative.EffectsAnalyzer.TupleFieldAccessor→stainless.Contextstainless.extraction.imperative.EffectsAnalyzer.UnknownArrayAccessor→stainless.Context
- Direction
- extraction.imperative.EffectsAnalyzer uses stainless, so a change to stainless can break extraction.imperative.EffectsAnalyzer, while a change to extraction.imperative.EffectsAnalyzer can't break stainless.
- 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→2 extraction.imperative uses extraction.imperative.EffectElaboration✕
- Connections
- 3 pairs of types, where a type in extraction.imperative uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.extraction.imperative.EffectElaboration→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.imperative.ReturnElimination→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- extraction.imperative uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break extraction.imperative, while a change to extraction.imperative can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→3 extraction.imperative uses extraction.oo.Trees✕
- Connections
- 1 pair of types, where a type in extraction.imperative uses a type in extraction.oo.Trees.
- The types involved
stainless.extraction.imperative.SymbolOps→stainless.extraction.oo.Trees.ClassType
- Direction
- extraction.imperative uses extraction.oo.Trees, so a change to extraction.oo.Trees can break extraction.imperative, while a change to extraction.imperative can't break extraction.oo.Trees.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→5 extraction.imperative uses genc.ir.IR✕
- Connections
- 13 pairs of types, where a type in extraction.imperative uses a type in genc.ir.IR.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.EffectElaboration→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.EffectsAnalyzer→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.EffectsChecker→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.ExprOps→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.GhostChecker→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.ImperativeCleanup→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.ImperativeCodeElimination→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.ReturnElimination→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.SymbolOps→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.Trees→stainless.genc.ir.IR.FunDefstainless.extraction.imperative.Trees→stainless.genc.ir.IR.ValDefstainless.extraction.imperative.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction.imperative uses genc.ir.IR, so a change to genc.ir.IR can break extraction.imperative, while a change to extraction.imperative can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→6 extraction.imperative uses genc.CAST✕
- Connections
- 17 pairs of types, where a type in extraction.imperative uses a type in genc.CAST.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer→stainless.genc.CAST.Exprstainless.extraction.imperative.EffectsAnalyzer→stainless.genc.CAST.Typestainless.extraction.imperative.ExprOps→stainless.genc.CAST.Exprstainless.extraction.imperative.GhostTraverser→stainless.genc.CAST.Exprstainless.extraction.imperative.ImperativeCleanup→stainless.genc.CAST.Exprstainless.extraction.imperative.Printer→stainless.genc.CAST.Exprstainless.extraction.imperative.Printer→stainless.genc.CAST.Treestainless.extraction.imperative.ReturnElimination→stainless.genc.CAST.Exprstainless.extraction.imperative.ReturnElimination→stainless.genc.CAST.Typestainless.extraction.imperative.SymbolOps→stainless.genc.CAST.Typestainless.extraction.imperative.TransformerWithPC→stainless.genc.CAST.Exprstainless.extraction.imperative.TransformerWithType→stainless.genc.CAST.Exprstainless.extraction.imperative.TransformerWithType→stainless.genc.CAST.Typestainless.extraction.imperative.TreeDeconstructor→stainless.genc.CAST.Exprstainless.extraction.imperative.TreeDeconstructor→stainless.genc.CAST.Typestainless.extraction.imperative.Trees→stainless.genc.CAST.Exprstainless.extraction.imperative.Trees→stainless.genc.CAST.Type
- Direction
- extraction.imperative uses genc.CAST, so a change to genc.CAST can break extraction.imperative, while a change to extraction.imperative can't break genc.CAST.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→8 extraction.imperative uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 1 pair of types, where a type in extraction.imperative uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.extraction.imperative.TransformerWithPC→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- extraction.imperative uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break extraction.imperative, while a change to extraction.imperative can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→10 extraction.imperative uses genc✕
- Connections
- 1 pair of types, where a type in extraction.imperative uses a type in genc.
- The types involved
stainless.extraction.imperative.Printer→stainless.genc.PrinterContext
- Direction
- extraction.imperative uses genc, so a change to genc can break extraction.imperative, while a change to extraction.imperative can't break genc.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→13 extraction.imperative uses extraction.imperative.EffectsAnalyzer✕
- Connections
- 6 pairs of types, where a type in extraction.imperative uses a type in extraction.imperative.EffectsAnalyzer.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer→stainless.extraction.imperative.EffectsAnalyzer.Accessorstainless.extraction.imperative.EffectsAnalyzer→stainless.extraction.imperative.EffectsAnalyzer.Effectstainless.extraction.imperative.EffectsAnalyzer→stainless.extraction.imperative.EffectsAnalyzer.EffectKindstainless.extraction.imperative.EffectsAnalyzer→stainless.extraction.imperative.EffectsAnalyzer.Targetstainless.extraction.imperative.EffectsChecker→stainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysisstainless.extraction.imperative.GhostChecker→stainless.extraction.imperative.EffectsAnalyzer.EffectsAnalysis
- Direction
- extraction.imperative uses extraction.imperative.EffectsAnalyzer, so a change to extraction.imperative.EffectsAnalyzer can break extraction.imperative, while a change to extraction.imperative can't break extraction.imperative.EffectsAnalyzer.
- Position
- Below the diagonal: extraction.imperative uses a module listed above it, which is the healthy direction.
14→17 extraction.imperative uses extraction part of a loop✕
- Connections
- 23 pairs of types, where a type in extraction.imperative uses a type in extraction.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.extraction.CachingPhasestainless.extraction.imperative.AntiAliasing→stainless.extraction.ExtractionSummarystainless.extraction.imperative.AntiAliasing→stainless.extraction.SimpleSortsstainless.extraction.imperative.EffectElaboration→stainless.extraction.CachingPhasestainless.extraction.imperative.EffectElaboration→stainless.extraction.NoSummaryPhasestainless.extraction.imperative.EffectElaboration→stainless.extraction.SimpleSortsstainless.extraction.imperative.EffectsAnalyzer→stainless.extraction.CachingPhasestainless.extraction.imperative.ImperativeCleanup→stainless.extraction.SimplePhasestainless.extraction.imperative.ImperativeCleanup→stainless.extraction.SimplyCachedFunctionsstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.SimplyCachedSortsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.CachingPhasestainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.ExtractionSummarystainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.IdentitySortsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.SimpleFunctionsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.SimplyCachedFunctionsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.SimplyCachedSortsstainless.extraction.imperative.ImperativeEliminationException→stainless.extraction.MalformedStainlessCodestainless.extraction.imperative.RefTransform→stainless.extraction.CachingPhasestainless.extraction.imperative.ReturnElimination→stainless.extraction.CachingPhasestainless.extraction.imperative.ReturnElimination→stainless.extraction.ExtractionSummarystainless.extraction.imperative.ReturnElimination→stainless.extraction.IdentitySortsstainless.extraction.imperative.ReturnElimination→stainless.extraction.SimpleFunctionsstainless.extraction.imperative.ReturnElimination→stainless.extraction.SimplyCachedFunctions
- Direction
- extraction.imperative uses extraction, so a change to extraction can break extraction.imperative, while a change to extraction.imperative can't break extraction.
- 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→19 extraction.imperative uses extraction.oo part of a loop✕
- Connections
- 11 pairs of types, where a type in extraction.imperative uses a type in extraction.oo.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.imperative.AntiAliasing→stainless.extraction.oo.SimpleClassesstainless.extraction.imperative.EffectElaboration→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.oo.SimplyCachedClassesstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.oo.SimplyCachedTypeDefsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.oo.IdentityClassesstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.oo.SimplyCachedClassesstainless.extraction.imperative.ReturnElimination→stainless.extraction.oo.IdentityClassesstainless.extraction.imperative.ReturnElimination→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.imperative.trees→stainless.extraction.oo.ClassSymbols
- Direction
- extraction.imperative uses extraction.oo, so a change to extraction.oo can break extraction.imperative, while a change to extraction.imperative can't break extraction.oo.
- 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→20 extraction.imperative uses extraction.imperative.trees part of a loop✕
- Connections
- 9 pairs of types, where a type in extraction.imperative uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.EffectElaboration→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.EffectsAnalyzer→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.ImperativeCodeElimination→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.ReturnElimination→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.TransformerWithType→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.Trees→stainless.extraction.imperative.trees.Symbolsstainless.extraction.imperative.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.imperative uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.imperative, while a change to extraction.imperative can't break extraction.imperative.trees.
- 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 extraction.imperative uses extraction.oo.Definitions part of a loop✕
- Connections
- 7 pairs of types, where a type in extraction.imperative uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.imperative.EffectElaboration→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.imperative.ImperativeCleanup→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.imperative.SymbolOps→stainless.extraction.oo.Definitions.TypedClassDefstainless.extraction.imperative.trees→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.imperative.trees→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.imperative uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.imperative, while a change to extraction.imperative can't break extraction.oo.Definitions.
- 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→23 extraction.imperative uses codegen.runtime part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.imperative uses a type in codegen.runtime.
- The types involved
stainless.extraction.imperative.EffectsAnalyzer→stainless.codegen.runtime.Setstainless.extraction.imperative.ExprOps→stainless.codegen.runtime.Mapstainless.extraction.imperative.SymbolOps→stainless.codegen.runtime.Setstainless.extraction.imperative.trees→stainless.codegen.runtime.Map
- Direction
- extraction.imperative uses codegen.runtime, so a change to codegen.runtime can break extraction.imperative, while a change to extraction.imperative can't break codegen.runtime.
- 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 extraction.imperative uses ast.ExprOps part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.imperative uses a type in ast.ExprOps.
- The types involved
stainless.extraction.imperative.ExprOps→stainless.ast.ExprOps.Specification
- Direction
- extraction.imperative uses ast.ExprOps, so a change to ast.ExprOps can break extraction.imperative, while a change to extraction.imperative can't break ast.ExprOps.
- 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→27 extraction.imperative uses ast part of a loop✕
- Connections
- 27 pairs of types, where a type in extraction.imperative uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.ast.Treesstainless.extraction.imperative.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.imperative.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.imperative.Definitions→stainless.ast.Treesstainless.extraction.imperative.EffectElaboration→stainless.ast.Treesstainless.extraction.imperative.EffectsAnalyzer→stainless.ast.Treesstainless.extraction.imperative.ExprOps→stainless.ast.Treesstainless.extraction.imperative.GhostTraverser→stainless.ast.Treesstainless.extraction.imperative.HeapASTExtractors→stainless.ast.Treesstainless.extraction.imperative.ImperativeCleanup→stainless.ast.Treesstainless.extraction.imperative.ImperativeCodeElimination→stainless.ast.Treesstainless.extraction.imperative.Printer→stainless.ast.Printerstainless.extraction.imperative.Printer→stainless.ast.Treesstainless.extraction.imperative.RefTransform→stainless.ast.Treesstainless.extraction.imperative.ReturnElimination→stainless.ast.Treesstainless.extraction.imperative.SymbolOps→stainless.ast.SymbolOpsstainless.extraction.imperative.SymbolOps→stainless.ast.TypeOpsstainless.extraction.imperative.TransformerWithPC→stainless.ast.Treesstainless.extraction.imperative.TransformerWithType→stainless.ast.Treesstainless.extraction.imperative.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.imperative.TreeDeconstructor→stainless.ast.Treesstainless.extraction.imperative.Trees→stainless.ast.Definitionsstainless.extraction.imperative.Trees→stainless.ast.ExprOpsstainless.extraction.imperative.Trees→stainless.ast.Treesstainless.extraction.imperative.TypeOps→stainless.ast.Trees
- Direction
- extraction.imperative uses ast, so a change to ast can break extraction.imperative, while a change to extraction.imperative can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→31 extraction.imperative uses stainless part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.imperative uses a type in stainless.
- The types involved
stainless.extraction.imperative.AntiAliasing→stainless.Contextstainless.extraction.imperative.ImperativeCleanup→stainless.Contextstainless.extraction.imperative.ImperativeCodeElimination→stainless.Contextstainless.extraction.imperative.ReturnElimination→stainless.Context
- Direction
- extraction.imperative uses stainless, so a change to stainless can break extraction.imperative, while a change to extraction.imperative can't break stainless.
- 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→2 extraction.innerclasses uses extraction.imperative.EffectElaboration✕
- Connections
- 1 pair of types, where a type in extraction.innerclasses uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.extraction.innerclasses.InnerClasses→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- extraction.innerclasses uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→5 extraction.innerclasses uses genc.ir.IR✕
- Connections
- 5 pairs of types, where a type in extraction.innerclasses uses a type in genc.ir.IR.
- The types involved
stainless.extraction.innerclasses.DependencyGraph→stainless.genc.ir.IR.FunDefstainless.extraction.innerclasses.ExprOps→stainless.genc.ir.IR.FunDefstainless.extraction.innerclasses.GhostTraverser→stainless.genc.ir.IR.FunDefstainless.extraction.innerclasses.InnerClasses→stainless.genc.ir.IR.FunDefstainless.extraction.innerclasses.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction.innerclasses uses genc.ir.IR, so a change to genc.ir.IR can break extraction.innerclasses, while a change to extraction.innerclasses can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→6 extraction.innerclasses uses genc.CAST✕
- Connections
- 7 pairs of types, where a type in extraction.innerclasses uses a type in genc.CAST.
- The types involved
stainless.extraction.innerclasses.ExprOps→stainless.genc.CAST.Exprstainless.extraction.innerclasses.GhostTraverser→stainless.genc.CAST.Exprstainless.extraction.innerclasses.Printer→stainless.genc.CAST.Exprstainless.extraction.innerclasses.Printer→stainless.genc.CAST.Treestainless.extraction.innerclasses.TreeDeconstructor→stainless.genc.CAST.Exprstainless.extraction.innerclasses.TreeDeconstructor→stainless.genc.CAST.Typestainless.extraction.innerclasses.TypeOps→stainless.genc.CAST.Type
- Direction
- extraction.innerclasses uses genc.CAST, so a change to genc.CAST can break extraction.innerclasses, while a change to extraction.innerclasses can't break genc.CAST.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→8 extraction.innerclasses uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 2 pairs of types, where a type in extraction.innerclasses uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.extraction.innerclasses.DefinitionTransformer→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.extraction.innerclasses.DefinitionTraverser→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- extraction.innerclasses uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→9 extraction.innerclasses uses extraction.innerclasses.Definitions✕
- Connections
- 11 pairs of types, where a type in extraction.innerclasses uses a type in extraction.innerclasses.Definitions.
- The types involved
stainless.extraction.innerclasses.DefinitionTransformer→stainless.extraction.innerclasses.Definitions.LocalClassDefstainless.extraction.innerclasses.DefinitionTransformer→stainless.extraction.innerclasses.Definitions.LocalMethodDefstainless.extraction.innerclasses.DefinitionTransformer→stainless.extraction.innerclasses.Definitions.LocalTypeDefstainless.extraction.innerclasses.DefinitionTraverser→stainless.extraction.innerclasses.Definitions.LocalClassDefstainless.extraction.innerclasses.DefinitionTraverser→stainless.extraction.innerclasses.Definitions.LocalMethodDefstainless.extraction.innerclasses.DependencyGraph→stainless.extraction.innerclasses.Definitions.LocalClassDefstainless.extraction.innerclasses.ExprOps→stainless.extraction.innerclasses.Definitions.LocalClassDefstainless.extraction.innerclasses.GhostTraverser→stainless.extraction.innerclasses.Definitions.LocalClassDefstainless.extraction.innerclasses.GhostTraverser→stainless.extraction.innerclasses.Definitions.LocalMethodDefstainless.extraction.innerclasses.Printer→stainless.extraction.innerclasses.Definitions.LocalMethodDefstainless.extraction.innerclasses.Printer→stainless.extraction.innerclasses.Definitions.LocalTypeDef
- Direction
- extraction.innerclasses uses extraction.innerclasses.Definitions, so a change to extraction.innerclasses.Definitions can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.innerclasses.Definitions.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→10 extraction.innerclasses uses genc✕
- Connections
- 1 pair of types, where a type in extraction.innerclasses uses a type in genc.
- The types involved
stainless.extraction.innerclasses.Printer→stainless.genc.PrinterContext
- Direction
- extraction.innerclasses uses genc, so a change to genc can break extraction.innerclasses, while a change to extraction.innerclasses can't break genc.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→14 extraction.innerclasses uses extraction.imperative✕
- Connections
- 1 pair of types, where a type in extraction.innerclasses uses a type in extraction.imperative.
- The types involved
stainless.extraction.innerclasses.GhostTraverser→stainless.extraction.imperative.GhostTraverser
- Direction
- extraction.innerclasses uses extraction.imperative, so a change to extraction.imperative can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.imperative.
- Position
- Below the diagonal: extraction.innerclasses uses a module listed above it, which is the healthy direction.
15→17 extraction.innerclasses uses extraction part of a loop✕
- Connections
- 5 pairs of types, where a type in extraction.innerclasses uses a type in extraction.
- The types involved
stainless.extraction.innerclasses.InnerClasses→stainless.extraction.CachingPhasestainless.extraction.innerclasses.InnerClasses→stainless.extraction.IdentitySortsstainless.extraction.innerclasses.InnerClasses→stainless.extraction.NoSummaryPhasestainless.extraction.innerclasses.InvalidInnerClassException→stainless.extraction.MalformedStainlessCodestainless.extraction.innerclasses.Trees→stainless.extraction.innerclasses
- Direction
- extraction.innerclasses uses extraction, so a change to extraction can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.
- 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→19 extraction.innerclasses uses extraction.oo part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.innerclasses uses a type in extraction.oo.
- The types involved
stainless.extraction.innerclasses.InnerClasses→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.innerclasses.InnerClasses→stainless.extraction.oo.SimpleClassesstainless.extraction.innerclasses.InnerClasses→stainless.extraction.oo.SimplyCachedClassesstainless.extraction.innerclasses.trees→stainless.extraction.oo.ClassSymbols
- Direction
- extraction.innerclasses uses extraction.oo, so a change to extraction.oo can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.oo.
- 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→20 extraction.innerclasses uses extraction.imperative.trees part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.innerclasses uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.innerclasses.InnerClasses→stainless.extraction.imperative.trees.Symbolsstainless.extraction.innerclasses.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.innerclasses uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.imperative.trees.
- 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→21 extraction.innerclasses uses extraction.oo.Definitions part of a loop✕
- Connections
- 3 pairs of types, where a type in extraction.innerclasses uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.innerclasses.InnerClasses→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.innerclasses.trees→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.innerclasses.trees→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.innerclasses uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.innerclasses, while a change to extraction.innerclasses can't break extraction.oo.Definitions.
- 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→23 extraction.innerclasses uses codegen.runtime part of a loop✕
- Connections
- 3 pairs of types, where a type in extraction.innerclasses uses a type in codegen.runtime.
- The types involved
stainless.extraction.innerclasses.DependencyGraph→stainless.codegen.runtime.Setstainless.extraction.innerclasses.ExprOps→stainless.codegen.runtime.Setstainless.extraction.innerclasses.trees→stainless.codegen.runtime.Map
- Direction
- extraction.innerclasses uses codegen.runtime, so a change to codegen.runtime can break extraction.innerclasses, while a change to extraction.innerclasses can't break codegen.runtime.
- 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→27 extraction.innerclasses uses ast part of a loop✕
- Connections
- 22 pairs of types, where a type in extraction.innerclasses uses a type in ast.
- The types involved
stainless.extraction.innerclasses.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.innerclasses.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.innerclasses.ConcreteTreeTransformer→stainless.ast.Treesstainless.extraction.innerclasses.DefinitionTransformer→stainless.ast.Treesstainless.extraction.innerclasses.DefinitionTraverser→stainless.ast.Treesstainless.extraction.innerclasses.Definitions→stainless.ast.Treesstainless.extraction.innerclasses.DependencyGraph→stainless.ast.DependencyGraphstainless.extraction.innerclasses.DependencyGraph→stainless.ast.Treesstainless.extraction.innerclasses.ExprOps→stainless.ast.Treesstainless.extraction.innerclasses.GhostTraverser→stainless.ast.Treesstainless.extraction.innerclasses.InnerClasses→stainless.ast.Treesstainless.extraction.innerclasses.Printer→stainless.ast.Printerstainless.extraction.innerclasses.Printer→stainless.ast.Treesstainless.extraction.innerclasses.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.innerclasses.TreeDeconstructor→stainless.ast.Treesstainless.extraction.innerclasses.Trees→stainless.ast.Definitionsstainless.extraction.innerclasses.Trees→stainless.ast.Treesstainless.extraction.innerclasses.Trees→stainless.ast.Typesstainless.extraction.innerclasses.TypeOps→stainless.ast.Treesstainless.extraction.innerclasses.TypeOps→stainless.ast.TypeOpsstainless.extraction.innerclasses.Types→stainless.ast.Treesstainless.extraction.innerclasses.trees→stainless.ast.Trees
- Direction
- extraction.innerclasses uses ast, so a change to ast can break extraction.innerclasses, while a change to extraction.innerclasses can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→31 extraction.innerclasses uses stainless part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.innerclasses uses a type in stainless.
- The types involved
stainless.extraction.innerclasses.InnerClasses→stainless.Context
- Direction
- extraction.innerclasses uses stainless, so a change to stainless can break extraction.innerclasses, while a change to extraction.innerclasses can't break stainless.
- 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→2 extraction.oo.TypeEncoding uses extraction.imperative.EffectElaboration✕
- Connections
- 1 pair of types, where a type in extraction.oo.TypeEncoding uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.extraction.oo.TypeEncoding.Scope→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- extraction.oo.TypeEncoding uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: extraction.oo.TypeEncoding uses a module listed above it, which is the healthy direction.
16→5 extraction.oo.TypeEncoding uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in extraction.oo.TypeEncoding uses a type in genc.ir.IR.
- The types involved
stainless.extraction.oo.TypeEncoding.Scope→stainless.genc.ir.IR.FunDefstainless.extraction.oo.TypeEncoding.Scope→stainless.genc.ir.IR.ValDefstainless.extraction.oo.TypeEncoding.TransformerContext→stainless.genc.ir.IR.FunDef
- Direction
- extraction.oo.TypeEncoding uses genc.ir.IR, so a change to genc.ir.IR can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.oo.TypeEncoding uses a module listed above it, which is the healthy direction.
16→6 extraction.oo.TypeEncoding uses genc.CAST✕
- Connections
- 4 pairs of types, where a type in extraction.oo.TypeEncoding uses a type in genc.CAST.
- The types involved
stainless.extraction.oo.TypeEncoding.ExprMapping→stainless.genc.CAST.Exprstainless.extraction.oo.TypeEncoding.ExprMapping→stainless.genc.CAST.Typestainless.extraction.oo.TypeEncoding.Scope→stainless.genc.CAST.Exprstainless.extraction.oo.TypeEncoding.Scope→stainless.genc.CAST.Type
- Direction
- extraction.oo.TypeEncoding uses genc.CAST, so a change to genc.CAST can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break genc.CAST.
- Position
- Below the diagonal: extraction.oo.TypeEncoding uses a module listed above it, which is the healthy direction.
16→11 extraction.oo.TypeEncoding uses extraction.innerfuns.Definitions✕
- Connections
- 2 pairs of types, where a type in extraction.oo.TypeEncoding uses a type in extraction.innerfuns.Definitions.
- The types involved
stainless.extraction.oo.TypeEncoding.FunInfo→stainless.extraction.innerfuns.Definitions.FunAbstractionstainless.extraction.oo.TypeEncoding.Scope→stainless.extraction.innerfuns.Definitions.FunAbstraction
- Direction
- extraction.oo.TypeEncoding uses extraction.innerfuns.Definitions, so a change to extraction.innerfuns.Definitions can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break extraction.innerfuns.Definitions.
- Position
- Below the diagonal: extraction.oo.TypeEncoding uses a module listed above it, which is the healthy direction.
16→14 extraction.oo.TypeEncoding uses extraction.imperative✕
- Connections
- 1 pair of types, where a type in extraction.oo.TypeEncoding uses a type in extraction.imperative.
- The types involved
stainless.extraction.oo.TypeEncoding.Scope→stainless.extraction.imperative.TransformerWithType
- Direction
- extraction.oo.TypeEncoding uses extraction.imperative, so a change to extraction.imperative can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break extraction.imperative.
- Position
- Below the diagonal: extraction.oo.TypeEncoding uses a module listed above it, which is the healthy direction.
16→20 extraction.oo.TypeEncoding uses extraction.imperative.trees part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.oo.TypeEncoding uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.oo.TypeEncoding.TransformerContext→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.oo.TypeEncoding uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break extraction.imperative.trees.
- 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 extraction.oo.TypeEncoding uses codegen.runtime part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.oo.TypeEncoding uses a type in codegen.runtime.
- The types involved
stainless.extraction.oo.TypeEncoding.FunInfo→stainless.codegen.runtime.Setstainless.extraction.oo.TypeEncoding.Scope→stainless.codegen.runtime.Mapstainless.extraction.oo.TypeEncoding.Scope→stainless.codegen.runtime.Setstainless.extraction.oo.TypeEncoding.SummaryData→stainless.codegen.runtime.Set
- Direction
- extraction.oo.TypeEncoding uses codegen.runtime, so a change to codegen.runtime can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break codegen.runtime.
- 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→24 extraction.oo.TypeEncoding uses ast.Expressions part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.oo.TypeEncoding uses a type in ast.Expressions.
- The types involved
stainless.extraction.oo.TypeEncoding.Scope→stainless.ast.Expressions.Pattern
- Direction
- extraction.oo.TypeEncoding uses ast.Expressions, so a change to ast.Expressions can break extraction.oo.TypeEncoding, while a change to extraction.oo.TypeEncoding can't break ast.Expressions.
- 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→2 extraction uses extraction.imperative.EffectElaboration✕
- Connections
- 5 pairs of types, where a type in extraction uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.extraction.CachingPhase→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.ExtractionContext→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.IdentityFunctions→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.IdentitySorts→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.SimplePhase→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- extraction uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break extraction, while a change to extraction can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
17→5 extraction uses genc.ir.IR✕
- Connections
- 7 pairs of types, where a type in extraction uses a type in genc.ir.IR.
- The types involved
stainless.extraction.CachingPhase→stainless.genc.ir.IR.FunDefstainless.extraction.CheckingTransformer→stainless.genc.ir.IR.ValDefstainless.extraction.IdentityFunctions→stainless.genc.ir.IR.FunDefstainless.extraction.SimpleFunctions→stainless.genc.ir.IR.FunDefstainless.extraction.SimplePhase→stainless.genc.ir.IR.FunDefstainless.extraction.SimplyCachedFunctions→stainless.genc.ir.IR.FunDefstainless.extraction.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction uses genc.ir.IR, so a change to genc.ir.IR can break extraction, while a change to extraction can't break genc.ir.IR.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
17→6 extraction uses genc.CAST✕
- Connections
- 3 pairs of types, where a type in extraction uses a type in genc.CAST.
- The types involved
stainless.extraction.CheckingTransformer→stainless.genc.CAST.Exprstainless.extraction.CheckingTransformer→stainless.genc.CAST.Typestainless.extraction.MalformedStainlessCode→stainless.genc.CAST.Tree
- Direction
- extraction uses genc.CAST, so a change to genc.CAST can break extraction, while a change to extraction can't break genc.CAST.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
17→15 extraction uses extraction.innerclasses✕
- Connections
- 1 pair of types, where a type in extraction uses a type in extraction.innerclasses.
- The types involved
stainless.extraction.CheckingTransformer→stainless.extraction.innerclasses.TreeTransformer
- Direction
- extraction uses extraction.innerclasses, so a change to extraction.innerclasses can break extraction, while a change to extraction can't break extraction.innerclasses.
- Position
- Below the diagonal: extraction uses a module listed above it, which is the healthy direction.
17→20 extraction uses extraction.imperative.trees part of a loop✕
- Connections
- 7 pairs of types, where a type in extraction uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.CachingPhase→stainless.extraction.imperative.trees.Symbolsstainless.extraction.ExtractionCaches→stainless.extraction.imperative.trees.Symbolsstainless.extraction.ExtractionContext→stainless.extraction.imperative.trees.Symbolsstainless.extraction.ExtractionPipeline→stainless.extraction.imperative.trees.Symbolsstainless.extraction.SimpleFunctions→stainless.extraction.imperative.trees.Symbolsstainless.extraction.SimpleSorts→stainless.extraction.imperative.trees.Symbolsstainless.extraction.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction, while a change to extraction can't break extraction.imperative.trees.
- 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→23 extraction uses codegen.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in extraction uses a type in codegen.runtime.
- The types involved
stainless.extraction.trees→stainless.codegen.runtime.Map
- Direction
- extraction uses codegen.runtime, so a change to codegen.runtime can break extraction, while a change to extraction can't break codegen.runtime.
- 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→24 extraction uses ast.Expressions part of a loop✕
- Connections
- 1 pair of types, where a type in extraction uses a type in ast.Expressions.
- The types involved
stainless.extraction.CheckingTransformer→stainless.ast.Expressions.Pattern
- Direction
- extraction uses ast.Expressions, so a change to ast.Expressions can break extraction, while a change to extraction can't break ast.Expressions.
- 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→27 extraction uses ast part of a loop✕
- Connections
- 10 pairs of types, where a type in extraction uses a type in ast.
- The types involved
stainless.extraction.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.ExprOps→stainless.ast.Treesstainless.extraction.ExtractionPipeline→stainless.ast.Treesstainless.extraction.Printer→stainless.ast.Printerstainless.extraction.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.TreeDeconstructor→stainless.ast.Treesstainless.extraction.Trees→stainless.ast.ExprOpsstainless.extraction.Trees→stainless.ast.Treesstainless.extraction.trees→stainless.ast.Trees
- Direction
- extraction uses ast, so a change to ast can break extraction, while a change to extraction can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→31 extraction uses stainless part of a loop✕
- Connections
- 11 pairs of types, where a type in extraction uses a type in stainless.
- The types involved
stainless.extraction.ExtractionPipeline→stainless.Contextstainless.extraction.imperative→stainless.Contextstainless.extraction.inlining→stainless.Contextstainless.extraction.innerclasses→stainless.Contextstainless.extraction.innerfuns→stainless.Contextstainless.extraction.methods→stainless.Contextstainless.extraction.oo→stainless.Contextstainless.extraction.termination→stainless.Contextstainless.extraction.throwing→stainless.Contextstainless.extraction.trace→stainless.Contextstainless.extraction.xlang→stainless.Context
- Direction
- extraction uses stainless, so a change to stainless can break extraction, while a change to extraction can't break stainless.
- 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→5 transformers uses genc.ir.IR✕
- Connections
- 2 pairs of types, where a type in transformers uses a type in genc.ir.IR.
- The types involved
stainless.transformers.GhostTraverser→stainless.genc.ir.IR.FunDefstainless.transformers.GhostTraverser→stainless.genc.ir.IR.ValDef
- Direction
- transformers uses genc.ir.IR, so a change to genc.ir.IR can break transformers, while a change to transformers can't break genc.ir.IR.
- Position
- Below the diagonal: transformers uses a module listed above it, which is the healthy direction.
18→6 transformers uses genc.CAST✕
- Connections
- 7 pairs of types, where a type in transformers uses a type in genc.CAST.
- The types involved
stainless.transformers.GhostTraverser→stainless.genc.CAST.Exprstainless.transformers.LatticesSimplifier→stainless.genc.CAST.Exprstainless.transformers.PartialEvaluator→stainless.genc.CAST.Exprstainless.transformers.SimplifierWithPC→stainless.genc.CAST.Exprstainless.transformers.Transformer→stainless.genc.CAST.Exprstainless.transformers.TransformerWithPC→stainless.genc.CAST.Exprstainless.transformers.Traverser→stainless.genc.CAST.Expr
- Direction
- transformers uses genc.CAST, so a change to genc.CAST can break transformers, while a change to transformers can't break genc.CAST.
- Position
- Below the diagonal: transformers uses a module listed above it, which is the healthy direction.
18→8 transformers uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 9 pairs of types, where a type in transformers uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.transformers.PartialEvaluator→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.SimplifierWithPC→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.Transformer→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.TransformerWithPC→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.TransformerWithPatternOp→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.Traverser→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.TraverserWithPatternOp→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.TreeTransformer→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.TreeTraverser→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- transformers uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break transformers, while a change to transformers can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: transformers uses a module listed above it, which is the healthy direction.
18→12 transformers uses genc.ir✕
- Connections
- 5 pairs of types, where a type in transformers uses a type in genc.ir.
- The types involved
stainless.transformers.DefinitionTransformer→stainless.genc.ir.Transformerstainless.transformers.SimplifierWithPC→stainless.genc.ir.Transformerstainless.transformers.Transformer→stainless.genc.ir.Transformerstainless.transformers.TransformerWithPC→stainless.genc.ir.Transformerstainless.transformers.TransformerWithPatternOp→stainless.genc.ir.Transformer
- Direction
- transformers uses genc.ir, so a change to genc.ir can break transformers, while a change to transformers can't break genc.ir.
- Position
- Below the diagonal: transformers uses a module listed above it, which is the healthy direction.
18→14 transformers uses extraction.imperative✕
- Connections
- 1 pair of types, where a type in transformers uses a type in extraction.imperative.
- The types involved
stainless.transformers.TransformerWithPC→stainless.extraction.imperative.TransformerWithPC
- Direction
- transformers uses extraction.imperative, so a change to extraction.imperative can break transformers, while a change to transformers can't break extraction.imperative.
- Position
- Below the diagonal: transformers uses a module listed above it, which is the healthy direction.
18→15 transformers uses extraction.innerclasses✕
- Connections
- 8 pairs of types, where a type in transformers uses a type in extraction.innerclasses.
- The types involved
stainless.transformers.ConcreteTreeTransformer→stainless.extraction.innerclasses.TreeTransformerstainless.transformers.DefinitionTransformer→stainless.extraction.innerclasses.DefinitionTransformerstainless.transformers.DefinitionTraverser→stainless.extraction.innerclasses.DefinitionTraverserstainless.transformers.GhostTraverser→stainless.extraction.innerclasses.DefinitionTraverserstainless.transformers.TreeTransformer→stainless.extraction.innerclasses.DefinitionTransformerstainless.transformers.TreeTransformer→stainless.extraction.innerclasses.TreeTransformerstainless.transformers.TreeTraverser→stainless.extraction.innerclasses.DefinitionTraverserstainless.transformers.TreeTraverser→stainless.extraction.innerclasses.TreeTraverser
- Direction
- transformers uses extraction.innerclasses, so a change to extraction.innerclasses can break transformers, while a change to transformers can't break extraction.innerclasses.
- Position
- Below the diagonal: transformers uses a module listed above it, which is the healthy direction.
18→20 transformers uses extraction.imperative.trees part of a loop✕
- Connections
- 3 pairs of types, where a type in transformers uses a type in extraction.imperative.trees.
- The types involved
stainless.transformers.GhostTraverser→stainless.extraction.imperative.trees.Symbolsstainless.transformers.LatticesSimplifier→stainless.extraction.imperative.trees.Symbolsstainless.transformers.TransformerWithPC→stainless.extraction.imperative.trees.Symbols
- Direction
- transformers uses extraction.imperative.trees, so a change to extraction.imperative.trees can break transformers, while a change to transformers can't break extraction.imperative.trees.
- 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→24 transformers uses ast.Expressions part of a loop✕
- Connections
- 8 pairs of types, where a type in transformers uses a type in ast.Expressions.
- The types involved
stainless.transformers.Transformer→stainless.ast.Expressions.MatchCasestainless.transformers.Transformer→stainless.ast.Expressions.Patternstainless.transformers.TransformerWithPC→stainless.ast.Expressions.MatchCasestainless.transformers.TransformerWithPatternOp→stainless.ast.Expressions.Patternstainless.transformers.Traverser→stainless.ast.Expressions.Patternstainless.transformers.TraverserWithPatternOp→stainless.ast.Expressions.Patternstainless.transformers.TreeTransformer→stainless.ast.Expressions.Patternstainless.transformers.TreeTraverser→stainless.ast.Expressions.Pattern
- Direction
- transformers uses ast.Expressions, so a change to ast.Expressions can break transformers, while a change to transformers can't break ast.Expressions.
- 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→27 transformers uses ast part of a loop✕
- Connections
- 6 pairs of types, where a type in transformers uses a type in ast.
- The types involved
stainless.transformers.ConcreteTreeTransformer→stainless.ast.Treesstainless.transformers.GhostTraverser→stainless.ast.Treesstainless.transformers.LatticesSimplifier→stainless.ast.Treesstainless.transformers.SimplifierWithPC→stainless.ast.Treesstainless.transformers.Transformer→stainless.ast.Treesstainless.transformers.Traverser→stainless.ast.Trees
- Direction
- transformers uses ast, so a change to ast can break transformers, while a change to transformers can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→31 transformers uses stainless part of a loop✕
- Connections
- 1 pair of types, where a type in transformers uses a type in stainless.
- The types involved
stainless.transformers.SimplifierWithSolver→stainless.Context
- Direction
- transformers uses stainless, so a change to stainless can break transformers, while a change to transformers can't break stainless.
- 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→1 extraction.oo uses algebra.ops✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in algebra.ops.
- The types involved
stainless.extraction.oo.TypeOps→stainless.algebra.ops.List
- Direction
- extraction.oo uses algebra.ops, so a change to algebra.ops can break extraction.oo, while a change to extraction.oo can't break algebra.ops.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→2 extraction.oo uses extraction.imperative.EffectElaboration✕
- Connections
- 7 pairs of types, where a type in extraction.oo uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.oo.CachingPhase→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.oo.IdentityClasses→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.oo.IdentityTypeDefs→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.oo.InvariantInitialization→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.oo.SimplePhase→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.oo.TypeEncoding→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- extraction.oo uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break extraction.oo, while a change to extraction.oo can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→3 extraction.oo uses extraction.oo.Trees✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in extraction.oo.Trees.
- The types involved
stainless.extraction.oo.TypeOps→stainless.extraction.oo.Trees.ClassType
- Direction
- extraction.oo uses extraction.oo.Trees, so a change to extraction.oo.Trees can break extraction.oo, while a change to extraction.oo can't break extraction.oo.Trees.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→4 extraction.oo uses lang✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in lang.
- The types involved
stainless.extraction.oo.Printer→stainless.lang.Either
- Direction
- extraction.oo uses lang, so a change to lang can break extraction.oo, while a change to extraction.oo can't break lang.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→5 extraction.oo uses genc.ir.IR✕
- Connections
- 6 pairs of types, where a type in extraction.oo uses a type in genc.ir.IR.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.genc.ir.IR.FunDefstainless.extraction.oo.ClassSymbols→stainless.genc.ir.IR.FunDefstainless.extraction.oo.SymbolOps→stainless.genc.ir.IR.ValDefstainless.extraction.oo.Trees→stainless.genc.ir.IR.ValDefstainless.extraction.oo.TypeEncoding→stainless.genc.ir.IR.FunDefstainless.extraction.oo.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction.oo uses genc.ir.IR, so a change to genc.ir.IR can break extraction.oo, while a change to extraction.oo can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→6 extraction.oo uses genc.CAST✕
- Connections
- 14 pairs of types, where a type in extraction.oo uses a type in genc.CAST.
- The types involved
stainless.extraction.oo.Definitions→stainless.genc.CAST.Exprstainless.extraction.oo.ExprOps→stainless.genc.CAST.Exprstainless.extraction.oo.GhostTraverser→stainless.genc.CAST.Exprstainless.extraction.oo.Printer→stainless.genc.CAST.Treestainless.extraction.oo.SymbolOps→stainless.genc.CAST.Exprstainless.extraction.oo.SymbolOps→stainless.genc.CAST.Typestainless.extraction.oo.TransformerWithType→stainless.genc.CAST.Exprstainless.extraction.oo.TransformerWithType→stainless.genc.CAST.Typestainless.extraction.oo.TreeDeconstructor→stainless.genc.CAST.Exprstainless.extraction.oo.TreeDeconstructor→stainless.genc.CAST.Typestainless.extraction.oo.Trees→stainless.genc.CAST.Typestainless.extraction.oo.TypeEncoding→stainless.genc.CAST.Exprstainless.extraction.oo.TypeEncoding→stainless.genc.CAST.Typestainless.extraction.oo.TypeOps→stainless.genc.CAST.Type
- Direction
- extraction.oo uses genc.CAST, so a change to genc.CAST can break extraction.oo, while a change to extraction.oo can't break genc.CAST.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→10 extraction.oo uses genc✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in genc.
- The types involved
stainless.extraction.oo.Printer→stainless.genc.PrinterContext
- Direction
- extraction.oo uses genc, so a change to genc can break extraction.oo, while a change to extraction.oo can't break genc.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→12 extraction.oo uses genc.ir✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in genc.ir.
- The types involved
stainless.extraction.oo.DefinitionTransformer→stainless.genc.ir.Transformer
- Direction
- extraction.oo uses genc.ir, so a change to genc.ir can break extraction.oo, while a change to extraction.oo can't break genc.ir.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→14 extraction.oo uses extraction.imperative✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in extraction.imperative.
- The types involved
stainless.extraction.oo.GhostTraverser→stainless.extraction.imperative.GhostTraverser
- Direction
- extraction.oo uses extraction.imperative, so a change to extraction.imperative can break extraction.oo, while a change to extraction.oo can't break extraction.imperative.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→15 extraction.oo uses extraction.innerclasses✕
- Connections
- 8 pairs of types, where a type in extraction.oo uses a type in extraction.innerclasses.
- The types involved
stainless.extraction.oo.ConcreteTreeTransformer→stainless.extraction.innerclasses.TreeTransformerstainless.extraction.oo.DefinitionTransformer→stainless.extraction.innerclasses.DefinitionTransformerstainless.extraction.oo.DefinitionTraverser→stainless.extraction.innerclasses.DefinitionTraverserstainless.extraction.oo.TransformerWithType→stainless.extraction.innerclasses.TreeTransformerstainless.extraction.oo.TreeTransformer→stainless.extraction.innerclasses.DefinitionTransformerstainless.extraction.oo.TreeTransformer→stainless.extraction.innerclasses.TreeTransformerstainless.extraction.oo.TreeTraverser→stainless.extraction.innerclasses.DefinitionTraverserstainless.extraction.oo.TreeTraverser→stainless.extraction.innerclasses.TreeTraverser
- Direction
- extraction.oo uses extraction.innerclasses, so a change to extraction.innerclasses can break extraction.oo, while a change to extraction.oo can't break extraction.innerclasses.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→16 extraction.oo uses extraction.oo.TypeEncoding✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in extraction.oo.TypeEncoding.
- The types involved
stainless.extraction.oo.TypeEncoding→stainless.extraction.oo.TypeEncoding.Scope
- Direction
- extraction.oo uses extraction.oo.TypeEncoding, so a change to extraction.oo.TypeEncoding can break extraction.oo, while a change to extraction.oo can't break extraction.oo.TypeEncoding.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→17 extraction.oo uses extraction✕
- Connections
- 27 pairs of types, where a type in extraction.oo uses a type in extraction. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.extraction.CachingPhasestainless.extraction.oo.AdtSpecialization→stainless.extraction.NoSummaryPhasestainless.extraction.oo.AdtSpecialization→stainless.extraction.SimpleFunctionsstainless.extraction.oo.AdtSpecialization→stainless.extraction.SimpleSortsstainless.extraction.oo.CachingPhase→stainless.extraction.CachingPhasestainless.extraction.oo.CachingPhase→stainless.extraction.ExtractionCachesstainless.extraction.oo.CachingPhase→stainless.extraction.ExtractionContextstainless.extraction.oo.ExtractionCaches→stainless.extraction.ExtractionCachesstainless.extraction.oo.ExtractionContext→stainless.extraction.ExtractionContextstainless.extraction.oo.ExtractionContext→stainless.extraction.ExtractionPipelinestainless.extraction.oo.ExtractionPipeline→stainless.extraction.ExtractionPipelinestainless.extraction.oo.InvariantInitialization→stainless.extraction.CachingPhasestainless.extraction.oo.InvariantInitialization→stainless.extraction.IdentityFunctionsstainless.extraction.oo.InvariantInitialization→stainless.extraction.NoSummaryPhasestainless.extraction.oo.NoSummaryPhase→stainless.extraction.CachingPhasestainless.extraction.oo.NoSummaryPhase→stainless.extraction.NoSummaryPhasestainless.extraction.oo.SimpleClasses→stainless.extraction.CachingPhasestainless.extraction.oo.SimplePhase→stainless.extraction.CachingPhasestainless.extraction.oo.SimplePhase→stainless.extraction.NoSummaryPhasestainless.extraction.oo.SimplePhase→stainless.extraction.SimplePhasestainless.extraction.oo.SimpleTypeDefs→stainless.extraction.CachingPhasestainless.extraction.oo.SimplyCachedClasses→stainless.extraction.CachingPhasestainless.extraction.oo.SimplyCachedTypeDefs→stainless.extraction.CachingPhasestainless.extraction.oo.TypeEncoding→stainless.extraction.CachingPhasestainless.extraction.oo.TypeEncoding→stainless.extraction.ExtractionPipeline
- Direction
- extraction.oo uses extraction, so a change to extraction can break extraction.oo, while a change to extraction.oo can't break extraction.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→18 extraction.oo uses transformers✕
- Connections
- 1 pair of types, where a type in extraction.oo uses a type in transformers.
- The types involved
stainless.extraction.oo.DefinitionTraverser→stainless.transformers.Traverser
- Direction
- extraction.oo uses transformers, so a change to transformers can break extraction.oo, while a change to extraction.oo can't break transformers.
- Position
- Below the diagonal: extraction.oo uses a module listed above it, which is the healthy direction.
19→20 extraction.oo uses extraction.imperative.trees part of a loop✕
- Connections
- 12 pairs of types, where a type in extraction.oo uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.CachingPhase→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.ClassSymbols→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.ExtractionCaches→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.InvariantInitialization→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.SimpleClasses→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.SimpleSymbolTransformer→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.SimpleTypeDefs→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.TransformerWithType→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Trees→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.TypeEncoding→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.oo uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.oo, while a change to extraction.oo can't break extraction.imperative.trees.
- 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→21 extraction.oo uses extraction.oo.Definitions part of a loop✕
- Connections
- 24 pairs of types, where a type in extraction.oo uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.AdtSpecialization→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.CachingPhase→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.CachingPhase→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.ClassSymbols→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.ClassSymbols→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.DefinitionTransformer→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.DefinitionTransformer→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.DefinitionTraverser→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.DefinitionTraverser→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.IdentityClasses→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.IdentityTypeDefs→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.SimpleClasses→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.SimplePhase→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.SimplePhase→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.SimpleSymbolTransformer→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.SimpleSymbolTransformer→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.SimpleTypeDefs→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.SimplyCachedClasses→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.SimplyCachedTypeDefs→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.TypeEncoding→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.TypeEncoding→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.oo.trees→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.oo.trees→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.oo uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.oo, while a change to extraction.oo can't break extraction.oo.Definitions.
- 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→23 extraction.oo uses codegen.runtime part of a loop✕
- Connections
- 5 pairs of types, where a type in extraction.oo uses a type in codegen.runtime.
- The types involved
stainless.extraction.oo.ClassSymbols→stainless.codegen.runtime.Mapstainless.extraction.oo.DependencyGraph→stainless.codegen.runtime.Setstainless.extraction.oo.SymbolOps→stainless.codegen.runtime.Mapstainless.extraction.oo.TypeEncoding→stainless.codegen.runtime.Lambdastainless.extraction.oo.trees→stainless.codegen.runtime.Map
- Direction
- extraction.oo uses codegen.runtime, so a change to codegen.runtime can break extraction.oo, while a change to extraction.oo can't break codegen.runtime.
- 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→24 extraction.oo uses ast.Expressions part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.oo uses a type in ast.Expressions.
- The types involved
stainless.extraction.oo.SymbolOps→stainless.ast.Expressions.Patternstainless.extraction.oo.TransformerWithType→stainless.ast.Expressions.Patternstainless.extraction.oo.TreeDeconstructor→stainless.ast.Expressions.Patternstainless.extraction.oo.TypeOps→stainless.ast.Expressions.Pattern
- Direction
- extraction.oo uses ast.Expressions, so a change to ast.Expressions can break extraction.oo, while a change to extraction.oo can't break ast.Expressions.
- 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→27 extraction.oo uses ast part of a loop✕
- Connections
- 29 pairs of types, where a type in extraction.oo uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.ast.Treesstainless.extraction.oo.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.oo.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.oo.ConcreteTreeTransformer→stainless.ast.Treesstainless.extraction.oo.DefinitionTransformer→stainless.ast.Treesstainless.extraction.oo.DefinitionTraverser→stainless.ast.Treesstainless.extraction.oo.Definitions→stainless.ast.Treesstainless.extraction.oo.DependencyGraph→stainless.ast.DependencyGraphstainless.extraction.oo.DependencyGraph→stainless.ast.Treesstainless.extraction.oo.ExprOps→stainless.ast.Treesstainless.extraction.oo.ExtractionPipeline→stainless.ast.Treesstainless.extraction.oo.GhostTraverser→stainless.ast.Treesstainless.extraction.oo.InvariantInitialization→stainless.ast.Treesstainless.extraction.oo.Printer→stainless.ast.Printerstainless.extraction.oo.Printer→stainless.ast.Treesstainless.extraction.oo.SimpleClasses→stainless.ast.Treesstainless.extraction.oo.SimpleSymbolTransformer→stainless.ast.Treesstainless.extraction.oo.SimpleTypeDefs→stainless.ast.Treesstainless.extraction.oo.SymbolOps→stainless.ast.SymbolOpsstainless.extraction.oo.SymbolOps→stainless.ast.TypeOpsstainless.extraction.oo.TransformerWithType→stainless.ast.Treesstainless.extraction.oo.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.oo.TreeDeconstructor→stainless.ast.Treesstainless.extraction.oo.Trees→stainless.ast.Definitionsstainless.extraction.oo.Trees→stainless.ast.Trees
- Direction
- extraction.oo uses ast, so a change to ast can break extraction.oo, while a change to extraction.oo can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→31 extraction.oo uses stainless part of a loop✕
- Connections
- 3 pairs of types, where a type in extraction.oo uses a type in stainless.
- The types involved
stainless.extraction.oo.AdtSpecialization→stainless.Contextstainless.extraction.oo.InvariantInitialization→stainless.Contextstainless.extraction.oo.TypeEncoding→stainless.Context
- Direction
- extraction.oo uses stainless, so a change to stainless can break extraction.oo, while a change to extraction.oo can't break stainless.
- 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→5 extraction.imperative.trees uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in extraction.imperative.trees uses a type in genc.ir.IR.
- The types involved
stainless.extraction.imperative.trees.Symbols→stainless.genc.ir.IR.FunDef
- Direction
- extraction.imperative.trees uses genc.ir.IR, so a change to genc.ir.IR can break extraction.imperative.trees, while a change to extraction.imperative.trees can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.imperative.trees uses a module listed above it, which is the healthy direction.
20→19 extraction.imperative.trees uses extraction.oo✕
- Connections
- 1 pair of types, where a type in extraction.imperative.trees uses a type in extraction.oo.
- The types involved
stainless.extraction.imperative.trees.Symbols→stainless.extraction.oo.ClassSymbols
- Direction
- extraction.imperative.trees uses extraction.oo, so a change to extraction.oo can break extraction.imperative.trees, while a change to extraction.imperative.trees can't break extraction.oo.
- Position
- Below the diagonal: extraction.imperative.trees uses a module listed above it, which is the healthy direction.
20→21 extraction.imperative.trees uses extraction.oo.Definitions part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.imperative.trees uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.imperative.trees.Symbols→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.imperative.trees.Symbols→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.imperative.trees uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.imperative.trees, while a change to extraction.imperative.trees can't break extraction.oo.Definitions.
- 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→23 extraction.imperative.trees uses codegen.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.imperative.trees uses a type in codegen.runtime.
- The types involved
stainless.extraction.imperative.trees.Symbols→stainless.codegen.runtime.Map
- Direction
- extraction.imperative.trees uses codegen.runtime, so a change to codegen.runtime can break extraction.imperative.trees, while a change to extraction.imperative.trees can't break codegen.runtime.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→27 extraction.imperative.trees uses ast part of a loop✕
- Connections
- 1 pair of types, where a type in extraction.imperative.trees uses a type in ast.
- The types involved
stainless.extraction.imperative.trees.printer→stainless.ast.Printer
- Direction
- extraction.imperative.trees uses ast, so a change to ast can break extraction.imperative.trees, while a change to extraction.imperative.trees can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→3 extraction.oo.Definitions uses extraction.oo.Trees✕
- Connections
- 3 pairs of types, where a type in extraction.oo.Definitions uses a type in extraction.oo.Trees.
- The types involved
stainless.extraction.oo.Definitions.AppliedTypeDef→stainless.extraction.oo.Trees.TypeBoundsstainless.extraction.oo.Definitions.ClassDef→stainless.extraction.oo.Trees.ClassTypestainless.extraction.oo.Definitions.TypeDef→stainless.extraction.oo.Trees.TypeBounds
- Direction
- extraction.oo.Definitions uses extraction.oo.Trees, so a change to extraction.oo.Trees can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break extraction.oo.Trees.
- Position
- Below the diagonal: extraction.oo.Definitions uses a module listed above it, which is the healthy direction.
21→4 extraction.oo.Definitions uses lang✕
- Connections
- 1 pair of types, where a type in extraction.oo.Definitions uses a type in lang.
- The types involved
stainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.lang.MutableMap
- Direction
- extraction.oo.Definitions uses lang, so a change to lang can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break lang.
- Position
- Below the diagonal: extraction.oo.Definitions uses a module listed above it, which is the healthy direction.
21→5 extraction.oo.Definitions uses genc.ir.IR✕
- Connections
- 2 pairs of types, where a type in extraction.oo.Definitions uses a type in genc.ir.IR.
- The types involved
stainless.extraction.oo.Definitions.ClassDef→stainless.genc.ir.IR.ValDefstainless.extraction.oo.Definitions.TypedClassDef→stainless.genc.ir.IR.ValDef
- Direction
- extraction.oo.Definitions uses genc.ir.IR, so a change to genc.ir.IR can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.oo.Definitions uses a module listed above it, which is the healthy direction.
21→6 extraction.oo.Definitions uses genc.CAST✕
- Connections
- 8 pairs of types, where a type in extraction.oo.Definitions uses a type in genc.CAST.
- The types involved
stainless.extraction.oo.Definitions.AppliedTypeDef→stainless.genc.CAST.Treestainless.extraction.oo.Definitions.AppliedTypeDef→stainless.genc.CAST.Typestainless.extraction.oo.Definitions.Bounds→stainless.genc.CAST.Typestainless.extraction.oo.Definitions.ClassDef→stainless.genc.CAST.Typestainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.genc.CAST.Typestainless.extraction.oo.Definitions.TypeDef→stainless.genc.CAST.Typestainless.extraction.oo.Definitions.TypedClassDef→stainless.genc.CAST.Treestainless.extraction.oo.Definitions.TypedClassDef→stainless.genc.CAST.Type
- Direction
- extraction.oo.Definitions uses genc.CAST, so a change to genc.CAST can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break genc.CAST.
- Position
- Below the diagonal: extraction.oo.Definitions uses a module listed above it, which is the healthy direction.
21→11 extraction.oo.Definitions uses extraction.innerfuns.Definitions✕
- Connections
- 1 pair of types, where a type in extraction.oo.Definitions uses a type in extraction.innerfuns.Definitions.
- The types involved
stainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.extraction.innerfuns.Definitions.InnerFunsAbstractSymbols
- Direction
- extraction.oo.Definitions uses extraction.innerfuns.Definitions, so a change to extraction.innerfuns.Definitions can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break extraction.innerfuns.Definitions.
- Position
- Below the diagonal: extraction.oo.Definitions uses a module listed above it, which is the healthy direction.
21→20 extraction.oo.Definitions uses extraction.imperative.trees✕
- Connections
- 5 pairs of types, where a type in extraction.oo.Definitions uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.oo.Definitions.AppliedTypeDef→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Definitions.ClassDef→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Definitions.TypeDef→stainless.extraction.imperative.trees.Symbolsstainless.extraction.oo.Definitions.TypedClassDef→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.oo.Definitions uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break extraction.imperative.trees.
- Position
- Below the diagonal: extraction.oo.Definitions uses a module listed above it, which is the healthy direction.
21→23 extraction.oo.Definitions uses codegen.runtime part of a loop✕
- Connections
- 2 pairs of types, where a type in extraction.oo.Definitions uses a type in codegen.runtime.
- The types involved
stainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.codegen.runtime.Mapstainless.extraction.oo.Definitions.TypedClassDef→stainless.codegen.runtime.Map
- Direction
- extraction.oo.Definitions uses codegen.runtime, so a change to codegen.runtime can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break codegen.runtime.
- 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→27 extraction.oo.Definitions uses ast part of a loop✕
- Connections
- 4 pairs of types, where a type in extraction.oo.Definitions uses a type in ast.
- The types involved
stainless.extraction.oo.Definitions.ClassDef→stainless.ast.SymbolIdentifierstainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.ast.DependencyGraphstainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.ast.SymbolOpsstainless.extraction.oo.Definitions.OOAbstractSymbols→stainless.ast.TypeOps
- Direction
- extraction.oo.Definitions uses ast, so a change to ast can break extraction.oo.Definitions, while a change to extraction.oo.Definitions can't break ast.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 genc.phases.IR2CImpl uses algebra.ops✕
- Connections
- 1 pair of types, where a type in genc.phases.IR2CImpl uses a type in algebra.ops.
- The types involved
stainless.genc.phases.IR2CImpl.CmpFactory→stainless.algebra.ops.List
- Direction
- genc.phases.IR2CImpl uses algebra.ops, so a change to algebra.ops can break genc.phases.IR2CImpl, while a change to genc.phases.IR2CImpl can't break algebra.ops.
- Position
- Below the diagonal: genc.phases.IR2CImpl uses a module listed above it, which is the healthy direction.
22→5 genc.phases.IR2CImpl uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in genc.phases.IR2CImpl uses a type in genc.ir.IR.
- The types involved
stainless.genc.phases.IR2CImpl.CmpFactory→stainless.genc.ir.IR.FunBodyASTstainless.genc.phases.IR2CImpl.CmpFactory→stainless.genc.ir.IR.FunDefstainless.genc.phases.IR2CImpl.CmpFactory→stainless.genc.ir.IR.FunVal
- Direction
- genc.phases.IR2CImpl uses genc.ir.IR, so a change to genc.ir.IR can break genc.phases.IR2CImpl, while a change to genc.phases.IR2CImpl can't break genc.ir.IR.
- Position
- Below the diagonal: genc.phases.IR2CImpl uses a module listed above it, which is the healthy direction.
22→6 genc.phases.IR2CImpl uses genc.CAST✕
- Connections
- 3 pairs of types, where a type in genc.phases.IR2CImpl uses a type in genc.CAST.
- The types involved
stainless.genc.phases.IR2CImpl.CmpFactory→stainless.genc.CAST.Bindingstainless.genc.phases.IR2CImpl.CmpFactory→stainless.genc.CAST.Exprstainless.genc.phases.IR2CImpl.CmpFactory→stainless.genc.CAST.Type
- Direction
- genc.phases.IR2CImpl uses genc.CAST, so a change to genc.CAST can break genc.phases.IR2CImpl, while a change to genc.phases.IR2CImpl can't break genc.CAST.
- Position
- Below the diagonal: genc.phases.IR2CImpl uses a module listed above it, which is the healthy direction.
22→21 genc.phases.IR2CImpl uses extraction.oo.Definitions✕
- Connections
- 1 pair of types, where a type in genc.phases.IR2CImpl uses a type in extraction.oo.Definitions.
- The types involved
stainless.genc.phases.IR2CImpl.CmpFactory→stainless.extraction.oo.Definitions.ClassDef
- Direction
- genc.phases.IR2CImpl uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break genc.phases.IR2CImpl, while a change to genc.phases.IR2CImpl can't break extraction.oo.Definitions.
- Position
- Below the diagonal: genc.phases.IR2CImpl uses a module listed above it, which is the healthy direction.
23→4 codegen.runtime uses lang✕
- Connections
- 3 pairs of types, where a type in codegen.runtime uses a type in lang.
- The types involved
stainless.codegen.runtime.Bag→stainless.lang.MutableMapstainless.codegen.runtime.BigArray→stainless.lang.MutableMapstainless.codegen.runtime.Map→stainless.lang.MutableMap
- Direction
- codegen.runtime uses lang, so a change to lang can break codegen.runtime, while a change to codegen.runtime can't break lang.
- Position
- Below the diagonal: codegen.runtime uses a module listed above it, which is the healthy direction.
23→22 codegen.runtime uses genc.phases.IR2CImpl✕
- Connections
- 10 pairs of types, where a type in codegen.runtime uses a type in genc.phases.IR2CImpl.
- The types involved
stainless.codegen.runtime.ADT→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.AnyRefBox→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.BitVector→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.BooleanBox→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.Box→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.BoxedArray→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.IntBox→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.Lambda→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.Monitor→stainless.genc.phases.IR2CImpl.Arraystainless.codegen.runtime.Set→stainless.genc.phases.IR2CImpl.Array
- Direction
- codegen.runtime uses genc.phases.IR2CImpl, so a change to genc.phases.IR2CImpl can break codegen.runtime, while a change to codegen.runtime can't break genc.phases.IR2CImpl.
- Position
- Below the diagonal: codegen.runtime uses a module listed above it, which is the healthy direction.
24→5 ast.Expressions uses genc.ir.IR✕
- Connections
- 8 pairs of types, where a type in ast.Expressions uses a type in genc.ir.IR.
- The types involved
stainless.ast.Expressions.ADTPattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.AlternativePattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.LiteralPattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.Pattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.RefinementPattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.TuplePattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.UnapplyPattern→stainless.genc.ir.IR.ValDefstainless.ast.Expressions.WildcardPattern→stainless.genc.ir.IR.ValDef
- Direction
- ast.Expressions uses genc.ir.IR, so a change to genc.ir.IR can break ast.Expressions, while a change to ast.Expressions can't break genc.ir.IR.
- Position
- Below the diagonal: ast.Expressions uses a module listed above it, which is the healthy direction.
24→6 ast.Expressions uses genc.CAST✕
- Connections
- 40 pairs of types, where a type in ast.Expressions uses a type in genc.CAST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.ast.Expressions.ADTPattern→stainless.genc.CAST.Typestainless.ast.Expressions.Annotated→stainless.genc.CAST.Exprstainless.ast.Expressions.Annotated→stainless.genc.CAST.Typestainless.ast.Expressions.AnnotatedType→stainless.genc.CAST.Typestainless.ast.Expressions.ArrayLength→stainless.genc.CAST.Exprstainless.ast.Expressions.ArrayLength→stainless.genc.CAST.Typestainless.ast.Expressions.ArraySelect→stainless.genc.CAST.Exprstainless.ast.Expressions.ArraySelect→stainless.genc.CAST.Typestainless.ast.Expressions.ArrayUpdated→stainless.genc.CAST.Exprstainless.ast.Expressions.ArrayUpdated→stainless.genc.CAST.Typestainless.ast.Expressions.Assert→stainless.genc.CAST.Exprstainless.ast.Expressions.Assert→stainless.genc.CAST.Typestainless.ast.Expressions.Decreases→stainless.genc.CAST.Exprstainless.ast.Expressions.Decreases→stainless.genc.CAST.Typestainless.ast.Expressions.Ensuring→stainless.genc.CAST.Exprstainless.ast.Expressions.Ensuring→stainless.genc.CAST.Typestainless.ast.Expressions.FiniteArray→stainless.genc.CAST.Exprstainless.ast.Expressions.FiniteArray→stainless.genc.CAST.Typestainless.ast.Expressions.LargeArray→stainless.genc.CAST.Exprstainless.ast.Expressions.LargeArray→stainless.genc.CAST.Typestainless.ast.Expressions.MatchCase→stainless.genc.CAST.Exprstainless.ast.Expressions.MatchCase→stainless.genc.CAST.Treestainless.ast.Expressions.MatchExpr→stainless.genc.CAST.Exprstainless.ast.Expressions.MatchExpr→stainless.genc.CAST.Typestainless.ast.Expressions.Max→stainless.genc.CAST.Expr
- Direction
- ast.Expressions uses genc.CAST, so a change to genc.CAST can break ast.Expressions, while a change to ast.Expressions can't break genc.CAST.
- Position
- Below the diagonal: ast.Expressions uses a module listed above it, which is the healthy direction.
24→20 ast.Expressions uses extraction.imperative.trees✕
- Connections
- 19 pairs of types, where a type in ast.Expressions uses a type in extraction.imperative.trees.
- The types involved
stainless.ast.Expressions.Annotated→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.AnnotatedType→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.ArrayLength→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.ArraySelect→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.ArrayUpdated→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.Assert→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.Decreases→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.Ensuring→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.FiniteArray→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.LargeArray→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.MatchExpr→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.Max→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.NoTree→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.Passes→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.RecursiveType→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.Require→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.SizedADT→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.UnapplyPattern→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions.ValueType→stainless.extraction.imperative.trees.Symbols
- Direction
- ast.Expressions uses extraction.imperative.trees, so a change to extraction.imperative.trees can break ast.Expressions, while a change to ast.Expressions can't break extraction.imperative.trees.
- Position
- Below the diagonal: ast.Expressions uses a module listed above it, which is the healthy direction.
24→23 ast.Expressions uses codegen.runtime✕
- Connections
- 4 pairs of types, where a type in ast.Expressions uses a type in codegen.runtime.
- The types involved
stainless.ast.Expressions.Ensuring→stainless.codegen.runtime.Lambdastainless.ast.Expressions.LargeArray→stainless.codegen.runtime.Mapstainless.ast.Expressions.Pattern→stainless.codegen.runtime.Setstainless.ast.Expressions.RefinementPattern→stainless.codegen.runtime.Lambda
- Direction
- ast.Expressions uses codegen.runtime, so a change to codegen.runtime can break ast.Expressions, while a change to ast.Expressions can't break codegen.runtime.
- Position
- Below the diagonal: ast.Expressions uses a module listed above it, which is the healthy direction.
25→5 ast.ExprOps uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in ast.ExprOps uses a type in genc.ir.IR.
- The types involved
stainless.ast.ExprOps.LetInSpec→stainless.genc.ir.IR.ValDef
- Direction
- ast.ExprOps uses genc.ir.IR, so a change to genc.ir.IR can break ast.ExprOps, while a change to ast.ExprOps can't break genc.ir.IR.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→6 ast.ExprOps uses genc.CAST✕
- Connections
- 6 pairs of types, where a type in ast.ExprOps uses a type in genc.CAST.
- The types involved
stainless.ast.ExprOps.BodyWithSpecs→stainless.genc.CAST.Exprstainless.ast.ExprOps.BodyWithSpecs→stainless.genc.CAST.Typestainless.ast.ExprOps.LetInSpec→stainless.genc.CAST.Exprstainless.ast.ExprOps.Measure→stainless.genc.CAST.Exprstainless.ast.ExprOps.Precondition→stainless.genc.CAST.Exprstainless.ast.ExprOps.Specification→stainless.genc.CAST.Expr
- Direction
- ast.ExprOps uses genc.CAST, so a change to genc.CAST can break ast.ExprOps, while a change to ast.ExprOps can't break genc.CAST.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→8 ast.ExprOps uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 6 pairs of types, where a type in ast.ExprOps uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.ast.ExprOps.LetInSpec→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.ast.ExprOps.Measure→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.ast.ExprOps.Postcondition→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.ast.ExprOps.Precondition→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.ast.ExprOps.Specification→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.ast.ExprOps.StainlessFreshener→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- ast.ExprOps uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break ast.ExprOps, while a change to ast.ExprOps can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→12 ast.ExprOps uses genc.ir✕
- Connections
- 6 pairs of types, where a type in ast.ExprOps uses a type in genc.ir.
- The types involved
stainless.ast.ExprOps.LetInSpec→stainless.genc.ir.Transformerstainless.ast.ExprOps.Measure→stainless.genc.ir.Transformerstainless.ast.ExprOps.Postcondition→stainless.genc.ir.Transformerstainless.ast.ExprOps.Precondition→stainless.genc.ir.Transformerstainless.ast.ExprOps.Specification→stainless.genc.ir.Transformerstainless.ast.ExprOps.StainlessFreshener→stainless.genc.ir.Transformer
- Direction
- ast.ExprOps uses genc.ir, so a change to genc.ir can break ast.ExprOps, while a change to ast.ExprOps can't break genc.ir.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→15 ast.ExprOps uses extraction.innerclasses✕
- Connections
- 10 pairs of types, where a type in ast.ExprOps uses a type in extraction.innerclasses.
- The types involved
stainless.ast.ExprOps.LetInSpec→stainless.extraction.innerclasses.TreeTransformerstainless.ast.ExprOps.LetInSpec→stainless.extraction.innerclasses.TreeTraverserstainless.ast.ExprOps.Measure→stainless.extraction.innerclasses.TreeTransformerstainless.ast.ExprOps.Measure→stainless.extraction.innerclasses.TreeTraverserstainless.ast.ExprOps.Postcondition→stainless.extraction.innerclasses.TreeTransformerstainless.ast.ExprOps.Postcondition→stainless.extraction.innerclasses.TreeTraverserstainless.ast.ExprOps.Precondition→stainless.extraction.innerclasses.TreeTransformerstainless.ast.ExprOps.Precondition→stainless.extraction.innerclasses.TreeTraverserstainless.ast.ExprOps.Specification→stainless.extraction.innerclasses.TreeTransformerstainless.ast.ExprOps.Specification→stainless.extraction.innerclasses.TreeTraverser
- Direction
- ast.ExprOps uses extraction.innerclasses, so a change to extraction.innerclasses can break ast.ExprOps, while a change to ast.ExprOps can't break extraction.innerclasses.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→20 ast.ExprOps uses extraction.imperative.trees✕
- Connections
- 1 pair of types, where a type in ast.ExprOps uses a type in extraction.imperative.trees.
- The types involved
stainless.ast.ExprOps.BodyWithSpecs→stainless.extraction.imperative.trees.Symbols
- Direction
- ast.ExprOps uses extraction.imperative.trees, so a change to extraction.imperative.trees can break ast.ExprOps, while a change to ast.ExprOps can't break extraction.imperative.trees.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→23 ast.ExprOps uses codegen.runtime✕
- Connections
- 1 pair of types, where a type in ast.ExprOps uses a type in codegen.runtime.
- The types involved
stainless.ast.ExprOps.Postcondition→stainless.codegen.runtime.Lambda
- Direction
- ast.ExprOps uses codegen.runtime, so a change to codegen.runtime can break ast.ExprOps, while a change to ast.ExprOps can't break codegen.runtime.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
25→24 ast.ExprOps uses ast.Expressions✕
- Connections
- 2 pairs of types, where a type in ast.ExprOps uses a type in ast.Expressions.
- The types involved
stainless.ast.ExprOps.StainlessFreshener→stainless.ast.Expressions.MatchCasestainless.ast.ExprOps.StainlessFreshener→stainless.ast.Expressions.Pattern
- Direction
- ast.ExprOps uses ast.Expressions, so a change to ast.Expressions can break ast.ExprOps, while a change to ast.ExprOps can't break ast.Expressions.
- Position
- Below the diagonal: ast.ExprOps uses a module listed above it, which is the healthy direction.
26→4 transformers.lattices.Core uses lang✕
- Connections
- 3 pairs of types, where a type in transformers.lattices.Core uses a type in lang.
- The types involved
stainless.transformers.lattices.Core.CodePurity→stainless.lang.Eitherstainless.transformers.lattices.Core.CodeTryFolder→stainless.lang.Eitherstainless.transformers.lattices.Core.occOf→stainless.lang.Either
- Direction
- transformers.lattices.Core uses lang, so a change to lang can break transformers.lattices.Core, while a change to transformers.lattices.Core can't break lang.
- Position
- Below the diagonal: transformers.lattices.Core uses a module listed above it, which is the healthy direction.
26→5 transformers.lattices.Core uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in transformers.lattices.Core uses a type in genc.ir.IR.
- The types involved
stainless.transformers.lattices.Core.uncoder→stainless.genc.ir.IR.ValDef
- Direction
- transformers.lattices.Core uses genc.ir.IR, so a change to genc.ir.IR can break transformers.lattices.Core, while a change to transformers.lattices.Core can't break genc.ir.IR.
- Position
- Below the diagonal: transformers.lattices.Core uses a module listed above it, which is the healthy direction.
26→6 transformers.lattices.Core uses genc.CAST✕
- Connections
- 4 pairs of types, where a type in transformers.lattices.Core uses a type in genc.CAST.
- The types involved
stainless.transformers.lattices.Core.CodeTransformer→stainless.genc.CAST.Typestainless.transformers.lattices.Core.CodeTryFolder→stainless.genc.CAST.Typestainless.transformers.lattices.Core.LinComb→stainless.genc.CAST.Typestainless.transformers.lattices.Core.RevRes→stainless.genc.CAST.Expr
- Direction
- transformers.lattices.Core uses genc.CAST, so a change to genc.CAST can break transformers.lattices.Core, while a change to transformers.lattices.Core can't break genc.CAST.
- Position
- Below the diagonal: transformers.lattices.Core uses a module listed above it, which is the healthy direction.
26→8 transformers.lattices.Core uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 10 pairs of types, where a type in transformers.lattices.Core uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.transformers.lattices.Core.CodePurity→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.CodeRes→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.CodeTransformer→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.CodeTryFolder→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.CodeUnfolder→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.Ctxs→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.Env→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.Occurrences→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.occOf→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core.uncoder→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- transformers.lattices.Core uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break transformers.lattices.Core, while a change to transformers.lattices.Core can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: transformers.lattices.Core uses a module listed above it, which is the healthy direction.
26→23 transformers.lattices.Core uses codegen.runtime✕
- Connections
- 13 pairs of types, where a type in transformers.lattices.Core uses a type in codegen.runtime.
- The types involved
stainless.transformers.lattices.Core.CodePurity→stainless.codegen.runtime.Mapstainless.transformers.lattices.Core.CodeTransformer→stainless.codegen.runtime.Mapstainless.transformers.lattices.Core.Ctxs→stainless.codegen.runtime.Setstainless.transformers.lattices.Core.IntLikeLitCode→stainless.codegen.runtime.BigIntstainless.transformers.lattices.Core.IntLikeLitSig→stainless.codegen.runtime.BigIntstainless.transformers.lattices.Core.LetValSubst→stainless.codegen.runtime.Mapstainless.transformers.lattices.Core.LinComb→stainless.codegen.runtime.BigIntstainless.transformers.lattices.Core.LinComb→stainless.codegen.runtime.Mapstainless.transformers.lattices.Core.Occurrences→stainless.codegen.runtime.Mapstainless.transformers.lattices.Core.Occurrences→stainless.codegen.runtime.Setstainless.transformers.lattices.Core.RevEnv→stainless.codegen.runtime.Mapstainless.transformers.lattices.Core.RevRes→stainless.codegen.runtime.Setstainless.transformers.lattices.Core.uncoder→stainless.codegen.runtime.Map
- Direction
- transformers.lattices.Core uses codegen.runtime, so a change to codegen.runtime can break transformers.lattices.Core, while a change to transformers.lattices.Core can't break codegen.runtime.
- Position
- Below the diagonal: transformers.lattices.Core uses a module listed above it, which is the healthy direction.
26→24 transformers.lattices.Core uses ast.Expressions✕
- Connections
- 1 pair of types, where a type in transformers.lattices.Core uses a type in ast.Expressions.
- The types involved
stainless.transformers.lattices.Core.uncoder→stainless.ast.Expressions.Pattern
- Direction
- transformers.lattices.Core uses ast.Expressions, so a change to ast.Expressions can break transformers.lattices.Core, while a change to transformers.lattices.Core can't break ast.Expressions.
- Position
- Below the diagonal: transformers.lattices.Core uses a module listed above it, which is the healthy direction.
27→1 ast uses algebra.ops✕
- Connections
- 1 pair of types, where a type in ast uses a type in algebra.ops.
- The types involved
stainless.ast.TypeOps→stainless.algebra.ops.List
- Direction
- ast uses algebra.ops, so a change to algebra.ops can break ast, while a change to ast can't break algebra.ops.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→4 ast uses lang✕
- Connections
- 1 pair of types, where a type in ast uses a type in lang.
- The types involved
stainless.ast.ExprOps→stainless.lang.Either
- Direction
- ast uses lang, so a change to lang can break ast, while a change to ast can't break lang.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→5 ast uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in ast uses a type in genc.ir.IR.
- The types involved
stainless.ast.ExprOps→stainless.genc.ir.IR.FunDefstainless.ast.SymbolOps→stainless.genc.ir.IR.FunDefstainless.ast.SymbolOps→stainless.genc.ir.IR.ValDef
- Direction
- ast uses genc.ir.IR, so a change to genc.ir.IR can break ast, while a change to ast can't break genc.ir.IR.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→6 ast uses genc.CAST✕
- Connections
- 14 pairs of types, where a type in ast uses a type in genc.CAST.
- The types involved
stainless.ast.Constructors→stainless.genc.CAST.Exprstainless.ast.Definitions→stainless.genc.CAST.Exprstainless.ast.ExprOps→stainless.genc.CAST.Exprstainless.ast.ExprOps→stainless.genc.CAST.Typestainless.ast.Expressions→stainless.genc.CAST.Exprstainless.ast.Printer→stainless.genc.CAST.Exprstainless.ast.Printer→stainless.genc.CAST.Treestainless.ast.ScalaPrinter→stainless.genc.CAST.Treestainless.ast.SymbolOps→stainless.genc.CAST.Exprstainless.ast.TreeDeconstructor→stainless.genc.CAST.Exprstainless.ast.TreeDeconstructor→stainless.genc.CAST.Typestainless.ast.TypeOps→stainless.genc.CAST.Exprstainless.ast.TypeOps→stainless.genc.CAST.Typestainless.ast.Types→stainless.genc.CAST.Type
- Direction
- ast uses genc.CAST, so a change to genc.CAST can break ast, while a change to ast can't break genc.CAST.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→10 ast uses genc✕
- Connections
- 2 pairs of types, where a type in ast uses a type in genc.
- The types involved
stainless.ast.Printer→stainless.genc.PrinterContextstainless.ast.ScalaPrinter→stainless.genc.PrinterContext
- Direction
- ast uses genc, so a change to genc can break ast, while a change to ast can't break genc.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→18 ast uses transformers✕
- Connections
- 1 pair of types, where a type in ast uses a type in transformers.
- The types involved
stainless.ast.SymbolOps→stainless.transformers.SimplifierWithPC
- Direction
- ast uses transformers, so a change to transformers can break ast, while a change to ast can't break transformers.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→20 ast uses extraction.imperative.trees✕
- Connections
- 3 pairs of types, where a type in ast uses a type in extraction.imperative.trees.
- The types involved
stainless.ast.Constructors→stainless.extraction.imperative.trees.Symbolsstainless.ast.Expressions→stainless.extraction.imperative.trees.Symbolsstainless.ast.Types→stainless.extraction.imperative.trees.Symbols
- Direction
- ast uses extraction.imperative.trees, so a change to extraction.imperative.trees can break ast, while a change to ast can't break extraction.imperative.trees.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→23 ast uses codegen.runtime✕
- Connections
- 4 pairs of types, where a type in ast uses a type in codegen.runtime.
- The types involved
stainless.ast.ExprOps→stainless.codegen.runtime.Lambdastainless.ast.ExprOps→stainless.codegen.runtime.Mapstainless.ast.SymbolOps→stainless.codegen.runtime.Mapstainless.ast.TypeOps→stainless.codegen.runtime.Map
- Direction
- ast uses codegen.runtime, so a change to codegen.runtime can break ast, while a change to ast can't break codegen.runtime.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→24 ast uses ast.Expressions✕
- Connections
- 10 pairs of types, where a type in ast uses a type in ast.Expressions.
- The types involved
stainless.ast.Constructors→stainless.ast.Expressions.MatchCasestainless.ast.ExprOps→stainless.ast.Expressions.Passesstainless.ast.Expressions→stainless.ast.Expressions.UnapplyPatternstainless.ast.SymbolOps→stainless.ast.Expressions.MatchCasestainless.ast.SymbolOps→stainless.ast.Expressions.MatchExprstainless.ast.SymbolOps→stainless.ast.Expressions.Maxstainless.ast.SymbolOps→stainless.ast.Expressions.Patternstainless.ast.TreeDeconstructor→stainless.ast.Expressions.MatchCasestainless.ast.TreeDeconstructor→stainless.ast.Expressions.Patternstainless.ast.TypeOps→stainless.ast.Expressions.Pattern
- Direction
- ast uses ast.Expressions, so a change to ast.Expressions can break ast, while a change to ast can't break ast.Expressions.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
27→25 ast uses ast.ExprOps✕
- Connections
- 2 pairs of types, where a type in ast uses a type in ast.ExprOps.
- The types involved
stainless.ast.ExprOps→stainless.ast.ExprOps.SpecKindstainless.ast.ExprOps→stainless.ast.ExprOps.Specification
- Direction
- ast uses ast.ExprOps, so a change to ast.ExprOps can break ast, while a change to ast can't break ast.ExprOps.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
28→4 transformers.lattices uses lang✕
- Connections
- 2 pairs of types, where a type in transformers.lattices uses a type in lang.
- The types involved
stainless.transformers.lattices.Core→stainless.lang.Eitherstainless.transformers.lattices.OCBSL→stainless.lang.Either
- Direction
- transformers.lattices uses lang, so a change to lang can break transformers.lattices, while a change to transformers.lattices can't break lang.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→6 transformers.lattices uses genc.CAST✕
- Connections
- 3 pairs of types, where a type in transformers.lattices uses a type in genc.CAST.
- The types involved
stainless.transformers.lattices.Core→stainless.genc.CAST.Exprstainless.transformers.lattices.Core→stainless.genc.CAST.Typestainless.transformers.lattices.Definitions→stainless.genc.CAST.Type
- Direction
- transformers.lattices uses genc.CAST, so a change to genc.CAST can break transformers.lattices, while a change to transformers.lattices can't break genc.CAST.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→8 transformers.lattices uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 4 pairs of types, where a type in transformers.lattices uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.transformers.lattices.Bland→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.Core→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.OCBSL→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.transformers.lattices.OL→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- transformers.lattices uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break transformers.lattices, while a change to transformers.lattices can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→20 transformers.lattices uses extraction.imperative.trees✕
- Connections
- 1 pair of types, where a type in transformers.lattices uses a type in extraction.imperative.trees.
- The types involved
stainless.transformers.lattices.Definitions→stainless.extraction.imperative.trees.Symbols
- Direction
- transformers.lattices uses extraction.imperative.trees, so a change to extraction.imperative.trees can break transformers.lattices, while a change to transformers.lattices can't break extraction.imperative.trees.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→23 transformers.lattices uses codegen.runtime✕
- Connections
- 3 pairs of types, where a type in transformers.lattices uses a type in codegen.runtime.
- The types involved
stainless.transformers.lattices.Core→stainless.codegen.runtime.BigIntstainless.transformers.lattices.Core→stainless.codegen.runtime.Mapstainless.transformers.lattices.Definitions→stainless.codegen.runtime.Map
- Direction
- transformers.lattices uses codegen.runtime, so a change to codegen.runtime can break transformers.lattices, while a change to transformers.lattices can't break codegen.runtime.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→24 transformers.lattices uses ast.Expressions✕
- Connections
- 1 pair of types, where a type in transformers.lattices uses a type in ast.Expressions.
- The types involved
stainless.transformers.lattices.Core→stainless.ast.Expressions.MatchCase
- Direction
- transformers.lattices uses ast.Expressions, so a change to ast.Expressions can break transformers.lattices, while a change to transformers.lattices can't break ast.Expressions.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→26 transformers.lattices uses transformers.lattices.Core✕
- Connections
- 17 pairs of types, where a type in transformers.lattices uses a type in transformers.lattices.Core.
- The types involved
stainless.transformers.lattices.Bland→stainless.transformers.lattices.Core.Ctxsstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.BindingCasestainless.transformers.lattices.Core→stainless.transformers.lattices.Core.CodeResstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.CodeResMatchCasestainless.transformers.lattices.Core→stainless.transformers.lattices.Core.Ctxsstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.ExplicitSigstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.LetValSubststainless.transformers.lattices.Core→stainless.transformers.lattices.Core.LinCombstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.Occurrencesstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.PatBdgsAndCondsstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.Retirementstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.RevResstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.SimplifiedCasestainless.transformers.lattices.Core→stainless.transformers.lattices.Core.SimplifiedCasesstainless.transformers.lattices.Core→stainless.transformers.lattices.Core.UnapplySubScrutsstainless.transformers.lattices.OCBSL→stainless.transformers.lattices.Core.Ctxsstainless.transformers.lattices.OL→stainless.transformers.lattices.Core.Ctxs
- Direction
- transformers.lattices uses transformers.lattices.Core, so a change to transformers.lattices.Core can break transformers.lattices, while a change to transformers.lattices can't break transformers.lattices.Core.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
28→27 transformers.lattices uses ast✕
- Connections
- 2 pairs of types, where a type in transformers.lattices uses a type in ast.
- The types involved
stainless.transformers.lattices.Core→stainless.ast.Definitionsstainless.transformers.lattices.Definitions→stainless.ast.Trees
- Direction
- transformers.lattices uses ast, so a change to ast can break transformers.lattices, while a change to transformers.lattices can't break ast.
- Position
- Below the diagonal: transformers.lattices uses a module listed above it, which is the healthy direction.
29→4 utils uses lang✕
- Connections
- 2 pairs of types, where a type in utils uses a type in lang.
- The types involved
stainless.utils.CtexRemapping→stainless.lang.Eitherstainless.utils.XLangDependenciesFinder→stainless.lang.MutableMap
- Direction
- utils uses lang, so a change to lang can break utils, while a change to utils can't break lang.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→5 utils uses genc.ir.IR✕
- Connections
- 6 pairs of types, where a type in utils uses a type in genc.ir.IR.
- The types involved
stainless.utils.Canonization→stainless.genc.ir.IR.FunDefstainless.utils.CheckFilter→stainless.genc.ir.IR.FunDefstainless.utils.CtexRemapping→stainless.genc.ir.IR.ValDefstainless.utils.DefinitionIdFinder→stainless.genc.ir.IR.FunDefstainless.utils.LibraryFilter→stainless.genc.ir.IR.FunDefstainless.utils.XLangDependenciesFinder→stainless.genc.ir.IR.FunDef
- Direction
- utils uses genc.ir.IR, so a change to genc.ir.IR can break utils, while a change to utils can't break genc.ir.IR.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→6 utils uses genc.CAST✕
- Connections
- 3 pairs of types, where a type in utils uses a type in genc.CAST.
- The types involved
stainless.utils.Canonization→stainless.genc.CAST.Exprstainless.utils.CtexRemapping→stainless.genc.CAST.Exprstainless.utils.CtexRemapping→stainless.genc.CAST.Type
- Direction
- utils uses genc.CAST, so a change to genc.CAST can break utils, while a change to utils can't break genc.CAST.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→8 utils uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 1 pair of types, where a type in utils uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.utils.DefinitionIdFinder→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- utils uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break utils, while a change to utils can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→13 utils uses extraction.imperative.EffectsAnalyzer✕
- Connections
- 1 pair of types, where a type in utils uses a type in extraction.imperative.EffectsAnalyzer.
- The types involved
stainless.utils.CheckFilter→stainless.extraction.imperative.EffectsAnalyzer.Path
- Direction
- utils uses extraction.imperative.EffectsAnalyzer, so a change to extraction.imperative.EffectsAnalyzer can break utils, while a change to utils can't break extraction.imperative.EffectsAnalyzer.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→15 utils uses extraction.innerclasses✕
- Connections
- 1 pair of types, where a type in utils uses a type in extraction.innerclasses.
- The types involved
stainless.utils.DefinitionIdFinder→stainless.extraction.innerclasses.DefinitionTraverser
- Direction
- utils uses extraction.innerclasses, so a change to extraction.innerclasses can break utils, while a change to utils can't break extraction.innerclasses.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→20 utils uses extraction.imperative.trees✕
- Connections
- 6 pairs of types, where a type in utils uses a type in extraction.imperative.trees.
- The types involved
stainless.utils.Canonization→stainless.extraction.imperative.trees.Symbolsstainless.utils.CheckFilter→stainless.extraction.imperative.trees.Symbolsstainless.utils.DefinitionIdFinder→stainless.extraction.imperative.trees.Symbolsstainless.utils.DependenciesFinder→stainless.extraction.imperative.trees.Symbolsstainless.utils.LibraryFilter→stainless.extraction.imperative.trees.Symbolsstainless.utils.XlangCanonization→stainless.extraction.imperative.trees.Symbols
- Direction
- utils uses extraction.imperative.trees, so a change to extraction.imperative.trees can break utils, while a change to utils can't break extraction.imperative.trees.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→21 utils uses extraction.oo.Definitions✕
- Connections
- 4 pairs of types, where a type in utils uses a type in extraction.oo.Definitions.
- The types involved
stainless.utils.XLangDependenciesFinder→stainless.extraction.oo.Definitions.ClassDefstainless.utils.XLangDependenciesFinder→stainless.extraction.oo.Definitions.TypeDefstainless.utils.XlangCanonization→stainless.extraction.oo.Definitions.ClassDefstainless.utils.XlangCanonization→stainless.extraction.oo.Definitions.TypeDef
- Direction
- utils uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break utils, while a change to utils can't break extraction.oo.Definitions.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→22 utils uses genc.phases.IR2CImpl✕
- Connections
- 1 pair of types, where a type in utils uses a type in genc.phases.IR2CImpl.
- The types involved
stainless.utils.Bytes→stainless.genc.phases.IR2CImpl.Array
- Direction
- utils uses genc.phases.IR2CImpl, so a change to genc.phases.IR2CImpl can break utils, while a change to utils can't break genc.phases.IR2CImpl.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→23 utils uses codegen.runtime✕
- Connections
- 6 pairs of types, where a type in utils uses a type in codegen.runtime.
- The types involved
stainless.utils.CtexRemapping→stainless.codegen.runtime.Mapstainless.utils.DefinitionIdFinder→stainless.codegen.runtime.Setstainless.utils.DependenciesFinder→stainless.codegen.runtime.Setstainless.utils.StainlessSerializer→stainless.codegen.runtime.Mapstainless.utils.XLangDependenciesFinder→stainless.codegen.runtime.Mapstainless.utils.XLangSerializer→stainless.codegen.runtime.Map
- Direction
- utils uses codegen.runtime, so a change to codegen.runtime can break utils, while a change to utils can't break codegen.runtime.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→27 utils uses ast✕
- Connections
- 8 pairs of types, where a type in utils uses a type in ast.
- The types involved
stainless.utils.Canonization→stainless.ast.Treesstainless.utils.CheckFilter→stainless.ast.Treesstainless.utils.CtexRemapping→stainless.ast.Treesstainless.utils.DependenciesFinder→stainless.ast.Treesstainless.utils.Serializer→stainless.ast.Treesstainless.utils.StainlessSerializer→stainless.ast.Treesstainless.utils.XLangSerializer→stainless.ast.Treesstainless.utils.XlangCanonization→stainless.ast.Trees
- Direction
- utils uses ast, so a change to ast can break utils, while a change to utils can't break ast.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
29→31 utils uses stainless part of a loop✕
- Connections
- 4 pairs of types, where a type in utils uses a type in stainless.
- The types involved
stainless.utils.Caches→stainless.Contextstainless.utils.CheckFilter→stainless.Componentstainless.utils.CheckFilter→stainless.Contextstainless.utils.CtexRemapping→stainless.Context
- Direction
- utils uses stainless, so a change to stainless can break utils, while a change to utils can't break stainless.
- 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→3 frontend uses extraction.oo.Trees✕
- Connections
- 1 pair of types, where a type in frontend uses a type in extraction.oo.Trees.
- The types involved
stainless.frontend.RecoverExternTypes→stainless.extraction.oo.Trees.ClassType
- Direction
- frontend uses extraction.oo.Trees, so a change to extraction.oo.Trees can break frontend, while a change to frontend can't break extraction.oo.Trees.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→5 frontend uses genc.ir.IR✕
- Connections
- 6 pairs of types, where a type in frontend uses a type in genc.ir.IR.
- The types involved
stainless.frontend.BatchedCallBack→stainless.genc.ir.IR.FunDefstainless.frontend.CallBack→stainless.genc.ir.IR.FunDefstainless.frontend.NoRecovery→stainless.genc.ir.IR.FunDefstainless.frontend.RecoverExternTypes→stainless.genc.ir.IR.FunDefstainless.frontend.RecoveryStrategy→stainless.genc.ir.IR.FunDefstainless.frontend.SplitCallBack→stainless.genc.ir.IR.FunDef
- Direction
- frontend uses genc.ir.IR, so a change to genc.ir.IR can break frontend, while a change to frontend can't break genc.ir.IR.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→6 frontend uses genc.CAST✕
- Connections
- 3 pairs of types, where a type in frontend uses a type in genc.CAST.
- The types involved
stainless.frontend.BVCleanerImpl→stainless.genc.CAST.Typestainless.frontend.RecoverExternTypes→stainless.genc.CAST.Typestainless.frontend.RecoveryStrategy→stainless.genc.CAST.Def
- Direction
- frontend uses genc.CAST, so a change to genc.CAST can break frontend, while a change to frontend can't break genc.CAST.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→15 frontend uses extraction.innerclasses✕
- Connections
- 1 pair of types, where a type in frontend uses a type in extraction.innerclasses.
- The types involved
stainless.frontend.BVCleanerImpl→stainless.extraction.innerclasses.ConcreteTreeTransformer
- Direction
- frontend uses extraction.innerclasses, so a change to extraction.innerclasses can break frontend, while a change to frontend can't break extraction.innerclasses.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→19 frontend uses extraction.oo✕
- Connections
- 2 pairs of types, where a type in frontend uses a type in extraction.oo.
- The types involved
stainless.frontend.Preprocessing→stainless.extraction.oo.SymbolTransformerstainless.frontend.UserFiltering→stainless.extraction.oo.SymbolTransformer
- Direction
- frontend uses extraction.oo, so a change to extraction.oo can break frontend, while a change to frontend can't break extraction.oo.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→20 frontend uses extraction.imperative.trees✕
- Connections
- 5 pairs of types, where a type in frontend uses a type in extraction.imperative.trees.
- The types involved
stainless.frontend.BatchedCallBack→stainless.extraction.imperative.trees.Symbolsstainless.frontend.CallGraphPrinter→stainless.extraction.imperative.trees.Symbolsstainless.frontend.Preprocessing→stainless.extraction.imperative.trees.Symbolsstainless.frontend.SplitCallBack→stainless.extraction.imperative.trees.Symbolsstainless.frontend.UserFiltering→stainless.extraction.imperative.trees.Symbols
- Direction
- frontend uses extraction.imperative.trees, so a change to extraction.imperative.trees can break frontend, while a change to frontend can't break extraction.imperative.trees.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→21 frontend uses extraction.oo.Definitions✕
- Connections
- 12 pairs of types, where a type in frontend uses a type in extraction.oo.Definitions.
- The types involved
stainless.frontend.BatchedCallBack→stainless.extraction.oo.Definitions.ClassDefstainless.frontend.BatchedCallBack→stainless.extraction.oo.Definitions.TypeDefstainless.frontend.CallBack→stainless.extraction.oo.Definitions.ClassDefstainless.frontend.CallBack→stainless.extraction.oo.Definitions.TypeDefstainless.frontend.NoRecovery→stainless.extraction.oo.Definitions.ClassDefstainless.frontend.NoRecovery→stainless.extraction.oo.Definitions.TypeDefstainless.frontend.RecoverExternTypes→stainless.extraction.oo.Definitions.ClassDefstainless.frontend.RecoverExternTypes→stainless.extraction.oo.Definitions.TypeDefstainless.frontend.RecoveryStrategy→stainless.extraction.oo.Definitions.ClassDefstainless.frontend.RecoveryStrategy→stainless.extraction.oo.Definitions.TypeDefstainless.frontend.SplitCallBack→stainless.extraction.oo.Definitions.ClassDefstainless.frontend.SplitCallBack→stainless.extraction.oo.Definitions.TypeDef
- Direction
- frontend uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break frontend, while a change to frontend can't break extraction.oo.Definitions.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→23 frontend uses codegen.runtime✕
- Connections
- 7 pairs of types, where a type in frontend uses a type in codegen.runtime.
- The types involved
stainless.frontend.DependencyResolver→stainless.codegen.runtime.Setstainless.frontend.NoRecovery→stainless.codegen.runtime.Setstainless.frontend.RecoverExternTypes→stainless.codegen.runtime.Setstainless.frontend.Recovery→stainless.codegen.runtime.Mapstainless.frontend.Recovery→stainless.codegen.runtime.Setstainless.frontend.RecoveryStrategy→stainless.codegen.runtime.Setstainless.frontend.SplitCallBack→stainless.codegen.runtime.Set
- Direction
- frontend uses codegen.runtime, so a change to codegen.runtime can break frontend, while a change to frontend can't break codegen.runtime.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→29 frontend uses utils✕
- Connections
- 2 pairs of types, where a type in frontend uses a type in utils.
- The types involved
stainless.frontend.SplitCallBack→stainless.utils.CheckFilterstainless.frontend.UserFiltering→stainless.utils.CheckFilter
- Direction
- frontend uses utils, so a change to utils can break frontend, while a change to frontend can't break utils.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
30→31 frontend uses stainless part of a loop✕
- Connections
- 11 pairs of types, where a type in frontend uses a type in stainless.
- The types involved
stainless.frontend.BatchedCallBack→stainless.AbstractReportstainless.frontend.BatchedCallBack→stainless.Contextstainless.frontend.CallBack→stainless.AbstractReportstainless.frontend.Frontend→stainless.AbstractReportstainless.frontend.FrontendFactory→stainless.Contextstainless.frontend.Preprocessing→stainless.Contextstainless.frontend.Recovery→stainless.Contextstainless.frontend.SplitCallBack→stainless.Contextstainless.frontend.StainlessReports→stainless.ComponentRunstainless.frontend.StainlessReports→stainless.RecordRowstainless.frontend.UserFiltering→stainless.Context
- Direction
- frontend uses stainless, so a change to stainless can break frontend, while a change to frontend can't break stainless.
- 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→1 stainless uses algebra.ops✕
- Connections
- 1 pair of types, where a type in stainless uses a type in algebra.ops.
- The types involved
stainless.genc→stainless.algebra.ops.List
- Direction
- stainless uses algebra.ops, so a change to algebra.ops can break stainless, while a change to stainless can't break algebra.ops.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→5 stainless uses genc.ir.IR✕
- Connections
- 1 pair of types, where a type in stainless uses a type in genc.ir.IR.
- The types involved
stainless.trees→stainless.genc.ir.IR.FunDef
- Direction
- stainless uses genc.ir.IR, so a change to genc.ir.IR can break stainless, while a change to stainless can't break genc.ir.IR.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→6 stainless uses genc.CAST✕
- Connections
- 1 pair of types, where a type in stainless uses a type in genc.CAST.
- The types involved
stainless.RecordRow→stainless.genc.CAST.Type
- Direction
- stainless uses genc.CAST, so a change to genc.CAST can break stainless, while a change to stainless can't break genc.CAST.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→10 stainless uses genc✕
- Connections
- 1 pair of types, where a type in stainless uses a type in genc.
- The types involved
stainless.genc→stainless.genc.DeclarationMode
- Direction
- stainless uses genc, so a change to genc can break stainless, while a change to stainless can't break genc.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→17 stainless uses extraction✕
- Connections
- 3 pairs of types, where a type in stainless uses a type in extraction.
- The types involved
stainless.AbstractReport→stainless.extraction.ExtractionSummarystainless.ComponentRun→stainless.extraction.ExtractionSummarystainless.extraction→stainless.extraction.ExtractionPipeline
- Direction
- stainless uses extraction, so a change to extraction can break stainless, while a change to stainless can't break extraction.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→20 stainless uses extraction.imperative.trees✕
- Connections
- 4 pairs of types, where a type in stainless uses a type in extraction.imperative.trees.
- The types involved
stainless.ComponentRun→stainless.extraction.imperative.trees.Symbolsstainless.extraction→stainless.extraction.imperative.trees.Symbolsstainless.genc→stainless.extraction.imperative.trees.Symbolsstainless.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- stainless uses extraction.imperative.trees, so a change to extraction.imperative.trees can break stainless, while a change to stainless can't break extraction.imperative.trees.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→23 stainless uses codegen.runtime✕
- Connections
- 7 pairs of types, where a type in stainless uses a type in codegen.runtime.
- The types involved
stainless.AbstractReport→stainless.codegen.runtime.Setstainless.AbstractReportHelper→stainless.codegen.runtime.Setstainless.BuildableAbstractReport→stainless.codegen.runtime.Setstainless.NoReport→stainless.codegen.runtime.Setstainless.extraction→stainless.codegen.runtime.Setstainless.math→stainless.codegen.runtime.BigIntstainless.trees→stainless.codegen.runtime.Map
- Direction
- stainless uses codegen.runtime, so a change to codegen.runtime can break stainless, while a change to stainless can't break codegen.runtime.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→27 stainless uses ast✕
- Connections
- 3 pairs of types, where a type in stainless uses a type in ast.
- The types involved
stainless.ComponentRun→stainless.ast.Treesstainless.extraction→stainless.ast.Treesstainless.trees→stainless.ast.Trees
- Direction
- stainless uses ast, so a change to ast can break stainless, while a change to stainless can't break ast.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→29 stainless uses utils✕
- Connections
- 1 pair of types, where a type in stainless uses a type in utils.
- The types involved
stainless.ComponentRun→stainless.utils.CheckFilter
- Direction
- stainless uses utils, so a change to utils can break stainless, while a change to stainless can't break utils.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
31→30 stainless uses frontend✕
- Connections
- 3 pairs of types, where a type in stainless uses a type in frontend.
- The types involved
stainless.frontend→stainless.frontend.CallBackstainless.frontend→stainless.frontend.Frontendstainless.frontend→stainless.frontend.FrontendFactory
- Direction
- stainless uses frontend, so a change to frontend can break stainless, while a change to stainless can't break frontend.
- Position
- Below the diagonal: stainless uses a module listed above it, which is the healthy direction.
32→5 extraction.innerfuns uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in extraction.innerfuns uses a type in genc.ir.IR.
- The types involved
stainless.extraction.innerfuns.FunctionClosure→stainless.genc.ir.IR.FunDefstainless.extraction.innerfuns.GhostTraverser→stainless.genc.ir.IR.FunDefstainless.extraction.innerfuns.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction.innerfuns uses genc.ir.IR, so a change to genc.ir.IR can break extraction.innerfuns, while a change to extraction.innerfuns can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→6 extraction.innerfuns uses genc.CAST✕
- Connections
- 6 pairs of types, where a type in extraction.innerfuns uses a type in genc.CAST.
- The types involved
stainless.extraction.innerfuns.ExprOps→stainless.genc.CAST.Exprstainless.extraction.innerfuns.GhostTraverser→stainless.genc.CAST.Exprstainless.extraction.innerfuns.Printer→stainless.genc.CAST.Exprstainless.extraction.innerfuns.Printer→stainless.genc.CAST.Treestainless.extraction.innerfuns.TransformerWithPC→stainless.genc.CAST.Exprstainless.extraction.innerfuns.TreeDeconstructor→stainless.genc.CAST.Expr
- Direction
- extraction.innerfuns uses genc.CAST, so a change to genc.CAST can break extraction.innerfuns, while a change to extraction.innerfuns can't break genc.CAST.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→8 extraction.innerfuns uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 1 pair of types, where a type in extraction.innerfuns uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.extraction.innerfuns.TransformerWithPC→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- extraction.innerfuns uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break extraction.innerfuns, while a change to extraction.innerfuns can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→10 extraction.innerfuns uses genc✕
- Connections
- 1 pair of types, where a type in extraction.innerfuns uses a type in genc.
- The types involved
stainless.extraction.innerfuns.Printer→stainless.genc.PrinterContext
- Direction
- extraction.innerfuns uses genc, so a change to genc can break extraction.innerfuns, while a change to extraction.innerfuns can't break genc.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→11 extraction.innerfuns uses extraction.innerfuns.Definitions✕
- Connections
- 2 pairs of types, where a type in extraction.innerfuns uses a type in extraction.innerfuns.Definitions.
- The types involved
stainless.extraction.innerfuns.ExprOps→stainless.extraction.innerfuns.Definitions.LocalFunDefstainless.extraction.innerfuns.GhostTraverser→stainless.extraction.innerfuns.Definitions.LocalFunDef
- Direction
- extraction.innerfuns uses extraction.innerfuns.Definitions, so a change to extraction.innerfuns.Definitions can break extraction.innerfuns, while a change to extraction.innerfuns can't break extraction.innerfuns.Definitions.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→14 extraction.innerfuns uses extraction.imperative✕
- Connections
- 2 pairs of types, where a type in extraction.innerfuns uses a type in extraction.imperative.
- The types involved
stainless.extraction.innerfuns.GhostTraverser→stainless.extraction.imperative.GhostTraverserstainless.extraction.innerfuns.TransformerWithPC→stainless.extraction.imperative.TransformerWithPC
- Direction
- extraction.innerfuns uses extraction.imperative, so a change to extraction.imperative can break extraction.innerfuns, while a change to extraction.innerfuns can't break extraction.imperative.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→17 extraction.innerfuns uses extraction✕
- Connections
- 4 pairs of types, where a type in extraction.innerfuns uses a type in extraction.
- The types involved
stainless.extraction.innerfuns.FunctionClosure→stainless.extraction.CachingPhasestainless.extraction.innerfuns.FunctionClosure→stainless.extraction.IdentitySortsstainless.extraction.innerfuns.FunctionClosure→stainless.extraction.NoSummaryPhasestainless.extraction.innerfuns.FunctionClosure→stainless.extraction.SimplyCachedFunctions
- Direction
- extraction.innerfuns uses extraction, so a change to extraction can break extraction.innerfuns, while a change to extraction.innerfuns can't break extraction.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→20 extraction.innerfuns uses extraction.imperative.trees✕
- Connections
- 2 pairs of types, where a type in extraction.innerfuns uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.innerfuns.FunctionClosure→stainless.extraction.imperative.trees.Symbolsstainless.extraction.innerfuns.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.innerfuns uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.innerfuns, while a change to extraction.innerfuns can't break extraction.imperative.trees.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→23 extraction.innerfuns uses codegen.runtime✕
- Connections
- 2 pairs of types, where a type in extraction.innerfuns uses a type in codegen.runtime.
- The types involved
stainless.extraction.innerfuns.ExprOps→stainless.codegen.runtime.Setstainless.extraction.innerfuns.trees→stainless.codegen.runtime.Map
- Direction
- extraction.innerfuns uses codegen.runtime, so a change to codegen.runtime can break extraction.innerfuns, while a change to extraction.innerfuns can't break codegen.runtime.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→27 extraction.innerfuns uses ast✕
- Connections
- 19 pairs of types, where a type in extraction.innerfuns uses a type in ast.
- The types involved
stainless.extraction.innerfuns.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.innerfuns.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.innerfuns.Definitions→stainless.ast.Treesstainless.extraction.innerfuns.ExprOps→stainless.ast.Treesstainless.extraction.innerfuns.FunctionClosure→stainless.ast.Treesstainless.extraction.innerfuns.GhostTraverser→stainless.ast.Treesstainless.extraction.innerfuns.Printer→stainless.ast.Printerstainless.extraction.innerfuns.Printer→stainless.ast.Treesstainless.extraction.innerfuns.SymbolOps→stainless.ast.SymbolOpsstainless.extraction.innerfuns.SymbolOps→stainless.ast.TypeOpsstainless.extraction.innerfuns.TransformerWithPC→stainless.ast.Treesstainless.extraction.innerfuns.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.innerfuns.TreeDeconstructor→stainless.ast.Treesstainless.extraction.innerfuns.Trees→stainless.ast.Definitionsstainless.extraction.innerfuns.Trees→stainless.ast.ExprOpsstainless.extraction.innerfuns.Trees→stainless.ast.Treesstainless.extraction.innerfuns.TypeOps→stainless.ast.Treesstainless.extraction.innerfuns.TypeOps→stainless.ast.TypeOpsstainless.extraction.innerfuns.trees→stainless.ast.Trees
- Direction
- extraction.innerfuns uses ast, so a change to ast can break extraction.innerfuns, while a change to extraction.innerfuns can't break ast.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
32→31 extraction.innerfuns uses stainless✕
- Connections
- 1 pair of types, where a type in extraction.innerfuns uses a type in stainless.
- The types involved
stainless.extraction.innerfuns.FunctionClosure→stainless.Context
- Direction
- extraction.innerfuns uses stainless, so a change to stainless can break extraction.innerfuns, while a change to extraction.innerfuns can't break stainless.
- Position
- Below the diagonal: extraction.innerfuns uses a module listed above it, which is the healthy direction.
33→2 extraction.methods uses extraction.imperative.EffectElaboration✕
- Connections
- 7 pairs of types, where a type in extraction.methods uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.extraction.methods.FieldAccessors→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.methods.Laws→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.methods.MergeInvariants→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.methods.Sealing→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.methods.SuperCalls→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.methods.SuperInvariants→stainless.extraction.imperative.EffectElaboration.TransformerContextstainless.extraction.methods.ValueClasses→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- extraction.methods uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break extraction.methods, while a change to extraction.methods can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→5 extraction.methods uses genc.ir.IR✕
- Connections
- 11 pairs of types, where a type in extraction.methods uses a type in genc.ir.IR.
- The types involved
stainless.extraction.methods.DependencyGraph→stainless.genc.ir.IR.FunDefstainless.extraction.methods.ExprOps→stainless.genc.ir.IR.FunDefstainless.extraction.methods.FieldAccessors→stainless.genc.ir.IR.FunDefstainless.extraction.methods.Laws→stainless.genc.ir.IR.FunDefstainless.extraction.methods.MergeInvariants→stainless.genc.ir.IR.FunDefstainless.extraction.methods.MethodLifting→stainless.genc.ir.IR.FunDefstainless.extraction.methods.Sealing→stainless.genc.ir.IR.FunDefstainless.extraction.methods.SuperCalls→stainless.genc.ir.IR.FunDefstainless.extraction.methods.SuperInvariants→stainless.genc.ir.IR.FunDefstainless.extraction.methods.ValueClasses→stainless.genc.ir.IR.FunDefstainless.extraction.methods.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction.methods uses genc.ir.IR, so a change to genc.ir.IR can break extraction.methods, while a change to extraction.methods can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→6 extraction.methods uses genc.CAST✕
- Connections
- 5 pairs of types, where a type in extraction.methods uses a type in genc.CAST.
- The types involved
stainless.extraction.methods.GhostTraverser→stainless.genc.CAST.Exprstainless.extraction.methods.Printer→stainless.genc.CAST.Treestainless.extraction.methods.TreeDeconstructor→stainless.genc.CAST.Exprstainless.extraction.methods.Trees→stainless.genc.CAST.Exprstainless.extraction.methods.TypeOps→stainless.genc.CAST.Type
- Direction
- extraction.methods uses genc.CAST, so a change to genc.CAST can break extraction.methods, while a change to extraction.methods can't break genc.CAST.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→10 extraction.methods uses genc✕
- Connections
- 1 pair of types, where a type in extraction.methods uses a type in genc.
- The types involved
stainless.extraction.methods.Printer→stainless.genc.PrinterContext
- Direction
- extraction.methods uses genc, so a change to genc can break extraction.methods, while a change to extraction.methods can't break genc.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→14 extraction.methods uses extraction.imperative✕
- Connections
- 1 pair of types, where a type in extraction.methods uses a type in extraction.imperative.
- The types involved
stainless.extraction.methods.GhostTraverser→stainless.extraction.imperative.GhostTraverser
- Direction
- extraction.methods uses extraction.imperative, so a change to extraction.imperative can break extraction.methods, while a change to extraction.methods can't break extraction.imperative.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→17 extraction.methods uses extraction✕
- Connections
- 28 pairs of types, where a type in extraction.methods uses a type in extraction. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.extraction.methods.FieldAccessors→stainless.extraction.CachingPhasestainless.extraction.methods.FieldAccessors→stainless.extraction.NoSummaryPhasestainless.extraction.methods.FieldAccessors→stainless.extraction.SimpleSortsstainless.extraction.methods.FieldAccessors→stainless.extraction.SimplyCachedSortsstainless.extraction.methods.Laws→stainless.extraction.CachingPhasestainless.extraction.methods.Laws→stainless.extraction.IdentitySortsstainless.extraction.methods.Laws→stainless.extraction.NoSummaryPhasestainless.extraction.methods.MergeInvariants→stainless.extraction.CachingPhasestainless.extraction.methods.MergeInvariants→stainless.extraction.IdentitySortsstainless.extraction.methods.MergeInvariants→stainless.extraction.NoSummaryPhasestainless.extraction.methods.MergeInvariants→stainless.extraction.SimpleFunctionsstainless.extraction.methods.MethodLifting→stainless.extraction.ExtractionCachesstainless.extraction.methods.MethodLifting→stainless.extraction.ExtractionContextstainless.extraction.methods.MethodsException→stainless.extraction.MalformedStainlessCodestainless.extraction.methods.MutabilityAnalyzer→stainless.extraction.ExtractionPipelinestainless.extraction.methods.Sealing→stainless.extraction.CachingPhasestainless.extraction.methods.Sealing→stainless.extraction.IdentitySortsstainless.extraction.methods.Sealing→stainless.extraction.NoSummaryPhasestainless.extraction.methods.SuperCalls→stainless.extraction.CachingPhasestainless.extraction.methods.SuperCalls→stainless.extraction.NoSummaryPhasestainless.extraction.methods.SuperCalls→stainless.extraction.SimpleSortsstainless.extraction.methods.SuperInvariants→stainless.extraction.CachingPhasestainless.extraction.methods.SuperInvariants→stainless.extraction.IdentitySortsstainless.extraction.methods.SuperInvariants→stainless.extraction.NoSummaryPhasestainless.extraction.methods.SuperInvariants→stainless.extraction.SimpleFunctions
- Direction
- extraction.methods uses extraction, so a change to extraction can break extraction.methods, while a change to extraction.methods can't break extraction.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→19 extraction.methods uses extraction.oo✕
- Connections
- 12 pairs of types, where a type in extraction.methods uses a type in extraction.oo.
- The types involved
stainless.extraction.methods.FieldAccessors→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.methods.FieldAccessors→stainless.extraction.oo.SimpleClassesstainless.extraction.methods.FieldAccessors→stainless.extraction.oo.SimplyCachedClassesstainless.extraction.methods.Laws→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.methods.MergeInvariants→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.methods.Sealing→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.methods.SuperCalls→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.methods.SuperCalls→stainless.extraction.oo.SimpleClassesstainless.extraction.methods.SuperInvariants→stainless.extraction.oo.IdentityClassesstainless.extraction.methods.SuperInvariants→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.methods.ValueClasses→stainless.extraction.oo.SimpleTypeDefsstainless.extraction.methods.trees→stainless.extraction.oo.ClassSymbols
- Direction
- extraction.methods uses extraction.oo, so a change to extraction.oo can break extraction.methods, while a change to extraction.methods can't break extraction.oo.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→20 extraction.methods uses extraction.imperative.trees✕
- Connections
- 10 pairs of types, where a type in extraction.methods uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.methods.FieldAccessors→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.Laws→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.MergeInvariants→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.MethodLifting→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.Sealing→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.SuperCalls→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.SuperInvariants→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.Trees→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.ValueClasses→stainless.extraction.imperative.trees.Symbolsstainless.extraction.methods.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.methods uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.methods, while a change to extraction.methods can't break extraction.imperative.trees.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→21 extraction.methods uses extraction.oo.Definitions✕
- Connections
- 12 pairs of types, where a type in extraction.methods uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.methods.DependencyGraph→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.ExprOps→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.ExprOps→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.methods.FieldAccessors→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.Laws→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.MergeInvariants→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.Sealing→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.SuperCalls→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.ValueClasses→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.ValueClasses→stainless.extraction.oo.Definitions.TypeDefstainless.extraction.methods.trees→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.methods.trees→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.methods uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.methods, while a change to extraction.methods can't break extraction.oo.Definitions.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→23 extraction.methods uses codegen.runtime✕
- Connections
- 2 pairs of types, where a type in extraction.methods uses a type in codegen.runtime.
- The types involved
stainless.extraction.methods.DependencyGraph→stainless.codegen.runtime.Setstainless.extraction.methods.trees→stainless.codegen.runtime.Map
- Direction
- extraction.methods uses codegen.runtime, so a change to codegen.runtime can break extraction.methods, while a change to extraction.methods can't break codegen.runtime.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→24 extraction.methods uses ast.Expressions✕
- Connections
- 1 pair of types, where a type in extraction.methods uses a type in ast.Expressions.
- The types involved
stainless.extraction.methods.Trees→stainless.ast.Expressions.UnapplyPattern
- Direction
- extraction.methods uses ast.Expressions, so a change to ast.Expressions can break extraction.methods, while a change to extraction.methods can't break ast.Expressions.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→27 extraction.methods uses ast✕
- Connections
- 28 pairs of types, where a type in extraction.methods uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.extraction.methods.CallGraph→stainless.ast.CallGraphstainless.extraction.methods.CallGraph→stainless.ast.Treesstainless.extraction.methods.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.methods.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.methods.DependencyGraph→stainless.ast.CallGraphstainless.extraction.methods.DependencyGraph→stainless.ast.DependencyGraphstainless.extraction.methods.ExprOps→stainless.ast.Treesstainless.extraction.methods.FieldAccessors→stainless.ast.Treesstainless.extraction.methods.GhostTraverser→stainless.ast.Treesstainless.extraction.methods.Laws→stainless.ast.Treesstainless.extraction.methods.MergeInvariants→stainless.ast.Treesstainless.extraction.methods.MethodLifting→stainless.ast.Treesstainless.extraction.methods.MutabilityAnalyzer→stainless.ast.Treesstainless.extraction.methods.Printer→stainless.ast.Printerstainless.extraction.methods.Printer→stainless.ast.Treesstainless.extraction.methods.Sealing→stainless.ast.Treesstainless.extraction.methods.SuperCalls→stainless.ast.SymbolIdentifierstainless.extraction.methods.SuperCalls→stainless.ast.Treesstainless.extraction.methods.SuperInvariants→stainless.ast.Treesstainless.extraction.methods.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.methods.TreeDeconstructor→stainless.ast.Treesstainless.extraction.methods.Trees→stainless.ast.ExprOpsstainless.extraction.methods.Trees→stainless.ast.Treesstainless.extraction.methods.TypeOps→stainless.ast.SymbolIdentifierstainless.extraction.methods.TypeOps→stainless.ast.Trees
- Direction
- extraction.methods uses ast, so a change to ast can break extraction.methods, while a change to extraction.methods can't break ast.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
33→31 extraction.methods uses stainless✕
- Connections
- 8 pairs of types, where a type in extraction.methods uses a type in stainless.
- The types involved
stainless.extraction.methods.FieldAccessors→stainless.Contextstainless.extraction.methods.Laws→stainless.Contextstainless.extraction.methods.MergeInvariants→stainless.Contextstainless.extraction.methods.MethodLifting→stainless.Contextstainless.extraction.methods.Sealing→stainless.Contextstainless.extraction.methods.SuperCalls→stainless.Contextstainless.extraction.methods.SuperInvariants→stainless.Contextstainless.extraction.methods.ValueClasses→stainless.Context
- Direction
- extraction.methods uses stainless, so a change to stainless can break extraction.methods, while a change to extraction.methods can't break stainless.
- Position
- Below the diagonal: extraction.methods uses a module listed above it, which is the healthy direction.
34→5 extraction.xlang uses genc.ir.IR✕
- Connections
- 2 pairs of types, where a type in extraction.xlang uses a type in genc.ir.IR.
- The types involved
stainless.extraction.xlang.ConstructsUsage→stainless.genc.ir.IR.FunDefstainless.extraction.xlang.trees→stainless.genc.ir.IR.FunDef
- Direction
- extraction.xlang uses genc.ir.IR, so a change to genc.ir.IR can break extraction.xlang, while a change to extraction.xlang can't break genc.ir.IR.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→6 extraction.xlang uses genc.CAST✕
- Connections
- 2 pairs of types, where a type in extraction.xlang uses a type in genc.CAST.
- The types involved
stainless.extraction.xlang.Printer→stainless.genc.CAST.Treestainless.extraction.xlang.Trees→stainless.genc.CAST.Expr
- Direction
- extraction.xlang uses genc.CAST, so a change to genc.CAST can break extraction.xlang, while a change to extraction.xlang can't break genc.CAST.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→10 extraction.xlang uses genc✕
- Connections
- 1 pair of types, where a type in extraction.xlang uses a type in genc.
- The types involved
stainless.extraction.xlang.Printer→stainless.genc.PrinterContext
- Direction
- extraction.xlang uses genc, so a change to genc can break extraction.xlang, while a change to extraction.xlang can't break genc.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→14 extraction.xlang uses extraction.imperative✕
- Connections
- 1 pair of types, where a type in extraction.xlang uses a type in extraction.imperative.
- The types involved
stainless.extraction.xlang.GhostTraverser→stainless.extraction.imperative.GhostTraverser
- Direction
- extraction.xlang uses extraction.imperative, so a change to extraction.imperative can break extraction.xlang, while a change to extraction.xlang can't break extraction.imperative.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→17 extraction.xlang uses extraction✕
- Connections
- 9 pairs of types, where a type in extraction.xlang uses a type in extraction.
- The types involved
stainless.extraction.xlang.ConstructsUsage→stainless.extraction.CachingPhasestainless.extraction.xlang.ConstructsUsage→stainless.extraction.ExtractionSummarystainless.extraction.xlang.ConstructsUsage→stainless.extraction.IdentitySortsstainless.extraction.xlang.ConstructsUsage→stainless.extraction.SimpleFunctionsstainless.extraction.xlang.ConstructsUsage→stainless.extraction.SimplyCachedFunctionsstainless.extraction.xlang.PartialFunctions→stainless.extraction.SimplePhasestainless.extraction.xlang.PartialFunctions→stainless.extraction.SimplyCachedFunctionsstainless.extraction.xlang.PartialFunctions→stainless.extraction.SimplyCachedSortsstainless.extraction.xlang.TreeSanitizer→stainless.extraction.MalformedStainlessCode
- Direction
- extraction.xlang uses extraction, so a change to extraction can break extraction.xlang, while a change to extraction.xlang can't break extraction.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→19 extraction.xlang uses extraction.oo✕
- Connections
- 6 pairs of types, where a type in extraction.xlang uses a type in extraction.oo.
- The types involved
stainless.extraction.xlang.ConstructsUsage→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.xlang.ConstructsUsage→stainless.extraction.oo.SimpleClassesstainless.extraction.xlang.ConstructsUsage→stainless.extraction.oo.SimplyCachedClassesstainless.extraction.xlang.PartialFunctions→stainless.extraction.oo.IdentityTypeDefsstainless.extraction.xlang.PartialFunctions→stainless.extraction.oo.SimplyCachedClassesstainless.extraction.xlang.trees→stainless.extraction.oo.ClassSymbols
- Direction
- extraction.xlang uses extraction.oo, so a change to extraction.oo can break extraction.xlang, while a change to extraction.xlang can't break extraction.oo.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→20 extraction.xlang uses extraction.imperative.trees✕
- Connections
- 4 pairs of types, where a type in extraction.xlang uses a type in extraction.imperative.trees.
- The types involved
stainless.extraction.xlang.ConstructsUsage→stainless.extraction.imperative.trees.Symbolsstainless.extraction.xlang.PartialFunctions→stainless.extraction.imperative.trees.Symbolsstainless.extraction.xlang.TreeSanitizer→stainless.extraction.imperative.trees.Symbolsstainless.extraction.xlang.trees→stainless.extraction.imperative.trees.Symbols
- Direction
- extraction.xlang uses extraction.imperative.trees, so a change to extraction.imperative.trees can break extraction.xlang, while a change to extraction.xlang can't break extraction.imperative.trees.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→21 extraction.xlang uses extraction.oo.Definitions✕
- Connections
- 3 pairs of types, where a type in extraction.xlang uses a type in extraction.oo.Definitions.
- The types involved
stainless.extraction.xlang.ConstructsUsage→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.xlang.trees→stainless.extraction.oo.Definitions.ClassDefstainless.extraction.xlang.trees→stainless.extraction.oo.Definitions.TypeDef
- Direction
- extraction.xlang uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break extraction.xlang, while a change to extraction.xlang can't break extraction.oo.Definitions.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→23 extraction.xlang uses codegen.runtime✕
- Connections
- 1 pair of types, where a type in extraction.xlang uses a type in codegen.runtime.
- The types involved
stainless.extraction.xlang.trees→stainless.codegen.runtime.Map
- Direction
- extraction.xlang uses codegen.runtime, so a change to codegen.runtime can break extraction.xlang, while a change to extraction.xlang can't break codegen.runtime.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→27 extraction.xlang uses ast✕
- Connections
- 12 pairs of types, where a type in extraction.xlang uses a type in ast.
- The types involved
stainless.extraction.xlang.ConcreteTreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.xlang.ConcreteTreeDeconstructor→stainless.ast.Treesstainless.extraction.xlang.ConstructsUsage→stainless.ast.Treesstainless.extraction.xlang.GhostTraverser→stainless.ast.Treesstainless.extraction.xlang.PartialFunctions→stainless.ast.Treesstainless.extraction.xlang.Printer→stainless.ast.Printerstainless.extraction.xlang.Printer→stainless.ast.Treesstainless.extraction.xlang.TreeDeconstructor→stainless.ast.TreeDeconstructorstainless.extraction.xlang.TreeDeconstructor→stainless.ast.Treesstainless.extraction.xlang.TreeSanitizer→stainless.ast.Treesstainless.extraction.xlang.Trees→stainless.ast.Treesstainless.extraction.xlang.trees→stainless.ast.Trees
- Direction
- extraction.xlang uses ast, so a change to ast can break extraction.xlang, while a change to extraction.xlang can't break ast.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
34→31 extraction.xlang uses stainless✕
- Connections
- 3 pairs of types, where a type in extraction.xlang uses a type in stainless.
- The types involved
stainless.extraction.xlang.ConstructsUsage→stainless.Contextstainless.extraction.xlang.PartialFunctions→stainless.Contextstainless.extraction.xlang.TreeSanitizer→stainless.Context
- Direction
- extraction.xlang uses stainless, so a change to stainless can break extraction.xlang, while a change to extraction.xlang can't break stainless.
- Position
- Below the diagonal: extraction.xlang uses a module listed above it, which is the healthy direction.
35→1 genc.phases uses algebra.ops✕
- Connections
- 1 pair of types, where a type in genc.phases uses a type in algebra.ops.
- The types involved
stainless.genc.phases.S2IRImpl→stainless.algebra.ops.List
- Direction
- genc.phases uses algebra.ops, so a change to algebra.ops can break genc.phases, while a change to genc.phases can't break algebra.ops.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→3 genc.phases uses extraction.oo.Trees✕
- Connections
- 1 pair of types, where a type in genc.phases uses a type in extraction.oo.Trees.
- The types involved
stainless.genc.phases.S2IRImpl→stainless.extraction.oo.Trees.ClassType
- Direction
- genc.phases uses extraction.oo.Trees, so a change to extraction.oo.Trees can break genc.phases, while a change to genc.phases can't break extraction.oo.Trees.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→4 genc.phases uses lang✕
- Connections
- 1 pair of types, where a type in genc.phases uses a type in lang.
- The types involved
stainless.genc.phases.IR2CImpl→stainless.lang.Either
- Direction
- genc.phases uses lang, so a change to lang can break genc.phases, while a change to genc.phases can't break lang.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→5 genc.phases uses genc.ir.IR✕
- Connections
- 8 pairs of types, where a type in genc.phases uses a type in genc.ir.IR.
- The types involved
stainless.genc.phases.GhostElimination→stainless.genc.ir.IR.FunDefstainless.genc.phases.IR2CImpl→stainless.genc.ir.IR.FunBodystainless.genc.phases.IR2CImpl→stainless.genc.ir.IR.FunDefstainless.genc.phases.IR2CImpl→stainless.genc.ir.IR.ValDefstainless.genc.phases.S2IRImpl→stainless.genc.ir.IR.FunDefstainless.genc.phases.S2IRImpl→stainless.genc.ir.IR.ValDefstainless.genc.phases.Trimmer→stainless.genc.ir.IR.FunDefstainless.genc.phases.VarInfo→stainless.genc.ir.IR.ValDef
- Direction
- genc.phases uses genc.ir.IR, so a change to genc.ir.IR can break genc.phases, while a change to genc.phases can't break genc.ir.IR.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→6 genc.phases uses genc.CAST✕
- Connections
- 26 pairs of types, where a type in genc.phases uses a type in genc.CAST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
stainless.genc.phases.GhostElimination→stainless.genc.CAST.Exprstainless.genc.phases.IR2CImpl→stainless.genc.CAST.DataTypestainless.genc.phases.IR2CImpl→stainless.genc.CAST.Enumstainless.genc.phases.IR2CImpl→stainless.genc.CAST.EnumLiteralstainless.genc.phases.IR2CImpl→stainless.genc.CAST.Exprstainless.genc.phases.IR2CImpl→stainless.genc.CAST.Includestainless.genc.phases.IR2CImpl→stainless.genc.CAST.Progstainless.genc.phases.IR2CImpl→stainless.genc.CAST.Structstainless.genc.phases.IR2CImpl→stainless.genc.CAST.StructInitstainless.genc.phases.IR2CImpl→stainless.genc.CAST.Typestainless.genc.phases.IR2CImpl→stainless.genc.CAST.Unionstainless.genc.phases.IR2CImpl→stainless.genc.CAST.Varstainless.genc.phases.IR2CPhase→stainless.genc.CAST.Progstainless.genc.phases.LiftingPhase→stainless.genc.CAST.Progstainless.genc.phases.NormalisationPhase→stainless.genc.CAST.Progstainless.genc.phases.ReferencingPhase→stainless.genc.CAST.Progstainless.genc.phases.S2IRImpl→stainless.genc.CAST.BinOpstainless.genc.phases.S2IRImpl→stainless.genc.CAST.Bindingstainless.genc.phases.S2IRImpl→stainless.genc.CAST.Exprstainless.genc.phases.S2IRImpl→stainless.genc.CAST.Typestainless.genc.phases.Scala2IRPhase→stainless.genc.CAST.Progstainless.genc.phases.StructInliningPhase→stainless.genc.CAST.Progstainless.genc.phases.TailRecElimPhase→stainless.genc.CAST.Progstainless.genc.phases.Trimmer→stainless.genc.CAST.Exprstainless.genc.phases.Trimmer→stainless.genc.CAST.Type
- Direction
- genc.phases uses genc.CAST, so a change to genc.CAST can break genc.phases, while a change to genc.phases can't break genc.CAST.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→8 genc.phases uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer✕
- Connections
- 2 pairs of types, where a type in genc.phases uses a type in extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- The types involved
stainless.genc.phases.GhostElimination→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Envstainless.genc.phases.S2IRImpl→stainless.extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.Env
- Direction
- genc.phases uses extraction.imperative.RefTransform.RefTransformContext.funRefTransformer, so a change to extraction.imperative.RefTransform.RefTransformContext.funRefTransformer can break genc.phases, while a change to genc.phases can't break extraction.imperative.RefTransform.RefTransformContext.funRefTransformer.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→10 genc.phases uses genc✕
- Connections
- 11 pairs of types, where a type in genc.phases uses a type in genc.
- The types involved
stainless.genc.phases.ComputeFunCtxPhase→stainless.genc.LeonPipelinestainless.genc.phases.GhostEliminationPhase→stainless.genc.LeonPipelinestainless.genc.phases.IR2CPhase→stainless.genc.LeonPipelinestainless.genc.phases.LiftingPhase→stainless.genc.LeonPipelinestainless.genc.phases.NormalisationPhase→stainless.genc.LeonPipelinestainless.genc.phases.ReferencingPhase→stainless.genc.LeonPipelinestainless.genc.phases.S2IRImpl→stainless.genc.DeclarationModestainless.genc.phases.Scala2IRPhase→stainless.genc.LeonPipelinestainless.genc.phases.StructInliningPhase→stainless.genc.LeonPipelinestainless.genc.phases.TailRecElimPhase→stainless.genc.LeonPipelinestainless.genc.phases.TrimSymbols→stainless.genc.LeonPipeline
- Direction
- genc.phases uses genc, so a change to genc can break genc.phases, while a change to genc.phases can't break genc.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→11 genc.phases uses extraction.innerfuns.Definitions✕
- Connections
- 3 pairs of types, where a type in genc.phases uses a type in extraction.innerfuns.Definitions.
- The types involved
stainless.genc.phases.GhostElimination→stainless.extraction.innerfuns.Definitions.LocalFunDefstainless.genc.phases.S2IRImpl→stainless.extraction.innerfuns.Definitions.FunAbstractionstainless.genc.phases.Trimmer→stainless.extraction.innerfuns.Definitions.LocalFunDef
- Direction
- genc.phases uses extraction.innerfuns.Definitions, so a change to extraction.innerfuns.Definitions can break genc.phases, while a change to genc.phases can't break extraction.innerfuns.Definitions.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→12 genc.phases uses genc.ir✕
- Connections
- 1 pair of types, where a type in genc.phases uses a type in genc.ir.
- The types involved
stainless.genc.phases.GhostElimination→stainless.genc.ir.Transformer
- Direction
- genc.phases uses genc.ir, so a change to genc.ir can break genc.phases, while a change to genc.phases can't break genc.ir.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→14 genc.phases uses extraction.imperative✕
- Connections
- 2 pairs of types, where a type in genc.phases uses a type in extraction.imperative.
- The types involved
stainless.genc.phases.S2IRImpl→stainless.extraction.imperative.EffectsAnalyzerstainless.genc.phases.Trimmer→stainless.extraction.imperative.TransformerWithType
- Direction
- genc.phases uses extraction.imperative, so a change to extraction.imperative can break genc.phases, while a change to genc.phases can't break extraction.imperative.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→17 genc.phases uses extraction✕
- Connections
- 3 pairs of types, where a type in genc.phases uses a type in extraction.
- The types involved
stainless.genc.phases.S2IRImpl→stainless.extraction.IdentityFunctionsstainless.genc.phases.S2IRImpl→stainless.extraction.IdentitySortsstainless.genc.phases.S2IRImpl→stainless.extraction.NoSummaryPhase
- Direction
- genc.phases uses extraction, so a change to extraction can break genc.phases, while a change to genc.phases can't break extraction.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→19 genc.phases uses extraction.oo✕
- Connections
- 2 pairs of types, where a type in genc.phases uses a type in extraction.oo.
- The types involved
stainless.genc.phases.S2IRImpl→stainless.extraction.oo.IdentityClassesstainless.genc.phases.S2IRImpl→stainless.extraction.oo.IdentityTypeDefs
- Direction
- genc.phases uses extraction.oo, so a change to extraction.oo can break genc.phases, while a change to genc.phases can't break extraction.oo.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→20 genc.phases uses extraction.imperative.trees✕
- Connections
- 8 pairs of types, where a type in genc.phases uses a type in extraction.imperative.trees.
- The types involved
stainless.genc.phases.ArraysLengthsExtraction→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.ComputeFunCtxPhase→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.GhostElimination→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.GhostEliminationPhase→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.GlobalStateChecker→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.S2IRImpl→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.TrimSymbols→stainless.extraction.imperative.trees.Symbolsstainless.genc.phases.Trimmer→stainless.extraction.imperative.trees.Symbols
- Direction
- genc.phases uses extraction.imperative.trees, so a change to extraction.imperative.trees can break genc.phases, while a change to genc.phases can't break extraction.imperative.trees.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→21 genc.phases uses extraction.oo.Definitions✕
- Connections
- 5 pairs of types, where a type in genc.phases uses a type in extraction.oo.Definitions.
- The types involved
stainless.genc.phases.GhostElimination→stainless.extraction.oo.Definitions.ClassDefstainless.genc.phases.IR2CImpl→stainless.extraction.oo.Definitions.ClassDefstainless.genc.phases.IR2CImpl→stainless.extraction.oo.Definitions.TypeDefstainless.genc.phases.S2IRImpl→stainless.extraction.oo.Definitions.ClassDefstainless.genc.phases.Trimmer→stainless.extraction.oo.Definitions.ClassDef
- Direction
- genc.phases uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break genc.phases, while a change to genc.phases can't break extraction.oo.Definitions.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→23 genc.phases uses codegen.runtime✕
- Connections
- 4 pairs of types, where a type in genc.phases uses a type in codegen.runtime.
- The types involved
stainless.genc.phases.ArraysLengthsExtraction→stainless.codegen.runtime.Mapstainless.genc.phases.IR2CImpl→stainless.codegen.runtime.Mapstainless.genc.phases.S2IRImpl→stainless.codegen.runtime.Setstainless.genc.phases.Scala2IRPhase→stainless.codegen.runtime.Map
- Direction
- genc.phases uses codegen.runtime, so a change to codegen.runtime can break genc.phases, while a change to genc.phases can't break codegen.runtime.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→24 genc.phases uses ast.Expressions✕
- Connections
- 1 pair of types, where a type in genc.phases uses a type in ast.Expressions.
- The types involved
stainless.genc.phases.S2IRImpl→stainless.ast.Expressions.MatchCase
- Direction
- genc.phases uses ast.Expressions, so a change to ast.Expressions can break genc.phases, while a change to genc.phases can't break ast.Expressions.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→27 genc.phases uses ast✕
- Connections
- 1 pair of types, where a type in genc.phases uses a type in ast.
- The types involved
stainless.genc.phases.GhostElimination→stainless.ast.Trees
- Direction
- genc.phases uses ast, so a change to ast can break genc.phases, while a change to genc.phases can't break ast.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
35→31 genc.phases uses stainless✕
- Connections
- 15 pairs of types, where a type in genc.phases uses a type in stainless.
- The types involved
stainless.genc.phases.ArraysLengthsExtraction→stainless.Contextstainless.genc.phases.ComputeFunCtxPhase→stainless.Contextstainless.genc.phases.GhostElimination→stainless.Contextstainless.genc.phases.GhostEliminationPhase→stainless.Contextstainless.genc.phases.GlobalStateChecker→stainless.Contextstainless.genc.phases.IR2CPhase→stainless.Contextstainless.genc.phases.LiftingPhase→stainless.Contextstainless.genc.phases.NormalisationPhase→stainless.Contextstainless.genc.phases.ReferencingPhase→stainless.Contextstainless.genc.phases.S2IRImpl→stainless.Contextstainless.genc.phases.Scala2IRPhase→stainless.Contextstainless.genc.phases.StructInliningPhase→stainless.Contextstainless.genc.phases.TailRecElimPhase→stainless.Contextstainless.genc.phases.TrimSymbols→stainless.Contextstainless.genc.phases.Trimmer→stainless.Context
- Direction
- genc.phases uses stainless, so a change to stainless can break genc.phases, while a change to genc.phases can't break stainless.
- Position
- Below the diagonal: genc.phases uses a module listed above it, which is the healthy direction.
36→1 termination uses algebra.ops✕
- Connections
- 2 pairs of types, where a type in termination uses a type in algebra.ops.
- The types involved
stainless.termination.DecreasesProcessor→stainless.algebra.ops.Liststainless.termination.ProcessingPipeline→stainless.algebra.ops.List
- Direction
- termination uses algebra.ops, so a change to algebra.ops can break termination, while a change to termination can't break algebra.ops.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→2 termination uses extraction.imperative.EffectElaboration✕
- Connections
- 1 pair of types, where a type in termination uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.termination.MeasureInference→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- termination uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break termination, while a change to termination can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→4 termination uses lang✕
- Connections
- 9 pairs of types, where a type in termination uses a type in lang.
- The types involved
stainless.termination.CICFA→stainless.lang.MutableMapstainless.termination.ChainBuilder→stainless.lang.MutableMapstainless.termination.ChainProcessor→stainless.lang.MutableMapstainless.termination.DatatypeChecker→stainless.lang.MutableMapstainless.termination.DecreasesProcessor→stainless.lang.PartialFunctionstainless.termination.ProcessingPipeline→stainless.lang.MutableMapstainless.termination.RelationBuilder→stainless.lang.MutableMapstainless.termination.SizeFunctions→stainless.lang.MutableMapstainless.termination.Strengthener→stainless.lang.MutableMap
- Direction
- termination uses lang, so a change to lang can break termination, while a change to termination can't break lang.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→5 termination uses genc.ir.IR✕
- Connections
- 13 pairs of types, where a type in termination uses a type in genc.ir.IR.
- The types involved
stainless.termination.ChainBuilder→stainless.genc.ir.IR.FunDefstainless.termination.ChainProcessor→stainless.genc.ir.IR.FunDefstainless.termination.DatatypeChecker→stainless.genc.ir.IR.FunDefstainless.termination.FailedMeasureInference→stainless.genc.ir.IR.FunDefstainless.termination.MeasureInference→stainless.genc.ir.IR.FunDefstainless.termination.ProcessingPipeline→stainless.genc.ir.IR.FunDefstainless.termination.RelationBuilder→stainless.genc.ir.IR.FunDefstainless.termination.SizeFunctions→stainless.genc.ir.IR.FunDefstainless.termination.Strengthener→stainless.genc.ir.IR.FunDefstainless.termination.Strengthener→stainless.genc.ir.IR.ValDefstainless.termination.StructuralSize→stainless.genc.ir.IR.FunDefstainless.termination.TerminationAnalysis→stainless.genc.ir.IR.FunDefstainless.termination.TerminationChecker→stainless.genc.ir.IR.FunDef
- Direction
- termination uses genc.ir.IR, so a change to genc.ir.IR can break termination, while a change to termination can't break genc.ir.IR.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→6 termination uses genc.CAST✕
- Connections
- 13 pairs of types, where a type in termination uses a type in genc.CAST.
- The types involved
stainless.termination.BVOrdering→stainless.genc.CAST.Exprstainless.termination.ChainProcessor→stainless.genc.CAST.Exprstainless.termination.DecreasesProcessor→stainless.genc.CAST.Exprstainless.termination.LexicographicOrdering→stainless.genc.CAST.Exprstainless.termination.OrderingProcessor→stainless.genc.CAST.Exprstainless.termination.OrderingRelation→stainless.genc.CAST.Exprstainless.termination.RecursionProcessor→stainless.genc.CAST.Exprstainless.termination.SelfCallsProcessor→stainless.genc.CAST.Exprstainless.termination.SizeFunctions→stainless.genc.CAST.Exprstainless.termination.Strengthener→stainless.genc.CAST.Exprstainless.termination.StructuralSize→stainless.genc.CAST.Exprstainless.termination.StructuralSize→stainless.genc.CAST.Typestainless.termination.SumOrdering→stainless.genc.CAST.Expr
- Direction
- termination uses genc.CAST, so a change to genc.CAST can break termination, while a change to termination can't break genc.CAST.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→15 termination uses extraction.innerclasses✕
- Connections
- 1 pair of types, where a type in termination uses a type in extraction.innerclasses.
- The types involved
stainless.termination.SolverProvider→stainless.extraction.innerclasses.TreeTransformer
- Direction
- termination uses extraction.innerclasses, so a change to extraction.innerclasses can break termination, while a change to termination can't break extraction.innerclasses.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→17 termination uses extraction✕
- Connections
- 6 pairs of types, where a type in termination uses a type in extraction.
- The types involved
stainless.termination.MeasureInference→stainless.extraction.CachingPhasestainless.termination.MeasureInference→stainless.extraction.IdentitySortsstainless.termination.MeasureInference→stainless.extraction.NoSummaryPhasestainless.termination.MeasureInference→stainless.extraction.SimplyCachedSortsstainless.termination.TerminationAnalysis→stainless.extraction.ExtractionSummarystainless.termination.TerminationRun→stainless.extraction.ExtractionSummary
- Direction
- termination uses extraction, so a change to extraction can break termination, while a change to termination can't break extraction.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→19 termination uses extraction.oo✕
- Connections
- 1 pair of types, where a type in termination uses a type in extraction.oo.
- The types involved
stainless.termination.SolverProvider→stainless.extraction.oo.SymbolTransformer
- Direction
- termination uses extraction.oo, so a change to extraction.oo can break termination, while a change to termination can't break extraction.oo.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→20 termination uses extraction.imperative.trees✕
- Connections
- 5 pairs of types, where a type in termination uses a type in extraction.imperative.trees.
- The types involved
stainless.termination.ChainProcessor→stainless.extraction.imperative.trees.Symbolsstainless.termination.MeasureInference→stainless.extraction.imperative.trees.Symbolsstainless.termination.SizeFunctions→stainless.extraction.imperative.trees.Symbolsstainless.termination.SolverProvider→stainless.extraction.imperative.trees.Symbolsstainless.termination.TerminationRun→stainless.extraction.imperative.trees.Symbols
- Direction
- termination uses extraction.imperative.trees, so a change to extraction.imperative.trees can break termination, while a change to termination can't break extraction.imperative.trees.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→22 termination uses genc.phases.IR2CImpl✕
- Connections
- 1 pair of types, where a type in termination uses a type in genc.phases.IR2CImpl.
- The types involved
stainless.termination.ProcessingPipeline→stainless.genc.phases.IR2CImpl.Array
- Direction
- termination uses genc.phases.IR2CImpl, so a change to genc.phases.IR2CImpl can break termination, while a change to termination can't break genc.phases.IR2CImpl.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→23 termination uses codegen.runtime✕
- Connections
- 9 pairs of types, where a type in termination uses a type in codegen.runtime.
- The types involved
stainless.termination.BVOrdering→stainless.codegen.runtime.Mapstainless.termination.ChainProcessor→stainless.codegen.runtime.Mapstainless.termination.DatatypeChecker→stainless.codegen.runtime.Setstainless.termination.RelationBuilder→stainless.codegen.runtime.Setstainless.termination.Strengthener→stainless.codegen.runtime.Lambdastainless.termination.Strengthener→stainless.codegen.runtime.Setstainless.termination.StructuralSize→stainless.codegen.runtime.Setstainless.termination.TerminationAnalysis→stainless.codegen.runtime.Mapstainless.termination.TerminationAnalysis→stainless.codegen.runtime.Set
- Direction
- termination uses codegen.runtime, so a change to codegen.runtime can break termination, while a change to termination can't break codegen.runtime.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→27 termination uses ast✕
- Connections
- 2 pairs of types, where a type in termination uses a type in ast.
- The types involved
stainless.termination.MeasureInference→stainless.ast.Treesstainless.termination.SizeFunctions→stainless.ast.Trees
- Direction
- termination uses ast, so a change to ast can break termination, while a change to termination can't break ast.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
36→31 termination uses stainless✕
- Connections
- 8 pairs of types, where a type in termination uses a type in stainless.
- The types involved
stainless.termination.CICFA→stainless.Contextstainless.termination.MeasureInference→stainless.Contextstainless.termination.TerminationAnalysis→stainless.AbstractAnalysisstainless.termination.TerminationChecker→stainless.Contextstainless.termination.TerminationComponent→stainless.Componentstainless.termination.TerminationComponent→stainless.Contextstainless.termination.TerminationRun→stainless.ComponentRunstainless.termination.TerminationRun→stainless.Context
- Direction
- termination uses stainless, so a change to stainless can break termination, while a change to termination can't break stainless.
- Position
- Below the diagonal: termination uses a module listed above it, which is the healthy direction.
37→2 verification uses extraction.imperative.EffectElaboration✕
- Connections
- 1 pair of types, where a type in verification uses a type in extraction.imperative.EffectElaboration.
- The types involved
stainless.verification.PartialEvaluation→stainless.extraction.imperative.EffectElaboration.TransformerContext
- Direction
- verification uses extraction.imperative.EffectElaboration, so a change to extraction.imperative.EffectElaboration can break verification, while a change to verification can't break extraction.imperative.EffectElaboration.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→5 verification uses genc.ir.IR✕
- Connections
- 5 pairs of types, where a type in verification uses a type in genc.ir.IR.
- The types involved
stainless.verification.CoqEncoder→stainless.genc.ir.IR.FunDefstainless.verification.PartialEvaluation→stainless.genc.ir.IR.FunDefstainless.verification.TypeChecker→stainless.genc.ir.IR.FunDefstainless.verification.TypeChecker→stainless.genc.ir.IR.ValDefstainless.verification.TypeCheckerUtils→stainless.genc.ir.IR.ValDef
- Direction
- verification uses genc.ir.IR, so a change to genc.ir.IR can break verification, while a change to verification can't break genc.ir.IR.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→6 verification uses genc.CAST✕
- Connections
- 10 pairs of types, where a type in verification uses a type in genc.CAST.
- The types involved
stainless.verification.AssertionInjector→stainless.genc.CAST.Exprstainless.verification.CoqEncoder→stainless.genc.CAST.Exprstainless.verification.CoqEncoder→stainless.genc.CAST.Typestainless.verification.CoqVerificationChecker→stainless.genc.CAST.Exprstainless.verification.TypeChecker→stainless.genc.CAST.Exprstainless.verification.TypeChecker→stainless.genc.CAST.Typestainless.verification.TypeCheckerUtils→stainless.genc.CAST.Exprstainless.verification.TypeCheckerUtils→stainless.genc.CAST.Typestainless.verification.VC→stainless.genc.CAST.Exprstainless.verification.VerificationChecker→stainless.genc.CAST.Expr
- Direction
- verification uses genc.CAST, so a change to genc.CAST can break verification, while a change to verification can't break genc.CAST.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→15 verification uses extraction.innerclasses✕
- Connections
- 1 pair of types, where a type in verification uses a type in extraction.innerclasses.
- The types involved
stainless.verification.AssertionInjector→stainless.extraction.innerclasses.ConcreteTreeTransformer
- Direction
- verification uses extraction.innerclasses, so a change to extraction.innerclasses can break verification, while a change to verification can't break extraction.innerclasses.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→17 verification uses extraction✕
- Connections
- 6 pairs of types, where a type in verification uses a type in extraction.
- The types involved
stainless.verification.PartialEvaluation→stainless.extraction.CachingPhasestainless.verification.PartialEvaluation→stainless.extraction.IdentitySortsstainless.verification.PartialEvaluation→stainless.extraction.NoSummaryPhasestainless.verification.PartialEvaluation→stainless.extraction.SimpleFunctionsstainless.verification.VerificationAnalysis→stainless.extraction.ExtractionSummarystainless.verification.VerificationRun→stainless.extraction.ExtractionSummary
- Direction
- verification uses extraction, so a change to extraction can break verification, while a change to verification can't break extraction.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→19 verification uses extraction.oo✕
- Connections
- 1 pair of types, where a type in verification uses a type in extraction.oo.
- The types involved
stainless.verification.OpaqueChooseInjector→stainless.extraction.oo.SymbolTransformer
- Direction
- verification uses extraction.oo, so a change to extraction.oo can break verification, while a change to verification can't break extraction.oo.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→20 verification uses extraction.imperative.trees✕
- Connections
- 4 pairs of types, where a type in verification uses a type in extraction.imperative.trees.
- The types involved
stainless.verification.AssertionInjector→stainless.extraction.imperative.trees.Symbolsstainless.verification.OpaqueChooseInjector→stainless.extraction.imperative.trees.Symbolsstainless.verification.PartialEvaluation→stainless.extraction.imperative.trees.Symbolsstainless.verification.VerificationRun→stainless.extraction.imperative.trees.Symbols
- Direction
- verification uses extraction.imperative.trees, so a change to extraction.imperative.trees can break verification, while a change to verification can't break extraction.imperative.trees.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→23 verification uses codegen.runtime✕
- Connections
- 7 pairs of types, where a type in verification uses a type in codegen.runtime.
- The types involved
stainless.verification.CoqTacticPattern→stainless.codegen.runtime.Mapstainless.verification.CoqVerificationChecker→stainless.codegen.runtime.Mapstainless.verification.CoqZNum→stainless.codegen.runtime.BigIntstainless.verification.TypeCheckerUtils→stainless.codegen.runtime.Mapstainless.verification.VerificationAnalysis→stainless.codegen.runtime.Mapstainless.verification.VerificationAnalysis→stainless.codegen.runtime.Setstainless.verification.VerificationChecker→stainless.codegen.runtime.Map
- Direction
- verification uses codegen.runtime, so a change to codegen.runtime can break verification, while a change to verification can't break codegen.runtime.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→24 verification uses ast.Expressions✕
- Connections
- 2 pairs of types, where a type in verification uses a type in ast.Expressions.
- The types involved
stainless.verification.CoqEncoder→stainless.ast.Expressions.MatchCasestainless.verification.CoqEncoder→stainless.ast.Expressions.Pattern
- Direction
- verification uses ast.Expressions, so a change to ast.Expressions can break verification, while a change to verification can't break ast.Expressions.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→27 verification uses ast✕
- Connections
- 3 pairs of types, where a type in verification uses a type in ast.
- The types involved
stainless.verification.AssertionInjector→stainless.ast.Treesstainless.verification.OpaqueChooseInjector→stainless.ast.Treesstainless.verification.PartialEvaluation→stainless.ast.Trees
- Direction
- verification uses ast, so a change to ast can break verification, while a change to verification can't break ast.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
37→31 verification uses stainless✕
- Connections
- 15 pairs of types, where a type in verification uses a type in stainless.
- The types involved
stainless.verification.CoqEncoder→stainless.Contextstainless.verification.CoqIO→stainless.Contextstainless.verification.CoqVerificationChecker→stainless.Contextstainless.verification.OpaqueChooseInjector→stainless.Contextstainless.verification.PartialEvaluation→stainless.Contextstainless.verification.TypeChecker→stainless.Contextstainless.verification.TypeCheckerUtils→stainless.Contextstainless.verification.VCResultMessage→stainless.ReportMessagestainless.verification.VerificationAnalysis→stainless.AbstractAnalysisstainless.verification.VerificationAnalysis→stainless.Contextstainless.verification.VerificationChecker→stainless.Contextstainless.verification.VerificationComponent→stainless.Componentstainless.verification.VerificationComponent→stainless.Contextstainless.verification.VerificationRun→stainless.ComponentRunstainless.verification.VerificationRun→stainless.Context
- Direction
- verification uses stainless, so a change to stainless can break verification, while a change to verification can't break stainless.
- Position
- Below the diagonal: verification uses a module listed above it, which is the healthy direction.
38→4 codegen uses lang✕
- Connections
- 2 pairs of types, where a type in codegen uses a type in lang.
- The types involved
stainless.codegen.CodeGeneration→stainless.lang.MutableMapstainless.codegen.CompilationUnit→stainless.lang.MutableMap
- Direction
- codegen uses lang, so a change to lang can break codegen, while a change to codegen can't break lang.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
38→5 codegen uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in codegen uses a type in genc.ir.IR.
- The types involved
stainless.codegen.CodeGeneration→stainless.genc.ir.IR.FunDefstainless.codegen.CodeGeneration→stainless.genc.ir.IR.ValDefstainless.codegen.CompilationUnit→stainless.genc.ir.IR.ValDef
- Direction
- codegen uses genc.ir.IR, so a change to genc.ir.IR can break codegen, while a change to codegen can't break genc.ir.IR.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
38→6 codegen uses genc.CAST✕
- Connections
- 4 pairs of types, where a type in codegen uses a type in genc.CAST.
- The types involved
stainless.codegen.CodeGeneration→stainless.genc.CAST.Exprstainless.codegen.CodeGeneration→stainless.genc.CAST.Typestainless.codegen.CompilationUnit→stainless.genc.CAST.Exprstainless.codegen.CompilationUnit→stainless.genc.CAST.Type
- Direction
- codegen uses genc.CAST, so a change to genc.CAST can break codegen, while a change to codegen can't break genc.CAST.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
38→23 codegen uses codegen.runtime✕
- Connections
- 2 pairs of types, where a type in codegen uses a type in codegen.runtime.
- The types involved
stainless.codegen.CodeGeneration→stainless.codegen.runtime.Lambdastainless.codegen.CompilationUnit→stainless.codegen.runtime.Monitor
- Direction
- codegen uses codegen.runtime, so a change to codegen.runtime can break codegen, while a change to codegen can't break codegen.runtime.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
38→29 codegen uses utils✕
- Connections
- 2 pairs of types, where a type in codegen uses a type in utils.
- The types involved
stainless.codegen.exprCounter→stainless.utils.UniqueCounterstainless.codegen.forallCounter→stainless.utils.UniqueCounter
- Direction
- codegen uses utils, so a change to utils can break codegen, while a change to codegen can't break utils.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
38→31 codegen uses stainless✕
- Connections
- 1 pair of types, where a type in codegen uses a type in stainless.
- The types involved
stainless.codegen.CompilationUnit→stainless.Context
- Direction
- codegen uses stainless, so a change to stainless can break codegen, while a change to codegen can't break stainless.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
38→37 codegen uses verification✕
- Connections
- 1 pair of types, where a type in codegen uses a type in verification.
- The types involved
stainless.codegen.CompilationUnit→stainless.verification.Constructor
- Direction
- codegen uses verification, so a change to verification can break codegen, while a change to codegen can't break verification.
- Position
- Below the diagonal: codegen uses a module listed above it, which is the healthy direction.
39→5 equivchk uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in equivchk uses a type in genc.ir.IR.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.genc.ir.IR.FunDefstainless.equivchk.EquivalenceChecker→stainless.genc.ir.IR.ValDefstainless.equivchk.Utils→stainless.genc.ir.IR.FunDef
- Direction
- equivchk uses genc.ir.IR, so a change to genc.ir.IR can break equivchk, while a change to equivchk can't break genc.ir.IR.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→6 equivchk uses genc.CAST✕
- Connections
- 1 pair of types, where a type in equivchk uses a type in genc.CAST.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.genc.CAST.Expr
- Direction
- equivchk uses genc.CAST, so a change to genc.CAST can break equivchk, while a change to equivchk can't break genc.CAST.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→17 equivchk uses extraction✕
- Connections
- 3 pairs of types, where a type in equivchk uses a type in extraction.
- The types involved
stainless.equivchk.EquivalenceCheckingAnalysis→stainless.extraction.ExtractionSummarystainless.equivchk.EquivalenceCheckingRun→stainless.extraction.ExtractionPipelinestainless.equivchk.EquivalenceCheckingRun→stainless.extraction.ExtractionSummary
- Direction
- equivchk uses extraction, so a change to extraction can break equivchk, while a change to equivchk can't break extraction.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→20 equivchk uses extraction.imperative.trees✕
- Connections
- 3 pairs of types, where a type in equivchk uses a type in extraction.imperative.trees.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.extraction.imperative.trees.Symbolsstainless.equivchk.EquivalenceCheckingRun→stainless.extraction.imperative.trees.Symbolsstainless.equivchk.Utils→stainless.extraction.imperative.trees.Symbols
- Direction
- equivchk uses extraction.imperative.trees, so a change to extraction.imperative.trees can break equivchk, while a change to equivchk can't break extraction.imperative.trees.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→23 equivchk uses codegen.runtime✕
- Connections
- 7 pairs of types, where a type in equivchk uses a type in codegen.runtime.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.codegen.runtime.Mapstainless.equivchk.EquivalenceChecker→stainless.codegen.runtime.Setstainless.equivchk.EquivalenceChecker→stainless.codegen.runtime.Tuplestainless.equivchk.EquivalenceCheckingAnalysis→stainless.codegen.runtime.Setstainless.equivchk.EquivalenceCheckingRun→stainless.codegen.runtime.Mapstainless.equivchk.EquivalenceCheckingRun→stainless.codegen.runtime.Setstainless.equivchk.Utils→stainless.codegen.runtime.Map
- Direction
- equivchk uses codegen.runtime, so a change to codegen.runtime can break equivchk, while a change to equivchk can't break codegen.runtime.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→27 equivchk uses ast✕
- Connections
- 2 pairs of types, where a type in equivchk uses a type in ast.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.ast.Treesstainless.equivchk.Utils→stainless.ast.Trees
- Direction
- equivchk uses ast, so a change to ast can break equivchk, while a change to equivchk can't break ast.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→29 equivchk uses utils✕
- Connections
- 1 pair of types, where a type in equivchk uses a type in utils.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.utils.CtexRemapping
- Direction
- equivchk uses utils, so a change to utils can break equivchk, while a change to equivchk can't break utils.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→31 equivchk uses stainless✕
- Connections
- 8 pairs of types, where a type in equivchk uses a type in stainless.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.Contextstainless.equivchk.EquivalenceCheckingAnalysis→stainless.AbstractAnalysisstainless.equivchk.EquivalenceCheckingComponent→stainless.Componentstainless.equivchk.EquivalenceCheckingComponent→stainless.Contextstainless.equivchk.EquivalenceCheckingRun→stainless.ComponentRunstainless.equivchk.EquivalenceCheckingRun→stainless.Contextstainless.equivchk.Utils→stainless.Contextstainless.equivchk.optEquivalenceOutput→stainless.FileOptionDef
- Direction
- equivchk uses stainless, so a change to stainless can break equivchk, while a change to equivchk can't break stainless.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
39→37 equivchk uses verification✕
- Connections
- 4 pairs of types, where a type in equivchk uses a type in verification.
- The types involved
stainless.equivchk.EquivalenceChecker→stainless.verification.VCstainless.equivchk.EquivalenceChecker→stainless.verification.VerificationAnalysisstainless.equivchk.EquivalenceCheckingRun→stainless.verification.VerificationAnalysisstainless.equivchk.EquivalenceCheckingRun→stainless.verification.VerificationRun
- Direction
- equivchk uses verification, so a change to verification can break equivchk, while a change to equivchk can't break verification.
- Position
- Below the diagonal: equivchk uses a module listed above it, which is the healthy direction.
40→1 frontends.dotc uses algebra.ops✕
- Connections
- 6 pairs of types, where a type in frontends.dotc uses a type in algebra.ops.
- The types involved
stainless.frontends.dotc.CodeExtraction→stainless.algebra.ops.Liststainless.frontends.dotc.DottyCompiler→stainless.algebra.ops.Liststainless.frontends.dotc.DottyDriver→stainless.algebra.ops.Liststainless.frontends.dotc.FragmentChecker→stainless.algebra.ops.Liststainless.frontends.dotc.StainlessExtraction→stainless.algebra.ops.Liststainless.frontends.dotc.Utils→stainless.algebra.ops.List
- Direction
- frontends.dotc uses algebra.ops, so a change to algebra.ops can break frontends.dotc, while a change to frontends.dotc can't break algebra.ops.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→5 frontends.dotc uses genc.ir.IR✕
- Connections
- 3 pairs of types, where a type in frontends.dotc uses a type in genc.ir.IR.
- The types involved
stainless.frontends.dotc.CodeExtraction→stainless.genc.ir.IR.FunDefstainless.frontends.dotc.CodeExtraction→stainless.genc.ir.IR.ValDefstainless.frontends.dotc.ExtractedUnit→stainless.genc.ir.IR.FunDef
- Direction
- frontends.dotc uses genc.ir.IR, so a change to genc.ir.IR can break frontends.dotc, while a change to frontends.dotc can't break genc.ir.IR.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→6 frontends.dotc uses genc.CAST✕
- Connections
- 8 pairs of types, where a type in frontends.dotc uses a type in genc.CAST.
- The types involved
stainless.frontends.dotc.ASTExtractors→stainless.genc.CAST.Treestainless.frontends.dotc.ASTExtractors→stainless.genc.CAST.Typestainless.frontends.dotc.CodeExtraction→stainless.genc.CAST.Exprstainless.frontends.dotc.CodeExtraction→stainless.genc.CAST.Treestainless.frontends.dotc.CodeExtraction→stainless.genc.CAST.Typestainless.frontends.dotc.FragmentChecker→stainless.genc.CAST.Treestainless.frontends.dotc.StainlessExtraction→stainless.genc.CAST.Treestainless.frontends.dotc.SymbolMapping→stainless.genc.CAST.Tree
- Direction
- frontends.dotc uses genc.CAST, so a change to genc.CAST can break frontends.dotc, while a change to frontends.dotc can't break genc.CAST.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→21 frontends.dotc uses extraction.oo.Definitions✕
- Connections
- 3 pairs of types, where a type in frontends.dotc uses a type in extraction.oo.Definitions.
- The types involved
stainless.frontends.dotc.CodeExtraction→stainless.extraction.oo.Definitions.TypeDefstainless.frontends.dotc.ExtractedUnit→stainless.extraction.oo.Definitions.ClassDefstainless.frontends.dotc.ExtractedUnit→stainless.extraction.oo.Definitions.TypeDef
- Direction
- frontends.dotc uses extraction.oo.Definitions, so a change to extraction.oo.Definitions can break frontends.dotc, while a change to frontends.dotc can't break extraction.oo.Definitions.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→23 frontends.dotc uses codegen.runtime✕
- Connections
- 3 pairs of types, where a type in frontends.dotc uses a type in codegen.runtime.
- The types involved
stainless.frontends.dotc.ASTExtractors→stainless.codegen.runtime.Mapstainless.frontends.dotc.ASTExtractors→stainless.codegen.runtime.Setstainless.frontends.dotc.FragmentChecker→stainless.codegen.runtime.Set
- Direction
- frontends.dotc uses codegen.runtime, so a change to codegen.runtime can break frontends.dotc, while a change to frontends.dotc can't break codegen.runtime.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→24 frontends.dotc uses ast.Expressions✕
- Connections
- 1 pair of types, where a type in frontends.dotc uses a type in ast.Expressions.
- The types involved
stainless.frontends.dotc.CodeExtraction→stainless.ast.Expressions.MatchCase
- Direction
- frontends.dotc uses ast.Expressions, so a change to ast.Expressions can break frontends.dotc, while a change to frontends.dotc can't break ast.Expressions.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→27 frontends.dotc uses ast✕
- Connections
- 6 pairs of types, where a type in frontends.dotc uses a type in ast.
- The types involved
stainless.frontends.dotc.ASTExtractors→stainless.ast.Symbolstainless.frontends.dotc.CodeExtraction→stainless.ast.Symbolstainless.frontends.dotc.CodeExtraction→stainless.ast.SymbolIdentifierstainless.frontends.dotc.FragmentChecker→stainless.ast.Symbolstainless.frontends.dotc.SymbolMapping→stainless.ast.Symbolstainless.frontends.dotc.SymbolMapping→stainless.ast.SymbolIdentifier
- Direction
- frontends.dotc uses ast, so a change to ast can break frontends.dotc, while a change to frontends.dotc can't break ast.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→31 frontends.dotc uses stainless✕
- Connections
- 3 pairs of types, where a type in frontends.dotc uses a type in stainless.
- The types involved
stainless.frontends.dotc.StainlessExtraction→stainless.Contextstainless.frontends.dotc.SymbolMapping→stainless.Contextstainless.frontends.dotc.Utils→stainless.Context
- Direction
- frontends.dotc uses stainless, so a change to stainless can break frontends.dotc, while a change to frontends.dotc can't break stainless.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
40→38 frontends.dotc uses codegen✕
- Connections
- 1 pair of types, where a type in frontends.dotc uses a type in codegen.
- The types involved
stainless.frontends.dotc.Utils→stainless.codegen.CompilationUnit
- Direction
- frontends.dotc uses codegen, so a change to codegen can break frontends.dotc, while a change to frontends.dotc can't break codegen.
- Position
- Below the diagonal: frontends.dotc uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 19 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.2 pts | Low | ADR Quality |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.7 pts | Medium | Visual & motion safety |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +2.3 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.1 pts | Medium | Page structure |
| 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. | +1.7 pts | Medium | Architecture documentation |
| 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.3 pts | Medium | Nullable reference types |
| Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with EquivalenceChecker.scala, EffectElaboration.scala, package.scala. | +0.6 pts | Low | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +1.0 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala | 5.5 | Mixed | Cyclomatic Complexity: Checker.traverse (cyclomatic 44) |
| core/src/main/scala/stainless/ast/Deconstructors.scala | 5.9 | Mixed | Code Duplication: Members sharing a duplicated core (12 members, 50+ identical tokens) |
| core/src/main/scala/stainless/extraction/imperative/AntiAliasing.scala | 6.0 | Mixed | Explicit Debt: XxxComment |
| core/src/main/scala/stainless/codegen/CodeGeneration.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/stainless/verification/TypeChecker.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| core/src/main/scala/stainless/transformers/lattices/Core.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| frontends/library/stainless/math/FdLibm.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/stainless/genc/phases/IR2CPhase.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/stainless/extraction/oo/TypeOps.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| core/src/main/scala/stainless/genc/CPrinter.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 65 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 — 65 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, 703 of 720 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: 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, 38 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. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/io/circe/circe-core_3/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- 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: 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — 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. `core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala`, `core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala`, `core/src/main/scala/stainless/extraction/innerfuns/FunctionClosure.scala`, `core/src/main/scala/stainless/extraction/methods/Trees.scala`, `core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala`, … (+77 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.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- 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 core/src/main/scala/stainless/extraction/oo/DependencyGraph.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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 12 | RUN unzip stainless-dotty-standalone-$STAINLESS_VERSION-linux.zip && rm -f stainless-dotty-standalone-$STAINLESS_VERSION-linux.zip -------------------- ERROR: failed to solve: process "/bin/sh -c wget --quiet https://github.com/epfl-lara/stainless/releases/download/v$STAINLESS_VERSION/stainless-dotty-standalone-$STAINLESS_VERSION-linux.zip" did not complete successfully: exit code: 8; runtime evidence skipped.
- 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 no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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
101 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AntiAliasing.extractFunction at 229. A further 24 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 uncoder.combineCtorAlike at 55 — they are counted neither in the figure above nor in this dimension's score. 10 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: core/src/main/scala/stainless/genc/CASTDependencies.scala (CASTTraverser.deconstruct at 45), core/src/main/scala/stainless/genc/ir/IRPrinter.scala (IRPrinter.rec at 34), core/src/main/scala/stainless/genc/ir/Transformer.scala (Transformer.recImpl at 33), core/src/main/scala/stainless/genc/ir/Visitor.scala (Visitor.rec at 32), core/src/main/scala/stainless/ast/Deconstructors.scala (TreeDeconstructor.deconstruct at 25), and 5 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 5 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with AntiAliasing.extractFunction (cyclomatic 229), CodeGeneration.mkExpr (cyclomatic 183), TypeChecker.inferType (cyclomatic 180). — 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 5 together lifts Cyclomatic Complexity from 5.1 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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
122 method(s) exceeded the cognitive complexity threshold of 15; the worst was Pow.compute at 339.
What to do
- Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with Pow.compute (cognitive 339). — Refactoring it lifts Cognitive Complexity from 4.0 to about 4.4/10.
- 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
30 god class(es) detected.
What to do
- Resolve the 15 FileTooLong finding(s) in God Classes — start with List.scala (2), Core.scala, CodeExtraction.scala. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 11 TooManyMethods finding(s) in God Classes — start with List.scala (2), Core.scala, Definitions.scala. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with CodeExtraction.scala, Scala2IRPhase.scala, FragmentChecker.scala. — One of this dimension's main actionable groups (3 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
80 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 17 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with FdLibm.scala (5), TypeChecker.scala (3), TypeEncoding.scala (2). — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 12 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with EquivalenceChecker.scala (2), FdLibm.scala (2), ReturnElimination.scala. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with CodeGeneration.scala (3), ExprOps.scala, EquivalenceChecker.scala. — One of this dimension's main actionable groups (9 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
8 production modules (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 4 of the 8 (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 116 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with Canonization.scala, ExprOps.scala, CodeGenEvaluator.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
82 test methods: 57 unit, 25 integration, 0 BDD, 0 e2e. The Scala suite contributes 82 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: frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala (6×178=1068); core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala (10×97=970); core/src/main/scala/stainless/genc/phases/IR2CPhase.scala (9×80=720)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with CodeExtraction.scala, Scala2IRPhase.scala, IR2CPhase.scala. — One of this dimension's main actionable groups (5 warning-level).
D16 · Bus Factor
34 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is frontends/library/stainless/math/FdLibm.scala. Counted over 277 of the 1846 production source files in this repository: 1559 are under the ~2,400-byte size floor this dimension measures over, and the remaining 10 have no attributable history left to measure.
What to do
- Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
141 deducted task-comment markers across 98107 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 87 TodoComment finding(s) in Explicit Debt — start with Core.scala (8), CellArrayMergeSort.scala (7), EffectElaboration.scala (7). — One of this dimension's main actionable groups (87 warning-level).
- Resolve the 53 FixmeComment finding(s) in Explicit Debt — start with Streams.scala (6), FullImperativeSuite.scala (4), BottomUpMergeSort.scala (4). — One of this dimension's main actionable groups (53 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with AntiAliasing.scala. — One of this dimension's main actionable groups (1 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 (sbt) 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)
19 finding(s): 0 critical, 19 high, 0 medium, 0 low. 13 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 45 file(s) — `core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala`, `core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala`, `core/src/main/scala/stainless/extraction/innerfuns/FunctionClosure.scala`, `core/src/main/scala/stainless/extraction/methods/Trees.scala`, `core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala`, … (+40 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 13 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
4 finding(s): 0 critical, 3 high, 1 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
133 of 287 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala. Counted over 287 of the 1846 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 127 Orphaned file finding(s) in Knowledge Freshness — start with Definitions.scala (2), RedBlackTree.scala (2), ListOperations.scala (2). — One of this dimension's main actionable groups (127 recommendation-level).
- Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with EquivalenceChecker.scala, EffectElaboration.scala, package.scala. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: Deconstructors.scala↔InoxEncoder.scala 63%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Deconstructors.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled. — core/src/sphinx/themes/sphinx_rtd_theme/layout.html:17
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.rst-versions .rst-current-version.rst-out-of-date` sets color: #fff on background-color: #e74c3c — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — core/src/sphinx/themes/sphinx_rtd_theme/static/css/badge_only.css:1
- `.rst-content .admonition-title,.wy-alert-title` sets color: #fff on background-color: #6ab0de — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.btn` sets color: #fff on background-color: #27ae60 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.btn:hover` sets color: #fff on background-color: #2cc36b — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.wy-dropdown-menu>dd>a:hover` sets color: #fff on background-color: #2980b9 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.wy-dropdown.wy-dropdown-bubble .wy-dropdown-menu a:hover` sets color: #fff on background-color: #2980b9 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.rst-content code,.rst-content tt,code` sets color: #e74c3c on background-color: #fff — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.wy-menu-vertical a:active` sets color: #fff on background-color: #2980b9 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.wy-side-nav-search` sets color: #fcfcfc on background-color: #2980b9 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.wy-nav .wy-menu-vertical a:hover` sets color: #fff on background-color: #2980b9 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.wy-nav-top` sets color: #fff on background-color: #2980b9 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.rst-versions .rst-current-version.rst-out-of-date` sets color: #fff on background-color: #e74c3c — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `html.writer-html4 .rst-content dl:not(.docutils)>dt,html.writer-html5 .rst-content dl[class]:not(.option-list):not(.field-list):not(.footnote):not(.citation):not(.glossary):not(.simple)>dt` sets color: #2980b9 on background-color: #e7f2fa — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `select:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.fa-spin` moves (`animation: fa-spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- `.fa-pulse` moves (`animation: fa-spin 1s steps(8) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 6 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `initEnv` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:277
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `initEnv` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:277
- `StaticChecks` has 4 unfinished members out of 4 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — frontends/library/stainless/lang/StaticChecks.scala:5
- `require` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — frontends/library/stainless/lang/StaticChecks.scala:31, frontends/library/stainless/lang/StaticChecks.scala:34
- `assert` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — frontends/library/stainless/lang/StaticChecks.scala:37, frontends/library/stainless/lang/StaticChecks.scala:40
- `inline` has an empty body — confirm it's an intentional no-op and not an unfinished method. — frontends/library/stainless/lang/StaticChecks.scala:26
- `opaque` has an empty body — confirm it's an intentional no-op and not an unfinished method. — frontends/library/stainless/lang/StaticChecks.scala:27
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- 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)
What to do
- 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
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 13706 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- 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.
PF3 · Async & latency hygiene
X1 · Async correctness
- The `Future` this starts is not kept anywhere, and `scala.concurrent.Future` never reports a failure on its own: `Future { … }` catches any non-fatal exception its body throws and stores it as the future's `Failure` — not rethrown, not printed, not passed to the `ExecutionContext`'s `reportFailure` — so once nobody holds the future the error is gone, and nothing can wait for the work to finish either. Keep the future and compose it into what the caller returns (`for`/`flatMap`, `Future.sequence`), or, for genuine fire-and-forget, attach a handler that reports the failure — `Future { … }.failed.foreach(error => log.error("…", error))` or `.onComplete { case Failure(e) => report(e); case _ => }` — or catch and report inside the body itself. — core/src/main/scala/stainless/utils/FileWatcher.scala:37
What to do
- Future started here is not kept
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
- `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.collect` 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(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — sbt-plugin/src/main/scala/ch/epfl/lara/sbt/stainless/StainlessPlugin.scala:174, core/src/main/scala/stainless/frontend/DependencyResolver.scala:156
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
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. (×4) — frontends/library/stainless/io/FileOutputStream.scala:119, frontends/library/stainless/io/FileOutputStream.scala:145, frontends/library/stainless/io/FileOutputStream.scala:171, …
- `case NonFatal(_)` 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. (×3) — core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:751, core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:773, core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:841
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 370 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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 50% | Adequate — gated by D2, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 51% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 47% | Adequate — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 18 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 — 53 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — not 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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.
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 12 | RUN unzip stainless-dotty-standalone-$STAINLESS_VERSION-linux.zip && rm -f stainless-dotty-standalone-$STAINLESS_VERSION-linux.zip -------------------- ERROR: failed to solve: process "/bin/sh -c wget --quiet https://github.com/epfl-lara/stainless/releases/download/v$STAINLESS_VERSION/stainless-dotty-standalone-$STAINLESS_VERSION-linux.zip" did not complete successfully: exit code: 8; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~5788 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 — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 5 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 5 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/typesafe/config/1.3.4/config-1.3.4.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 — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python, Scala, html 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 — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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.
- D32 Data Compliance (PII/GDPR) — 82 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1754 value object(s); 19 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 4 current-state document(s) make no claim of a kind M4 checks. 6 claim(s) of kinds M4 does not check were not checked (path 5, command argument 1); M4 checks only links and versions and artefact counts.
- 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 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 pom.xml, 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 71,996 production line(s), 6 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- S1 Web-Security Posture — No web surface: 347 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.
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:1
- Orphaned knowledge core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:1
- Orphaned knowledge frontends/library/stainless/math/package.scala:1
- Orphaned knowledge core/src/main/scala/stainless/extraction/innerclasses/InnerClasses.scala:1
- Orphaned knowledge core/src/main/scala/stainless/extraction/imperative/ReturnElimination.scala:1
- Orphaned knowledge core/src/main/scala/stainless/equivchk/EquivalenceCheckingComponent.scala:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 529 finding(s)
- TodoComment frontends/library/stainless/math/FdLibm.scala:377
- TodoComment frontends/library/stainless/math/FdLibm.scala:976
- TodoComment frontends/library/stainless/math/FdLibm.scala:977
- TodoComment frontends/library/stainless/lang/package.scala:11
- TodoComment frontends/library/stainless/lang/package.scala:130
- TodoComment frontends/library/stainless/io/FileInputStream.scala:212
- TodoComment frontends/library/stainless/io/StdIn.scala:79
- TodoComment frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1943
- TodoComment frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1957
- TodoComment frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1973
- TodoComment frontends/dotty/src/main/scala/stainless/frontends/dotc/DottyCompiler.scala:211
- TodoComment frontends/dotty/src/main/scala/stainless/frontends/dotc/StainlessExtraction.scala:154
- TodoComment frontends/dotty/src/it/scala/stainless/verification/CheckFilesUtils.scala:192
- TodoComment frontends/dotty/src/it/scala/stainless/verification/FullImperativeSuite.scala:40
- TodoComment frontends/benchmarks/verification/valid/PartialCompiler.scala:50
- TodoComment frontends/benchmarks/verification/invalid/i1295.scala:5
- TodoComment frontends/benchmarks/termination/valid/ConstantPropagation.scala:190
- TodoComment frontends/benchmarks/full-imperative/valid/AllocatorMono.scala:93
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:71
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:158
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:239
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:240
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:242
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:409
- TodoComment frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:413
- FixmeComment sbt-plugin/src/main/scala/ch/epfl/lara/sbt/stainless/StainlessPlugin.scala:254
- FixmeComment frontends/library/stainless/io/FileOutputStream.scala:37
- FixmeComment frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:888
- FixmeComment frontends/dotty/src/it/scala/stainless/verification/FullImperativeSuite.scala:22
- FixmeComment frontends/dotty/src/it/scala/stainless/verification/FullImperativeSuite.scala:24
- FixmeComment frontends/dotty/src/it/scala/stainless/verification/FullImperativeSuite.scala:27
- FixmeComment frontends/dotty/src/it/scala/stainless/verification/FullImperativeSuite.scala:29
- FixmeComment frontends/benchmarks/verification/valid/MicroTests/BVDivSemantics.scala:18
- FixmeComment frontends/benchmarks/termination/valid/BottomUpMergeSort.scala:44
- FixmeComment frontends/benchmarks/termination/valid/BottomUpMergeSort.scala:65
- FixmeComment frontends/benchmarks/termination/valid/BottomUpMergeSort.scala:81
- FixmeComment frontends/benchmarks/termination/valid/BottomUpMergeSort.scala:109
- FixmeComment frontends/benchmarks/termination/valid/ConstantPropagation.scala:127
- FixmeComment frontends/benchmarks/termination/valid/NNFSimple.scala:48
- FixmeComment frontends/benchmarks/termination/valid/Numeric1.scala:10
- FixmeComment frontends/benchmarks/termination/valid/Numeric1.scala:15
- FixmeComment frontends/benchmarks/termination/valid/RealTimeQueue.scala:28
- FixmeComment frontends/benchmarks/termination/false-invalid/Streams.scala:9
- FixmeComment frontends/benchmarks/termination/false-invalid/Streams.scala:17
- FixmeComment frontends/benchmarks/termination/false-invalid/Streams.scala:26
- FixmeComment frontends/benchmarks/termination/false-invalid/Streams.scala:35
- FixmeComment frontends/benchmarks/termination/false-invalid/Streams.scala:43
- FixmeComment frontends/benchmarks/termination/false-invalid/Streams.scala:51
- FixmeComment frontends/benchmarks/termination/valid/XPlus2N.scala:13
- FixmeComment frontends/benchmarks/full-imperative/valid/AllocatorMono.scala:48
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/extraction/innerclasses/ExprOps.scala:58
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:1077
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/extraction/oo/TypeOps.scala:162
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/solvers/InoxEncoder.scala:115
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/verification/TypeChecker.scala:837
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/verification/TypeChecker.scala:965
- Duplicated block (5 lines × 2) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1902
- Duplicated block (5 lines × 2) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:2401
- Duplicated block (5 lines × 2) frontends/library/stainless/math/FdLibm.scala:1188
- Duplicated block (5 lines × 2) frontends/library/stainless/math/FdLibm.scala:1327
- Duplicated block (5 lines × 2) frontends/library/stainless/collection/List.scala:602
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:829
- Duplicated block (5 lines × 2) core/src/main/scala/stainless/verification/TypeChecker.scala:1009
- Duplicated block (5 lines × 2) frontends/library/stainless/covcollection/List.scala:471
- Duplicated block (5 lines × 2) frontends/library/stainless/math/FdLibm.scala:151
- Duplicated block (5 lines × 2) frontends/library/stainless/math/FdLibm.scala:245
- Duplicated block (5 lines × 2) frontends/library/stainless/math/FdLibm.scala:2126
- FileTooLong: lattices/Core.scala core/src/main/scala/stainless/transformers/lattices/Core.scala
- FileTooLong: dotc/CodeExtraction.scala frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala
- FileTooLong: math/FdLibm.scala frontends/library/stainless/math/FdLibm.scala
- FileTooLong: verification/TypeChecker.scala core/src/main/scala/stainless/verification/TypeChecker.scala
- FileTooLong: dotc/ASTExtractors.scala frontends/dotty/src/main/scala/stainless/frontends/dotc/ASTExtractors.scala
- FileTooLong: oo/TypeEncoding.scala core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala
- FileTooLong: imperative/AntiAliasing.scala core/src/main/scala/stainless/extraction/imperative/AntiAliasing.scala
- FileTooLong: equivchk/EquivalenceChecker.scala core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala
- FileTooLong: phases/Scala2IRPhase.scala core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala
- FileTooLong: collection/ListMap.scala frontends/library/stainless/collection/ListMap.scala
- FileTooLong: imperative/EffectsAnalyzer.scala core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala
- FileTooLong: collection/List.scala frontends/library/stainless/collection/List.scala
- FileTooLong: covcollection/List.scala frontends/library/stainless/covcollection/List.scala
- FileTooLong: verification/CoqEncoder.scala core/src/main/scala/stainless/verification/CoqEncoder.scala
- FileTooLong: imperative/EffectElaboration.scala core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:399
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:399
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/extraction/imperative/ReturnElimination.scala:350
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/extraction/inlining/FunctionInlining.scala:59
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/extraction/oo/TransformerWithType.scala:410
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/termination/SizeFunctions.scala:102
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/termination/TerminationChecker.scala:40
- Duplicated block (7 lines × 2) frontends/library/stainless/collection/List.scala:613
- Duplicated block (7 lines × 2) frontends/library/stainless/collection/ListMapLemmas.scala:348
- Duplicated block (7 lines × 2) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:240
- Duplicated block (7 lines × 2) frontends/library/stainless/math/FdLibm.scala:1392
- Duplicated block (7 lines × 2) frontends/library/stainless/math/FdLibm.scala:1866
- TooManyMethods: Core core/src/main/scala/stainless/transformers/lattices/Core.scala:8
- TooManyMethods: Definitions core/src/main/scala/stainless/transformers/lattices/Definitions.scala:7
- TooManyMethods: List frontends/library/stainless/covcollection/List.scala:12
- TooManyMethods: List frontends/library/stainless/collection/List.scala:12
- TooManyMethods: math frontends/library/stainless/math/package.scala:139
- TooManyMethods: CodeExtraction frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:31
- TooManyMethods: S2IRImpl core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:54
- TooManyMethods: TupleListOpsGenK frontends/library/stainless/collection/ListMap.scala:147
- TooManyMethods: ASTExtractors frontends/dotty/src/main/scala/stainless/frontends/dotc/ASTExtractors.scala:23
- TooManyMethods: ListMapLemmas frontends/library/stainless/collection/ListMapLemmas.scala:11
- TooManyMethods: CoqEncoder core/src/main/scala/stainless/verification/CoqEncoder.scala:9
- Duplicated block (6 lines × 2) core/src/main/scala/stainless/ast/ExprOps.scala:398
- Duplicated block (6 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1661
- Duplicated block (6 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1686
- Duplicated block (6 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:2292
- Duplicated block (6 lines × 2) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:393
- Duplicated block (6 lines × 2) core/src/main/scala/stainless/verification/TypeChecker.scala:1077
- Duplicated block (6 lines × 2) frontends/library/stainless/collection/ListMap.scala:306
- Duplicated block (6 lines × 2) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1940
- Duplicated block (6 lines × 2) frontends/library/stainless/math/FdLibm.scala:1573
- Duplicated block (8 lines × 2) core/src/main/scala/stainless/ast/ExprOps.scala:443
- Duplicated block (8 lines × 2) core/src/main/scala/stainless/extraction/innerclasses/DependencyGraph.scala:64
- Duplicated block (8 lines × 2) core/src/main/scala/stainless/extraction/innerclasses/TypeOps.scala:46
- Duplicated block (8 lines × 2) core/src/main/scala/stainless/transformers/lattices/Core.scala:3451
- Duplicated block (8 lines × 2) frontends/library/stainless/math/FdLibm.scala:1773
- Duplicated block (8 lines × 2) core/src/main/scala/stainless/frontend/BatchedCallBack.scala:137
- Duplicated block (8 lines × 2) frontends/library/stainless/math/FdLibm.scala:1652
- Swallowed exception (caught, then discarded) frontends/library/stainless/io/FileOutputStream.scala:119
- Swallowed exception (caught, then discarded) frontends/library/stainless/io/FileOutputStream.scala:145
- Swallowed exception (caught, then discarded) frontends/library/stainless/io/FileOutputStream.scala:171
- Swallowed exception (caught, then discarded) frontends/library/stainless/io/FileOutputStream.scala:197
- Swallowed exception (caught, then discarded) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:751
- Swallowed exception (caught, then discarded) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:773
- Swallowed exception (caught, then discarded) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:841
- Duplicated block (9 lines × 2) core/src/main/scala/stainless/evaluators/RecursiveEvaluator.scala:120
- Duplicated block (9 lines × 2) core/src/main/scala/stainless/extraction/imperative/GhostChecker.scala:128
- Duplicated block (9 lines × 2) frontends/dotty/src/main/scala/stainless/frontends/dotc/ASTExtractors.scala:1776
- Duplicated block (9 lines × 2) frontends/library/stainless/math/FdLibm.scala:1271
- Duplicated block (9 lines × 2) frontends/library/stainless/math/FdLibm.scala:1503
- Duplicated block (9 lines × 2) frontends/library/stainless/math/FdLibm.scala:1725
- Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (4.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Hotspot: frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1416
- Hotspot: core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:1030
- Hotspot: core/src/main/scala/stainless/genc/phases/IR2CPhase.scala core/src/main/scala/stainless/genc/phases/IR2CPhase.scala:210
- Hotspot: core/src/main/scala/stainless/genc/CPrinter.scala core/src/main/scala/stainless/genc/CPrinter.scala:46
- Hotspot: core/src/main/scala/stainless/verification/AssertionInjector.scala core/src/main/scala/stainless/verification/AssertionInjector.scala:53
- Duplicated block (13 lines × 2) core/src/main/scala/stainless/extraction/imperative/ReturnElimination.scala:359
- Duplicated block (13 lines × 2) core/src/main/scala/stainless/extraction/imperative/SymbolOps.scala:24
- Duplicated block (13 lines × 2) core/src/main/scala/stainless/extraction/inlining/FunctionInlining.scala:42
- Duplicated block (13 lines × 2) core/src/main/scala/stainless/genc/ir/Referentiator.scala:74
- Duplicated block (13 lines × 2) core/src/main/scala/stainless/genc/phases/GlobalStateChecker.scala:28
- Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/badge_only.css:1
- Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (3.8:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Duplicated block (11 lines × 2) core/src/main/scala/stainless/ast/Deconstructors.scala:77
- Duplicated block (11 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1906
- Duplicated block (11 lines × 2) core/src/main/scala/stainless/extraction/imperative/EffectsChecker.scala:386
- Duplicated block (11 lines × 2) frontends/library/stainless/collection/ListMap.scala:292
- Low cohesion: Canonization (LCOM4 8) core/src/main/scala/stainless/utils/Canonization.scala:8
- Low cohesion: ExprOps (LCOM4 7) core/src/main/scala/stainless/ast/ExprOps.scala:13
- Low cohesion: Monitor (LCOM4 5) core/src/main/scala/stainless/evaluators/CodeGenEvaluator.scala:37
- Low cohesion: FragmentChecker (LCOM4 5) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:37
- Empty method body — does nothing with its inputs frontends/library/stainless/lang/StaticChecks.scala:31
- Empty method body — does nothing with its inputs frontends/library/stainless/lang/StaticChecks.scala:34
- Empty method body — does nothing with its inputs frontends/library/stainless/lang/StaticChecks.scala:37
- Empty method body — does nothing with its inputs frontends/library/stainless/lang/StaticChecks.scala:40
- ClassTooLong: CodeExtraction frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:31
- ClassTooLong: S2IRImpl core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:54
- ClassTooLong: FragmentChecker frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:37
- Duplicated block (10 lines × 2) core/src/main/scala/stainless/extraction/imperative/GhostChecker.scala:242
- Duplicated block (10 lines × 2) core/src/main/scala/stainless/extraction/innerclasses/Definitions.scala:30
- Duplicated block (10 lines × 2) core/src/main/scala/stainless/extraction/package.scala:210
- Animation without a prefers-reduced-motion guard core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Animation without a prefers-reduced-motion guard core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- REDACTED
- REDACTED
- Disposable created and abandoned in the function that made it sbt-plugin/src/main/scala/ch/epfl/lara/sbt/stainless/StainlessPlugin.scala:174
- Disposable created and abandoned in the function that made it core/src/main/scala/stainless/frontend/DependencyResolver.scala:156
- Multiple navigation landmarks without distinguishing labels core/src/sphinx/themes/sphinx_rtd_theme/layout.html:17
- Low contrast colour pair in CSS (2.4:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (2.9:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (2.3:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Low contrast colour pair in CSS (4.2:1) core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Focus outline removed in CSS without a :focus replacement core/src/sphinx/themes/sphinx_rtd_theme/static/css/theme.css:4
- Accessibility enforcement below the top rung
- AntiAliasing.extractFunction (cyclomatic 229) core/src/main/scala/stainless/extraction/imperative/AntiAliasing.scala:99
- CodeGeneration.mkExpr (cyclomatic 183) core/src/main/scala/stainless/codegen/CodeGeneration.scala:623
- TypeChecker.inferType (cyclomatic 180) core/src/main/scala/stainless/verification/TypeChecker.scala:453
- CodeExtraction.extractTree (cyclomatic 178) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1416
- CodeExtraction.extractCall (cyclomatic 144) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:2059
- TransformerWithType.transform (cyclomatic 119) core/src/main/scala/stainless/extraction/oo/TransformerWithType.scala:69
- EffectsChecker.checkEffects (cyclomatic 115) core/src/main/scala/stainless/extraction/imperative/EffectsChecker.scala:18
- Core.simplifyTopLvl (cyclomatic 107) core/src/main/scala/stainless/transformers/lattices/Core.scala:1237
- S2IRImpl.rec (cyclomatic 97) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:1030
- Pow.compute (cyclomatic 97) frontends/library/stainless/math/FdLibm.scala:1877
- CodeExtraction.extractType (cyclomatic 86) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:2635
- GhostChecker.checkGhost (cyclomatic 85) core/src/main/scala/stainless/extraction/imperative/GhostChecker.scala:10
- IR2CImpl.rec (cyclomatic 80) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala:210
- Core.codeOfExpr (cyclomatic 78) core/src/main/scala/stainless/transformers/lattices/Core.scala:713
- TypeOps.typeBound (cyclomatic 72) core/src/main/scala/stainless/extraction/oo/TypeOps.scala:12
- EffectsAnalyzer.getTargets (cyclomatic 71) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:517
- CPrinter.pp (cyclomatic 71) core/src/main/scala/stainless/genc/CPrinter.scala:46
- CompilationUnit.valueToJVM (cyclomatic 67) core/src/main/scala/stainless/codegen/CompilationUnit.scala:130
- Atan2.compute (cyclomatic 56) frontends/library/stainless/math/FdLibm.scala:1206
- TypeEncoding.instanceOf (cyclomatic 55) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:321
- CoqEncoder.transformTree (cyclomatic 54) core/src/main/scala/stainless/verification/CoqEncoder.scala:74
- Log1p.compute (cyclomatic 47) frontends/library/stainless/math/FdLibm.scala:1674
- Printer.ppBody (cyclomatic 46) core/src/main/scala/stainless/ast/Printers.scala:41
- ImperativeCodeElimination.extractFunction (cyclomatic 46) core/src/main/scala/stainless/extraction/imperative/ImperativeCodeElimination.scala:29
- CodeGeneration.mkBranch (cyclomatic 45) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1586
- EffectsAnalyzer.expressionEffects (cyclomatic 45) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:804
- CodeExtraction.extractClass (cyclomatic 45) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:517
- Checker.traverse (cyclomatic 44) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:566
- AssertionInjector.transform (cyclomatic 42) core/src/main/scala/stainless/verification/AssertionInjector.scala:53
- Printer.ppBody (cyclomatic 39) core/src/main/scala/stainless/extraction/oo/Trees.scala:261
- Normaliser.recImpl (cyclomatic 39) core/src/main/scala/stainless/genc/ir/Normaliser.scala:37
- Core.generateCond (cyclomatic 39) core/src/main/scala/stainless/transformers/lattices/Core.scala:1575
- Hypot.compute (cyclomatic 38) frontends/library/stainless/math/FdLibm.scala:1346
- RecursiveEvaluator.e (cyclomatic 37) core/src/main/scala/stainless/evaluators/RecursiveEvaluator.scala:15
- ReturnElimination.extractFunction (cyclomatic 37) core/src/main/scala/stainless/extraction/imperative/ReturnElimination.scala:109
- Analysis.rec (cyclomatic 37) core/src/main/scala/stainless/termination/ControlFlowAnalysis.scala:191
- Expr.getType (cyclomatic 36) core/src/main/scala/stainless/genc/ir/IR.scala:190
- FunctionInlining.extractFunction (cyclomatic 35) core/src/main/scala/stainless/extraction/inlining/FunctionInlining.scala:36
- CodeExtraction.extractPattern (cyclomatic 35) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:983
- CodeExtraction.extractBlock (cyclomatic 35) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1221
- Checker.checkType (cyclomatic 35) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:427
- CPrinter.pp (cyclomatic 34) core/src/main/scala/stainless/genc/CPrinter.scala:362
- Expm1.compute (cyclomatic 34) frontends/library/stainless/math/FdLibm.scala:1599
- MethodsAbstractSymbols.ensureWellFormedClass (cyclomatic 33) core/src/main/scala/stainless/extraction/methods/Trees.scala:104
- CodeExtraction.extractStatic (cyclomatic 31) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:213
- CompilationUnit.jvmToValue (cyclomatic 30) core/src/main/scala/stainless/codegen/CompilationUnit.scala:302
- CodePurity.tryFoldImpl (cyclomatic 30) core/src/main/scala/stainless/transformers/lattices/Core.scala:1973
- VerificationChecker.checkVC (cyclomatic 29) core/src/main/scala/stainless/verification/VerificationChecker.scala:295
- Atan.compute (cyclomatic 29) frontends/library/stainless/math/FdLibm.scala:1139
- EvaluatorRun.execute (cyclomatic 28) core/src/main/scala/stainless/evaluators/EvaluatorComponent.scala:74
- CodeTryFolder.tryFoldImpl (cyclomatic 28) core/src/main/scala/stainless/transformers/lattices/Core.scala:2876
- Exp.compute (cyclomatic 28) frontends/library/stainless/math/FdLibm.scala:1537
- math.atan2 (cyclomatic 28) frontends/library/stainless/math/package.scala:242
- RefTransformContext.transformFun (cyclomatic 27) core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:468
- EffectsAnalyzer.isExpressionFresh (cyclomatic 27) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:701
- Strengthener.strengthenApplications (cyclomatic 27) core/src/main/scala/stainless/termination/Strengthener.scala:132
- OL.latticesLeq (cyclomatic 27) core/src/main/scala/stainless/transformers/lattices/OL.scala:29
- FunctionSpecialization.extractFunction (cyclomatic 26) core/src/main/scala/stainless/extraction/inlining/FunctionSpecialization.scala:38
- FunctionClosure.extractFunction (cyclomatic 26) core/src/main/scala/stainless/extraction/innerfuns/FunctionClosure.scala:23
- AbstractReport.usageConstructExtendedSummary (cyclomatic 25) core/src/main/scala/stainless/Report.scala:236
- EquivalenceChecker.concludeRound (cyclomatic 25) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:379
- TypeChecker.isType (cyclomatic 25) core/src/main/scala/stainless/verification/TypeChecker.scala:341
- Asin.compute (cyclomatic 25) frontends/library/stainless/math/FdLibm.scala:1016
- math.pow (cyclomatic 25) frontends/library/stainless/math/package.scala:601
- GhostRewriteTransformer.transform (cyclomatic 24) frontends/dotty/src/main/scala/stainless/frontends/dotc/GhostAccessRewriter.scala:89
- KernelRemPio2.computeModulo (cyclomatic 24) frontends/library/stainless/math/FdLibm.scala:748
- ScalaPrinter.ppBody (cyclomatic 23) core/src/main/scala/stainless/ast/Printers.scala:216
- TypeOps.patternIsTyped (cyclomatic 23) core/src/main/scala/stainless/ast/TypeOps.scala:20
- CodeGeneration.mkUnbox (cyclomatic 23) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1508
- Scope.empty (cyclomatic 23) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:1028
- LeonInlining.extractFunction (cyclomatic 23) core/src/main/scala/stainless/genc/LeonInlining.scala:38
- TreeEncoder.transform (cyclomatic 23) core/src/main/scala/stainless/solvers/InoxEncoder.scala:91
- SimplifierWithPC.simplify (cyclomatic 23) core/src/main/scala/stainless/transformers/SimplifierWithPC.scala:14
- Log.compute (cyclomatic 23) frontends/library/stainless/math/FdLibm.scala:1413
- MethodLifting.makeFunction (cyclomatic 22) core/src/main/scala/stainless/extraction/methods/MethodLifting.scala:232
- Scope.transform (cyclomatic 22) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:902
- InductElimination.extractFunction (cyclomatic 22) core/src/main/scala/stainless/extraction/termination/InductElimination.scala:26
- OL.doSimplifyDisjunction (cyclomatic 22) core/src/main/scala/stainless/transformers/lattices/OL.scala:149
- AbstractReport.emitSummary (cyclomatic 21) core/src/main/scala/stainless/Report.scala:155
- RecursiveEvaluator.matchesCase (cyclomatic 21) core/src/main/scala/stainless/evaluators/RecursiveEvaluator.scala:107
- funRefTransformer.transform (cyclomatic 21) core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:295
- GhostAnnotationChecker.traverse (cyclomatic 21) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:284
- S2IRImpl.rec (cyclomatic 20) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:745
- TrimSymbols.run (cyclomatic 20) core/src/main/scala/stainless/genc/phases/TrimSymbols.scala:28
- CodeGeneration.compileLambda (cyclomatic 19) core/src/main/scala/stainless/codegen/CodeGeneration.scala:365
- Scope.transform (cyclomatic 19) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:803
- IR2CImpl.checkGlobalInit (cyclomatic 19) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala:115
- CallGraphPrinter.apply (cyclomatic 18) core/src/main/scala/stainless/frontend/CallGraphPrinter.scala:15
- GhostElimination.transform (cyclomatic 18) core/src/main/scala/stainless/genc/phases/GhostEliminationPhase.scala:96
- CodePurity.fnPurity (cyclomatic 18) core/src/main/scala/stainless/transformers/lattices/Core.scala:2079
- OL.arithLeq (cyclomatic 18) core/src/main/scala/stainless/transformers/lattices/OL.scala:106
- EquivalenceChecker.tryCreate (cyclomatic 17) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:1168
- CustomPrinter.ppBody (cyclomatic 17) core/src/main/scala/stainless/testgen/ScalaTestGen.scala:203
- Tan.__kernel_tan (cyclomatic 17) frontends/library/stainless/math/FdLibm.scala:268
- EquivalenceChecker.pickNextExamination (cyclomatic 16) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:304
- Printer.ppBody (cyclomatic 16) core/src/main/scala/stainless/extraction/innerclasses/Trees.scala:130
- Referentiator.recImpl (cyclomatic 16) core/src/main/scala/stainless/genc/ir/Referentiator.scala:125
- S2IRImpl.rec (cyclomatic 16) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:902
- CodeExtraction.extractAccessor (cyclomatic 16) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:678
- CodeExtraction.extractFunction (cyclomatic 16) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:815
- KernelRemPio2.timesPiOverTwo (cyclomatic 16) frontends/library/stainless/math/FdLibm.scala:845
- XxxComment core/src/main/scala/stainless/extraction/imperative/AntiAliasing.scala:70
- Pow.compute (cognitive 339) frontends/library/stainless/math/FdLibm.scala:1877
- AntiAliasing.extractFunction (cognitive 218) core/src/main/scala/stainless/extraction/imperative/AntiAliasing.scala:99
- TypeChecker.inferType (cognitive 167) core/src/main/scala/stainless/verification/TypeChecker.scala:453
- EffectsChecker.checkEffects (cognitive 164) core/src/main/scala/stainless/extraction/imperative/EffectsChecker.scala:18
- Log1p.compute (cognitive 156) frontends/library/stainless/math/FdLibm.scala:1674
- CodeExtraction.extractTree (cognitive 140) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1416
- Core.simplifyTopLvl (cognitive 138) core/src/main/scala/stainless/transformers/lattices/Core.scala:1237
- Hypot.compute (cognitive 137) frontends/library/stainless/math/FdLibm.scala:1346
- CodeGeneration.mkExpr (cognitive 134) core/src/main/scala/stainless/codegen/CodeGeneration.scala:623
- CompilationUnit.valueToJVM (cognitive 107) core/src/main/scala/stainless/codegen/CompilationUnit.scala:130
- Expm1.compute (cognitive 107) frontends/library/stainless/math/FdLibm.scala:1599
- CodeExtraction.extractCall (cognitive 81) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:2059
- Atan2.compute (cognitive 81) frontends/library/stainless/math/FdLibm.scala:1206
- Exp.compute (cognitive 77) frontends/library/stainless/math/FdLibm.scala:1537
- Log.compute (cognitive 70) frontends/library/stainless/math/FdLibm.scala:1413
- GhostChecker.checkGhost (cognitive 66) core/src/main/scala/stainless/extraction/imperative/GhostChecker.scala:10
- AbstractReport.emitSummary (cognitive 59) core/src/main/scala/stainless/Report.scala:155
- Strengthener.strengthenApplications (cognitive 57) core/src/main/scala/stainless/termination/Strengthener.scala:132
- Checker.traverse (cognitive 57) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:566
- Atan.compute (cognitive 55) frontends/library/stainless/math/FdLibm.scala:1139
- EffectsAnalyzer.getTargets (cognitive 52) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:517
- Asin.compute (cognitive 52) frontends/library/stainless/math/FdLibm.scala:1016
- EquivalenceChecker.concludeRound (cognitive 51) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:379
- TypeOps.typeBound (cognitive 50) core/src/main/scala/stainless/extraction/oo/TypeOps.scala:12
- IR2CImpl.rec (cognitive 50) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala:210
- CodePurity.tryFoldImpl (cognitive 49) core/src/main/scala/stainless/transformers/lattices/Core.scala:1973
- CodeExtraction.extractClass (cognitive 48) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:517
- RefTransformContext.transformFun (cognitive 47) core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:468
- ImperativeCodeElimination.extractFunction (cognitive 45) core/src/main/scala/stainless/extraction/imperative/ImperativeCodeElimination.scala:29
- GlobalStateChecker.checkGlobalUsage (cognitive 45) core/src/main/scala/stainless/genc/phases/GlobalStateChecker.scala:87
- EffectsAnalyzer.expressionEffects (cognitive 44) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:804
- FunctionInlining.extractFunction (cognitive 43) core/src/main/scala/stainless/extraction/inlining/FunctionInlining.scala:36
- CodeExtraction.extractBlock (cognitive 43) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:1221
- Printer.ppBody (cognitive 42) core/src/main/scala/stainless/extraction/oo/Trees.scala:261
- CodeTryFolder.tryFoldImpl (cognitive 40) core/src/main/scala/stainless/transformers/lattices/Core.scala:2876
- RecursiveEvaluator.e (cognitive 39) core/src/main/scala/stainless/evaluators/RecursiveEvaluator.scala:15
- Checker.checkType (cognitive 39) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:427
- KernelRemPio2.computeModulo (cognitive 38) frontends/library/stainless/math/FdLibm.scala:748
- CallGraphPrinter.apply (cognitive 37) core/src/main/scala/stainless/frontend/CallGraphPrinter.scala:15
- SimplifierWithPC.simplify (cognitive 37) core/src/main/scala/stainless/transformers/SimplifierWithPC.scala:14
- VerificationChecker.checkVC (cognitive 37) core/src/main/scala/stainless/verification/VerificationChecker.scala:295
- MethodsAbstractSymbols.ensureWellFormedClass (cognitive 36) core/src/main/scala/stainless/extraction/methods/Trees.scala:104
- S2IRImpl.rec (cognitive 36) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:1030
- ReturnElimination.extractFunction (cognitive 35) core/src/main/scala/stainless/extraction/imperative/ReturnElimination.scala:109
- FunctionSpecialization.extractFunction (cognitive 35) core/src/main/scala/stainless/extraction/inlining/FunctionSpecialization.scala:38
- Analysis.rec (cognitive 35) core/src/main/scala/stainless/termination/ControlFlowAnalysis.scala:191
- OL.doSimplifyDisjunction (cognitive 35) core/src/main/scala/stainless/transformers/lattices/OL.scala:149
- CodeExtraction.extractType (cognitive 35) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:2635
- RecursiveEvaluator.matchesCase (cognitive 34) core/src/main/scala/stainless/evaluators/RecursiveEvaluator.scala:107
- FunctionClosure.extractFunction (cognitive 34) core/src/main/scala/stainless/extraction/innerfuns/FunctionClosure.scala:23
- CodeExtraction.extractPattern (cognitive 34) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:983
- Sinh.compute (cognitive 34) frontends/library/stainless/math/FdLibm.scala:1740
- CPrinter.pp (cognitive 33) core/src/main/scala/stainless/genc/CPrinter.scala:46
- VerificationRun.execute (cognitive 33) core/src/main/scala/stainless/verification/VerificationComponent.scala:82
- AbstractReport.usageConstructExtendedSummary (cognitive 32) core/src/main/scala/stainless/Report.scala:236
- CodeGeneration.compileLambda (cognitive 32) core/src/main/scala/stainless/codegen/CodeGeneration.scala:365
- Core.needsBinding (cognitive 32) core/src/main/scala/stainless/transformers/lattices/Core.scala:2212
- MethodLifting.makeFunction (cognitive 31) core/src/main/scala/stainless/extraction/methods/MethodLifting.scala:232
- Normaliser.recImpl (cognitive 31) core/src/main/scala/stainless/genc/ir/Normaliser.scala:37
- S2IRImpl.rec (cognitive 31) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:902
- AssertionInjector.transform (cognitive 31) core/src/main/scala/stainless/verification/AssertionInjector.scala:53
- InductElimination.extractFunction (cognitive 30) core/src/main/scala/stainless/extraction/termination/InductElimination.scala:26
- S2IRImpl.rec (cognitive 30) core/src/main/scala/stainless/genc/phases/Scala2IRPhase.scala:745
- Core.flattenAssocArith (cognitive 30) core/src/main/scala/stainless/transformers/lattices/Core.scala:1750
- CodePurity.fnPurity (cognitive 29) core/src/main/scala/stainless/transformers/lattices/Core.scala:2079
- Tan.__kernel_tan (cognitive 29) frontends/library/stainless/math/FdLibm.scala:268
- TypeEncoding.instanceOf (cognitive 28) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:321
- RecursionProcessor.run (cognitive 27) core/src/main/scala/stainless/termination/RecursionProcessor.scala:39
- Core.generateCond (cognitive 27) core/src/main/scala/stainless/transformers/lattices/Core.scala:1575
- math.atan2 (cognitive 27) frontends/library/stainless/math/package.scala:242
- Sealing.extractClass (cognitive 26) core/src/main/scala/stainless/extraction/methods/Sealing.scala:117
- Scope.empty (cognitive 26) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:1028
- Acos.compute (cognitive 26) frontends/library/stainless/math/FdLibm.scala:1069
- Tanh.compute (cognitive 26) frontends/library/stainless/math/FdLibm.scala:1837
- Laws.extractFunction (cognitive 25) core/src/main/scala/stainless/extraction/methods/Laws.scala:93
- TypeChecker.checkType (cognitive 25) core/src/main/scala/stainless/verification/TypeChecker.scala:1529
- RemPio2.__ieee754_rem_pio2 (cognitive 25) frontends/library/stainless/math/FdLibm.scala:344
- CodeExtraction.extractFunction (cognitive 24) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:815
- GhostAnnotationChecker.traverse (cognitive 24) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:284
- math.pow (cognitive 24) frontends/library/stainless/math/package.scala:601
- funRefTransformer.transform (cognitive 23) core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:295
- Scope.transform (cognitive 23) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:803
- CustomPrinter.ppBody (cognitive 23) core/src/main/scala/stainless/testgen/ScalaTestGen.scala:203
- CoqEncoder.transformTree (cognitive 23) core/src/main/scala/stainless/verification/CoqEncoder.scala:74
- GhostRewriteTransformer.transform (cognitive 23) frontends/dotty/src/main/scala/stainless/frontends/dotc/GhostAccessRewriter.scala:89
- TypeOps.patternIsTyped (cognitive 22) core/src/main/scala/stainless/ast/TypeOps.scala:20
- EquivalenceChecker.pickNextExamination (cognitive 22) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:304
- EquivalenceChecker.allSubFnsMatches (cognitive 22) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:920
- OL.arithLeq (cognitive 22) core/src/main/scala/stainless/transformers/lattices/OL.scala:106
- Log10.compute (cognitive 22) frontends/library/stainless/math/FdLibm.scala:1485
- CodeGeneration.mkBranch (cognitive 21) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1586
- CompilationUnit.jvmToValue (cognitive 21) core/src/main/scala/stainless/codegen/CompilationUnit.scala:302
- Scope.transform (cognitive 21) core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala:902
- LeonInlining.extractFunction (cognitive 21) core/src/main/scala/stainless/genc/LeonInlining.scala:38
- Printer.ppBody (cognitive 20) core/src/main/scala/stainless/extraction/xlang/Trees.scala:80
- TrimSymbols.run (cognitive 20) core/src/main/scala/stainless/genc/phases/TrimSymbols.scala:28
- Core.simplifiedDisjunction (cognitive 20) core/src/main/scala/stainless/transformers/lattices/Core.scala:1010
- CoqEncoder.transformFunction (cognitive 20) core/src/main/scala/stainless/verification/CoqEncoder.scala:440
- EquivalenceChecker.tryCreate (cognitive 19) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:1168
- CodeGenEvaluator.compile (cognitive 19) core/src/main/scala/stainless/evaluators/CodeGenEvaluator.scala:149
- Path.wrap (cognitive 19) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:295
- ReconstructTuple.unapply (cognitive 19) core/src/main/scala/stainless/extraction/imperative/ImperativeCleanup.scala:55
- DependencyGraph.computeDependencyGraph (cognitive 19) core/src/main/scala/stainless/extraction/oo/DependencyGraph.scala:67
- PartialEvaluator.simplify (cognitive 19) core/src/main/scala/stainless/transformers/PartialEvaluator.scala:11
- OL.latticesLeq (cognitive 19) core/src/main/scala/stainless/transformers/lattices/OL.scala:29
- Cosh.compute (cognitive 19) frontends/library/stainless/math/FdLibm.scala:1786
- EquivalenceChecker.evalCheck (cognitive 18) core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala:718
- MutabilityAnalysis.checkMutability (cognitive 18) core/src/main/scala/stainless/extraction/methods/MutabilityAnalyzer.scala:87
- AdtSpecialization.extractClass (cognitive 18) core/src/main/scala/stainless/extraction/oo/AdtSpecialization.scala:172
- RelationProcessor.run (cognitive 18) core/src/main/scala/stainless/termination/RelationProcessor.scala:28
- Transformer.transform (cognitive 18) core/src/main/scala/stainless/transformers/Transformer.scala:66
- CodeGeneration.compileADTConstructor (cognitive 17) core/src/main/scala/stainless/codegen/CodeGeneration.scala:2085
- DebugSymbols.debug (cognitive 17) core/src/main/scala/stainless/extraction/utils/NamedPipeline.scala:54
- IgnoredFields.traverse (cognitive 17) core/src/main/scala/stainless/extraction/xlang/TreeSanitizer.scala:214
- IR2CImpl.checkGlobalInit (cognitive 17) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala:115
- CodeExtraction.extractStatic (cognitive 17) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:213
- GhostAnnotationPropagater.traverse (cognitive 17) frontends/dotty/src/main/scala/stainless/frontends/dotc/FragmentChecker.scala:183
- CodeGeneration.loadTypes (cognitive 16) core/src/main/scala/stainless/codegen/CodeGeneration.scala:579
- FunctionInlining.extractSymbols (cognitive 16) core/src/main/scala/stainless/extraction/inlining/FunctionInlining.scala:168
- TransformerContext.transform (cognitive 16) core/src/main/scala/stainless/extraction/xlang/PartialFunctions.scala:43
- GenCTestGen.readExistingTestBodies (cognitive 16) core/src/main/scala/stainless/testgen/GenCTestGen.scala:98
- ASTExtractors.getAnnotations (cognitive 16) frontends/dotty/src/main/scala/stainless/frontends/dotc/ASTExtractors.scala:74
- MethodTooLong: InnerClasses.getContext core/src/main/scala/stainless/extraction/innerclasses/InnerClasses.scala:67
- REDACTED
- Change coupling: Deconstructors.scala ↔ InoxEncoder.scala core/src/main/scala/stainless/ast/Deconstructors.scala:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) frontends/library/stainless/math/FdLibm.scala:1207
- Edited copy of a member (16 corresponding lines) frontends/library/stainless/math/FdLibm.scala:1878
- Members sharing a duplicated core (12 members, 50+ identical tokens) core/src/main/scala/stainless/ast/Deconstructors.scala:247
- Members sharing a duplicated core (4 members, 50+ identical tokens) frontends/library/stainless/math/FdLibm.scala:458
- Duplicated block (27–28 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:508
- Duplicated block (19 lines × 2) core/src/main/scala/stainless/codegen/CompilationUnit.scala:232
- Duplicated block (17–18 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1863
- Duplicated block (18 lines × 2) frontends/library/stainless/io/FileInputStream.scala:231
- Duplicated block (15 lines × 4) frontends/library/stainless/math/FdLibm.scala:458
- Duplicated block (15 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:478
- Duplicated block (14–15 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:1886
- Duplicated block (13–14 lines × 2) frontends/library/stainless/io/FileInputStream.scala:252
- Duplicated block (11 lines × 3) core/src/main/scala/stainless/genc/phases/IR2CPhase.scala:242
- Duplicated block (10–11 lines × 2) core/src/main/scala/stainless/codegen/CodeGeneration.scala:991
- Duplicated block (7–8 lines × 2) core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala:331
- Duplicated block (6–8 lines × 2) core/src/main/scala/stainless/testgen/GenCTestGen.scala:21
- Duplicated block (6–7 lines × 2) core/src/main/scala/stainless/extraction/imperative/SymbolOps.scala:88
- Duplicated block (6 lines × 12) core/src/main/scala/stainless/ast/Deconstructors.scala:248
- Duplicated block (5 lines × 4) frontends/dotty/src/main/scala/stainless/frontends/dotc/CodeExtraction.scala:2374
- Duplicated block (3–5 lines × 3) core/src/main/scala/stainless/verification/AssertionInjector.scala:225
- Duplicated block (8 lines × 3) core/src/main/scala/stainless/ast/Definitions.scala:110
- Unfinished stub — body is `???` core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:277
- Unfinished stub — body is ??? / NotImplementedError core/src/main/scala/stainless/extraction/imperative/EffectElaboration.scala:277
- Skeleton type — most members are unfinished frontends/library/stainless/lang/StaticChecks.scala:5
- Future started here is not kept core/src/main/scala/stainless/utils/FileWatcher.scala:37
Minor — 163 finding(s)
- Orphaned file frontends/benchmarks/verification/valid/GodelNumbering.scala:1
- Orphaned file core/src/main/scala/stainless/extraction/xlang/TreeSanitizer.scala:1
- Orphaned file core/src/main/scala/stainless/verification/CoqExpression.scala:1
- Orphaned file frontends/benchmarks/full-imperative/valid/CellDataStructuresAndRepr.scala:1
- Orphaned file core/src/main/scala/stainless/transformers/lattices/Definitions.scala:1
- Orphaned file frontends/benchmarks/verification/valid/BalancedParentheses.scala:1
- Orphaned file core/src/main/scala/stainless/extraction/xlang/ConstructsUsage.scala:1
- Orphaned file core/src/main/scala/stainless/extraction/innerclasses/Trees.scala:1
- Orphaned file core/src/main/scala/stainless/frontend/Recovery.scala:1
- Orphaned file frontends/benchmarks/full-imperative/valid/CellArrayMergeSort.scala:1
- Orphaned file core/src/main/scala/stainless/extraction/inlining/FunctionSpecialization.scala:1
- Orphaned file core/src/main/scala/stainless/transformers/lattices/OL.scala:1
- Orphaned file core/src/main/scala/stainless/genc/ir/Referentiator.scala:1
- Orphaned file core/src/main/scala/stainless/verification/TypeCheckerDerivation.scala:1
- Orphaned file core/src/main/scala/stainless/testgen/ScalaTestGen.scala:1
- Orphaned file frontends/benchmarks/imperative/valid/TargetMutation10.scala:1
- Orphaned file frontends/benchmarks/equivalence/boardgame/Model.scala:1
- Orphaned file core/src/main/scala/stainless/equivchk/Utils.scala:1
- Orphaned file frontends/benchmarks/verification/valid/NaturalDeduction.scala:1
- Orphaned file frontends/benchmarks/dotty-specific/valid/ExportedMethods.scala:1
- Orphaned file core/src/main/scala/stainless/genc/ir/Transformer.scala:1
- Orphaned file core/src/main/scala/stainless/utils/CtexRemapping.scala:1
- Orphaned file core/src/main/scala/stainless/extraction/termination/InductElimination.scala:1
- Orphaned file core/src/main/scala/stainless/genc/ir/ClassLifter.scala:1
- Orphaned file core/src/main/scala/stainless/genc/phases/GlobalStateChecker.scala:1
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1393
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1107
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:246
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1726
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1504
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1266
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1653
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:2127
- Duplicated predicate frontends/library/stainless/covcollection/Option.scala:27
- Duplicated predicate core/src/main/scala/stainless/extraction/imperative/AntiAliasing.scala:1116
- Duplicated predicate core/src/main/scala/stainless/extraction/inlining/FunctionInlining.scala:58
- Duplicated predicate core/src/main/scala/stainless/codegen/CodeGeneration.scala:1346
- Duplicated predicate core/src/main/scala/stainless/codegen/CodeGeneration.scala:2294
- Duplicated predicate core/src/main/scala/stainless/extraction/imperative/EffectsChecker.scala:205
- Duplicated predicate frontends/library/stainless/collection/List.scala:617
- Duplicated predicate frontends/library/stainless/math/FdLibm.scala:1774
- Duplicated predicate frontends/library/stainless/collection/List.scala:603
- Duplicated predicate core/src/main/scala/stainless/evaluators/EvaluatorComponent.scala:84
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Empty method body frontends/library/stainless/lang/StaticChecks.scala:26
- Empty method body frontends/library/stainless/lang/StaticChecks.scala:27
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No changelog
- Scala's null is not held to the type system everywhere
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-3060bfb44aad421185d819bf46193f16/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-3060bfb44aad421185d819bf46193f16/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude core/src/sphinx . | 19 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-0ad0b6e1697648269c169b713bad2840 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 82 file(s) — `core/src/main/scala/stainless/equivchk/EquivalenceChecker.scala`, `core/src/main/scala/stainless/extraction/imperative/EffectsAnalyzer.scala`, `core/src/main/scala/stainless/extraction/innerfuns/FunctionClosure.scala`, `core/src/main/scala/stainless/extraction/methods/Trees.scala`, `core/src/main/scala/stainless/extraction/oo/TypeEncoding.scala`, … (+77 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-0ad0b6e1697648269c169b713bad2840 | 0 | artifacts/raw/osv-scanner.json |