Executive summary
apalache-mc/apalache falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 59 out of 100 and is rated Adequate, and 57 of its 59 critical findings are security problems in the build pipeline and in the packages it uses.
Code Health, at 56, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is serving traffic only over an encrypted connection, worth about 3 points. Declaring which values may be missing would lift Code Health itself, worth about 2 points.
Fifty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and one known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. The pipeline step that runs a download without checking it needs each download checked against a known checksum first. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 55,179 lines, about €100,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 5 findings
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €100,000 · Estimate
| Cost to rebuild | €33,000 to €170,000, for 558 to 1,770 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.8 at a score of 59. 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: 55,179 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 at.forsyte.apalache.io.annotations.parser.CommentPreprocessor | 2 at.forsyte.apalache.tla.lir.formulas | 3 at.forsyte.apalache.io.annotations.parser | 4 at.forsyte.apalache.tla.lir.oper | 5 at.forsyte.apalache.tla.lir.transformations | 6 at.forsyte.apalache.io.tlc.config | 7 at.forsyte.apalache.tla.lir | 8 at.forsyte.apalache.infra.passes | 9 at.forsyte.apalache.io.config | 10 at.forsyte.apalache.io.lir | 11 at.forsyte.apalache.io.quint | 12 at.forsyte.apalache.tla.bmcmt.types | 13 at.forsyte.apalache.tla.lir.src | 14 at.forsyte.apalache.tla.lir.transformations.standard | 15 at.forsyte.apalache.tla.typecheck.etc | 16 at.forsyte.apalache.tla.typecomp | 17 at.forsyte.apalache.io.InputSource | 18 at.forsyte.apalache.tla.bmcmt.Checker | 19 at.forsyte.apalache.tla.imp | 20 at.forsyte.apalache.tla.typecheck | 21 com.github.apalachemc.apalache.jsonrpc | 22 at.forsyte.apalache.io | 23 at.forsyte.apalache.tla.bmcmt.search | 24 at.forsyte.apalache.tla.bmcmt.smt | 25 at.forsyte.apalache.io.config.ApalacheConfigJsonParser | 26 at.forsyte.apalache.tla.bmcmt.arena | 27 at.forsyte.apalache.tla.passes.imp | 28 at.forsyte.apalache.tla.tracee | 29 at.forsyte.apalache.io.json | 30 at.forsyte.apalache.tla.bmcmt.rewriter | 31 at.forsyte.apalache.tla.bmcmt.rules.support | 32 at.forsyte.apalache.tla.passes.pp | 33 at.forsyte.apalache.tla.passes.typecheck | 34 at.forsyte.apalache.tla.bmcmt.caches | 35 at.forsyte.apalache.tla.bmcmt.trex | 36 at.forsyte.apalache.tla.bmcmt | 37 at.forsyte.apalache.tla.bmcmt.passes | 38 at.forsyte.apalache.tla.bmcmt.rules | 39 at.forsyte.apalache.tla.bmcmt.stratifiedRules | 40 at.forsyte.apalache.tla.bmcmt.stratifiedRules.support |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 at.forsyte.apalache.io.annotations.parser.CommentPreprocessor | ||||||||||||||||||||||||||||||||||||||||
| 2 at.forsyte.apalache.tla.lir.formulas | ||||||||||||||||||||||||||||||||||||||||
| 3 at.forsyte.apalache.io.annotations.parser | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 at.forsyte.apalache.tla.lir.oper | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 at.forsyte.apalache.tla.lir.transformations | 8 | |||||||||||||||||||||||||||||||||||||||
| 6 at.forsyte.apalache.io.tlc.config | 5 | |||||||||||||||||||||||||||||||||||||||
| 7 at.forsyte.apalache.tla.lir | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 at.forsyte.apalache.infra.passes | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 at.forsyte.apalache.io.config | 3 | 2 | 11 | |||||||||||||||||||||||||||||||||||||
| 10 at.forsyte.apalache.io.lir | 2 | 20 | ||||||||||||||||||||||||||||||||||||||
| 11 at.forsyte.apalache.io.quint | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 at.forsyte.apalache.tla.bmcmt.types | 6 | |||||||||||||||||||||||||||||||||||||||
| 13 at.forsyte.apalache.tla.lir.src | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 14 at.forsyte.apalache.tla.lir.transformations.standard | 1 | 11 | 27 | |||||||||||||||||||||||||||||||||||||
| 15 at.forsyte.apalache.tla.typecheck.etc | 22 | 3 | ||||||||||||||||||||||||||||||||||||||
| 16 at.forsyte.apalache.tla.typecomp | 3 | 14 | ||||||||||||||||||||||||||||||||||||||
| 17 at.forsyte.apalache.io.InputSource | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 at.forsyte.apalache.tla.bmcmt.Checker | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 at.forsyte.apalache.tla.imp | 4 | 15 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 at.forsyte.apalache.tla.typecheck | 1 | 11 | 8 | |||||||||||||||||||||||||||||||||||||
| 21 com.github.apalachemc.apalache.jsonrpc | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 at.forsyte.apalache.io | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 at.forsyte.apalache.tla.bmcmt.search | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 at.forsyte.apalache.tla.bmcmt.smt | 3 | 3 | 4 | 2 | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||
| 25 at.forsyte.apalache.io.config.ApalacheConfigJsonParser | 1 | 8 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 at.forsyte.apalache.tla.bmcmt.arena | 2 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 27 at.forsyte.apalache.tla.passes.imp | 2 | 2 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 28 at.forsyte.apalache.tla.tracee | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 at.forsyte.apalache.io.json | 27 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 at.forsyte.apalache.tla.bmcmt.rewriter | 6 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 31 at.forsyte.apalache.tla.bmcmt.rules.support | 15 | 1 | 7 | 3 | 29 | |||||||||||||||||||||||||||||||||||
| 32 at.forsyte.apalache.tla.passes.pp | 2 | 1 | 11 | 1 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 33 at.forsyte.apalache.tla.passes.typecheck | 4 | 1 | 3 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 at.forsyte.apalache.tla.bmcmt.caches | 2 | 5 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 at.forsyte.apalache.tla.bmcmt.trex | 5 | 4 | 3 | 1 | 3 | 4 | 5 | |||||||||||||||||||||||||||||||||
| 36 at.forsyte.apalache.tla.bmcmt | 27 | 4 | 2 | 1 | 1 | 3 | 2 | 5 | 2 | 9 | 11 | 2 | ||||||||||||||||||||||||||||
| 37 at.forsyte.apalache.tla.bmcmt.passes | 4 | 2 | 1 | 1 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 38 at.forsyte.apalache.tla.bmcmt.rules | 1 | 3 | 26 | 4 | 119 | |||||||||||||||||||||||||||||||||||
| 39 at.forsyte.apalache.tla.bmcmt.stratifiedRules | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 40 at.forsyte.apalache.tla.bmcmt.stratifiedRules.support | 1 | 2 | 1 | 2 |
3→1 at.forsyte.apalache.io.annotations.parser uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.io.annotations.parser uses a type in at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- The types involved
at.forsyte.apalache.io.annotations.parser.CommentPreprocessor→at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.State
- Direction
- at.forsyte.apalache.io.annotations.parser uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor, so a change to at.forsyte.apalache.io.annotations.parser.CommentPreprocessor can break at.forsyte.apalache.io.annotations.parser, while a change to at.forsyte.apalache.io.annotations.parser can't break at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- Position
- Below the diagonal: at.forsyte.apalache.io.annotations.parser uses a module listed above it, which is the healthy direction.
4→7 at.forsyte.apalache.tla.lir.oper uses at.forsyte.apalache.tla.lir part of a loop✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.lir.oper uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.lir.oper.TlaOper→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.lir.oper uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.lir.oper, while a change to at.forsyte.apalache.tla.lir.oper can't break at.forsyte.apalache.tla.lir.
- 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→7 at.forsyte.apalache.tla.lir.transformations uses at.forsyte.apalache.tla.lir part of a loop✕
- Connections
- 8 pairs of types, where a type in at.forsyte.apalache.tla.lir.transformations uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.lir.transformations.LanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.LanguagePred→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.LanguageWatchdog→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.LanguageWatchdog→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.TransformationListener→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.lir.transformations.TransformationListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.TransformationTracker→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.TransformationTracker→at.forsyte.apalache.tla.lir.TlaOperDecl
- Direction
- at.forsyte.apalache.tla.lir.transformations uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.lir.transformations, while a change to at.forsyte.apalache.tla.lir.transformations can't break at.forsyte.apalache.tla.lir.
- 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→3 at.forsyte.apalache.io.tlc.config uses at.forsyte.apalache.io.annotations.parser✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.io.tlc.config uses a type in at.forsyte.apalache.io.annotations.parser.
- The types involved
at.forsyte.apalache.io.tlc.config.TlcConfigLexer→at.forsyte.apalache.io.annotations.parser.BOOLEANat.forsyte.apalache.io.tlc.config.TlcConfigLexer→at.forsyte.apalache.io.annotations.parser.COMMAat.forsyte.apalache.io.tlc.config.TlcConfigLexer→at.forsyte.apalache.io.annotations.parser.IDENTat.forsyte.apalache.io.tlc.config.TlcConfigLexer→at.forsyte.apalache.io.annotations.parser.NUMBERat.forsyte.apalache.io.tlc.config.TlcConfigLexer→at.forsyte.apalache.io.annotations.parser.STRING
- Direction
- at.forsyte.apalache.io.tlc.config uses at.forsyte.apalache.io.annotations.parser, so a change to at.forsyte.apalache.io.annotations.parser can break at.forsyte.apalache.io.tlc.config, while a change to at.forsyte.apalache.io.tlc.config can't break at.forsyte.apalache.io.annotations.parser.
- Position
- Below the diagonal: at.forsyte.apalache.io.tlc.config uses a module listed above it, which is the healthy direction.
7→4 at.forsyte.apalache.tla.lir uses at.forsyte.apalache.tla.lir.oper✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.lir uses a type in at.forsyte.apalache.tla.lir.oper.
- The types involved
at.forsyte.apalache.tla.lir.Builder→at.forsyte.apalache.tla.lir.oper.TlaOperat.forsyte.apalache.tla.lir.BuilderOper→at.forsyte.apalache.tla.lir.oper.TlaOperat.forsyte.apalache.tla.lir.OperEx→at.forsyte.apalache.tla.lir.oper.TlaOper
- Direction
- at.forsyte.apalache.tla.lir uses at.forsyte.apalache.tla.lir.oper, so a change to at.forsyte.apalache.tla.lir.oper can break at.forsyte.apalache.tla.lir, while a change to at.forsyte.apalache.tla.lir can't break at.forsyte.apalache.tla.lir.oper.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir uses a module listed above it, which is the healthy direction.
7→5 at.forsyte.apalache.tla.lir uses at.forsyte.apalache.tla.lir.transformations✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.lir uses a type in at.forsyte.apalache.tla.lir.transformations.
- The types involved
at.forsyte.apalache.tla.lir.transformations→at.forsyte.apalache.tla.lir.transformations.TransformationTracker
- Direction
- at.forsyte.apalache.tla.lir uses at.forsyte.apalache.tla.lir.transformations, so a change to at.forsyte.apalache.tla.lir.transformations can break at.forsyte.apalache.tla.lir, while a change to at.forsyte.apalache.tla.lir can't break at.forsyte.apalache.tla.lir.transformations.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir uses a module listed above it, which is the healthy direction.
8→7 at.forsyte.apalache.infra.passes uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.infra.passes uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.infra.passes.Pass→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.infra.passes.PassChainExecutor→at.forsyte.apalache.tla.lir.TlaModule
- Direction
- at.forsyte.apalache.infra.passes uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.infra.passes, while a change to at.forsyte.apalache.infra.passes can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.infra.passes uses a module listed above it, which is the healthy direction.
9→6 at.forsyte.apalache.io.config uses at.forsyte.apalache.io.tlc.config✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.io.config uses a type in at.forsyte.apalache.io.tlc.config.
- The types involved
at.forsyte.apalache.io.config.ApalacheConfigResolver→at.forsyte.apalache.io.tlc.config.TlcConfigat.forsyte.apalache.io.config.SpecificationOptions→at.forsyte.apalache.io.tlc.config.BehaviorSpecat.forsyte.apalache.io.config.TlcConfigInput→at.forsyte.apalache.io.tlc.config.TlcConfig
- Direction
- at.forsyte.apalache.io.config uses at.forsyte.apalache.io.tlc.config, so a change to at.forsyte.apalache.io.tlc.config can break at.forsyte.apalache.io.config, while a change to at.forsyte.apalache.io.config can't break at.forsyte.apalache.io.tlc.config.
- Position
- Below the diagonal: at.forsyte.apalache.io.config uses a module listed above it, which is the healthy direction.
9→7 at.forsyte.apalache.io.config uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.config uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.io.config.CommonOptions→at.forsyte.apalache.tla.lir.Featureat.forsyte.apalache.io.config.CommonPatch→at.forsyte.apalache.tla.lir.Feature
- Direction
- at.forsyte.apalache.io.config uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.io.config, while a change to at.forsyte.apalache.io.config can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.io.config uses a module listed above it, which is the healthy direction.
9→22 at.forsyte.apalache.io.config uses at.forsyte.apalache.io part of a loop✕
- Connections
- 11 pairs of types, where a type in at.forsyte.apalache.io.config uses a type in at.forsyte.apalache.io.
- The types involved
at.forsyte.apalache.io.config.ApalacheConfig→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ApalacheConfigJsonParser→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ApalacheConfigResolver→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.CommandInitializationOptions→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ModuleIoOptions→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.TraceEvaluationOptions→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.TraceEvaluationPatch→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ValidatedCheckOptions→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ValidatedParseOptions→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ValidatedTraceOptions→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.config.ValidatedTypecheckOptions→at.forsyte.apalache.io.InputSource
- Direction
- at.forsyte.apalache.io.config uses at.forsyte.apalache.io, so a change to at.forsyte.apalache.io can break at.forsyte.apalache.io.config, while a change to at.forsyte.apalache.io.config can't break at.forsyte.apalache.io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 at.forsyte.apalache.io.lir uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.lir uses a type in at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- The types involved
at.forsyte.apalache.io.lir.TlaCounterexampleWriter→at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.Stateat.forsyte.apalache.io.lir.Trace→at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.State
- Direction
- at.forsyte.apalache.io.lir uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor, so a change to at.forsyte.apalache.io.annotations.parser.CommentPreprocessor can break at.forsyte.apalache.io.lir, while a change to at.forsyte.apalache.io.lir can't break at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- Position
- Below the diagonal: at.forsyte.apalache.io.lir uses a module listed above it, which is the healthy direction.
10→7 at.forsyte.apalache.io.lir uses at.forsyte.apalache.tla.lir✕
- Connections
- 20 pairs of types, where a type in at.forsyte.apalache.io.lir uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.io.lir.CounterexampleWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.ItfCounterexampleWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.JsonCounterexampleWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.PrettyWriter→at.forsyte.apalache.tla.lir.OperParamat.forsyte.apalache.io.lir.PrettyWriter→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.lir.PrettyWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.PrettyWriter→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.lir.PrettyWriter→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.io.lir.TlaCounterexampleWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.TlaDeclAnnotator→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.lir.TlaType1TagPrinter→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.io.lir.TlaWriter→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.lir.TlaWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.TlaWriter→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.lir.TlaWriterFactory→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.lir.TlcCounterexampleWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.lir.Trace→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.lir.TypeTagPrinter→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.io.lir.TypeTagReader→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.io.lir.UntypedReader→at.forsyte.apalache.tla.lir.TypeTag
- Direction
- at.forsyte.apalache.io.lir uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.io.lir, while a change to at.forsyte.apalache.io.lir can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.io.lir uses a module listed above it, which is the healthy direction.
11→7 at.forsyte.apalache.io.quint uses at.forsyte.apalache.tla.lir✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.io.quint uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.io.quint.Quint→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.quint.Quint→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.io.quint.QuintTypeConverter→at.forsyte.apalache.tla.lir.RowT1at.forsyte.apalache.io.quint.QuintTypeConverter→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.io.quint uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.io.quint, while a change to at.forsyte.apalache.io.quint can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.io.quint uses a module listed above it, which is the healthy direction.
12→7 at.forsyte.apalache.tla.bmcmt.types uses at.forsyte.apalache.tla.lir✕
- Connections
- 6 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.types uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.types.CellT→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.types.CellTFrom→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.types.FinFunSetT→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.types.InfSetT→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.types.PowSetT→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.types.UnknownT→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.bmcmt.types uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.types, while a change to at.forsyte.apalache.tla.bmcmt.types can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.types uses a module listed above it, which is the healthy direction.
13→5 at.forsyte.apalache.tla.lir.src uses at.forsyte.apalache.tla.lir.transformations✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.lir.src uses a type in at.forsyte.apalache.tla.lir.transformations.
- The types involved
at.forsyte.apalache.tla.lir.src.SaveToStoreTransformationListener→at.forsyte.apalache.tla.lir.transformations.TransformationListenerat.forsyte.apalache.tla.lir.src.SourceStore→at.forsyte.apalache.tla.lir.transformations.TransformationListener
- Direction
- at.forsyte.apalache.tla.lir.src uses at.forsyte.apalache.tla.lir.transformations, so a change to at.forsyte.apalache.tla.lir.transformations can break at.forsyte.apalache.tla.lir.src, while a change to at.forsyte.apalache.tla.lir.src can't break at.forsyte.apalache.tla.lir.transformations.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir.src uses a module listed above it, which is the healthy direction.
13→7 at.forsyte.apalache.tla.lir.src uses at.forsyte.apalache.tla.lir✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.tla.lir.src uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.lir.src.SaveToStoreTransformationListener→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.lir.src.SaveToStoreTransformationListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.src.SourceStore→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.lir.src.SourceStore→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.src.SourceStore→at.forsyte.apalache.tla.lir.UID
- Direction
- at.forsyte.apalache.tla.lir.src uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.lir.src, while a change to at.forsyte.apalache.tla.lir.src can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir.src uses a module listed above it, which is the healthy direction.
14→4 at.forsyte.apalache.tla.lir.transformations.standard uses at.forsyte.apalache.tla.lir.oper✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.lir.transformations.standard uses a type in at.forsyte.apalache.tla.lir.oper.
- The types involved
at.forsyte.apalache.tla.lir.transformations.standard.Flatten→at.forsyte.apalache.tla.lir.oper.TlaOper
- Direction
- at.forsyte.apalache.tla.lir.transformations.standard uses at.forsyte.apalache.tla.lir.oper, so a change to at.forsyte.apalache.tla.lir.oper can break at.forsyte.apalache.tla.lir.transformations.standard, while a change to at.forsyte.apalache.tla.lir.transformations.standard can't break at.forsyte.apalache.tla.lir.oper.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir.transformations.standard uses a module listed above it, which is the healthy direction.
14→5 at.forsyte.apalache.tla.lir.transformations.standard uses at.forsyte.apalache.tla.lir.transformations✕
- Connections
- 11 pairs of types, where a type in at.forsyte.apalache.tla.lir.transformations.standard uses a type in at.forsyte.apalache.tla.lir.transformations.
- The types involved
at.forsyte.apalache.tla.lir.transformations.standard.ContextualLanguagePred→at.forsyte.apalache.tla.lir.transformations.LanguagePredat.forsyte.apalache.tla.lir.transformations.standard.ContextualLanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResultat.forsyte.apalache.tla.lir.transformations.standard.FlatLanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResultat.forsyte.apalache.tla.lir.transformations.standard.Flatten→at.forsyte.apalache.tla.lir.transformations.TransformationTrackerat.forsyte.apalache.tla.lir.transformations.standard.KeraLanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResultat.forsyte.apalache.tla.lir.transformations.standard.KeramelizerInputLanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResultat.forsyte.apalache.tla.lir.transformations.standard.MonotypeLanguagePred→at.forsyte.apalache.tla.lir.transformations.LanguagePredat.forsyte.apalache.tla.lir.transformations.standard.MonotypeLanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResultat.forsyte.apalache.tla.lir.transformations.standard.NonrecursiveLanguagePred→at.forsyte.apalache.tla.lir.transformations.LanguagePredat.forsyte.apalache.tla.lir.transformations.standard.NonrecursiveLanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResultat.forsyte.apalache.tla.lir.transformations.standard.ReTLALanguagePred→at.forsyte.apalache.tla.lir.transformations.PredResult
- Direction
- at.forsyte.apalache.tla.lir.transformations.standard uses at.forsyte.apalache.tla.lir.transformations, so a change to at.forsyte.apalache.tla.lir.transformations can break at.forsyte.apalache.tla.lir.transformations.standard, while a change to at.forsyte.apalache.tla.lir.transformations.standard can't break at.forsyte.apalache.tla.lir.transformations.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir.transformations.standard uses a module listed above it, which is the healthy direction.
14→7 at.forsyte.apalache.tla.lir.transformations.standard uses at.forsyte.apalache.tla.lir✕
- Connections
- 27 pairs of types, where a type in at.forsyte.apalache.tla.lir.transformations.standard uses a type in at.forsyte.apalache.tla.lir. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
at.forsyte.apalache.tla.lir.transformations.standard.ContextualLanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.ContextualLanguagePred→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.standard.ContextualLanguagePred→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.lir.transformations.standard.DeclarationSorter→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.lir.transformations.standard.DeclarationSorter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.DeclarationSorter→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.standard.DeclarationSorter→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.lir.transformations.standard.DeepCopy→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.standard.FlatLanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.Flatten→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.Flatten→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.tla.lir.transformations.standard.IncrementalRenaming→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.lir.transformations.standard.IncrementalRenaming→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.KeraLanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.KeramelizerInputLanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.ModuleByExTransformer→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.standard.MonotypeLanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.MonotypeLanguagePred→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.standard.MonotypeLanguagePred→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.lir.transformations.standard.MonotypeLanguagePred→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.lir.transformations.standard.NonrecursiveLanguagePred→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.NonrecursiveLanguagePred→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.lir.transformations.standard.NonrecursiveLanguagePred→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.lir.transformations.standard.PrimePropagation→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.lir.transformations.standard.ReTLALanguagePred→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.lir.transformations.standard uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.lir.transformations.standard, while a change to at.forsyte.apalache.tla.lir.transformations.standard can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.lir.transformations.standard uses a module listed above it, which is the healthy direction.
15→7 at.forsyte.apalache.tla.typecheck.etc uses at.forsyte.apalache.tla.lir✕
- Connections
- 22 pairs of types, where a type in at.forsyte.apalache.tla.typecheck.etc uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.typecheck.etc.BlameRef→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.typecheck.etc.Clause→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EqClause→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EqClause→at.forsyte.apalache.tla.lir.VarT1at.forsyte.apalache.tla.typecheck.etc.EtcApp→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EtcBuilder→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EtcConst→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EtcExpr→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EtcRef→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.typecheck.etc.EtcTypeChecker→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.EtcTypeDecl→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.ExactRef→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.NameExat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.OperParamat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.OperT1at.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.TlaValueat.forsyte.apalache.tla.typecheck.etc.ToEtcExpr→at.forsyte.apalache.tla.lir.VarT1at.forsyte.apalache.tla.typecheck.etc.TypeAliasSubstitution→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.typecheck.etc uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.typecheck.etc, while a change to at.forsyte.apalache.tla.typecheck.etc can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.typecheck.etc uses a module listed above it, which is the healthy direction.
15→20 at.forsyte.apalache.tla.typecheck.etc uses at.forsyte.apalache.tla.typecheck part of a loop✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.typecheck.etc uses a type in at.forsyte.apalache.tla.typecheck.
- The types involved
at.forsyte.apalache.tla.typecheck.etc.EtcTypeChecker→at.forsyte.apalache.tla.typecheck.TypeCheckerat.forsyte.apalache.tla.typecheck.etc.EtcTypeChecker→at.forsyte.apalache.tla.typecheck.TypeCheckerListenerat.forsyte.apalache.tla.typecheck.etc.EtcTypeChecker→at.forsyte.apalache.tla.typecheck.TypeContext
- Direction
- at.forsyte.apalache.tla.typecheck.etc uses at.forsyte.apalache.tla.typecheck, so a change to at.forsyte.apalache.tla.typecheck can break at.forsyte.apalache.tla.typecheck.etc, while a change to at.forsyte.apalache.tla.typecheck.etc can't break at.forsyte.apalache.tla.typecheck.
- 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→4 at.forsyte.apalache.tla.typecomp uses at.forsyte.apalache.tla.lir.oper✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.typecomp uses a type in at.forsyte.apalache.tla.lir.oper.
- The types involved
at.forsyte.apalache.tla.typecomp.BuilderUtil→at.forsyte.apalache.tla.lir.oper.OperArityat.forsyte.apalache.tla.typecomp.BuilderUtil→at.forsyte.apalache.tla.lir.oper.TlaOperat.forsyte.apalache.tla.typecomp.TypeComputationFactory→at.forsyte.apalache.tla.lir.oper.TlaOper
- Direction
- at.forsyte.apalache.tla.typecomp uses at.forsyte.apalache.tla.lir.oper, so a change to at.forsyte.apalache.tla.lir.oper can break at.forsyte.apalache.tla.typecomp, while a change to at.forsyte.apalache.tla.typecomp can't break at.forsyte.apalache.tla.lir.oper.
- Position
- Below the diagonal: at.forsyte.apalache.tla.typecomp uses a module listed above it, which is the healthy direction.
16→7 at.forsyte.apalache.tla.typecomp uses at.forsyte.apalache.tla.lir✕
- Connections
- 14 pairs of types, where a type in at.forsyte.apalache.tla.typecomp uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.typecomp.Applicative→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecomp.BuilderUtil→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.typecomp.NoOpBuild→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.typecomp.ParamUtil→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecomp.ScopeUnsafeBuilder→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.typecomp.ScopeUnsafeBuilder→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.typecomp.ScopeUnsafeBuilder→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecomp.ScopeUnsafeBuilder→at.forsyte.apalache.tla.lir.TlaVarDeclat.forsyte.apalache.tla.typecomp.ScopedBuilder→at.forsyte.apalache.tla.lir.OperParamat.forsyte.apalache.tla.typecomp.ScopedBuilder→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.typecomp.ScopedBuilder→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.typecomp.ScopedBuilder→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecomp.ScopedBuilder→at.forsyte.apalache.tla.lir.TlaVarDeclat.forsyte.apalache.tla.typecomp.TBuilderContext→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.typecomp uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.typecomp, while a change to at.forsyte.apalache.tla.typecomp can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.typecomp uses a module listed above it, which is the healthy direction.
17→9 at.forsyte.apalache.io.InputSource uses at.forsyte.apalache.io.config✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.InputSource uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.io.InputSource.FileSource→at.forsyte.apalache.io.config.ConfigParseResultat.forsyte.apalache.io.InputSource.StringSource→at.forsyte.apalache.io.config.ConfigParseResult
- Direction
- at.forsyte.apalache.io.InputSource uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.io.InputSource, while a change to at.forsyte.apalache.io.InputSource can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.io.InputSource uses a module listed above it, which is the healthy direction.
17→22 at.forsyte.apalache.io.InputSource uses at.forsyte.apalache.io part of a loop✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.InputSource uses a type in at.forsyte.apalache.io.
- The types involved
at.forsyte.apalache.io.InputSource.FileSource→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.io.InputSource.StringSource→at.forsyte.apalache.io.InputSource
- Direction
- at.forsyte.apalache.io.InputSource uses at.forsyte.apalache.io, so a change to at.forsyte.apalache.io can break at.forsyte.apalache.io.InputSource, while a change to at.forsyte.apalache.io.InputSource can't break at.forsyte.apalache.io.
- 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→7 at.forsyte.apalache.tla.bmcmt.Checker uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.Checker uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.Checker.Deadlock→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.Checker.Error→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.Checker uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.Checker, while a change to at.forsyte.apalache.tla.bmcmt.Checker can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.Checker uses a module listed above it, which is the healthy direction.
18→10 at.forsyte.apalache.tla.bmcmt.Checker uses at.forsyte.apalache.io.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.Checker uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.Checker.Deadlock→at.forsyte.apalache.io.lir.Traceat.forsyte.apalache.tla.bmcmt.Checker.Error→at.forsyte.apalache.io.lir.Trace
- Direction
- at.forsyte.apalache.tla.bmcmt.Checker uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.tla.bmcmt.Checker, while a change to at.forsyte.apalache.tla.bmcmt.Checker can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.Checker uses a module listed above it, which is the healthy direction.
19→4 at.forsyte.apalache.tla.imp uses at.forsyte.apalache.tla.lir.oper✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.imp uses a type in at.forsyte.apalache.tla.lir.oper.
- The types involved
at.forsyte.apalache.tla.imp.ExprOrOpArgNodeTranslator→at.forsyte.apalache.tla.lir.oper.TlaOperat.forsyte.apalache.tla.imp.OpApplTranslator→at.forsyte.apalache.tla.lir.oper.TlaOperat.forsyte.apalache.tla.imp.OperAliasUnit→at.forsyte.apalache.tla.lir.oper.TlaOperat.forsyte.apalache.tla.imp.StandardLibrary→at.forsyte.apalache.tla.lir.oper.TlaOper
- Direction
- at.forsyte.apalache.tla.imp uses at.forsyte.apalache.tla.lir.oper, so a change to at.forsyte.apalache.tla.lir.oper can break at.forsyte.apalache.tla.imp, while a change to at.forsyte.apalache.tla.imp can't break at.forsyte.apalache.tla.lir.oper.
- Position
- Below the diagonal: at.forsyte.apalache.tla.imp uses a module listed above it, which is the healthy direction.
19→7 at.forsyte.apalache.tla.imp uses at.forsyte.apalache.tla.lir✕
- Connections
- 15 pairs of types, where a type in at.forsyte.apalache.tla.imp uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.imp.AnnotationExtractor→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.imp.AssumeTranslator→at.forsyte.apalache.tla.lir.TlaAssumeDeclat.forsyte.apalache.tla.imp.DeclUnit→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.imp.ExprOrOpArgNodeTranslator→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.imp.FormalParamTranslator→at.forsyte.apalache.tla.lir.OperParamat.forsyte.apalache.tla.imp.ModuleTranslator→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.imp.ModuleTranslator→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.imp.ModuleTranslator→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.imp.NullOpDefTranslator→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.imp.OpApplTranslator→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.imp.OpDefTranslator→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.imp.StandardLibrary→at.forsyte.apalache.tla.lir.TlaValueat.forsyte.apalache.tla.imp.SubstTranslator→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.imp.ValueAliasUnit→at.forsyte.apalache.tla.lir.TlaValueat.forsyte.apalache.tla.imp.utils→at.forsyte.apalache.tla.lir.TlaModule
- Direction
- at.forsyte.apalache.tla.imp uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.imp, while a change to at.forsyte.apalache.tla.imp can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.imp uses a module listed above it, which is the healthy direction.
19→9 at.forsyte.apalache.tla.imp uses at.forsyte.apalache.io.config✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.imp uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.tla.imp.utils→at.forsyte.apalache.io.config.CommonOptions
- Direction
- at.forsyte.apalache.tla.imp uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.tla.imp, while a change to at.forsyte.apalache.tla.imp can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.tla.imp uses a module listed above it, which is the healthy direction.
19→10 at.forsyte.apalache.tla.imp uses at.forsyte.apalache.io.lir✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.imp uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.tla.imp.utils→at.forsyte.apalache.io.lir.TlaWriterFactory
- Direction
- at.forsyte.apalache.tla.imp uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.tla.imp, while a change to at.forsyte.apalache.tla.imp can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.imp uses a module listed above it, which is the healthy direction.
19→13 at.forsyte.apalache.tla.imp uses at.forsyte.apalache.tla.lir.src✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.imp uses a type in at.forsyte.apalache.tla.lir.src.
- The types involved
at.forsyte.apalache.tla.imp.utils→at.forsyte.apalache.tla.lir.src.SourceStore
- Direction
- at.forsyte.apalache.tla.imp uses at.forsyte.apalache.tla.lir.src, so a change to at.forsyte.apalache.tla.lir.src can break at.forsyte.apalache.tla.imp, while a change to at.forsyte.apalache.tla.imp can't break at.forsyte.apalache.tla.lir.src.
- Position
- Below the diagonal: at.forsyte.apalache.tla.imp uses a module listed above it, which is the healthy direction.
20→5 at.forsyte.apalache.tla.typecheck uses at.forsyte.apalache.tla.lir.transformations✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.typecheck uses a type in at.forsyte.apalache.tla.lir.transformations.
- The types involved
at.forsyte.apalache.tla.typecheck.TypeCheckerTool→at.forsyte.apalache.tla.lir.transformations.TransformationTracker
- Direction
- at.forsyte.apalache.tla.typecheck uses at.forsyte.apalache.tla.lir.transformations, so a change to at.forsyte.apalache.tla.lir.transformations can break at.forsyte.apalache.tla.typecheck, while a change to at.forsyte.apalache.tla.typecheck can't break at.forsyte.apalache.tla.lir.transformations.
- Position
- Below the diagonal: at.forsyte.apalache.tla.typecheck uses a module listed above it, which is the healthy direction.
20→7 at.forsyte.apalache.tla.typecheck uses at.forsyte.apalache.tla.lir✕
- Connections
- 11 pairs of types, where a type in at.forsyte.apalache.tla.typecheck uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.typecheck.DefaultTypeCheckerListener→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.MultiTypeCheckerListener→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.SourceAwareTypeCheckerListener→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.typecheck.TypeChecker→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.TypeCheckerListener→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.TypeCheckerTool→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.typecheck.TypeCheckerTool→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.typecheck.TypeCheckerTool→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.typecheck.TypeCheckerTool→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.typecheck.TypeContext→at.forsyte.apalache.tla.lir.TlaType1Schemeat.forsyte.apalache.tla.typecheck.TypingInputException→at.forsyte.apalache.tla.lir.TypingException
- Direction
- at.forsyte.apalache.tla.typecheck uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.typecheck, while a change to at.forsyte.apalache.tla.typecheck can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.typecheck uses a module listed above it, which is the healthy direction.
20→15 at.forsyte.apalache.tla.typecheck uses at.forsyte.apalache.tla.typecheck.etc✕
- Connections
- 8 pairs of types, where a type in at.forsyte.apalache.tla.typecheck uses a type in at.forsyte.apalache.tla.typecheck.etc.
- The types involved
at.forsyte.apalache.tla.typecheck.DefaultTypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.EtcRefat.forsyte.apalache.tla.typecheck.DefaultTypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.ExactRefat.forsyte.apalache.tla.typecheck.MultiTypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.EtcRefat.forsyte.apalache.tla.typecheck.MultiTypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.ExactRefat.forsyte.apalache.tla.typecheck.TypeChecker→at.forsyte.apalache.tla.typecheck.etc.EtcExprat.forsyte.apalache.tla.typecheck.TypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.EtcRefat.forsyte.apalache.tla.typecheck.TypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.ExactRefat.forsyte.apalache.tla.typecheck.TypeCheckerTool→at.forsyte.apalache.tla.typecheck.etc.TypeAliasSubstitution
- Direction
- at.forsyte.apalache.tla.typecheck uses at.forsyte.apalache.tla.typecheck.etc, so a change to at.forsyte.apalache.tla.typecheck.etc can break at.forsyte.apalache.tla.typecheck, while a change to at.forsyte.apalache.tla.typecheck can't break at.forsyte.apalache.tla.typecheck.etc.
- Position
- Below the diagonal: at.forsyte.apalache.tla.typecheck uses a module listed above it, which is the healthy direction.
21→7 com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.tla.lir✕
- Connections
- 1 pair of types, where a type in com.github.apalachemc.apalache.jsonrpc uses a type in at.forsyte.apalache.tla.lir.
- The types involved
com.github.apalachemc.apalache.jsonrpc.ExplorationService→at.forsyte.apalache.tla.lir.TlaOperDecl
- Direction
- com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break com.github.apalachemc.apalache.jsonrpc, while a change to com.github.apalachemc.apalache.jsonrpc can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: com.github.apalachemc.apalache.jsonrpc uses a module listed above it, which is the healthy direction.
21→9 com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.io.config✕
- Connections
- 4 pairs of types, where a type in com.github.apalachemc.apalache.jsonrpc uses a type in at.forsyte.apalache.io.config.
- The types involved
com.github.apalachemc.apalache.jsonrpc.ExplorationService→at.forsyte.apalache.io.config.ConfigParseResultcom.github.apalachemc.apalache.jsonrpc.ExplorationService→at.forsyte.apalache.io.config.ValidatedCheckOptionscom.github.apalachemc.apalache.jsonrpc.JsonRpcServerApp→at.forsyte.apalache.io.config.ApalacheConfigcom.github.apalachemc.apalache.jsonrpc.JsonRpcServerApp→at.forsyte.apalache.io.config.ConfigParseResult
- Direction
- com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break com.github.apalachemc.apalache.jsonrpc, while a change to com.github.apalachemc.apalache.jsonrpc can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: com.github.apalachemc.apalache.jsonrpc uses a module listed above it, which is the healthy direction.
21→35 com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.tla.bmcmt.trex part of a loop✕
- Connections
- 1 pair of types, where a type in com.github.apalachemc.apalache.jsonrpc uses a type in at.forsyte.apalache.tla.bmcmt.trex.
- The types involved
com.github.apalachemc.apalache.jsonrpc.ExplorationService→at.forsyte.apalache.tla.bmcmt.trex.IncrementalExecutionContextSnapshot
- Direction
- com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.tla.bmcmt.trex, so a change to at.forsyte.apalache.tla.bmcmt.trex can break com.github.apalachemc.apalache.jsonrpc, while a change to com.github.apalachemc.apalache.jsonrpc can't break at.forsyte.apalache.tla.bmcmt.trex.
- 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→36 com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 1 pair of types, where a type in com.github.apalachemc.apalache.jsonrpc uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
com.github.apalachemc.apalache.jsonrpc.ExplorationService→at.forsyte.apalache.tla.bmcmt.ModelCheckerContext
- Direction
- com.github.apalachemc.apalache.jsonrpc uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break com.github.apalachemc.apalache.jsonrpc, while a change to com.github.apalachemc.apalache.jsonrpc can't break at.forsyte.apalache.tla.bmcmt.
- 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→9 at.forsyte.apalache.io uses at.forsyte.apalache.io.config✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.io uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.io.InputSource→at.forsyte.apalache.io.config.ConfigParseResultat.forsyte.apalache.io.OutputManager→at.forsyte.apalache.io.config.CommandInitializationOptionsat.forsyte.apalache.io.OutputManagerState→at.forsyte.apalache.io.config.CommandInitializationOptionsat.forsyte.apalache.io.OutputManagerState→at.forsyte.apalache.io.config.CommonOptions
- Direction
- at.forsyte.apalache.io uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.io, while a change to at.forsyte.apalache.io can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.io uses a module listed above it, which is the healthy direction.
22→17 at.forsyte.apalache.io uses at.forsyte.apalache.io.InputSource✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.io uses a type in at.forsyte.apalache.io.InputSource.
- The types involved
at.forsyte.apalache.io.InputSource→at.forsyte.apalache.io.InputSource.Format
- Direction
- at.forsyte.apalache.io uses at.forsyte.apalache.io.InputSource, so a change to at.forsyte.apalache.io.InputSource can break at.forsyte.apalache.io, while a change to at.forsyte.apalache.io can't break at.forsyte.apalache.io.InputSource.
- Position
- Below the diagonal: at.forsyte.apalache.io uses a module listed above it, which is the healthy direction.
23→7 at.forsyte.apalache.tla.bmcmt.search uses at.forsyte.apalache.tla.lir✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.search uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.search.SearchState→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.search uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.search, while a change to at.forsyte.apalache.tla.bmcmt.search can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.search uses a module listed above it, which is the healthy direction.
23→10 at.forsyte.apalache.tla.bmcmt.search uses at.forsyte.apalache.io.lir✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.search uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.search.SearchState→at.forsyte.apalache.io.lir.Trace
- Direction
- at.forsyte.apalache.tla.bmcmt.search uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.tla.bmcmt.search, while a change to at.forsyte.apalache.tla.bmcmt.search can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.search uses a module listed above it, which is the healthy direction.
23→18 at.forsyte.apalache.tla.bmcmt.search uses at.forsyte.apalache.tla.bmcmt.Checker✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.search uses a type in at.forsyte.apalache.tla.bmcmt.Checker.
- The types involved
at.forsyte.apalache.tla.bmcmt.search.SearchState→at.forsyte.apalache.tla.bmcmt.Checker.CheckerResult
- Direction
- at.forsyte.apalache.tla.bmcmt.search uses at.forsyte.apalache.tla.bmcmt.Checker, so a change to at.forsyte.apalache.tla.bmcmt.Checker can break at.forsyte.apalache.tla.bmcmt.search, while a change to at.forsyte.apalache.tla.bmcmt.search can't break at.forsyte.apalache.tla.bmcmt.Checker.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.search uses a module listed above it, which is the healthy direction.
24→2 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.lir.formulas✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.tla.lir.formulas.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.tla.lir.formulas.Sortat.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.tla.lir.formulas.Termat.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.tla.lir.formulas.Sort
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.lir.formulas, so a change to at.forsyte.apalache.tla.lir.formulas can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.tla.lir.formulas.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.smt uses a module listed above it, which is the healthy direction.
24→7 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.lir✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.smt.SolverContext→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.smt uses a module listed above it, which is the healthy direction.
24→9 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.io.config✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.io.config.SMTEncodingat.forsyte.apalache.tla.bmcmt.smt.SolverConfig→at.forsyte.apalache.io.config.SMTEncodingat.forsyte.apalache.tla.bmcmt.smt.SolverConfig→at.forsyte.apalache.io.config.SMTSolverat.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.io.config.SMTEncoding
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.smt uses a module listed above it, which is the healthy direction.
24→12 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.bmcmt.types✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.tla.bmcmt.types.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.tla.bmcmt.types.CellTat.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.tla.bmcmt.types.CellT
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.bmcmt.types, so a change to at.forsyte.apalache.tla.bmcmt.types can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.tla.bmcmt.types.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.smt uses a module listed above it, which is the healthy direction.
24→19 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.imp✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.tla.imp.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.tla.imp.Context
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.imp, so a change to at.forsyte.apalache.tla.imp can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.tla.imp.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.smt uses a module listed above it, which is the healthy direction.
24→26 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.bmcmt.arena part of a loop✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.tla.bmcmt.arena.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.smt.SolverContext→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.bmcmt.arena, so a change to at.forsyte.apalache.tla.bmcmt.arena can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.tla.bmcmt.arena.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→36 at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.smt uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.smt.Cvc5SolverContext→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.smt.SolverContext→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.smt.SolverContext→at.forsyte.apalache.tla.bmcmt.StackableContextat.forsyte.apalache.tla.bmcmt.smt.Z3SolverContext→at.forsyte.apalache.tla.bmcmt.ArenaCell
- Direction
- at.forsyte.apalache.tla.bmcmt.smt uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.smt, while a change to at.forsyte.apalache.tla.bmcmt.smt can't break at.forsyte.apalache.tla.bmcmt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→7 at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.tla.lir✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.tla.lir.Feature
- Direction
- at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.io.config.ApalacheConfigJsonParser, while a change to at.forsyte.apalache.io.config.ApalacheConfigJsonParser can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a module listed above it, which is the healthy direction.
25→9 at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.io.config✕
- Connections
- 8 pairs of types, where a type in at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.ApalacheConfigat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.CheckerPatchat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.CommonPatchat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.ConfigParseResultat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.RunContextPatchat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.ServerPatchat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.TraceEvaluationPatchat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.config.TypecheckerPatch
- Direction
- at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.io.config.ApalacheConfigJsonParser, while a change to at.forsyte.apalache.io.config.ApalacheConfigJsonParser can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a module listed above it, which is the healthy direction.
25→17 at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.io.InputSource✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a type in at.forsyte.apalache.io.InputSource.
- The types involved
at.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.InputSource.FileSourceat.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.InputSource.Format
- Direction
- at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.io.InputSource, so a change to at.forsyte.apalache.io.InputSource can break at.forsyte.apalache.io.config.ApalacheConfigJsonParser, while a change to at.forsyte.apalache.io.config.ApalacheConfigJsonParser can't break at.forsyte.apalache.io.InputSource.
- Position
- Below the diagonal: at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a module listed above it, which is the healthy direction.
25→22 at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.io✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a type in at.forsyte.apalache.io.
- The types involved
at.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder→at.forsyte.apalache.io.InputSource
- Direction
- at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses at.forsyte.apalache.io, so a change to at.forsyte.apalache.io can break at.forsyte.apalache.io.config.ApalacheConfigJsonParser, while a change to at.forsyte.apalache.io.config.ApalacheConfigJsonParser can't break at.forsyte.apalache.io.
- Position
- Below the diagonal: at.forsyte.apalache.io.config.ApalacheConfigJsonParser uses a module listed above it, which is the healthy direction.
26→7 at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.arena uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.arena, while a change to at.forsyte.apalache.tla.bmcmt.arena can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.arena uses a module listed above it, which is the healthy direction.
26→12 at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.bmcmt.types✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.arena uses a type in at.forsyte.apalache.tla.bmcmt.types.
- The types involved
at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.bmcmt.types.CellT
- Direction
- at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.bmcmt.types, so a change to at.forsyte.apalache.tla.bmcmt.types can break at.forsyte.apalache.tla.bmcmt.arena, while a change to at.forsyte.apalache.tla.bmcmt.arena can't break at.forsyte.apalache.tla.bmcmt.types.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.arena uses a module listed above it, which is the healthy direction.
26→24 at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.arena uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.bmcmt.smt.SolverContext
- Direction
- at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt.arena, while a change to at.forsyte.apalache.tla.bmcmt.arena can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.arena uses a module listed above it, which is the healthy direction.
26→36 at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.arena uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.arena.PtrUtil→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.arena.PtrUtil→at.forsyte.apalache.tla.bmcmt.ElemPtrat.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.bmcmt.ElemPtrat.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter→at.forsyte.apalache.tla.bmcmt.PureArena
- Direction
- at.forsyte.apalache.tla.bmcmt.arena uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.arena, while a change to at.forsyte.apalache.tla.bmcmt.arena can't break at.forsyte.apalache.tla.bmcmt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→7 at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.imp uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.passes.imp.PassWithOutputs→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.imp.SanyParserPassImpl→at.forsyte.apalache.tla.lir.TlaModule
- Direction
- at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.passes.imp, while a change to at.forsyte.apalache.tla.passes.imp can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.imp uses a module listed above it, which is the healthy direction.
27→8 at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.infra.passes✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.imp uses a type in at.forsyte.apalache.infra.passes.
- The types involved
at.forsyte.apalache.tla.passes.imp.ParserModule→at.forsyte.apalache.infra.passes.ToolModuleat.forsyte.apalache.tla.passes.imp.PassWithOutputs→at.forsyte.apalache.infra.passes.Pass
- Direction
- at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.infra.passes, so a change to at.forsyte.apalache.infra.passes can break at.forsyte.apalache.tla.passes.imp, while a change to at.forsyte.apalache.tla.passes.imp can't break at.forsyte.apalache.infra.passes.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.imp uses a module listed above it, which is the healthy direction.
27→9 at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.io.config✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.imp uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl→at.forsyte.apalache.io.config.CommonOptionsat.forsyte.apalache.tla.passes.imp.SanyParserPassImpl→at.forsyte.apalache.io.config.ModuleIoOptions
- Direction
- at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.tla.passes.imp, while a change to at.forsyte.apalache.tla.passes.imp can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.imp uses a module listed above it, which is the healthy direction.
27→10 at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.io.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.imp uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.tla.passes.imp.PassWithOutputs→at.forsyte.apalache.io.lir.TlaWriterFactoryat.forsyte.apalache.tla.passes.imp.SanyParserPassImpl→at.forsyte.apalache.io.lir.TlaWriterFactory
- Direction
- at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.tla.passes.imp, while a change to at.forsyte.apalache.tla.passes.imp can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.imp uses a module listed above it, which is the healthy direction.
27→13 at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.tla.lir.src✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.imp uses a type in at.forsyte.apalache.tla.lir.src.
- The types involved
at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl→at.forsyte.apalache.tla.lir.src.SourceStore
- Direction
- at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.tla.lir.src, so a change to at.forsyte.apalache.tla.lir.src can break at.forsyte.apalache.tla.passes.imp, while a change to at.forsyte.apalache.tla.passes.imp can't break at.forsyte.apalache.tla.lir.src.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.imp uses a module listed above it, which is the healthy direction.
27→22 at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.io✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.imp uses a type in at.forsyte.apalache.io.
- The types involved
at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl→at.forsyte.apalache.io.InputSource
- Direction
- at.forsyte.apalache.tla.passes.imp uses at.forsyte.apalache.io, so a change to at.forsyte.apalache.io can break at.forsyte.apalache.tla.passes.imp, while a change to at.forsyte.apalache.tla.passes.imp can't break at.forsyte.apalache.io.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.imp uses a module listed above it, which is the healthy direction.
28→1 at.forsyte.apalache.tla.tracee uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.tracee uses a type in at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- The types involved
at.forsyte.apalache.tla.tracee.DrivenTransitionConstructor→at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.State
- Direction
- at.forsyte.apalache.tla.tracee uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor, so a change to at.forsyte.apalache.io.annotations.parser.CommentPreprocessor can break at.forsyte.apalache.tla.tracee, while a change to at.forsyte.apalache.tla.tracee can't break at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- Position
- Below the diagonal: at.forsyte.apalache.tla.tracee uses a module listed above it, which is the healthy direction.
28→7 at.forsyte.apalache.tla.tracee uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.tracee uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.tracee.DrivenTransitionConstructor→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.tracee.UJsonTraceReader→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.tracee uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.tracee, while a change to at.forsyte.apalache.tla.tracee can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.tracee uses a module listed above it, which is the healthy direction.
28→22 at.forsyte.apalache.tla.tracee uses at.forsyte.apalache.io✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.tracee uses a type in at.forsyte.apalache.io.
- The types involved
at.forsyte.apalache.tla.tracee.TraceReader→at.forsyte.apalache.io.InputSourceat.forsyte.apalache.tla.tracee.UJsonTraceReader→at.forsyte.apalache.io.InputSource
- Direction
- at.forsyte.apalache.tla.tracee uses at.forsyte.apalache.io, so a change to at.forsyte.apalache.io can break at.forsyte.apalache.tla.tracee, while a change to at.forsyte.apalache.tla.tracee can't break at.forsyte.apalache.io.
- Position
- Below the diagonal: at.forsyte.apalache.tla.tracee uses a module listed above it, which is the healthy direction.
29→7 at.forsyte.apalache.io.json uses at.forsyte.apalache.tla.lir✕
- Connections
- 27 pairs of types, where a type in at.forsyte.apalache.io.json uses a type in at.forsyte.apalache.tla.lir. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
at.forsyte.apalache.io.json.DefaultTagJsonReader→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.io.json.JsonDecoder→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.json.JsonDecoder→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.json.JsonDecoder→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.json.JsonEncoder→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.json.JsonEncoder→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.json.JsonEncoder→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.json.JsonTlaWriter→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.json.JsonTlaWriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.json.JsonTlaWriter→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.tla.lir.Identifiableat.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.tla.lir.OperParamat.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.tla.lir.TlaValueat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.Identifiableat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.OperParamat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.TypeTagat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.tla.lir.TypeTaggedat.forsyte.apalache.io.json.TlaToJson→at.forsyte.apalache.tla.lir.Identifiableat.forsyte.apalache.io.json.TlaToJson→at.forsyte.apalache.tla.lir.TlaDecl
- Direction
- at.forsyte.apalache.io.json uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.io.json, while a change to at.forsyte.apalache.io.json can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.io.json uses a module listed above it, which is the healthy direction.
29→10 at.forsyte.apalache.io.json uses at.forsyte.apalache.io.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.json uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.io.json.DefaultTagJsonReader→at.forsyte.apalache.io.lir.TypeTagReaderat.forsyte.apalache.io.json.JsonTlaWriter→at.forsyte.apalache.io.lir.TlaWriter
- Direction
- at.forsyte.apalache.io.json uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.io.json, while a change to at.forsyte.apalache.io.json can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.io.json uses a module listed above it, which is the healthy direction.
29→25 at.forsyte.apalache.io.json uses at.forsyte.apalache.io.config.ApalacheConfigJsonParser✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.io.json uses a type in at.forsyte.apalache.io.config.ApalacheConfigJsonParser.
- The types involved
at.forsyte.apalache.io.json.JsonToTla→at.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoderat.forsyte.apalache.io.json.JsonToTlaViaBuilder→at.forsyte.apalache.io.config.ApalacheConfigJsonParser.JsonDecoder
- Direction
- at.forsyte.apalache.io.json uses at.forsyte.apalache.io.config.ApalacheConfigJsonParser, so a change to at.forsyte.apalache.io.config.ApalacheConfigJsonParser can break at.forsyte.apalache.io.json, while a change to at.forsyte.apalache.io.json can't break at.forsyte.apalache.io.config.ApalacheConfigJsonParser.
- Position
- Below the diagonal: at.forsyte.apalache.io.json uses a module listed above it, which is the healthy direction.
30→7 at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.lir✕
- Connections
- 6 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rewriter uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.rewriter.ConstSimplifierForSmt→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rewriter.MetricProfilerListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rewriter.MetricProfilerListener→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.rewriter, while a change to at.forsyte.apalache.tla.bmcmt.rewriter can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rewriter uses a module listed above it, which is the healthy direction.
30→24 at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rewriter uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.rewriter.MetricProfilerListener→at.forsyte.apalache.tla.bmcmt.smt.SolverContextMetricsat.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterListener→at.forsyte.apalache.tla.bmcmt.smt.SolverContextMetrics
- Direction
- at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt.rewriter, while a change to at.forsyte.apalache.tla.bmcmt.rewriter can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rewriter uses a module listed above it, which is the healthy direction.
30→26 at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt.arena✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.rewriter uses a type in at.forsyte.apalache.tla.bmcmt.arena.
- The types involved
at.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter
- Direction
- at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt.arena, so a change to at.forsyte.apalache.tla.bmcmt.arena can break at.forsyte.apalache.tla.bmcmt.rewriter, while a change to at.forsyte.apalache.tla.bmcmt.rewriter can't break at.forsyte.apalache.tla.bmcmt.arena.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rewriter uses a module listed above it, which is the healthy direction.
30→34 at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt.caches part of a loop✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rewriter uses a type in at.forsyte.apalache.tla.bmcmt.caches.
- The types involved
at.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot→at.forsyte.apalache.tla.bmcmt.caches.AbstractCacheSnapshotat.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot→at.forsyte.apalache.tla.bmcmt.caches.SimpleCacheSnapshot
- Direction
- at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt.caches, so a change to at.forsyte.apalache.tla.bmcmt.caches can break at.forsyte.apalache.tla.bmcmt.rewriter, while a change to at.forsyte.apalache.tla.bmcmt.rewriter can't break at.forsyte.apalache.tla.bmcmt.caches.
- 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→36 at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.rewriter uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot→at.forsyte.apalache.tla.bmcmt.ArenaCell
- Direction
- at.forsyte.apalache.tla.bmcmt.rewriter uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.rewriter, while a change to at.forsyte.apalache.tla.bmcmt.rewriter can't break at.forsyte.apalache.tla.bmcmt.
- 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→7 at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.lir✕
- Connections
- 15 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules.support uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.lir.FunT1at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.lir.RecT1at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.lir.SeqT1at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.lir.SetT1at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.lir.TupT1at.forsyte.apalache.tla.bmcmt.rules.support.DefaultValueFactory→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.support.MapBase→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.support.ProtoSeqOps→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.support.ProtoSeqOps→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.support.RecordAndVariantOps→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.support.ValueGenerator→at.forsyte.apalache.tla.lir.FunT1at.forsyte.apalache.tla.bmcmt.rules.support.ValueGenerator→at.forsyte.apalache.tla.lir.RecT1at.forsyte.apalache.tla.bmcmt.rules.support.ValueGenerator→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.support.ValueGenerator→at.forsyte.apalache.tla.lir.TupT1
- Direction
- at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.rules.support, while a change to at.forsyte.apalache.tla.bmcmt.rules.support can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules.support uses a module listed above it, which is the healthy direction.
31→12 at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt.types✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.rules.support uses a type in at.forsyte.apalache.tla.bmcmt.types.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.bmcmt.types.CellT
- Direction
- at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt.types, so a change to at.forsyte.apalache.tla.bmcmt.types can break at.forsyte.apalache.tla.bmcmt.rules.support, while a change to at.forsyte.apalache.tla.bmcmt.rules.support can't break at.forsyte.apalache.tla.bmcmt.types.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules.support uses a module listed above it, which is the healthy direction.
31→24 at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 7 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules.support uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.support.IntOracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.rules.support.MockOracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.rules.support.Oracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.rules.support.PropositionalOracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.rules.support.SparseOracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.rules.support.UninterpretedConstOracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.rules.support.ZipOracle→at.forsyte.apalache.tla.bmcmt.smt.SolverContext
- Direction
- at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt.rules.support, while a change to at.forsyte.apalache.tla.bmcmt.rules.support can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules.support uses a module listed above it, which is the healthy direction.
31→26 at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt.arena✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules.support uses a type in at.forsyte.apalache.tla.bmcmt.arena.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.support.DefaultValueFactory→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.rules.support.ProtoSeqOps→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.rules.support.RecordAndVariantOps→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter
- Direction
- at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt.arena, so a change to at.forsyte.apalache.tla.bmcmt.arena can break at.forsyte.apalache.tla.bmcmt.rules.support, while a change to at.forsyte.apalache.tla.bmcmt.rules.support can't break at.forsyte.apalache.tla.bmcmt.arena.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules.support uses a module listed above it, which is the healthy direction.
31→36 at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 29 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules.support uses a type in at.forsyte.apalache.tla.bmcmt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.CherryPick→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.IntOracle→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.IntOracle→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.MapBase→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.MapBase→at.forsyte.apalache.tla.bmcmt.ElemPtrat.forsyte.apalache.tla.bmcmt.rules.support.MapBase→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.MockOracle→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.Oracle→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.OracleFactory→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.OracleHelper→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.OracleHelper→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.OracleHelper→at.forsyte.apalache.tla.bmcmt.SymbStateRewriterat.forsyte.apalache.tla.bmcmt.rules.support.PowSetCtor→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.PowSetCtor→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.PropositionalOracle→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.ProtoSeqOps→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.ProtoSeqOps→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.RecordAndVariantOps→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.RecordAndVariantOps→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.SetOps→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.SetOps→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.SparseOracle→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.support.SupportOps→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.support.SupportOps→at.forsyte.apalache.tla.bmcmt.SymbState
- Direction
- at.forsyte.apalache.tla.bmcmt.rules.support uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.rules.support, while a change to at.forsyte.apalache.tla.bmcmt.rules.support can't break at.forsyte.apalache.tla.bmcmt.
- 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.
32→5 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.lir.transformations✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.tla.lir.transformations.
- The types involved
at.forsyte.apalache.tla.passes.pp.PreproPassPartial→at.forsyte.apalache.tla.lir.transformations.LanguagePredat.forsyte.apalache.tla.passes.pp.WatchdogPassImpl→at.forsyte.apalache.tla.lir.transformations.LanguagePred
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.lir.transformations, so a change to at.forsyte.apalache.tla.lir.transformations can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.tla.lir.transformations.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
32→6 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.io.tlc.config✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.io.tlc.config.
- The types involved
at.forsyte.apalache.tla.passes.pp.ConfigurationPassImpl→at.forsyte.apalache.io.tlc.config.TlcConfig
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.io.tlc.config, so a change to at.forsyte.apalache.io.tlc.config can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.io.tlc.config.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
32→7 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.lir✕
- Connections
- 11 pairs of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.passes.pp.ConfigurationPassImpl→at.forsyte.apalache.tla.lir.TlaDeclat.forsyte.apalache.tla.passes.pp.ConfigurationPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.DesugarerPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.InlinePassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.OptPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.PreproPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.PreproPassPartial→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.PreproPassPartial→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.passes.pp.ReTLAPreproPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.TemporalPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.pp.WatchdogPassImpl→at.forsyte.apalache.tla.lir.TlaModule
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
32→8 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.infra.passes✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.infra.passes.
- The types involved
at.forsyte.apalache.tla.passes.pp.WatchdogPass→at.forsyte.apalache.infra.passes.Pass
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.infra.passes, so a change to at.forsyte.apalache.infra.passes can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.infra.passes.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
32→9 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.io.config✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.tla.passes.pp.ConfigurationPassImpl→at.forsyte.apalache.io.config.SpecificationOptionsat.forsyte.apalache.tla.passes.pp.PreproPassPartial→at.forsyte.apalache.io.config.CommonOptions
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
32→14 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.lir.transformations.standard✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.tla.lir.transformations.standard.
- The types involved
at.forsyte.apalache.tla.passes.pp.PreproPassPartial→at.forsyte.apalache.tla.lir.transformations.standard.ModuleByExTransformer
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.lir.transformations.standard, so a change to at.forsyte.apalache.tla.lir.transformations.standard can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.tla.lir.transformations.standard.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
32→27 at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.passes.imp✕
- Connections
- 6 pairs of types, where a type in at.forsyte.apalache.tla.passes.pp uses a type in at.forsyte.apalache.tla.passes.imp.
- The types involved
at.forsyte.apalache.tla.passes.pp.ConfigurationPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputsat.forsyte.apalache.tla.passes.pp.DesugarerPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputsat.forsyte.apalache.tla.passes.pp.InlinePass→at.forsyte.apalache.tla.passes.imp.PassWithOutputsat.forsyte.apalache.tla.passes.pp.OptPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputsat.forsyte.apalache.tla.passes.pp.PreproPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputsat.forsyte.apalache.tla.passes.pp.TemporalPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputs
- Direction
- at.forsyte.apalache.tla.passes.pp uses at.forsyte.apalache.tla.passes.imp, so a change to at.forsyte.apalache.tla.passes.imp can break at.forsyte.apalache.tla.passes.pp, while a change to at.forsyte.apalache.tla.passes.pp can't break at.forsyte.apalache.tla.passes.imp.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.pp uses a module listed above it, which is the healthy direction.
33→7 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.lir✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerAdapter→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.tla.lir.UIDat.forsyte.apalache.tla.passes.typecheck.LoggingTypeCheckerListener→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→8 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.infra.passes✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.infra.passes.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.TypeCheckerModule→at.forsyte.apalache.infra.passes.ToolModule
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.infra.passes, so a change to at.forsyte.apalache.infra.passes can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.infra.passes.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→9 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.io.config✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.io.config.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.io.config.CommonOptionsat.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.io.config.ModuleIoOptionsat.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.io.config.TypecheckerOptions
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.io.config, so a change to at.forsyte.apalache.io.config can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.io.config.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→10 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.io.lir✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.io.lir.TlaWriterFactory
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→13 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.lir.src✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.tla.lir.src.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPassImpl→at.forsyte.apalache.tla.lir.src.SourceStore
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.lir.src, so a change to at.forsyte.apalache.tla.lir.src can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.tla.lir.src.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→15 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.typecheck.etc✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.tla.typecheck.etc.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.LoggingTypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.EtcRefat.forsyte.apalache.tla.passes.typecheck.LoggingTypeCheckerListener→at.forsyte.apalache.tla.typecheck.etc.ExactRef
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.typecheck.etc, so a change to at.forsyte.apalache.tla.typecheck.etc can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.tla.typecheck.etc.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→20 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.typecheck✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.tla.typecheck.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.LoggingTypeCheckerListener→at.forsyte.apalache.tla.typecheck.SourceAwareTypeCheckerListener
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.typecheck, so a change to at.forsyte.apalache.tla.typecheck can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.tla.typecheck.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
33→27 at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.passes.imp✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.passes.typecheck uses a type in at.forsyte.apalache.tla.passes.imp.
- The types involved
at.forsyte.apalache.tla.passes.typecheck.EtcTypeCheckerPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputs
- Direction
- at.forsyte.apalache.tla.passes.typecheck uses at.forsyte.apalache.tla.passes.imp, so a change to at.forsyte.apalache.tla.passes.imp can break at.forsyte.apalache.tla.passes.typecheck, while a change to at.forsyte.apalache.tla.passes.typecheck can't break at.forsyte.apalache.tla.passes.imp.
- Position
- Below the diagonal: at.forsyte.apalache.tla.passes.typecheck uses a module listed above it, which is the healthy direction.
34→7 at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.lir✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.caches uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.caches.DefaultValueCache→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.caches.ExprCache→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.caches, while a change to at.forsyte.apalache.tla.bmcmt.caches can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.caches uses a module listed above it, which is the healthy direction.
34→26 at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.bmcmt.arena✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.caches uses a type in at.forsyte.apalache.tla.bmcmt.arena.
- The types involved
at.forsyte.apalache.tla.bmcmt.caches.DefaultValueCache→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.caches.IntRangeCache→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.caches.IntValueCache→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.caches.ModelValueCache→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.caches.RecordDomainCache→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter
- Direction
- at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.bmcmt.arena, so a change to at.forsyte.apalache.tla.bmcmt.arena can break at.forsyte.apalache.tla.bmcmt.caches, while a change to at.forsyte.apalache.tla.bmcmt.caches can't break at.forsyte.apalache.tla.bmcmt.arena.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.caches uses a module listed above it, which is the healthy direction.
34→30 at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.bmcmt.rewriter✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.caches uses a type in at.forsyte.apalache.tla.bmcmt.rewriter.
- The types involved
at.forsyte.apalache.tla.bmcmt.caches.AbstractCache→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverableat.forsyte.apalache.tla.bmcmt.caches.SimpleCache→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverable
- Direction
- at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.bmcmt.rewriter, so a change to at.forsyte.apalache.tla.bmcmt.rewriter can break at.forsyte.apalache.tla.bmcmt.caches, while a change to at.forsyte.apalache.tla.bmcmt.caches can't break at.forsyte.apalache.tla.bmcmt.rewriter.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.caches uses a module listed above it, which is the healthy direction.
34→36 at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.caches uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.caches.AbstractCache→at.forsyte.apalache.tla.bmcmt.StackableContextat.forsyte.apalache.tla.bmcmt.caches.SimpleCache→at.forsyte.apalache.tla.bmcmt.StackableContext
- Direction
- at.forsyte.apalache.tla.bmcmt.caches uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.caches, while a change to at.forsyte.apalache.tla.bmcmt.caches can't break at.forsyte.apalache.tla.bmcmt.
- 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.
35→7 at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.lir✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.ConstrainedTransitionExecutor→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.trex.DecodedState→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.trex.FilteredTransitionExecutor→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutor→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutorImpl→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.trex uses a module listed above it, which is the healthy direction.
35→21 at.forsyte.apalache.tla.bmcmt.trex uses com.github.apalachemc.apalache.jsonrpc✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in com.github.apalachemc.apalache.jsonrpc.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.ConstrainedTransitionExecutor→com.github.apalachemc.apalache.jsonrpc.InvariantKindat.forsyte.apalache.tla.bmcmt.trex.FilteredTransitionExecutor→com.github.apalachemc.apalache.jsonrpc.InvariantKindat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutor→com.github.apalachemc.apalache.jsonrpc.InvariantKindat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutorImpl→com.github.apalachemc.apalache.jsonrpc.InvariantKind
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses com.github.apalachemc.apalache.jsonrpc, so a change to com.github.apalachemc.apalache.jsonrpc can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break com.github.apalachemc.apalache.jsonrpc.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.trex uses a module listed above it, which is the healthy direction.
35→24 at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.ExecutionContext→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.trex.OfflineExecutionContextSnapshot→at.forsyte.apalache.tla.bmcmt.smt.SmtLogat.forsyte.apalache.tla.bmcmt.trex.OfflineExecutionContextSnapshot→at.forsyte.apalache.tla.bmcmt.smt.SolverConfig
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.trex uses a module listed above it, which is the healthy direction.
35→26 at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.arena✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in at.forsyte.apalache.tla.bmcmt.arena.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.EncodedExecution→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.arena, so a change to at.forsyte.apalache.tla.bmcmt.arena can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break at.forsyte.apalache.tla.bmcmt.arena.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.trex uses a module listed above it, which is the healthy direction.
35→30 at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.rewriter✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in at.forsyte.apalache.tla.bmcmt.rewriter.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.ExecutionContext→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverableat.forsyte.apalache.tla.bmcmt.trex.OfflineExecutionContextSnapshot→at.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshotat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutor→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverable
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.rewriter, so a change to at.forsyte.apalache.tla.bmcmt.rewriter can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break at.forsyte.apalache.tla.bmcmt.rewriter.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.trex uses a module listed above it, which is the healthy direction.
35→31 at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.rules.support✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in at.forsyte.apalache.tla.bmcmt.rules.support.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.ConstrainedTransitionExecutor→at.forsyte.apalache.tla.bmcmt.rules.support.Oracleat.forsyte.apalache.tla.bmcmt.trex.FilteredTransitionExecutor→at.forsyte.apalache.tla.bmcmt.rules.support.Oracleat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutor→at.forsyte.apalache.tla.bmcmt.rules.support.Oracleat.forsyte.apalache.tla.bmcmt.trex.TransitionExecutorImpl→at.forsyte.apalache.tla.bmcmt.rules.support.Oracle
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt.rules.support, so a change to at.forsyte.apalache.tla.bmcmt.rules.support can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break at.forsyte.apalache.tla.bmcmt.rules.support.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.trex uses a module listed above it, which is the healthy direction.
35→36 at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt part of a loop✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.trex uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.trex.EncodedTransition→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.trex.EncodedTransition→at.forsyte.apalache.tla.bmcmt.Bindingat.forsyte.apalache.tla.bmcmt.trex.ExecutionContext→at.forsyte.apalache.tla.bmcmt.SymbStateRewriterat.forsyte.apalache.tla.bmcmt.trex.IncrementalExecutionContext→at.forsyte.apalache.tla.bmcmt.SymbStateRewriterat.forsyte.apalache.tla.bmcmt.trex.OfflineExecutionContext→at.forsyte.apalache.tla.bmcmt.SymbStateRewriter
- Direction
- at.forsyte.apalache.tla.bmcmt.trex uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.trex, while a change to at.forsyte.apalache.tla.bmcmt.trex can't break at.forsyte.apalache.tla.bmcmt.
- 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.
36→7 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.lir✕
- Connections
- 27 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.lir. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
at.forsyte.apalache.tla.bmcmt.CheckerException→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.CheckerInput→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.CheckerInput→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.bmcmt.CheckerInput→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.bmcmt.CheckerInputVC→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.CollectCounterexamplesModelCheckerListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.DumpFilesModelCheckerListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.LazyEquality→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.LazyEquality→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.ModelCheckerListener→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.PureArena→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.SeqModelChecker→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.SeqModelChecker→at.forsyte.apalache.tla.lir.TlaOperDeclat.forsyte.apalache.tla.bmcmt.SymbState→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.SymbStateDecoder→at.forsyte.apalache.tla.lir.RecT1at.forsyte.apalache.tla.bmcmt.SymbStateDecoder→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.SymbStateDecoder→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.Theory→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.VCGenerator→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.VCGenerator→at.forsyte.apalache.tla.lir.TlaLevelat.forsyte.apalache.tla.bmcmt.VCGenerator→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.bmcmt.VCGenerator→at.forsyte.apalache.tla.lir.TlaOperDecl
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→10 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.io.lir✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.io.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.CollectCounterexamplesModelCheckerListener→at.forsyte.apalache.io.lir.Traceat.forsyte.apalache.tla.bmcmt.DumpFilesModelCheckerListener→at.forsyte.apalache.io.lir.Traceat.forsyte.apalache.tla.bmcmt.ModelCheckerListener→at.forsyte.apalache.io.lir.Traceat.forsyte.apalache.tla.bmcmt.SeqModelChecker→at.forsyte.apalache.io.lir.Trace
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.io.lir, so a change to at.forsyte.apalache.io.lir can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.io.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→12 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.types✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.types.
- The types involved
at.forsyte.apalache.tla.bmcmt.PureArena→at.forsyte.apalache.tla.bmcmt.types.CellTat.forsyte.apalache.tla.bmcmt.stratifiedRules→at.forsyte.apalache.tla.bmcmt.types.CellT
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.types, so a change to at.forsyte.apalache.tla.bmcmt.types can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.types.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→14 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.lir.transformations.standard✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.lir.transformations.standard.
- The types involved
at.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.lir.transformations.standard.IncrementalRenaming
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.lir.transformations.standard, so a change to at.forsyte.apalache.tla.lir.transformations.standard can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.lir.transformations.standard.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→18 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.Checker✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.Checker.
- The types involved
at.forsyte.apalache.tla.bmcmt.SeqModelChecker→at.forsyte.apalache.tla.bmcmt.Checker.CheckerResult
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.Checker, so a change to at.forsyte.apalache.tla.bmcmt.Checker can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.Checker.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→21 at.forsyte.apalache.tla.bmcmt uses com.github.apalachemc.apalache.jsonrpc✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in com.github.apalachemc.apalache.jsonrpc.
- The types involved
at.forsyte.apalache.tla.bmcmt.ActionInvariant→com.github.apalachemc.apalache.jsonrpc.InvariantKindat.forsyte.apalache.tla.bmcmt.SeqModelChecker→com.github.apalachemc.apalache.jsonrpc.InvariantKindat.forsyte.apalache.tla.bmcmt.StateInvariant→com.github.apalachemc.apalache.jsonrpc.InvariantKind
- Direction
- at.forsyte.apalache.tla.bmcmt uses com.github.apalachemc.apalache.jsonrpc, so a change to com.github.apalachemc.apalache.jsonrpc can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break com.github.apalachemc.apalache.jsonrpc.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→23 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.search✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.search.
- The types involved
at.forsyte.apalache.tla.bmcmt.ModelCheckerContext→at.forsyte.apalache.tla.bmcmt.search.ModelCheckerParamsat.forsyte.apalache.tla.bmcmt.SeqModelChecker→at.forsyte.apalache.tla.bmcmt.search.SearchState
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.search, so a change to at.forsyte.apalache.tla.bmcmt.search can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.search.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→24 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 5 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.Arena→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.RewritingRule→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.bmcmt.smt.SolverContext
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→26 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.arena✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.arena.
- The types involved
at.forsyte.apalache.tla.bmcmt.SymbState→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapterat.forsyte.apalache.tla.bmcmt.SymbStateDecoder→at.forsyte.apalache.tla.bmcmt.arena.PureArenaAdapter
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.arena, so a change to at.forsyte.apalache.tla.bmcmt.arena can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.arena.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→30 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.rewriter✕
- Connections
- 9 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.rewriter.
- The types involved
at.forsyte.apalache.tla.bmcmt.LazyEquality→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverableat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverableat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.rewriter.RewriterConfigat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.rewriter.RewriterConfigat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshotat.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.bmcmt.rewriter.MetricProfilerListenerat.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.bmcmt.rewriter.Recoverableat.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.bmcmt.rewriter.RewriterConfigat.forsyte.apalache.tla.bmcmt.SymbStateRewriterImpl→at.forsyte.apalache.tla.bmcmt.rewriter.SymbStateRewriterSnapshot
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.rewriter, so a change to at.forsyte.apalache.tla.bmcmt.rewriter can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.rewriter.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→34 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.caches✕
- Connections
- 11 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.caches.
- The types involved
at.forsyte.apalache.tla.bmcmt.LazyEquality→at.forsyte.apalache.tla.bmcmt.caches.EqCacheSnapshotat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.caches.DefaultValueCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.caches.ExprCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.caches.IntValueCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.caches.ModelValueCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriter→at.forsyte.apalache.tla.bmcmt.caches.RecordDomainCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.caches.DefaultValueCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.caches.ExprCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.caches.IntValueCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.caches.ModelValueCacheat.forsyte.apalache.tla.bmcmt.SymbStateRewriterAuto→at.forsyte.apalache.tla.bmcmt.caches.RecordDomainCache
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.caches, so a change to at.forsyte.apalache.tla.bmcmt.caches can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.caches.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
36→35 at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.trex✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt uses a type in at.forsyte.apalache.tla.bmcmt.trex.
- The types involved
at.forsyte.apalache.tla.bmcmt.ModelCheckerContext→at.forsyte.apalache.tla.bmcmt.trex.TransitionExecutorat.forsyte.apalache.tla.bmcmt.SeqModelChecker→at.forsyte.apalache.tla.bmcmt.trex.ConstrainedTransitionExecutor
- Direction
- at.forsyte.apalache.tla.bmcmt uses at.forsyte.apalache.tla.bmcmt.trex, so a change to at.forsyte.apalache.tla.bmcmt.trex can break at.forsyte.apalache.tla.bmcmt, while a change to at.forsyte.apalache.tla.bmcmt can't break at.forsyte.apalache.tla.bmcmt.trex.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt uses a module listed above it, which is the healthy direction.
37→7 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.lir✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.AnalysisPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.bmcmt.passes.ReTLAToVMTTranspilePassImpl→at.forsyte.apalache.tla.lir.TlaModuleat.forsyte.apalache.tla.bmcmt.passes.VCGenPassImpl→at.forsyte.apalache.tla.lir.TlaModule
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→8 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.infra.passes✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.infra.passes.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPass→at.forsyte.apalache.infra.passes.Passat.forsyte.apalache.tla.bmcmt.passes.TranspilePass→at.forsyte.apalache.infra.passes.Pass
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.infra.passes, so a change to at.forsyte.apalache.infra.passes can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.infra.passes.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→18 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.Checker✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.bmcmt.Checker.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.bmcmt.Checker.CheckerResult
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.Checker, so a change to at.forsyte.apalache.tla.bmcmt.Checker can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.bmcmt.Checker.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→23 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.search✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.bmcmt.search.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.bmcmt.search.ModelCheckerParams
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.search, so a change to at.forsyte.apalache.tla.bmcmt.search can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.bmcmt.search.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→24 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.bmcmt.smt.SolverConfig
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→27 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.passes.imp✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.passes.imp.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.AnalysisPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputsat.forsyte.apalache.tla.bmcmt.passes.VCGenPass→at.forsyte.apalache.tla.passes.imp.PassWithOutputs
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.passes.imp, so a change to at.forsyte.apalache.tla.passes.imp can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.passes.imp.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→35 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.trex✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.bmcmt.trex.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.bmcmt.trex.IncrementalExecutionContextSnapshot
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt.trex, so a change to at.forsyte.apalache.tla.bmcmt.trex can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.bmcmt.trex.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
37→36 at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.passes uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.bmcmt.CheckerInputat.forsyte.apalache.tla.bmcmt.passes.BoundedCheckerPassImpl→at.forsyte.apalache.tla.bmcmt.ModelCheckerContext
- Direction
- at.forsyte.apalache.tla.bmcmt.passes uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.passes, while a change to at.forsyte.apalache.tla.bmcmt.passes can't break at.forsyte.apalache.tla.bmcmt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.passes uses a module listed above it, which is the healthy direction.
38→1 at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.rules uses a type in at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.vmt→at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.State
- Direction
- at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.io.annotations.parser.CommentPreprocessor, so a change to at.forsyte.apalache.io.annotations.parser.CommentPreprocessor can break at.forsyte.apalache.tla.bmcmt.rules, while a change to at.forsyte.apalache.tla.bmcmt.rules can't break at.forsyte.apalache.io.annotations.parser.CommentPreprocessor.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules uses a module listed above it, which is the healthy direction.
38→2 at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.lir.formulas✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules uses a type in at.forsyte.apalache.tla.lir.formulas.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.vmt→at.forsyte.apalache.tla.lir.formulas.Sortat.forsyte.apalache.tla.bmcmt.rules.vmt→at.forsyte.apalache.tla.lir.formulas.Termat.forsyte.apalache.tla.bmcmt.rules.vmt→at.forsyte.apalache.tla.lir.formulas.Variable
- Direction
- at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.lir.formulas, so a change to at.forsyte.apalache.tla.lir.formulas can break at.forsyte.apalache.tla.bmcmt.rules, while a change to at.forsyte.apalache.tla.bmcmt.rules can't break at.forsyte.apalache.tla.lir.formulas.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules uses a module listed above it, which is the healthy direction.
38→7 at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.lir✕
- Connections
- 26 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules uses a type in at.forsyte.apalache.tla.lir. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.ChooseOrGuessRule→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.DomainRule→at.forsyte.apalache.tla.lir.TupT1at.forsyte.apalache.tla.bmcmt.rules.FunAppRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.FunAppRule→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.FunAppRuleWithArrays→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.FunCtorRule→at.forsyte.apalache.tla.lir.FunT1at.forsyte.apalache.tla.bmcmt.rules.FunCtorRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.FunCtorRuleWithArrays→at.forsyte.apalache.tla.lir.FunT1at.forsyte.apalache.tla.bmcmt.rules.FunCtorRuleWithArrays→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.FunExceptRule→at.forsyte.apalache.tla.lir.RecT1at.forsyte.apalache.tla.bmcmt.rules.FunExceptRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.FunExceptRule→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.FunExceptRule→at.forsyte.apalache.tla.lir.TupT1at.forsyte.apalache.tla.bmcmt.rules.FunSetCtorRule→at.forsyte.apalache.tla.lir.FunT1at.forsyte.apalache.tla.bmcmt.rules.IntDotDotRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.QuantRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.QuantRule→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.RecCtorRule→at.forsyte.apalache.tla.lir.RecT1at.forsyte.apalache.tla.bmcmt.rules.RecCtorRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.SeqOpsRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.SeqOpsRule→at.forsyte.apalache.tla.lir.TlaType1at.forsyte.apalache.tla.bmcmt.rules.TupleOrSeqCtorRule→at.forsyte.apalache.tla.lir.SeqT1at.forsyte.apalache.tla.bmcmt.rules.TupleOrSeqCtorRule→at.forsyte.apalache.tla.lir.TupT1at.forsyte.apalache.tla.bmcmt.rules.VariantOpsRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.rules.VariantOpsRule→at.forsyte.apalache.tla.lir.TlaType1
- Direction
- at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.rules, while a change to at.forsyte.apalache.tla.bmcmt.rules can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules uses a module listed above it, which is the healthy direction.
38→12 at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.bmcmt.types✕
- Connections
- 4 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules uses a type in at.forsyte.apalache.tla.bmcmt.types.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.FunAppRule→at.forsyte.apalache.tla.bmcmt.types.CellTat.forsyte.apalache.tla.bmcmt.rules.IfThenElseRule→at.forsyte.apalache.tla.bmcmt.types.CellTat.forsyte.apalache.tla.bmcmt.rules.SetInRule→at.forsyte.apalache.tla.bmcmt.types.CellTat.forsyte.apalache.tla.bmcmt.rules.SetInRuleWithArrays→at.forsyte.apalache.tla.bmcmt.types.CellT
- Direction
- at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.bmcmt.types, so a change to at.forsyte.apalache.tla.bmcmt.types can break at.forsyte.apalache.tla.bmcmt.rules, while a change to at.forsyte.apalache.tla.bmcmt.rules can't break at.forsyte.apalache.tla.bmcmt.types.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules uses a module listed above it, which is the healthy direction.
38→36 at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.bmcmt✕
- Connections
- 119 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.rules uses a type in at.forsyte.apalache.tla.bmcmt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
at.forsyte.apalache.tla.bmcmt.rules.AndRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.AndRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.AssignmentRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.AssignmentRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.BuiltinConstRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.BuiltinConstRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.CardinalityConstRule→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.CardinalityConstRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.CardinalityConstRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.CardinalityRule→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.CardinalityRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.CardinalityRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.ChooseOrGuessRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.ChooseOrGuessRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.DomainRule→at.forsyte.apalache.tla.bmcmt.ArenaCellat.forsyte.apalache.tla.bmcmt.rules.DomainRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.DomainRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.DomainRuleWithArrays→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.EqRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.EqRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.FoldSeqRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.FoldSeqRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.FoldSetRule→at.forsyte.apalache.tla.bmcmt.RewritingRuleat.forsyte.apalache.tla.bmcmt.rules.FoldSetRule→at.forsyte.apalache.tla.bmcmt.SymbStateat.forsyte.apalache.tla.bmcmt.rules.FunAppRule→at.forsyte.apalache.tla.bmcmt.ArenaCell
- Direction
- at.forsyte.apalache.tla.bmcmt.rules uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.rules, while a change to at.forsyte.apalache.tla.bmcmt.rules can't break at.forsyte.apalache.tla.bmcmt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.rules uses a module listed above it, which is the healthy direction.
39→7 at.forsyte.apalache.tla.bmcmt.stratifiedRules uses at.forsyte.apalache.tla.lir✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.stratifiedRules.Rewriter→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.stratifiedRules.StratifiedRule→at.forsyte.apalache.tla.lir.TlaExat.forsyte.apalache.tla.bmcmt.stratifiedRules.StratifiedRuleInterface→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.stratifiedRules uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.stratifiedRules, while a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.stratifiedRules uses a module listed above it, which is the healthy direction.
39→36 at.forsyte.apalache.tla.bmcmt.stratifiedRules uses at.forsyte.apalache.tla.bmcmt✕
- Connections
- 3 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules uses a type in at.forsyte.apalache.tla.bmcmt.
- The types involved
at.forsyte.apalache.tla.bmcmt.stratifiedRules.RewriterScope→at.forsyte.apalache.tla.bmcmt.Bindingat.forsyte.apalache.tla.bmcmt.stratifiedRules.RewriterScope→at.forsyte.apalache.tla.bmcmt.PureArenaat.forsyte.apalache.tla.bmcmt.stratifiedRules.StratifiedRule→at.forsyte.apalache.tla.bmcmt.ArenaCell
- Direction
- at.forsyte.apalache.tla.bmcmt.stratifiedRules uses at.forsyte.apalache.tla.bmcmt, so a change to at.forsyte.apalache.tla.bmcmt can break at.forsyte.apalache.tla.bmcmt.stratifiedRules, while a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules can't break at.forsyte.apalache.tla.bmcmt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.stratifiedRules uses a module listed above it, which is the healthy direction.
40→7 at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.lir✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a type in at.forsyte.apalache.tla.lir.
- The types involved
at.forsyte.apalache.tla.bmcmt.stratifiedRules.support.RewriterImpl→at.forsyte.apalache.tla.lir.TlaEx
- Direction
- at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.lir, so a change to at.forsyte.apalache.tla.lir can break at.forsyte.apalache.tla.bmcmt.stratifiedRules.support, while a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules.support can't break at.forsyte.apalache.tla.lir.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a module listed above it, which is the healthy direction.
40→24 at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.bmcmt.smt✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a type in at.forsyte.apalache.tla.bmcmt.smt.
- The types involved
at.forsyte.apalache.tla.bmcmt.stratifiedRules.support.DelayedConstraintGenerator→at.forsyte.apalache.tla.bmcmt.smt.SolverContextat.forsyte.apalache.tla.bmcmt.stratifiedRules.support.RewriterImpl→at.forsyte.apalache.tla.bmcmt.smt.SolverContext
- Direction
- at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.bmcmt.smt, so a change to at.forsyte.apalache.tla.bmcmt.smt can break at.forsyte.apalache.tla.bmcmt.stratifiedRules.support, while a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules.support can't break at.forsyte.apalache.tla.bmcmt.smt.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a module listed above it, which is the healthy direction.
40→34 at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.bmcmt.caches✕
- Connections
- 1 pair of types, where a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a type in at.forsyte.apalache.tla.bmcmt.caches.
- The types involved
at.forsyte.apalache.tla.bmcmt.stratifiedRules.support.RewriterImpl→at.forsyte.apalache.tla.bmcmt.caches.IntValueCache
- Direction
- at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.bmcmt.caches, so a change to at.forsyte.apalache.tla.bmcmt.caches can break at.forsyte.apalache.tla.bmcmt.stratifiedRules.support, while a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules.support can't break at.forsyte.apalache.tla.bmcmt.caches.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a module listed above it, which is the healthy direction.
40→39 at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.bmcmt.stratifiedRules✕
- Connections
- 2 pairs of types, where a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a type in at.forsyte.apalache.tla.bmcmt.stratifiedRules.
- The types involved
at.forsyte.apalache.tla.bmcmt.stratifiedRules.support.RewriterImpl→at.forsyte.apalache.tla.bmcmt.stratifiedRules.Rewriterat.forsyte.apalache.tla.bmcmt.stratifiedRules.support.RewriterImpl→at.forsyte.apalache.tla.bmcmt.stratifiedRules.StratifiedRuleInterface
- Direction
- at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses at.forsyte.apalache.tla.bmcmt.stratifiedRules, so a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules can break at.forsyte.apalache.tla.bmcmt.stratifiedRules.support, while a change to at.forsyte.apalache.tla.bmcmt.stratifiedRules.support can't break at.forsyte.apalache.tla.bmcmt.stratifiedRules.
- Position
- Below the diagonal: at.forsyte.apalache.tla.bmcmt.stratifiedRules.support uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 57 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | High / Critical |
Roadmap
First, secure the server's transport by enforcing TLS and HSTS headers to protect data in transit. Next, eliminate null references by enabling strict compiler checks and wrapping external values in Option types to prevent runtime failures. Then, replace interpolated log messages with structured logging to improve observability and debugging. Finally, update documentation links to match the current codebase and refactor the most complex functions to reduce maintenance risk.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`). | +2.7 pts | Medium | Web-Security Posture |
| 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. | +2.4 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +2.3 pts | Medium | Structured logging |
| Reconcile the README with reality: CONTRIBUTING.md links to `./docs/internal/using-bloop.md`, but `docs/internal/using-bloop.md` does not exist; CONTRIBUTING.md links to `~/.doom.d/init.el`, but `~/.doom.d/init.el` does not exist; shai/README.md links to `../tla/bmcmt/trex/TransitionExecutor.scala`, but `tla/bmcmt/trex/TransitionExecutor.scala` does not exist; shai/README.md links to `src/main/scala/at/forsyte/apalache/shai/rpcServer.scala`, but `shai/src/main/scala/at/forsyte/apalache/shai/rpcServer.scala` does not exist; test/tla/bakery-pluscal/README.md links to `Bakery.tla`, but `test/tla/bakery-pluscal/Bakery.tla` does not exist. | +2.1 pts | Medium | Documentation accuracy |
| Bring the 29 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ToEtcExpr.transform (cyclomatic 110), BuilderCallByName.apply (cyclomatic 106), ConstSimplifierBase.simplifyShallow (cyclomatic 98). | +2.0 pts | High | Cyclomatic Complexity |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with TableauEncoder.scala. | +0.9 pts | Low | Knowledge Freshness |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Z3SolverContext.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/PreproSolverContext.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| shai/src/main/scala/at/forsyte/apalache/shai/v1/TransExplorerService.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/FunAppRuleWithArrays.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/CherryPick.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbStateRewriterImpl.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/config/CheckerModule.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/SetInRule.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ExprOptimizer.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopedBuilder.scala | 6.3 | Mixed | Cognitive Complexity: ScopedBuilder.decl (cognitive 17) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 67 of 67 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 67 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, 445 of 483 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 214 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D20 ADR Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The ADR lexicon (adr-lexicon-1) covers de, en, it, nl. A record identified as another language, or whose language could not be identified (fewer than 25 words of prose, or no clear winner), is never read with English rules: its missing-section, status, consequence-cost and same-question rules abstain, and only the structural rules (title, single option, dangling link, enforcement field) run.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `tlair/src/main/scala/at/forsyte/apalache/tla/lir/src/SourceRegion.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
29 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ToEtcExpr.transform at 110. A further 8 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 SimplePrinter.getSimple at 33 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/config/CheckerExceptionAdapter.scala (CheckerExceptionAdapter.toMessage at 23), tlair/src/main/scala/at/forsyte/apalache/tla/lir/TypedPredefs.scala (BuilderExAsTyped.buildTyped at 21), tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/KeraLanguagePred.scala (KeraLanguagePred.isOkInContext at 21), tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/vmt/TermToVMTWriter.scala (TermToVMTWriter.mkSMT2String at 19). 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 29 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ToEtcExpr.transform (cyclomatic 110), BuilderCallByName.apply (cyclomatic 106), ConstSimplifierBase.simplifyShallow (cyclomatic 98). — 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 29 together lifts Cyclomatic Complexity from 5.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
54 method(s) exceeded the cognitive complexity threshold of 15; the worst was ItfJsonToTla.parseItfValueToTlaExpr at 148.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with ItfJsonToTla.parseItfValueToTlaExpr (cognitive 148). — Refactoring it lifts Cognitive Complexity from 5.6 to about 5.8/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
16 god class(es) detected.
What to do
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with ConstSimplifierBase.scala (4), PrettyWriter.scala, ItfJsonToTla.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 FileTooLong finding(s) in God Classes — start with Z3SolverContext.scala, ToEtcExpr.scala, JsonRpcServer.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Builder.scala, ApalacheConfigJsonParser.scala. — One of this dimension's main actionable groups (2 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
51 duplicated block group(s) detected.
What to do
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with JsonToTla.scala (4), SeqModelChecker.scala, Cvc5SolverContext.scala. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Keramelizer.scala (2), BoundedCheckerPassImpl.scala, JsonToTla.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with ParseCmd.scala, Cvc5SolverContext.scala, JsonToTla.scala. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
14 production modules (npm+sbt), 0 dependency cycle(s), 3 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; 2 module(s) off the main sequence, with abstractness counted on 12 of the 14 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Unstable project json_rpc finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project shai finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
4 of 107 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with JsonParameterParser.scala, ApalacheCommand.scala, Keramelizer.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.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Resolve the 27 Classify ADR enforcement finding(s) in Architectural Integrity — start with 001rfc-types.md, 002adr-types.md, 003adr-trex.md. — One of this dimension's main actionable groups (27 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
1874 test methods: 1872 unit, 2 integration, 0 BDD, 0 e2e. The Scala suite contributes 1874 test case(s) across 172 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.
D12 · Dependency Hygiene
19 outdated direct sbt declarations. 27 of 28 direct declarations were graded against Maven Central (1 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 27 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 2 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 2 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala (8×72=576)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with PrettyWriter.scala. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
74 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/CherryPick.scala. Counted over 256 of the 572 production source files in this repository: 310 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
98 deducted task-comment markers across 55179 LoC (0.2/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 94 TodoComment finding(s) in Explicit Debt — start with CrossTestEncodings.scala (8), TransExplorerService.scala (4), TestHybrid.scala (3). — One of this dimension's main actionable groups (94 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with SourceStore.scala, OpApplTranslator.scala, PreproSolverContext.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with ModuleTranslator.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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 88 document(s) read across 1 unit(s).
D20 · ADR Quality
5 of 25 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question). How well each record argues its case is not measured.
D26 · Project Cohesion
1 of 3 build units (npm, 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)
57 finding(s): 0 critical, 56 high, 1 medium, 0 low. 53 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 1 file(s) — `tlair/src/main/scala/at/forsyte/apalache/tla/lir/src/SourceRegion.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 53 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 (53 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 1 high, 0 medium, 1 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
62 of 262 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/temporal/TableauEncoder.scala. Counted over 262 of the 572 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 61 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (2), ScopedBuilder.scala, QuintIR.scala. — One of this dimension's main actionable groups (61 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with TableauEncoder.scala. — One of this dimension's main actionable groups (1 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: FunAppRuleWithArrays.scala↔FunExceptRuleWithArrays.scala 67%; FunCtorRuleWithArrays.scala↔FunExceptRuleWithArrays.scala 67%; ExplorationServiceParams.scala↔ExplorationServiceResult.scala 55%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with CheckCmd.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with ExplorationServiceParams.scala, ExplorationServiceResult.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with FunAppRuleWithArrays.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `ExprGradeStoreImpl` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (store; e.g. `store` in `put` at line 13). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/analyses/ExprGradeStoreImpl.scala:8
- `BoundedCheckerPassImpl` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (modelCheckerContext; e.g. `modelCheckerContext` in `prepareRemoteContext` at line 242). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/passes/BoundedCheckerPassImpl.scala:35
- `SourceStore` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (filenameToIndex, indexToFilename, trees, idToRegion; e.g. `filenameToIndex` in `getOrCreateFilenameIndex` at line 165). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — tlair/src/main/scala/at/forsyte/apalache/tla/lir/src/SourceStore.scala:23
- `ChangeListener` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (map; e.g. `map` in `conditionalInsert` at line 31). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — tlair/src/main/scala/at/forsyte/apalache/tla/lir/storage/ChangeListener.scala:25
- `IncrementalRenaming` is one shared instance (@Singleton: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (nameCounters; e.g. `nameCounters` in `getNextUnique` at line 149). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:130
What to do
- Scala: keep controllers and singletons stateless — per-request data in locals, shared data in a store — or hold the state in a thread-safe type (TrieMap, AtomicInteger/AtomicReference, a cats-effect Ref) or update it under `synchronized { }`; a flag that is only ever overwritten can be a `@volatile var`.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `SymbStateRewriter` declares 17 abstract members: `solverContext`, `solverContext_=`, `contextLevel`, `config`, `lazyEq`, `intValueCache`, `modelValueCache`, `defaultValueCache`, `recordDomainCache`, `exprCache`, `exprGradeStore`, `rewriteOnce`, `rewriteUntilDone`, `rewriteSeqUntilDone`, `rewriteBoundSeqUntilDone`, `flushStatistics`, `getRewritingStack`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbStateRewriter.scala:28
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — tla-bmcmt/src/test/scala/at/forsyte/apalache/tla/bmcmt/CrossTestEncodings.scala:500, tla-bmcmt/src/test/scala/at/forsyte/apalache/tla/bmcmt/stratifiedRules/support/oracles/TestUninterpretedConstOracle.scala:140, tla-bmcmt/src/test/scala/at/forsyte/apalache/tla/bmcmt/stratifiedRules/support/oracles/TestZipOracle.scala:58
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 29) — reach 50 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `./docs/internal/using-bloop.md`, but `docs/internal/using-bloop.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:279
- CONTRIBUTING.md links to `~/.doom.d/init.el`, but `~/.doom.d/init.el` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:295
- shai/README.md links to `../tla/bmcmt/trex/TransitionExecutor.scala`, but `tla/bmcmt/trex/TransitionExecutor.scala` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — shai/README.md:11
- shai/README.md links to `src/main/scala/at/forsyte/apalache/shai/rpcServer.scala`, but `shai/src/main/scala/at/forsyte/apalache/shai/rpcServer.scala` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — shai/README.md:121
- test/tla/bakery-pluscal/README.md links to `Bakery.tla`, but `test/tla/bakery-pluscal/Bakery.tla` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — test/tla/bakery-pluscal/README.md:16
- test/tla/bakery-pluscal/README.md links to `Boulanger.tla`, but `test/tla/bakery-pluscal/Boulanger.tla` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — test/tla/bakery-pluscal/README.md:19
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `./docs/internal/using-bloop.md`, but `docs/internal/using-bloop.md` does not exist; CONTRIBUTING.md links to `~/.doom.d/init.el`, but `~/.doom.d/init.el` does not exist; shai/README.md links to `../tla/bmcmt/trex/TransitionExecutor.scala`, but `tla/bmcmt/trex/TransitionExecutor.scala` does not exist; shai/README.md links to `src/main/scala/at/forsyte/apalache/shai/rpcServer.scala`, but `shai/src/main/scala/at/forsyte/apalache/shai/rpcServer.scala` does not exist; test/tla/bakery-pluscal/README.md links to `Bakery.tla`, but `test/tla/bakery-pluscal/Bakery.tla` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:779 — `HttpServlet`.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:779 — `HttpServlet`.
- No handler of this repository's Scala server answers 400, 413 or 422 (`BadRequest`, `StatusCodes.BadRequest`, `Status.BadRequest`, `UnprocessableEntity`), and nothing declares validation — no Play `Form(mapping(…))` or `validate[T]`, no tapir `Validator`, no akka/pekko-http `validate(…)` or `withSizeLimit`, no validation library (refined, iron, accord, cats `Validated`, Jakarta Bean Validation) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:779 — `HttpServlet`.
What to do
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: a Play form or `validate[T]` answered with `BadRequest`, tapir `Validator`s on the endpoint's inputs, or akka/pekko-http's `validate(…)` and `withSizeLimit` directives.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
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
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 327 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigResolver.scala:327
- `info` at line 382 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigResolver.scala:382
- `info` at line 398 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigResolver.scala:398
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 564 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 56% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 74% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Strong | Solid. |
| Security | 57% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 11 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 — 50 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~40008 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Scala not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 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.
- 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): 190 value object(s); 1 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python 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 62,380 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Python were 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; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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.
- 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 — 59 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/temporal/TableauEncoder.scala:1
- Boundary-crossing change coupling: CheckCmd.scala ↔ BoundedCheckerPassImpl.scala mod-tool/src/main/scala/at/forsyte/apalache/tla/tooling/opt/CheckCmd.scala:1
Serious — 275 finding(s)
- TodoComment tlair/src/test/scala/at/forsyte/apalache/tla/typecomp/TestHybrid.scala:172
- TodoComment tlair/src/test/scala/at/forsyte/apalache/tla/typecomp/TestHybrid.scala:214
- TodoComment tlair/src/test/scala/at/forsyte/apalache/tla/typecomp/TestHybrid.scala:559
- TodoComment tlair/src/test/scala/at/forsyte/apalache/tla/typecomp/pbt/TypecompPBT.scala:49
- TodoComment tlair/src/test/scala/at/forsyte/apalache/tla/typecomp/pbt/TypecompPBT.scala:61
- TodoComment tlair/src/test/scala/at/forsyte/apalache/tla/typecomp/pbt/TypecompPBT.scala:90
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/Builder.scala:444
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/TlaEx.scala:13
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/TypedPredefs.scala:79
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/TypedPredefs.scala:127
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:13
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:14
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:15
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/PrimePropagation.scala:36
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/storage/BodyMapFactory.scala:8
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/storage/BodyMapFactory.scala:9
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/oper/TlaOper.scala:141
- TodoComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/oper/TlaOper.scala:156
- TodoComment tla-pp/src/test/scala/at/forsyte/apalache/tla/pp/TestKeramelizer.scala:520
- TodoComment tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ExprOptimizer.scala:271
- TodoComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/ExprOrOpArgNodeTranslator.scala:110
- TodoComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/ModuleTranslator.scala:90
- TodoComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/ModuleTranslator.scala:157
- TodoComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/ModuleTranslator.scala:169
- TodoComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/ParserExceptionAdapter.scala:8
- MethodTooLong: PrettyWriter.exToDoc tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:128
- MethodTooLong: ConstSimplifierBase.trueEx tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:47
- MethodTooLong: ConstSimplifierBase.falseEx tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:48
- MethodTooLong: ConstSimplifierBase.emptySet tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:49
- MethodTooLong: ConstSimplifierBase.simplifyShallow tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:54
- MethodTooLong: ItfJsonToTla.attemptUnserializable tla-io/src/main/scala/at/forsyte/apalache/io/itf/ItfJsonToTla.scala:144
- FileTooLong: smt/Z3SolverContext.scala tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Z3SolverContext.scala
- FileTooLong: etc/ToEtcExpr.scala tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/ToEtcExpr.scala
- FileTooLong: jsonrpc/JsonRpcServer.scala json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala
- FileTooLong: support/CherryPick.scala tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/CherryPick.scala
- FileTooLong: tuning/FineTuningParser.scala tla-io/src/main/scala/at/forsyte/apalache/io/tuning/FineTuningParser.scala
- FileTooLong: lir/PrettyWriter.scala tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala
- Duplicated block (10 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SeqModelChecker.scala:138
- Duplicated block (10 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:92
- Duplicated block (10 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:111
- Duplicated block (10 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:126
- Duplicated block (10 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:211
- Duplicated block (10 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:182
- Stateful singleton: ExprGradeStoreImpl tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/analyses/ExprGradeStoreImpl.scala:8
- Stateful singleton: BoundedCheckerPassImpl tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/passes/BoundedCheckerPassImpl.scala:35
- Stateful singleton: SourceStore tlair/src/main/scala/at/forsyte/apalache/tla/lir/src/SourceStore.scala:23
- Stateful singleton: ChangeListener tlair/src/main/scala/at/forsyte/apalache/tla/lir/storage/ChangeListener.scala:25
- Stateful singleton: IncrementalRenaming tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:130
- Duplicated block (5 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/passes/BoundedCheckerPassImpl.scala:172
- Duplicated block (5 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:86
- Duplicated block (5 lines × 2) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Keramelizer.scala:234
- Duplicated block (5 lines × 2) tlair/src/main/scala/at/forsyte/apalache/tla/types/TypeUnifier.scala:182
- Duplicated block (5 lines × 2) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Keramelizer.scala:102
- Duplicated block (13 lines × 2) mod-tool/src/main/scala/at/forsyte/apalache/tla/tooling/opt/ParseCmd.scala:31
- Duplicated block (13 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:168
- Duplicated block (13 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:35
- Duplicated block (13 lines × 2) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/TypeAliasSubstitution.scala:214
- Duplicated block (6 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:447
- Duplicated block (6 lines × 2) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopeUnsafeBuilder.scala:103
- Duplicated block (6 lines × 2) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopeUnsafeBuilder.scala:117
- Duplicated block (6 lines × 2) REDACTED:95
- Low cohesion: JsonParameterParser (LCOM4 11) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonParameterParser.scala:11
- Low cohesion: ApalacheCommand (LCOM4 6) mod-tool/src/main/scala/at/forsyte/apalache/tla/tooling/opt/ApalacheCommand.scala:22
- Low cohesion: Keramelizer (LCOM4 4) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Keramelizer.scala:21
- Low cohesion: ScopedBuilder (LCOM4 4) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopedBuilder.scala:140
- FixmeComment tlair/src/main/scala/at/forsyte/apalache/tla/lir/src/SourceStore.scala:58
- FixmeComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/OpApplTranslator.scala:233
- FixmeComment tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/PreproSolverContext.scala:42
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10–11 lines × 2) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:219
- Duplicated block (10–11 lines × 2) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ExprOptimizer.scala:82
- Duplicated block (10–11 lines × 2) tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/Flatten.scala:48
- Duplicated block (9 lines × 2) tla-assignments/src/main/scala/at/forsyte/apalache/tla/assignments/SymbTransGenerator.scala:91
- Duplicated block (9 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:151
- Duplicated block (9 lines × 2) tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/KeraLanguagePred.scala:23
- TooManyMethods: Builder tlair/src/main/scala/at/forsyte/apalache/tla/lir/Builder.scala:110
- TooManyMethods: JsonDecoder tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigJsonParser.scala:102
- ClassTooLong: CherryPick tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/CherryPick.scala:25
- ClassTooLong: ExplorationService json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:55
- Change coupling: ExplorationServiceParams.scala ↔ ExplorationServiceResult.scala json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/ExplorationServiceParams.scala:1
- Change coupling: ExplorationServiceResult.scala ↔ JsonParameterParser.scala json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/ExplorationServiceResult.scala:1
- Duplicated block (17 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/Arena.scala:477
- Duplicated block (17 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:223
- Duplicated block (15 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/SetInRule.scala:77
- Duplicated block (15 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:137
- Duplicated block (8 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:350
- Duplicated block (8 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/stratifiedRules/support/caches/IntRangeCache.scala:50
- Duplicated block (7 lines × 3) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:287
- Duplicated block (7 lines × 3) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ExprOptimizer.scala:275
- Duplicated block (7 lines × 2) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:578
- Duplicated block (7 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/IntOracle.scala:32
- Off the main sequence: tlair
- Off the main sequence: tla_io
- ToEtcExpr.transform (cyclomatic 110) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/ToEtcExpr.scala:182
- BuilderCallByName.apply (cyclomatic 106) tla-io/src/main/scala/at/forsyte/apalache/io/json/impl/BuilderCallByName.scala:126
- ConstSimplifierBase.simplifyShallow (cyclomatic 98) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:54
- UTFPrinter.apply (cyclomatic 93) tlair/src/main/scala/at/forsyte/apalache/tla/lir/io/Printer.scala:61
- PrettyWriter.exToDoc (cyclomatic 72) tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:128
- Normalizer.nnf (cyclomatic 53) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Normalizer.scala:29
- Z3SolverContext.toExpr (cyclomatic 47) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Z3SolverContext.scala:722
- ItfJsonToTla.parseItfValueToTlaExpr (cyclomatic 47) tla-io/src/main/scala/at/forsyte/apalache/io/itf/ItfJsonToTla.scala:160
- Cvc5SolverContext.toExpr (cyclomatic 37) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:367
- EtcTypeChecker.computeRec (cyclomatic 32) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/EtcTypeChecker.scala:62
- TypeUnifier.compute (cyclomatic 31) tlair/src/main/scala/at/forsyte/apalache/tla/types/TypeUnifier.scala:123
- SymbStateDecoder.decodeCellToTlaEx (cyclomatic 29) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbStateDecoder.scala:36
- Desugarer.transform (cyclomatic 28) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Desugarer.scala:31
- TypeAliasSubstitution.mk (cyclomatic 26) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/TypeAliasSubstitution.scala:132
- EUFRule.apply (cyclomatic 25) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/vmt/EUFRule.scala:94
- CommentPreprocessor.getNextState (cyclomatic 24) tla-io/src/main/scala/at/forsyte/apalache/io/annotations/parser/CommentPreprocessor.scala:201
- Substitution.sub (cyclomatic 24) tlair/src/main/scala/at/forsyte/apalache/tla/types/Substitution.scala:29
- SeqModelChecker.prepareTransitionsAndCheckInvariants (cyclomatic 23) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SeqModelChecker.scala:182
- CommentPreprocessor.apply (cyclomatic 23) tla-io/src/main/scala/at/forsyte/apalache/io/annotations/parser/CommentPreprocessor.scala:101
- helperFunctions.allSelections (cyclomatic 21) tla-assignments/src/main/scala/at/forsyte/apalache/tla/assignments/SymbTransGenerator.scala:68
- PreproSolverContext.preprocess (cyclomatic 21) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/PreproSolverContext.scala:112
- ExpansionMarker.transform (cyclomatic 20) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/analyses/ExpansionMarker.scala:33
- TableauEncoder.encodeSyntaxTreeInPredicates (cyclomatic 20) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/temporal/TableauEncoder.scala:143
- PreproSolverContext.assertGroundExpr (cyclomatic 17) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/PreproSolverContext.scala:56
- TypeUnifier.unifyRows (cyclomatic 17) tlair/src/main/scala/at/forsyte/apalache/tla/types/TypeUnifier.scala:245
- ApalacheExplorer.explore (cyclomatic 17) REDACTED:375
- ExplorationService.checkInvariant (cyclomatic 16) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:416
- helperFunctions.sliceWith (cyclomatic 16) tla-assignments/src/main/scala/at/forsyte/apalache/tla/assignments/SymbTransGenerator.scala:182
- Quint.tlaExpression (cyclomatic 16) tla-io/src/main/scala/at/forsyte/apalache/io/quint/Quint.scala:729
- Hotspot: tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:128
- XxxComment tla-parser/src/main/scala/at/forsyte/apalache/tla/imp/ModuleTranslator.scala:94
- ItfJsonToTla.parseItfValueToTlaExpr (cognitive 148) tla-io/src/main/scala/at/forsyte/apalache/io/itf/ItfJsonToTla.scala:160
- ItfJsonToTla.parseHeaderAndVarTypes (cognitive 86) tla-io/src/main/scala/at/forsyte/apalache/io/itf/ItfJsonToTla.scala:87
- SeqModelChecker.prepareTransitionsAndCheckInvariants (cognitive 79) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SeqModelChecker.scala:182
- Normalizer.nnf (cognitive 74) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Normalizer.scala:29
- BuilderUtil.boundVarIntroductionVariadic (cognitive 66) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/BuilderUtil.scala:103
- PrettyWriter.exToDoc (cognitive 63) tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:128
- EUFRule.apply (cognitive 60) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/vmt/EUFRule.scala:94
- ExplorationService.assumeTransition (cognitive 55) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:179
- EtcTypeChecker.computeRec (cognitive 54) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/EtcTypeChecker.scala:62
- ToEtcExpr.transform (cognitive 50) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/ToEtcExpr.scala:182
- BuilderUtil.boundVarIntroductionTernary (cognitive 46) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/BuilderUtil.scala:53
- CommentPreprocessor.getNextState (cognitive 38) tla-io/src/main/scala/at/forsyte/apalache/io/annotations/parser/CommentPreprocessor.scala:201
- CommentPreprocessor.apply (cognitive 37) tla-io/src/main/scala/at/forsyte/apalache/io/annotations/parser/CommentPreprocessor.scala:101
- Z3SolverContext.toExpr (cognitive 36) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Z3SolverContext.scala:722
- JsonToTla.getSourceLocationOpt (cognitive 36) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTla.scala:86
- JsonToTlaViaBuilder.getSourceLocationOpt (cognitive 36) tla-io/src/main/scala/at/forsyte/apalache/io/json/JsonToTlaViaBuilder.scala:105
- TypeUnifier.unifyRows (cognitive 36) tlair/src/main/scala/at/forsyte/apalache/tla/types/TypeUnifier.scala:245
- ApalacheExplorer.explore (cognitive 36) REDACTED:375
- ConstSimplifierBase.simplifyShallow (cognitive 34) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstSimplifierBase.scala:54
- SymbStateDecoder.decodeCellToTlaEx (cognitive 32) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbStateDecoder.scala:36
- ItfJsonToTla.parseTrace (cognitive 32) tla-io/src/main/scala/at/forsyte/apalache/io/itf/ItfJsonToTla.scala:50
- ExplorationService.assumeState (cognitive 31) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:359
- helperFunctions.allSelections (cognitive 29) tla-assignments/src/main/scala/at/forsyte/apalache/tla/assignments/SymbTransGenerator.scala:68
- UTFPrinter.apply (cognitive 28) tlair/src/main/scala/at/forsyte/apalache/tla/lir/io/Printer.scala:61
- ExplorationService.checkInvariant (cognitive 26) json-rpc/src/main/scala/com/github/apalachemc/apalache/jsonrpc/JsonRpcServer.scala:416
- TableauEncoder.encodeSyntaxTreeInPredicates (cognitive 25) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/temporal/TableauEncoder.scala:143
- TypeAliasSubstitution.mk (cognitive 25) tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/TypeAliasSubstitution.scala:132
- TypeUnifier.compute (cognitive 25) tlair/src/main/scala/at/forsyte/apalache/tla/types/TypeUnifier.scala:123
- SanyParserPassImpl.loadFromJsonSource (cognitive 24) passes/src/main/scala/at/forsyte/apalache/tla/passes/imp/SanyParserPassImpl.scala:44
- PreproSolverContext.assertGroundExpr (cognitive 24) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/PreproSolverContext.scala:56
- PrettyWriter.declToDoc (cognitive 24) tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:586
- Desugarer.transform (cognitive 24) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Desugarer.scala:31
- ConfigurationPassImpl.extractFromSpec (cognitive 22) passes/src/main/scala/at/forsyte/apalache/tla/passes/pp/ConfigurationPassImpl.scala:251
- TransExplorerService.loadModel (cognitive 22) shai/src/main/scala/at/forsyte/apalache/shai/v1/TransExplorerService.scala:146
- BuilderUtil.boundVarIntroductionBinary (cognitive 22) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/BuilderUtil.scala:81
- IncrementalRenaming.rename (cognitive 21) tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:159
- FunAppRuleWithArrays.applyFun (cognitive 20) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/FunAppRuleWithArrays.scala:20
- Substitution.sub (cognitive 20) tlair/src/main/scala/at/forsyte/apalache/tla/types/Substitution.scala:29
- helperFunctions.sliceWith (cognitive 19) tla-assignments/src/main/scala/at/forsyte/apalache/tla/assignments/SymbTransGenerator.scala:182
- PreproSolverContext.preprocess (cognitive 19) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/PreproSolverContext.scala:112
- CherryPick.pickRecordDomain (cognitive 18) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/CherryPick.scala:463
- Desugarer.eatFunType (cognitive 18) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/Desugarer.scala:323
- SetOperSignatures.getMap (cognitive 18) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/signatures/SetOperSignatures.scala:22
- SeqModelChecker.makeStep (cognitive 17) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SeqModelChecker.scala:123
- SetAsFunRule.apply (cognitive 17) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/SetAsFunRule.scala:23
- CherryPick.pickFunFromFunSet (cognitive 17) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/CherryPick.scala:977
- ConstAndDefRewriter.apply (cognitive 17) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/ConstAndDefRewriter.scala:21
- IncrementalRenaming.shiftCounters (cognitive 17) tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/IncrementalRenaming.scala:260
- ScopedBuilder.decl (cognitive 17) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopedBuilder.scala:176
- ScopedBuilder.declWithInferredParameterTypes (cognitive 17) tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopedBuilder.scala:196
- SeqModelChecker.checkInvariants (cognitive 16) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SeqModelChecker.scala:345
- ValueGenerator.genFun (cognitive 16) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/ValueGenerator.scala:203
- Cvc5SolverContext.toExpr (cognitive 16) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:367
- OperAppToLetInDef.wrap (cognitive 16) tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/OperAppToLetInDef.scala:30
- REDACTED
- Change coupling clique: FunAppRuleWithArrays.scala, FunCtorRuleWithArrays.scala, FunExceptRuleWithArrays.scala tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/FunAppRuleWithArrays.scala
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12–32 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbStateRewriterImpl.scala:632
- Duplicated block (25 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/config/CheckerModule.scala:36
- Duplicated block (20–21 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/DomainRule.scala:30
- Duplicated block (20 lines × 3) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/config/CheckerModule.scala:49
- Duplicated block (20 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/AndRule.scala:47
- Duplicated block (17 lines × 3) tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/FlatLanguagePred.scala:22
- Duplicated block (16 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:115
- Duplicated block (13–15 lines × 3) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/SetInRule.scala:106
- Duplicated block (14 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/arena/PureArenaAdapter.scala:349
- Duplicated block (3–14 lines × 3) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/config/CheckerModule.scala:31
- Duplicated block (10–13 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/FunExceptRule.scala:78
- Duplicated block (8–12 lines × 2) tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:271
- Duplicated block (11 lines × 2) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/FoldSetRule.scala:76
- Duplicated block (6–8 lines × 5) tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:246
- Duplicated block (3–5 lines × 3) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:98
- Duplicated block (8 lines × 5) passes/src/main/scala/at/forsyte/apalache/tla/passes/pp/PreproPassPartial.scala:99
- Unstable project json_rpc
- Unstable project shai
- Unstable project tool
- JavaScript dependencies are not locked
Minor — 130 finding(s)
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopedBuilder.scala:1
- Orphaned file tla-io/src/main/scala/at/forsyte/apalache/io/quint/QuintIR.scala:1
- Orphaned file tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/arena/PureArenaAdapter.scala:1
- Orphaned file project/sbt-changeling/Changeling.scala:1
- Orphaned file tla-assignments/src/main/scala/at/forsyte/apalache/tla/assignments/SmtFreeSymbolicTransitionExtractor.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/BuilderUtil.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/bmcmt/PureArena.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/unsafe/UnsafeFunBuilder.scala:1
- Orphaned file tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/vmt/EUFRule.scala:1
- Orphaned file tla-io/src/main/scala/at/forsyte/apalache/io/json/TlaToJson.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/unsafe/UnsafeSetBuilder.scala:1
- Orphaned file tla-pp/src/main/scala/at/forsyte/apalache/tla/pp/temporal/LoopEncoder.scala:1
- Orphaned file mod-infra/src/main/scala/at/forsyte/apalache/infra/passes/DerivedPredicates.scala:1
- Orphaned file tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/vmt/TermToVMTWriter.scala:1
- Orphaned file tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/stratifiedRules/support/caches/Cache.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/types/package.scala:1
- Orphaned file tla-typechecker/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/EtcExpr.scala:1
- Orphaned file tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/SetInclusionRuleWithArrays.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/unsafe/UnsafeApalacheBuilder.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/lir/storage/DisjointSets.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/ScopeUnsafeBuilder.scala:1
- Orphaned file tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/vmt/TlaExToVMTWriter.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/subbuilder/SetBuilder.scala:1
- Orphaned file tlair/src/main/scala/at/forsyte/apalache/tla/lir/transformations/standard/ReTLALanguagePred.scala:1
- Orphaned file passes/src/main/scala/at/forsyte/apalache/tla/passes/pp/TemporalPassImpl.scala:1
- Classify ADR enforcement: RFC 001: types and type annotations docs/src/adr/001rfc-types.md
- Classify ADR enforcement: ADR-002: types and type annotations docs/src/adr/002adr-types.md
- Classify ADR enforcement: ADR-003: transition executor (TRex) docs/src/adr/003adr-trex.md
- Classify ADR enforcement: ADR-004: Syntax for Java-like annotations in TLA+ comments docs/src/adr/004adr-annotations.md
- Classify ADR enforcement: ADR-005: JSON Serialization Format docs/src/adr/005adr-json.md
- Classify ADR enforcement: RFC-006: Unit testing and property-based testing of TLA+ specifications docs/src/adr/006rfc-unit-testing.md
- Classify ADR enforcement: ADR-007: Apalache Package Structure Guidelines docs/src/adr/007adr-restructuring.md
- Classify ADR enforcement: ADR-008: Apalache Exceptions docs/src/adr/008adr-exceptions.md
- Classify ADR enforcement: ADR-009: Apalache Outputs docs/src/adr/009adr-outputs.md
- Classify ADR enforcement: RFC-010: Implementation of Transition Exploration Server docs/src/adr/010rfc-transition-explorer.md
- Classify ADR enforcement: ADR-011: alternative SMT encoding using arrays docs/src/adr/011adr-smt-arrays.md
- Classify ADR enforcement: ADR-013: Configuration Management Component docs/src/adr/013adr-configuration.md
- Classify ADR enforcement: ADR-014: Precise type inference for records and variants docs/src/adr/014adr-precise-records.md
- Classify ADR enforcement: ADR-015: Informal Trace Format in JSON docs/src/adr/015adr-trace.md
- Classify ADR enforcement: ADR-16: ReTLA - Relational TLA docs/src/adr/016adr-retla.md
- Classify ADR enforcement: PDR-017: Checking temporal properties docs/src/adr/017pdr-temporal.md
- Classify ADR enforcement: ADR-018: Inlining in Apalache docs/src/adr/018adr-inlining.md
- Classify ADR enforcement: ADR-019: Harmonize changelog management docs/src/adr/019adr-harmonize-changelog.md
- Classify ADR enforcement: ADR-020: Introduce static membership in arenas docs/src/adr/020adr-arenas.md
- Classify ADR enforcement: RFC-021: Prioritization of Work docs/src/adr/021rfc-prioritization.md
- Classify ADR enforcement: ADR-022: Unify Configuration Management and "Pass Options" docs/src/adr/022adr-unification-of-configs-and-options.md
- Classify ADR enforcement: ADR-023: Trace evaluation docs/src/adr/023adr-trace-evaluation.md
- Classify ADR enforcement: ADR-024: Arena computation isolation docs/src/adr/024adr-arena-pass.md
- Classify ADR enforcement: ADR-025: CVC5 solver backend integration docs/src/adr/025adr-cvc5-solver-backend.md
- Classify ADR enforcement: ADR-026: Explicit configuration and command options docs/src/adr/026adr-explicit-configuration.md
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbState.scala:59
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:388
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/rules/support/IntOracle.scala:33
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:329
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/smt/Cvc5SolverContext.scala:156
- Duplicated predicate tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:428
- Duplicated predicate tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:189
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/analyses/ExpansionMarker.scala:73
- Duplicated predicate tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/analyses/ExpansionMarker.scala:104
- Duplicated predicate tla-io/src/main/scala/at/forsyte/apalache/io/lir/PrettyWriter.scala:436
- Duplicated predicate tlair/src/main/scala/at/forsyte/apalache/tla/typecomp/signatures/FunOperSignatures.scala:26
- README/code drift CONTRIBUTING.md:279
- README/code drift CONTRIBUTING.md:295
- README/code drift shai/README.md:11
- README/code drift shai/README.md:121
- README/code drift test/tla/bakery-pluscal/README.md:16
- README/code drift test/tla/bakery-pluscal/README.md:19
- ADR Consequences section is empty docs/src/adr/018adr-inlining.md:151
- ADR Consequences section is empty docs/src/adr/022adr-unification-of-configs-and-options.md:109
- ADR Consequences section is empty docs/src/adr/023adr-trace-evaluation.md:415
- Disabled test tla-bmcmt/src/test/scala/at/forsyte/apalache/tla/bmcmt/CrossTestEncodings.scala:500
- Disabled test tla-bmcmt/src/test/scala/at/forsyte/apalache/tla/bmcmt/stratifiedRules/support/oracles/TestUninterpretedConstOracle.scala:140
- Disabled test tla-bmcmt/src/test/scala/at/forsyte/apalache/tla/bmcmt/stratifiedRules/support/oracles/TestZipOracle.scala:58
- Interpolated log message defeats structured logging tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigResolver.scala:327
- Interpolated log message defeats structured logging tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigResolver.scala:382
- Interpolated log message defeats structured logging tla-io/src/main/scala/at/forsyte/apalache/io/config/ApalacheConfigResolver.scala:398
- Fat interface: SymbStateRewriter (17 abstract members) tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/SymbStateRewriter.scala:28
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- ADR has no Decision section docs/src/adr/019adr-harmonize-changelog.md:1
- ADR considers only one option docs/src/adr/021rfc-prioritization.md:49
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- Logging is not universal
- No app-layer HTTPS enforcement detected
- No security response headers detected
- No inbound request validation detected
- Scala's null is not held to the type system everywhere
Minor — 19 finding(s)
- Outdated: ch.qos.logback:logback-classic
- Outdated: ch.qos.logback:logback-core
- Outdated: com.fasterxml.jackson.core:jackson-databind
- Outdated: com.fasterxml.jackson.module:jackson-module-scala_2.13
- Outdated: com.lihaoyi:ujson_2.13
- Outdated: com.lihaoyi:upickle_2.13
- Outdated: dev.zio:zio_2.13
- Outdated: io.github.cvc5:cvc5
- Outdated: io.grpc:grpc-netty
- Outdated: org.apache.commons:commons-configuration2
- Outdated: org.eclipse.jetty:jetty-server
- Outdated: org.eclipse.jetty.compression:jetty-compression-gzip
- Outdated: org.eclipse.jetty.compression:jetty-compression-server
- Outdated: org.eclipse.jetty.compression:jetty-compression-zstandard
- Outdated: org.eclipse.jetty.ee10:jetty-ee10-servlet
- Outdated: org.scala-lang.modules:scala-collection-contrib_2.13
- Outdated: org.scala-lang.modules:scala-parser-combinators_2.13
- Outdated: org.scalaz:scalaz-core_2.13
- Outdated: org.slf4j:slf4j-api
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aa87fd27d7d045308f7a56f1fd312774/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aa87fd27d7d045308f7a56f1fd312774/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs/highlightjs-tlaplus/dist . | 57 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 2 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `tlair/src/main/scala/at/forsyte/apalache/tla/lir/src/SourceRegion.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |