Executive summary
biomejs/gritql is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 64 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 57, is the weakest lens and counts most in the score. The best first step is fixing the test that is switched off, worth about 4 points. Automating dependency updates would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 68.
Forty-three known security holes in the packages the code depends on can be used by attackers. Three pipeline steps install packages that can change without warning, and three pipeline steps run downloads nobody checks. Updating the vulnerable packages, pinning what the pipeline installs and checking each download against a checksum would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and the place where the code runs text as code or as a command needs a direct call instead.
The product code is 70,694 lines, about €74,000 to rebuild.
If Production Readiness rose from 57 to 70, the lowest score rated Strong, the score would rise from 64 to about 68.
New since the last survey: 25 findings
- Test Quality · Skipped test: can run inside a storage context js/gritql/__test__/napi.spec.mts
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Async & latency hygiene · Sync-over-async blocking js/gritql/src/search.rs
Fixed since the last survey: 7 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €74,000 · Estimate
| Cost to rebuild | €25,000 to €120,000, for 410 to 1,302 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. 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: 70,694 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 marzano_cli.flags | 2 marzano_gritmodule.fetcher | 3 grit_pattern_matcher.pattern.iter_pattern | 4 grit_pattern_matcher.pattern.pattern_definition | 5 grit_pattern_matcher.pattern.predicate_definition | 6 grit_util.ranges | 7 marzano_util.rich_path | 8 grit_pattern_matcher.pattern.range | 9 marzano_util.node_with_source | 10 grit_util.code_range | 11 grit_util.language | 12 grit_pattern_matcher.pattern.accessor | 13 grit_pattern_matcher.pattern.list_index | 14 marzano_language.language | 15 grit_util.parser | 16 marzano_language.target_language | 17 marzano_core.marzano_binding | 18 marzano_core.marzano_resolved_pattern | 19 marzano_core.marzano_context | 20 marzano_core.built_in_functions | 21 marzano_core.pattern_compiler.compiler | 22 marzano_core.pattern_compiler.node_compiler | 23 marzano_core.problem | 24 marzano_core.api | 25 grit_util.analysis_logs | 26 marzano_gritmodule.config | 27 marzano_messenger.emit | 28 grit_pattern_matcher.pattern.variable | 29 grit_pattern_matcher.pattern.state | 30 grit_pattern_matcher.effects | 31 grit_pattern_matcher.pattern.resolved_pattern | 32 grit_pattern_matcher.pattern.dynamic_snippet | 33 grit_pattern_matcher.pattern.patterns | 34 grit_pattern_matcher.pattern.functions | 35 grit_pattern_matcher.pattern.predicates | 36 grit_pattern_matcher.pattern.function_definition | 37 grit_pattern_matcher.context | 38 marzano_core.pattern_compiler.builder | 39 grit_pattern_matcher.binding | 40 marzano_core.ast_node |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 marzano_cli.flags | ||||||||||||||||||||||||||||||||||||||||
| 2 marzano_gritmodule.fetcher | ||||||||||||||||||||||||||||||||||||||||
| 3 grit_pattern_matcher.pattern.iter_pattern | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 4 grit_pattern_matcher.pattern.pattern_definition | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 5 grit_pattern_matcher.pattern.predicate_definition | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 6 grit_util.ranges | 7 | |||||||||||||||||||||||||||||||||||||||
| 7 marzano_util.rich_path | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 grit_pattern_matcher.pattern.range | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 9 marzano_util.node_with_source | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 grit_util.code_range | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 grit_util.language | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 grit_pattern_matcher.pattern.accessor | 1 | 2 | 1 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 13 grit_pattern_matcher.pattern.list_index | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 14 marzano_language.language | 2 | 1 | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||
| 15 grit_util.parser | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 marzano_language.target_language | 1 | 1 | 1 | 3 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 17 marzano_core.marzano_binding | 1 | 1 | 2 | 2 | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||
| 18 marzano_core.marzano_resolved_pattern | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 5 | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||
| 19 marzano_core.marzano_context | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 20 marzano_core.built_in_functions | 1 | 3 | 3 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 21 marzano_core.pattern_compiler.compiler | 2 | 2 | 4 | 1 | 4 | 2 | 1 | 3 | 3 | 3 | 2 | |||||||||||||||||||||||||||||
| 22 marzano_core.pattern_compiler.node_compiler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 marzano_core.problem | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 24 marzano_core.api | 4 | 9 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 grit_util.analysis_logs | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 marzano_gritmodule.config | 3 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 marzano_messenger.emit | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 grit_pattern_matcher.pattern.variable | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 29 grit_pattern_matcher.pattern.state | 1 | 2 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 30 grit_pattern_matcher.effects | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 grit_pattern_matcher.pattern.resolved_pattern | 1 | 1 | 5 | 1 | 1 | 4 | 8 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||
| 32 grit_pattern_matcher.pattern.dynamic_snippet | 1 | 1 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 33 grit_pattern_matcher.pattern.patterns | 2 | 2 | 2 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 34 grit_pattern_matcher.pattern.functions | 1 | 4 | 4 | 1 | 4 | 3 | ||||||||||||||||||||||||||||||||||
| 35 grit_pattern_matcher.pattern.predicates | 2 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 36 grit_pattern_matcher.pattern.function_definition | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 grit_pattern_matcher.context | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 marzano_core.pattern_compiler.builder | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 39 grit_pattern_matcher.binding | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 40 marzano_core.ast_node | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 4 | 1 |
3→33 grit_pattern_matcher.pattern.iter_pattern uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.iter_pattern uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicateIterator→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- grit_pattern_matcher.pattern.iter_pattern uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.iter_pattern, while a change to grit_pattern_matcher.pattern.iter_pattern can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→35 grit_pattern_matcher.pattern.iter_pattern uses grit_pattern_matcher.pattern.predicates part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.iter_pattern uses a type in grit_pattern_matcher.pattern.predicates.
- The types involved
grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicateIterator→grit_pattern_matcher.pattern.predicates.Predicate
- Direction
- grit_pattern_matcher.pattern.iter_pattern uses grit_pattern_matcher.pattern.predicates, so a change to grit_pattern_matcher.pattern.predicates can break grit_pattern_matcher.pattern.iter_pattern, while a change to grit_pattern_matcher.pattern.iter_pattern can't break grit_pattern_matcher.pattern.predicates.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→37 grit_pattern_matcher.pattern.iter_pattern uses grit_pattern_matcher.context part of a loop✕
- Connections
- 3 pairs of types, where a type in grit_pattern_matcher.pattern.iter_pattern uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicate→grit_pattern_matcher.context.StaticDefinitionsgrit_pattern_matcher.pattern.iter_pattern.PatternOrPredicateIterator→grit_pattern_matcher.context.StaticDefinitionsgrit_pattern_matcher.pattern.iter_pattern.iter_pattern$module→grit_pattern_matcher.context.StaticDefinitions
- Direction
- grit_pattern_matcher.pattern.iter_pattern uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.iter_pattern, while a change to grit_pattern_matcher.pattern.iter_pattern can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→25 grit_pattern_matcher.pattern.pattern_definition uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.pattern_definition uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.pattern_definition.PatternDefinition→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.pattern_definition uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.pattern_definition, while a change to grit_pattern_matcher.pattern.pattern_definition can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→29 grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.pattern_definition uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.pattern_definition.PatternDefinition→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.pattern_definition, while a change to grit_pattern_matcher.pattern.pattern_definition can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→31 grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.pattern_definition uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.pattern_definition.PatternDefinition→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.pattern_definition, while a change to grit_pattern_matcher.pattern.pattern_definition can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→33 grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.pattern_definition uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.pattern_definition.PatternDefinition→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.pattern_definition, while a change to grit_pattern_matcher.pattern.pattern_definition can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→37 grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.pattern_definition uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.pattern_definition.PatternDefinition→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.pattern_definition uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.pattern_definition, while a change to grit_pattern_matcher.pattern.pattern_definition can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→25 grit_pattern_matcher.pattern.predicate_definition uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicate_definition uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.predicate_definition uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.predicate_definition, while a change to grit_pattern_matcher.pattern.predicate_definition can't break grit_util.analysis_logs.
- 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→29 grit_pattern_matcher.pattern.predicate_definition uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicate_definition uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.predicate_definition uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.predicate_definition, while a change to grit_pattern_matcher.pattern.predicate_definition can't break grit_pattern_matcher.pattern.state.
- 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→35 grit_pattern_matcher.pattern.predicate_definition uses grit_pattern_matcher.pattern.predicates part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicate_definition uses a type in grit_pattern_matcher.pattern.predicates.
- The types involved
grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition→grit_pattern_matcher.pattern.predicates.Predicate
- Direction
- grit_pattern_matcher.pattern.predicate_definition uses grit_pattern_matcher.pattern.predicates, so a change to grit_pattern_matcher.pattern.predicates can break grit_pattern_matcher.pattern.predicate_definition, while a change to grit_pattern_matcher.pattern.predicate_definition can't break grit_pattern_matcher.pattern.predicates.
- 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→37 grit_pattern_matcher.pattern.predicate_definition uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicate_definition uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.predicate_definition uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.predicate_definition, while a change to grit_pattern_matcher.pattern.predicate_definition can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→8 grit_util.ranges uses grit_pattern_matcher.pattern.range part of a loop✕
- Connections
- 7 pairs of types, where a type in grit_util.ranges uses a type in grit_pattern_matcher.pattern.range.
- The types involved
grit_util.ranges.ByteRange→grit_pattern_matcher.pattern.range.Rangegrit_util.ranges.EffectRange→grit_pattern_matcher.pattern.range.Rangegrit_util.ranges.InputRanges→grit_pattern_matcher.pattern.range.Rangegrit_util.ranges.Range→grit_pattern_matcher.pattern.range.Rangegrit_util.ranges.RangeWithoutByte→grit_pattern_matcher.pattern.range.Rangegrit_util.ranges.UtilRange→grit_pattern_matcher.pattern.range.Rangegrit_util.ranges.VariableMatch→grit_pattern_matcher.pattern.range.Range
- Direction
- grit_util.ranges uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break grit_util.ranges, while a change to grit_util.ranges can't break grit_pattern_matcher.pattern.range.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→24 marzano_util.rich_path uses marzano_core.api part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_util.rich_path uses a type in marzano_core.api.
- The types involved
marzano_util.rich_path.RichFile→marzano_core.api.InputFile
- Direction
- marzano_util.rich_path uses marzano_core.api, so a change to marzano_core.api can break marzano_util.rich_path, while a change to marzano_util.rich_path can't break marzano_core.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→6 grit_pattern_matcher.pattern.range uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.range uses a type in grit_util.ranges.
- The types involved
grit_pattern_matcher.pattern.range.Range→grit_util.ranges.UtilRange
- Direction
- grit_pattern_matcher.pattern.range uses grit_util.ranges, so a change to grit_util.ranges can break grit_pattern_matcher.pattern.range, while a change to grit_pattern_matcher.pattern.range can't break grit_util.ranges.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.range uses a module listed above it, which is the healthy direction.
8→25 grit_pattern_matcher.pattern.range uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.range uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.range.Range→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.range uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.range, while a change to grit_pattern_matcher.pattern.range can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→29 grit_pattern_matcher.pattern.range uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.range uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.range.Range→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.range uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.range, while a change to grit_pattern_matcher.pattern.range can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→31 grit_pattern_matcher.pattern.range uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.range uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.range.Range→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.range uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.range, while a change to grit_pattern_matcher.pattern.range can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→33 grit_pattern_matcher.pattern.range uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.range uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.range.Range→grit_pattern_matcher.pattern.patterns.Matchergrit_pattern_matcher.pattern.range.Range→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.range uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.range, while a change to grit_pattern_matcher.pattern.range can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→37 grit_pattern_matcher.pattern.range uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.range uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.range.Range→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.range uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.range, while a change to grit_pattern_matcher.pattern.range can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→6 marzano_util.node_with_source uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in marzano_util.node_with_source uses a type in grit_util.ranges.
- The types involved
marzano_util.node_with_source.NodeWithSource→grit_util.ranges.ByteRange
- Direction
- marzano_util.node_with_source uses grit_util.ranges, so a change to grit_util.ranges can break marzano_util.node_with_source, while a change to marzano_util.node_with_source can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_util.node_with_source uses a module listed above it, which is the healthy direction.
9→8 marzano_util.node_with_source uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in marzano_util.node_with_source uses a type in grit_pattern_matcher.pattern.range.
- The types involved
marzano_util.node_with_source.NodeWithSource→grit_pattern_matcher.pattern.range.Range
- Direction
- marzano_util.node_with_source uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break marzano_util.node_with_source, while a change to marzano_util.node_with_source can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: marzano_util.node_with_source uses a module listed above it, which is the healthy direction.
9→10 marzano_util.node_with_source uses grit_util.code_range part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_util.node_with_source uses a type in grit_util.code_range.
- The types involved
marzano_util.node_with_source.NodeWithSource→grit_util.code_range.CodeRange
- Direction
- marzano_util.node_with_source uses grit_util.code_range, so a change to grit_util.code_range can break marzano_util.node_with_source, while a change to marzano_util.node_with_source can't break grit_util.code_range.
- 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→9 grit_util.code_range uses marzano_util.node_with_source✕
- Connections
- 1 pair of types, where a type in grit_util.code_range uses a type in marzano_util.node_with_source.
- The types involved
grit_util.code_range.CodeRange→marzano_util.node_with_source.NodeWithSource
- Direction
- grit_util.code_range uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break grit_util.code_range, while a change to grit_util.code_range can't break marzano_util.node_with_source.
- Position
- Below the diagonal: grit_util.code_range uses a module listed above it, which is the healthy direction.
11→6 grit_util.language uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in grit_util.language uses a type in grit_util.ranges.
- The types involved
grit_util.language.Language→grit_util.ranges.ByteRange
- Direction
- grit_util.language uses grit_util.ranges, so a change to grit_util.ranges can break grit_util.language, while a change to grit_util.language can't break grit_util.ranges.
- Position
- Below the diagonal: grit_util.language uses a module listed above it, which is the healthy direction.
11→8 grit_util.language uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in grit_util.language uses a type in grit_pattern_matcher.pattern.range.
- The types involved
grit_util.language.Replacement→grit_pattern_matcher.pattern.range.Range
- Direction
- grit_util.language uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break grit_util.language, while a change to grit_util.language can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: grit_util.language uses a module listed above it, which is the healthy direction.
11→10 grit_util.language uses grit_util.code_range✕
- Connections
- 1 pair of types, where a type in grit_util.language uses a type in grit_util.code_range.
- The types involved
grit_util.language.Language→grit_util.code_range.CodeRange
- Direction
- grit_util.language uses grit_util.code_range, so a change to grit_util.code_range can break grit_util.language, while a change to grit_util.language can't break grit_util.code_range.
- Position
- Below the diagonal: grit_util.language uses a module listed above it, which is the healthy direction.
12→3 grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.iter_pattern✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_pattern_matcher.pattern.iter_pattern.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicate
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.iter_pattern, so a change to grit_pattern_matcher.pattern.iter_pattern can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_pattern_matcher.pattern.iter_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.accessor uses a module listed above it, which is the healthy direction.
12→11 grit_pattern_matcher.pattern.accessor uses grit_util.language✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_util.language.Languagegrit_pattern_matcher.pattern.accessor.accessor$module→grit_util.language.Language
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.accessor uses a module listed above it, which is the healthy direction.
12→25 grit_pattern_matcher.pattern.accessor uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.accessor.accessor$module→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→31 grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPatterngrit_pattern_matcher.pattern.accessor.accessor$module→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→33 grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.pattern.patterns.Matchergrit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→37 grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.context part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.accessor uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.accessor.Accessor→grit_pattern_matcher.context.StaticDefinitions
- Direction
- grit_pattern_matcher.pattern.accessor uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.accessor, while a change to grit_pattern_matcher.pattern.accessor can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→3 grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.iter_pattern✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_pattern_matcher.pattern.iter_pattern.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicate
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.iter_pattern, so a change to grit_pattern_matcher.pattern.iter_pattern can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_pattern_matcher.pattern.iter_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.list_index uses a module listed above it, which is the healthy direction.
13→11 grit_pattern_matcher.pattern.list_index uses grit_util.language✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_util.language.Language
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.list_index uses a module listed above it, which is the healthy direction.
13→25 grit_pattern_matcher.pattern.list_index uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→31 grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→33 grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.pattern.patterns.Matchergrit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→37 grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.context part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.list_index uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.list_index.ListIndex→grit_pattern_matcher.context.StaticDefinitions
- Direction
- grit_pattern_matcher.pattern.list_index uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.list_index, while a change to grit_pattern_matcher.pattern.list_index can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→9 marzano_language.language uses marzano_util.node_with_source✕
- Connections
- 2 pairs of types, where a type in marzano_language.language uses a type in marzano_util.node_with_source.
- The types involved
marzano_language.language.MarzanoLanguage→marzano_util.node_with_source.NodeWithSourcemarzano_language.language.language$module→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_language.language uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_language.language, while a change to marzano_language.language can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_language.language uses a module listed above it, which is the healthy direction.
14→10 marzano_language.language uses grit_util.code_range✕
- Connections
- 1 pair of types, where a type in marzano_language.language uses a type in grit_util.code_range.
- The types involved
marzano_language.language.MarzanoLanguage→grit_util.code_range.CodeRange
- Direction
- marzano_language.language uses grit_util.code_range, so a change to grit_util.code_range can break marzano_language.language, while a change to marzano_language.language can't break grit_util.code_range.
- Position
- Below the diagonal: marzano_language.language uses a module listed above it, which is the healthy direction.
14→11 marzano_language.language uses grit_util.language✕
- Connections
- 1 pair of types, where a type in marzano_language.language uses a type in grit_util.language.
- The types involved
marzano_language.language.MarzanoLanguage→grit_util.language.Language
- Direction
- marzano_language.language uses grit_util.language, so a change to grit_util.language can break marzano_language.language, while a change to marzano_language.language can't break grit_util.language.
- Position
- Below the diagonal: marzano_language.language uses a module listed above it, which is the healthy direction.
14→15 marzano_language.language uses grit_util.parser part of a loop✕
- Connections
- 6 pairs of types, where a type in marzano_language.language uses a type in grit_util.parser.
- The types involved
marzano_language.language.MarzanoLanguage→grit_util.parser.SnippetTreemarzano_language.language.MarzanoParser→grit_util.parser.FileOriginmarzano_language.language.MarzanoParser→grit_util.parser.Parsermarzano_language.language.MarzanoParser→grit_util.parser.SnippetTreemarzano_language.language.Tree→grit_util.parser.Astmarzano_language.language.language$module→grit_util.parser.SnippetTree
- Direction
- marzano_language.language uses grit_util.parser, so a change to grit_util.parser can break marzano_language.language, while a change to marzano_language.language can't break grit_util.parser.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→25 marzano_language.language uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_language.language uses a type in grit_util.analysis_logs.
- The types involved
marzano_language.language.MarzanoParser→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_language.language uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_language.language, while a change to marzano_language.language can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→14 grit_util.parser uses marzano_language.language✕
- Connections
- 2 pairs of types, where a type in grit_util.parser uses a type in marzano_language.language.
- The types involved
grit_util.parser.Parser→marzano_language.language.Treegrit_util.parser.SnippetTree→marzano_language.language.Tree
- Direction
- grit_util.parser uses marzano_language.language, so a change to marzano_language.language can break grit_util.parser, while a change to grit_util.parser can't break marzano_language.language.
- Position
- Below the diagonal: grit_util.parser uses a module listed above it, which is the healthy direction.
15→25 grit_util.parser uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in grit_util.parser uses a type in grit_util.analysis_logs.
- The types involved
grit_util.parser.Parser→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_util.parser uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_util.parser, while a change to grit_util.parser can't break grit_util.analysis_logs.
- 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→6 marzano_language.target_language uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in marzano_language.target_language uses a type in grit_util.ranges.
- The types involved
marzano_language.target_language.TargetLanguage→grit_util.ranges.ByteRange
- Direction
- marzano_language.target_language uses grit_util.ranges, so a change to grit_util.ranges can break marzano_language.target_language, while a change to marzano_language.target_language can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_language.target_language uses a module listed above it, which is the healthy direction.
16→9 marzano_language.target_language uses marzano_util.node_with_source✕
- Connections
- 1 pair of types, where a type in marzano_language.target_language uses a type in marzano_util.node_with_source.
- The types involved
marzano_language.target_language.TargetLanguage→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_language.target_language uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_language.target_language, while a change to marzano_language.target_language can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_language.target_language uses a module listed above it, which is the healthy direction.
16→10 marzano_language.target_language uses grit_util.code_range✕
- Connections
- 1 pair of types, where a type in marzano_language.target_language uses a type in grit_util.code_range.
- The types involved
marzano_language.target_language.TargetLanguage→grit_util.code_range.CodeRange
- Direction
- marzano_language.target_language uses grit_util.code_range, so a change to grit_util.code_range can break marzano_language.target_language, while a change to marzano_language.target_language can't break grit_util.code_range.
- Position
- Below the diagonal: marzano_language.target_language uses a module listed above it, which is the healthy direction.
16→11 marzano_language.target_language uses grit_util.language✕
- Connections
- 3 pairs of types, where a type in marzano_language.target_language uses a type in grit_util.language.
- The types involved
marzano_language.target_language.TargetLanguage→grit_util.language.GritMetaValuemarzano_language.target_language.TargetLanguage→grit_util.language.Languagemarzano_language.target_language.TargetLanguage→grit_util.language.Replacement
- Direction
- marzano_language.target_language uses grit_util.language, so a change to grit_util.language can break marzano_language.target_language, while a change to marzano_language.target_language can't break grit_util.language.
- Position
- Below the diagonal: marzano_language.target_language uses a module listed above it, which is the healthy direction.
16→14 marzano_language.target_language uses marzano_language.language✕
- Connections
- 4 pairs of types, where a type in marzano_language.target_language uses a type in marzano_language.language.
- The types involved
marzano_language.target_language.PatternLanguage→marzano_language.language.Treemarzano_language.target_language.TargetLanguage→marzano_language.language.MarzanoLanguagemarzano_language.target_language.TargetLanguage→marzano_language.language.NodeTypesmarzano_language.target_language.TargetLanguage→marzano_language.language.Tree
- Direction
- marzano_language.target_language uses marzano_language.language, so a change to marzano_language.language can break marzano_language.target_language, while a change to marzano_language.target_language can't break marzano_language.language.
- Position
- Below the diagonal: marzano_language.target_language uses a module listed above it, which is the healthy direction.
16→15 marzano_language.target_language uses grit_util.parser✕
- Connections
- 1 pair of types, where a type in marzano_language.target_language uses a type in grit_util.parser.
- The types involved
marzano_language.target_language.TargetLanguage→grit_util.parser.SnippetTree
- Direction
- marzano_language.target_language uses grit_util.parser, so a change to grit_util.parser can break marzano_language.target_language, while a change to marzano_language.target_language can't break grit_util.parser.
- Position
- Below the diagonal: marzano_language.target_language uses a module listed above it, which is the healthy direction.
17→6 marzano_core.marzano_binding uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_binding uses a type in grit_util.ranges.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→grit_util.ranges.ByteRange
- Direction
- marzano_core.marzano_binding uses grit_util.ranges, so a change to grit_util.ranges can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_core.marzano_binding uses a module listed above it, which is the healthy direction.
17→8 marzano_core.marzano_binding uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_binding uses a type in grit_pattern_matcher.pattern.range.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→grit_pattern_matcher.pattern.range.Range
- Direction
- marzano_core.marzano_binding uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: marzano_core.marzano_binding uses a module listed above it, which is the healthy direction.
17→9 marzano_core.marzano_binding uses marzano_util.node_with_source✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_binding uses a type in marzano_util.node_with_source.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→marzano_util.node_with_source.NodeWithSourcemarzano_core.marzano_binding.marzano_binding$module→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_core.marzano_binding uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_core.marzano_binding uses a module listed above it, which is the healthy direction.
17→10 marzano_core.marzano_binding uses grit_util.code_range✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_binding uses a type in grit_util.code_range.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→grit_util.code_range.CodeRangemarzano_core.marzano_binding.marzano_binding$module→grit_util.code_range.CodeRange
- Direction
- marzano_core.marzano_binding uses grit_util.code_range, so a change to grit_util.code_range can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_util.code_range.
- Position
- Below the diagonal: marzano_core.marzano_binding uses a module listed above it, which is the healthy direction.
17→11 marzano_core.marzano_binding uses grit_util.language✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_binding uses a type in grit_util.language.
- The types involved
marzano_core.marzano_binding.marzano_binding$module→grit_util.language.Language
- Direction
- marzano_core.marzano_binding uses grit_util.language, so a change to grit_util.language can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_util.language.
- Position
- Below the diagonal: marzano_core.marzano_binding uses a module listed above it, which is the healthy direction.
17→16 marzano_core.marzano_binding uses marzano_language.target_language✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_binding uses a type in marzano_language.target_language.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→marzano_language.target_language.TargetLanguage
- Direction
- marzano_core.marzano_binding uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_core.marzano_binding uses a module listed above it, which is the healthy direction.
17→25 marzano_core.marzano_binding uses grit_util.analysis_logs part of a loop✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_binding uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→grit_util.analysis_logs.AnalysisLogsmarzano_core.marzano_binding.marzano_binding$module→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.marzano_binding uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 marzano_core.marzano_binding uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_binding uses a type in grit_pattern_matcher.pattern.state.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→grit_pattern_matcher.pattern.state.FileRegistrymarzano_core.marzano_binding.marzano_binding$module→grit_pattern_matcher.pattern.state.FileRegistry
- Direction
- marzano_core.marzano_binding uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→39 marzano_core.marzano_binding uses grit_pattern_matcher.binding part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_binding uses a type in grit_pattern_matcher.binding.
- The types involved
marzano_core.marzano_binding.MarzanoBinding→grit_pattern_matcher.binding.Binding
- Direction
- marzano_core.marzano_binding uses grit_pattern_matcher.binding, so a change to grit_pattern_matcher.binding can break marzano_core.marzano_binding, while a change to marzano_core.marzano_binding can't break grit_pattern_matcher.binding.
- 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→8 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.range.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.range.Range
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: marzano_core.marzano_resolved_pattern uses a module listed above it, which is the healthy direction.
18→9 marzano_core.marzano_resolved_pattern uses marzano_util.node_with_source✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in marzano_util.node_with_source.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_core.marzano_resolved_pattern uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_core.marzano_resolved_pattern uses a module listed above it, which is the healthy direction.
18→12 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.accessor✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.accessor.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.accessor.Accessor
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.accessor, so a change to grit_pattern_matcher.pattern.accessor can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.accessor.
- Position
- Below the diagonal: marzano_core.marzano_resolved_pattern uses a module listed above it, which is the healthy direction.
18→13 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.list_index✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.list_index.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.list_index.ListIndex
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.list_index, so a change to grit_pattern_matcher.pattern.list_index can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.list_index.
- Position
- Below the diagonal: marzano_core.marzano_resolved_pattern uses a module listed above it, which is the healthy direction.
18→16 marzano_core.marzano_resolved_pattern uses marzano_language.target_language✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_resolved_pattern uses a type in marzano_language.target_language.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoFile→marzano_language.target_language.TargetLanguagemarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→marzano_language.target_language.TargetLanguage
- Direction
- marzano_core.marzano_resolved_pattern uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_core.marzano_resolved_pattern uses a module listed above it, which is the healthy direction.
18→17 marzano_core.marzano_resolved_pattern uses marzano_core.marzano_binding✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in marzano_core.marzano_binding.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→marzano_core.marzano_binding.MarzanoBinding
- Direction
- marzano_core.marzano_resolved_pattern uses marzano_core.marzano_binding, so a change to marzano_core.marzano_binding can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break marzano_core.marzano_binding.
- Position
- Below the diagonal: marzano_core.marzano_resolved_pattern uses a module listed above it, which is the healthy direction.
18→19 marzano_core.marzano_resolved_pattern uses marzano_core.marzano_context part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in marzano_core.marzano_context.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→marzano_core.marzano_context.MarzanoContext
- Direction
- marzano_core.marzano_resolved_pattern uses marzano_core.marzano_context, so a change to marzano_core.marzano_context can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break marzano_core.marzano_context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→23 marzano_core.marzano_resolved_pattern uses marzano_core.problem part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in marzano_core.problem.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→marzano_core.problem.FilePattern
- Direction
- marzano_core.marzano_resolved_pattern uses marzano_core.problem, so a change to marzano_core.problem can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break marzano_core.problem.
- 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→25 marzano_core.marzano_resolved_pattern uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.marzano_resolved_pattern uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_util.analysis_logs.
- 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→29 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 5 pairs of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.state.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoFile→grit_pattern_matcher.pattern.state.FileRegistrymarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.state.FilePtrmarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.state.FileRegistrymarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.state.Statemarzano_core.marzano_resolved_pattern.marzano_resolved_pattern$module→grit_pattern_matcher.pattern.state.FilePtr
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.state.
- 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→30 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.effects part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.effects.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.effects.Effect
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.effects, so a change to grit_pattern_matcher.effects can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.effects.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→31 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 3 pairs of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoFile→grit_pattern_matcher.pattern.resolved_pattern.Filemarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPatternmarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.resolved_pattern.ResolvedSnippet
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.resolved_pattern.
- 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→32 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.dynamic_snippet part of a loop✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.dynamic_snippet.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.dynamic_snippet.DynamicPatternmarzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.dynamic_snippet.DynamicSnippet
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.dynamic_snippet, so a change to grit_pattern_matcher.pattern.dynamic_snippet can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.dynamic_snippet.
- 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→33 marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_resolved_pattern uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- marzano_core.marzano_resolved_pattern uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.marzano_resolved_pattern, while a change to marzano_core.marzano_resolved_pattern can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→4 marzano_core.marzano_context uses grit_pattern_matcher.pattern.pattern_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_pattern_matcher.pattern.pattern_definition.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_pattern_matcher.pattern.pattern_definition.PatternDefinition
- Direction
- marzano_core.marzano_context uses grit_pattern_matcher.pattern.pattern_definition, so a change to grit_pattern_matcher.pattern.pattern_definition can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_pattern_matcher.pattern.pattern_definition.
- Position
- Below the diagonal: marzano_core.marzano_context uses a module listed above it, which is the healthy direction.
19→5 marzano_core.marzano_context uses grit_pattern_matcher.pattern.predicate_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_pattern_matcher.pattern.predicate_definition.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition
- Direction
- marzano_core.marzano_context uses grit_pattern_matcher.pattern.predicate_definition, so a change to grit_pattern_matcher.pattern.predicate_definition can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_pattern_matcher.pattern.predicate_definition.
- Position
- Below the diagonal: marzano_core.marzano_context uses a module listed above it, which is the healthy direction.
19→16 marzano_core.marzano_context uses marzano_language.target_language✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in marzano_language.target_language.
- The types involved
marzano_core.marzano_context.MarzanoContext→marzano_language.target_language.TargetLanguage
- Direction
- marzano_core.marzano_context uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_core.marzano_context uses a module listed above it, which is the healthy direction.
19→18 marzano_core.marzano_context uses marzano_core.marzano_resolved_pattern✕
- Connections
- 2 pairs of types, where a type in marzano_core.marzano_context uses a type in marzano_core.marzano_resolved_pattern.
- The types involved
marzano_core.marzano_context.MarzanoContext→marzano_core.marzano_resolved_pattern.MarzanoFilemarzano_core.marzano_context.MarzanoContext→marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern
- Direction
- marzano_core.marzano_context uses marzano_core.marzano_resolved_pattern, so a change to marzano_core.marzano_resolved_pattern can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break marzano_core.marzano_resolved_pattern.
- Position
- Below the diagonal: marzano_core.marzano_context uses a module listed above it, which is the healthy direction.
19→20 marzano_core.marzano_context uses marzano_core.built_in_functions part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in marzano_core.built_in_functions.
- The types involved
marzano_core.marzano_context.MarzanoContext→marzano_core.built_in_functions.BuiltIns
- Direction
- marzano_core.marzano_context uses marzano_core.built_in_functions, so a change to marzano_core.built_in_functions can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break marzano_core.built_in_functions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→25 marzano_core.marzano_context uses grit_util.analysis_logs part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.marzano_context uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→29 marzano_core.marzano_context uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_pattern_matcher.pattern.state.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_pattern_matcher.pattern.state.State
- Direction
- marzano_core.marzano_context uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→33 marzano_core.marzano_context uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- marzano_core.marzano_context uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→36 marzano_core.marzano_context uses grit_pattern_matcher.pattern.function_definition part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_pattern_matcher.pattern.function_definition.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_pattern_matcher.pattern.function_definition.GritFunctionDefinition
- Direction
- marzano_core.marzano_context uses grit_pattern_matcher.pattern.function_definition, so a change to grit_pattern_matcher.pattern.function_definition can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_pattern_matcher.pattern.function_definition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→37 marzano_core.marzano_context uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.marzano_context uses a type in grit_pattern_matcher.context.
- The types involved
marzano_core.marzano_context.MarzanoContext→grit_pattern_matcher.context.ExecContext
- Direction
- marzano_core.marzano_context uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break marzano_core.marzano_context, while a change to marzano_core.marzano_context can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→18 marzano_core.built_in_functions uses marzano_core.marzano_resolved_pattern✕
- Connections
- 1 pair of types, where a type in marzano_core.built_in_functions uses a type in marzano_core.marzano_resolved_pattern.
- The types involved
marzano_core.built_in_functions.BuiltIns→marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern
- Direction
- marzano_core.built_in_functions uses marzano_core.marzano_resolved_pattern, so a change to marzano_core.marzano_resolved_pattern can break marzano_core.built_in_functions, while a change to marzano_core.built_in_functions can't break marzano_core.marzano_resolved_pattern.
- Position
- Below the diagonal: marzano_core.built_in_functions uses a module listed above it, which is the healthy direction.
20→19 marzano_core.built_in_functions uses marzano_core.marzano_context✕
- Connections
- 3 pairs of types, where a type in marzano_core.built_in_functions uses a type in marzano_core.marzano_context.
- The types involved
marzano_core.built_in_functions.BuiltInFunction→marzano_core.marzano_context.MarzanoContextmarzano_core.built_in_functions.BuiltIns→marzano_core.marzano_context.MarzanoContextmarzano_core.built_in_functions.built_in_functions$module→marzano_core.marzano_context.MarzanoContext
- Direction
- marzano_core.built_in_functions uses marzano_core.marzano_context, so a change to marzano_core.marzano_context can break marzano_core.built_in_functions, while a change to marzano_core.built_in_functions can't break marzano_core.marzano_context.
- Position
- Below the diagonal: marzano_core.built_in_functions uses a module listed above it, which is the healthy direction.
20→25 marzano_core.built_in_functions uses grit_util.analysis_logs part of a loop✕
- Connections
- 3 pairs of types, where a type in marzano_core.built_in_functions uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.built_in_functions.BuiltInFunction→grit_util.analysis_logs.AnalysisLogsmarzano_core.built_in_functions.BuiltIns→grit_util.analysis_logs.AnalysisLogsmarzano_core.built_in_functions.built_in_functions$module→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.built_in_functions uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.built_in_functions, while a change to marzano_core.built_in_functions can't break grit_util.analysis_logs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→29 marzano_core.built_in_functions uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 3 pairs of types, where a type in marzano_core.built_in_functions uses a type in grit_pattern_matcher.pattern.state.
- The types involved
marzano_core.built_in_functions.BuiltInFunction→grit_pattern_matcher.pattern.state.Statemarzano_core.built_in_functions.BuiltIns→grit_pattern_matcher.pattern.state.Statemarzano_core.built_in_functions.built_in_functions$module→grit_pattern_matcher.pattern.state.State
- Direction
- marzano_core.built_in_functions uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break marzano_core.built_in_functions, while a change to marzano_core.built_in_functions can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→33 marzano_core.built_in_functions uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.built_in_functions uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.built_in_functions.BuiltIns→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- marzano_core.built_in_functions uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.built_in_functions, while a change to marzano_core.built_in_functions can't break grit_pattern_matcher.pattern.patterns.
- 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→4 marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.pattern_definition✕
- Connections
- 2 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_pattern_matcher.pattern.pattern_definition.
- The types involved
marzano_core.pattern_compiler.compiler.DefinitionOutput→grit_pattern_matcher.pattern.pattern_definition.PatternDefinitionmarzano_core.pattern_compiler.compiler.compiler$module→grit_pattern_matcher.pattern.pattern_definition.PatternDefinition
- Direction
- marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.pattern_definition, so a change to grit_pattern_matcher.pattern.pattern_definition can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_pattern_matcher.pattern.pattern_definition.
- Position
- Below the diagonal: marzano_core.pattern_compiler.compiler uses a module listed above it, which is the healthy direction.
21→5 marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.predicate_definition✕
- Connections
- 2 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_pattern_matcher.pattern.predicate_definition.
- The types involved
marzano_core.pattern_compiler.compiler.DefinitionOutput→grit_pattern_matcher.pattern.predicate_definition.PredicateDefinitionmarzano_core.pattern_compiler.compiler.compiler$module→grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition
- Direction
- marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.predicate_definition, so a change to grit_pattern_matcher.pattern.predicate_definition can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_pattern_matcher.pattern.predicate_definition.
- Position
- Below the diagonal: marzano_core.pattern_compiler.compiler uses a module listed above it, which is the healthy direction.
21→6 marzano_core.pattern_compiler.compiler uses grit_util.ranges✕
- Connections
- 4 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_util.ranges.
- The types involved
marzano_core.pattern_compiler.compiler.NodeCompilationContext→grit_util.ranges.ByteRangemarzano_core.pattern_compiler.compiler.SnippetCompilationContext→grit_util.ranges.ByteRangemarzano_core.pattern_compiler.compiler.VariableLocations→grit_util.ranges.VariableMatchmarzano_core.pattern_compiler.compiler.compiler$module→grit_util.ranges.FileRange
- Direction
- marzano_core.pattern_compiler.compiler uses grit_util.ranges, so a change to grit_util.ranges can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_core.pattern_compiler.compiler uses a module listed above it, which is the healthy direction.
21→9 marzano_core.pattern_compiler.compiler uses marzano_util.node_with_source✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.compiler uses a type in marzano_util.node_with_source.
- The types involved
marzano_core.pattern_compiler.compiler.compiler$module→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_core.pattern_compiler.compiler uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_core.pattern_compiler.compiler uses a module listed above it, which is the healthy direction.
21→16 marzano_core.pattern_compiler.compiler uses marzano_language.target_language✕
- Connections
- 4 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in marzano_language.target_language.
- The types involved
marzano_core.pattern_compiler.compiler.CompilationContext→marzano_language.target_language.TargetLanguagemarzano_core.pattern_compiler.compiler.NodeCompilationContext→marzano_language.target_language.TargetLanguagemarzano_core.pattern_compiler.compiler.SnippetCompilationContext→marzano_language.target_language.TargetLanguagemarzano_core.pattern_compiler.compiler.compiler$module→marzano_language.target_language.TargetLanguage
- Direction
- marzano_core.pattern_compiler.compiler uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_core.pattern_compiler.compiler uses a module listed above it, which is the healthy direction.
21→20 marzano_core.pattern_compiler.compiler uses marzano_core.built_in_functions✕
- Connections
- 2 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in marzano_core.built_in_functions.
- The types involved
marzano_core.pattern_compiler.compiler.CompilationContext→marzano_core.built_in_functions.BuiltInsmarzano_core.pattern_compiler.compiler.compiler$module→marzano_core.built_in_functions.BuiltIns
- Direction
- marzano_core.pattern_compiler.compiler uses marzano_core.built_in_functions, so a change to marzano_core.built_in_functions can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break marzano_core.built_in_functions.
- Position
- Below the diagonal: marzano_core.pattern_compiler.compiler uses a module listed above it, which is the healthy direction.
21→23 marzano_core.pattern_compiler.compiler uses marzano_core.problem part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.compiler uses a type in marzano_core.problem.
- The types involved
marzano_core.pattern_compiler.compiler.CompilationResult→marzano_core.problem.Problem
- Direction
- marzano_core.pattern_compiler.compiler uses marzano_core.problem, so a change to marzano_core.problem can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break marzano_core.problem.
- 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→25 marzano_core.pattern_compiler.compiler uses grit_util.analysis_logs part of a loop✕
- Connections
- 3 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.pattern_compiler.compiler.CompilationResult→grit_util.analysis_logs.AnalysisLogsmarzano_core.pattern_compiler.compiler.NodeCompilationContext→grit_util.analysis_logs.AnalysisLogsmarzano_core.pattern_compiler.compiler.compiler$module→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.pattern_compiler.compiler uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_util.analysis_logs.
- 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→28 marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.variable part of a loop✕
- Connections
- 3 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_pattern_matcher.pattern.variable.
- The types involved
marzano_core.pattern_compiler.compiler.DefinitionOutput→grit_pattern_matcher.pattern.variable.VariableSourcemarzano_core.pattern_compiler.compiler.NodeCompilationContext→grit_pattern_matcher.pattern.variable.VariableSourcemarzano_core.pattern_compiler.compiler.VariableLocations→grit_pattern_matcher.pattern.variable.VariableSource
- Direction
- marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.variable, so a change to grit_pattern_matcher.pattern.variable can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_pattern_matcher.pattern.variable.
- 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→33 marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 3 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.pattern_compiler.compiler.CompilationResult→grit_pattern_matcher.pattern.patterns.Patternmarzano_core.pattern_compiler.compiler.NodeCompilationContext→grit_pattern_matcher.pattern.patterns.Patternmarzano_core.pattern_compiler.compiler.SnippetCompilationContext→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_pattern_matcher.pattern.patterns.
- 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 marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.function_definition part of a loop✕
- Connections
- 2 pairs of types, where a type in marzano_core.pattern_compiler.compiler uses a type in grit_pattern_matcher.pattern.function_definition.
- The types involved
marzano_core.pattern_compiler.compiler.DefinitionOutput→grit_pattern_matcher.pattern.function_definition.GritFunctionDefinitionmarzano_core.pattern_compiler.compiler.compiler$module→grit_pattern_matcher.pattern.function_definition.GritFunctionDefinition
- Direction
- marzano_core.pattern_compiler.compiler uses grit_pattern_matcher.pattern.function_definition, so a change to grit_pattern_matcher.pattern.function_definition can break marzano_core.pattern_compiler.compiler, while a change to marzano_core.pattern_compiler.compiler can't break grit_pattern_matcher.pattern.function_definition.
- 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 marzano_core.pattern_compiler.node_compiler uses marzano_util.node_with_source✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.node_compiler uses a type in marzano_util.node_with_source.
- The types involved
marzano_core.pattern_compiler.node_compiler.NodeCompiler→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_core.pattern_compiler.node_compiler uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_core.pattern_compiler.node_compiler, while a change to marzano_core.pattern_compiler.node_compiler can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_core.pattern_compiler.node_compiler uses a module listed above it, which is the healthy direction.
22→21 marzano_core.pattern_compiler.node_compiler uses marzano_core.pattern_compiler.compiler✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.node_compiler uses a type in marzano_core.pattern_compiler.compiler.
- The types involved
marzano_core.pattern_compiler.node_compiler.NodeCompiler→marzano_core.pattern_compiler.compiler.NodeCompilationContext
- Direction
- marzano_core.pattern_compiler.node_compiler uses marzano_core.pattern_compiler.compiler, so a change to marzano_core.pattern_compiler.compiler can break marzano_core.pattern_compiler.node_compiler, while a change to marzano_core.pattern_compiler.node_compiler can't break marzano_core.pattern_compiler.compiler.
- Position
- Below the diagonal: marzano_core.pattern_compiler.node_compiler uses a module listed above it, which is the healthy direction.
23→4 marzano_core.problem uses grit_pattern_matcher.pattern.pattern_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in grit_pattern_matcher.pattern.pattern_definition.
- The types involved
marzano_core.problem.Problem→grit_pattern_matcher.pattern.pattern_definition.PatternDefinition
- Direction
- marzano_core.problem uses grit_pattern_matcher.pattern.pattern_definition, so a change to grit_pattern_matcher.pattern.pattern_definition can break marzano_core.problem, while a change to marzano_core.problem can't break grit_pattern_matcher.pattern.pattern_definition.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→5 marzano_core.problem uses grit_pattern_matcher.pattern.predicate_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in grit_pattern_matcher.pattern.predicate_definition.
- The types involved
marzano_core.problem.Problem→grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition
- Direction
- marzano_core.problem uses grit_pattern_matcher.pattern.predicate_definition, so a change to grit_pattern_matcher.pattern.predicate_definition can break marzano_core.problem, while a change to marzano_core.problem can't break grit_pattern_matcher.pattern.predicate_definition.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→6 marzano_core.problem uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in grit_util.ranges.
- The types involved
marzano_core.problem.Problem→grit_util.ranges.VariableMatch
- Direction
- marzano_core.problem uses grit_util.ranges, so a change to grit_util.ranges can break marzano_core.problem, while a change to marzano_core.problem can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→7 marzano_core.problem uses marzano_util.rich_path✕
- Connections
- 2 pairs of types, where a type in marzano_core.problem uses a type in marzano_util.rich_path.
- The types involved
marzano_core.problem.Problem→marzano_util.rich_path.RichFilemarzano_core.problem.Problem→marzano_util.rich_path.RichPath
- Direction
- marzano_core.problem uses marzano_util.rich_path, so a change to marzano_util.rich_path can break marzano_core.problem, while a change to marzano_core.problem can't break marzano_util.rich_path.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→14 marzano_core.problem uses marzano_language.language✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in marzano_language.language.
- The types involved
marzano_core.problem.Problem→marzano_language.language.Tree
- Direction
- marzano_core.problem uses marzano_language.language, so a change to marzano_language.language can break marzano_core.problem, while a change to marzano_core.problem can't break marzano_language.language.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→16 marzano_core.problem uses marzano_language.target_language✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in marzano_language.target_language.
- The types involved
marzano_core.problem.Problem→marzano_language.target_language.TargetLanguage
- Direction
- marzano_core.problem uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_core.problem, while a change to marzano_core.problem can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→20 marzano_core.problem uses marzano_core.built_in_functions✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in marzano_core.built_in_functions.
- The types involved
marzano_core.problem.Problem→marzano_core.built_in_functions.BuiltIns
- Direction
- marzano_core.problem uses marzano_core.built_in_functions, so a change to marzano_core.built_in_functions can break marzano_core.problem, while a change to marzano_core.problem can't break marzano_core.built_in_functions.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→21 marzano_core.problem uses marzano_core.pattern_compiler.compiler✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in marzano_core.pattern_compiler.compiler.
- The types involved
marzano_core.problem.Problem→marzano_core.pattern_compiler.compiler.VariableLocations
- Direction
- marzano_core.problem uses marzano_core.pattern_compiler.compiler, so a change to marzano_core.pattern_compiler.compiler can break marzano_core.problem, while a change to marzano_core.problem can't break marzano_core.pattern_compiler.compiler.
- Position
- Below the diagonal: marzano_core.problem uses a module listed above it, which is the healthy direction.
23→24 marzano_core.problem uses marzano_core.api part of a loop✕
- Connections
- 2 pairs of types, where a type in marzano_core.problem uses a type in marzano_core.api.
- The types involved
marzano_core.problem.Problem→marzano_core.api.MatchResultmarzano_core.problem.problem$module→marzano_core.api.MatchResult
- Direction
- marzano_core.problem uses marzano_core.api, so a change to marzano_core.api can break marzano_core.problem, while a change to marzano_core.problem can't break marzano_core.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 marzano_core.problem uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in grit_pattern_matcher.pattern.state.
- The types involved
marzano_core.problem.FilePattern→grit_pattern_matcher.pattern.state.FilePtr
- Direction
- marzano_core.problem uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break marzano_core.problem, while a change to marzano_core.problem can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→33 marzano_core.problem uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.problem.Problem→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- marzano_core.problem uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.problem, while a change to marzano_core.problem can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→36 marzano_core.problem uses grit_pattern_matcher.pattern.function_definition part of a loop✕
- Connections
- 1 pair of types, where a type in marzano_core.problem uses a type in grit_pattern_matcher.pattern.function_definition.
- The types involved
marzano_core.problem.Problem→grit_pattern_matcher.pattern.function_definition.GritFunctionDefinition
- Direction
- marzano_core.problem uses grit_pattern_matcher.pattern.function_definition, so a change to grit_pattern_matcher.pattern.function_definition can break marzano_core.problem, while a change to marzano_core.problem can't break grit_pattern_matcher.pattern.function_definition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→37 marzano_core.problem uses grit_pattern_matcher.context part of a loop✕
- Connections
- 2 pairs of types, where a type in marzano_core.problem uses a type in grit_pattern_matcher.context.
- The types involved
marzano_core.problem.MarzanoQueryContext→grit_pattern_matcher.context.QueryContextmarzano_core.problem.Problem→grit_pattern_matcher.context.StaticDefinitions
- Direction
- marzano_core.problem uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break marzano_core.problem, while a change to marzano_core.problem can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→6 marzano_core.api uses grit_util.ranges✕
- Connections
- 4 pairs of types, where a type in marzano_core.api uses a type in grit_util.ranges.
- The types involved
marzano_core.api.EntireFile→grit_util.ranges.ByteRangemarzano_core.api.EntireFile→grit_util.ranges.VariableMatchmarzano_core.api.Match→grit_util.ranges.VariableMatchmarzano_core.api.PatternInfo→grit_util.ranges.VariableMatch
- Direction
- marzano_core.api uses grit_util.ranges, so a change to grit_util.ranges can break marzano_core.api, while a change to marzano_core.api can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_core.api uses a module listed above it, which is the healthy direction.
24→8 marzano_core.api uses grit_pattern_matcher.pattern.range✕
- Connections
- 9 pairs of types, where a type in marzano_core.api uses a type in grit_pattern_matcher.pattern.range.
- The types involved
marzano_core.api.AnalysisLog→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.CreateFile→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.EntireFile→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.FileMatchResult→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.Match→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.MatchResult→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.Message→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.RemoveFile→grit_pattern_matcher.pattern.range.Rangemarzano_core.api.Rewrite→grit_pattern_matcher.pattern.range.Range
- Direction
- marzano_core.api uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break marzano_core.api, while a change to marzano_core.api can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: marzano_core.api uses a module listed above it, which is the healthy direction.
24→23 marzano_core.api uses marzano_core.problem✕
- Connections
- 1 pair of types, where a type in marzano_core.api uses a type in marzano_core.problem.
- The types involved
marzano_core.api.PatternInfo→marzano_core.problem.Problem
- Direction
- marzano_core.api uses marzano_core.problem, so a change to marzano_core.problem can break marzano_core.api, while a change to marzano_core.api can't break marzano_core.problem.
- Position
- Below the diagonal: marzano_core.api uses a module listed above it, which is the healthy direction.
25→8 grit_util.analysis_logs uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in grit_util.analysis_logs uses a type in grit_pattern_matcher.pattern.range.
- The types involved
grit_util.analysis_logs.AnalysisLog→grit_pattern_matcher.pattern.range.Range
- Direction
- grit_util.analysis_logs uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break grit_util.analysis_logs, while a change to grit_util.analysis_logs can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: grit_util.analysis_logs uses a module listed above it, which is the healthy direction.
25→24 grit_util.analysis_logs uses marzano_core.api✕
- Connections
- 1 pair of types, where a type in grit_util.analysis_logs uses a type in marzano_core.api.
- The types involved
grit_util.analysis_logs.AnalysisLogs→marzano_core.api.AnalysisLog
- Direction
- grit_util.analysis_logs uses marzano_core.api, so a change to marzano_core.api can break grit_util.analysis_logs, while a change to grit_util.analysis_logs can't break marzano_core.api.
- Position
- Below the diagonal: grit_util.analysis_logs uses a module listed above it, which is the healthy direction.
26→2 marzano_gritmodule.config uses marzano_gritmodule.fetcher✕
- Connections
- 3 pairs of types, where a type in marzano_gritmodule.config uses a type in marzano_gritmodule.fetcher.
- The types involved
marzano_gritmodule.config.ModuleGritPattern→marzano_gritmodule.fetcher.ModuleRepomarzano_gritmodule.config.ResolvedGritDefinition→marzano_gritmodule.fetcher.ModuleRepomarzano_gritmodule.config.config$module→marzano_gritmodule.fetcher.ModuleRepo
- Direction
- marzano_gritmodule.config uses marzano_gritmodule.fetcher, so a change to marzano_gritmodule.fetcher can break marzano_gritmodule.config, while a change to marzano_gritmodule.config can't break marzano_gritmodule.fetcher.
- Position
- Below the diagonal: marzano_gritmodule.config uses a module listed above it, which is the healthy direction.
26→8 marzano_gritmodule.config uses grit_pattern_matcher.pattern.range✕
- Connections
- 2 pairs of types, where a type in marzano_gritmodule.config uses a type in grit_pattern_matcher.pattern.range.
- The types involved
marzano_gritmodule.config.GritDefinitionConfig→grit_pattern_matcher.pattern.range.Rangemarzano_gritmodule.config.GritPatternSample→grit_pattern_matcher.pattern.range.Range
- Direction
- marzano_gritmodule.config uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break marzano_gritmodule.config, while a change to marzano_gritmodule.config can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: marzano_gritmodule.config uses a module listed above it, which is the healthy direction.
26→16 marzano_gritmodule.config uses marzano_language.target_language✕
- Connections
- 2 pairs of types, where a type in marzano_gritmodule.config uses a type in marzano_language.target_language.
- The types involved
marzano_gritmodule.config.ModuleGritPattern→marzano_language.target_language.PatternLanguagemarzano_gritmodule.config.ResolvedGritDefinition→marzano_language.target_language.PatternLanguage
- Direction
- marzano_gritmodule.config uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_gritmodule.config, while a change to marzano_gritmodule.config can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_gritmodule.config uses a module listed above it, which is the healthy direction.
26→24 marzano_gritmodule.config uses marzano_core.api✕
- Connections
- 2 pairs of types, where a type in marzano_gritmodule.config uses a type in marzano_core.api.
- The types involved
marzano_gritmodule.config.GritPatternMetadata→marzano_core.api.EnforcementLevelmarzano_gritmodule.config.ResolvedGritDefinition→marzano_core.api.EnforcementLevel
- Direction
- marzano_gritmodule.config uses marzano_core.api, so a change to marzano_core.api can break marzano_gritmodule.config, while a change to marzano_gritmodule.config can't break marzano_core.api.
- Position
- Below the diagonal: marzano_gritmodule.config uses a module listed above it, which is the healthy direction.
27→16 marzano_messenger.emit uses marzano_language.target_language✕
- Connections
- 1 pair of types, where a type in marzano_messenger.emit uses a type in marzano_language.target_language.
- The types involved
marzano_messenger.emit.Messager→marzano_language.target_language.TargetLanguage
- Direction
- marzano_messenger.emit uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_messenger.emit, while a change to marzano_messenger.emit can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_messenger.emit uses a module listed above it, which is the healthy direction.
27→24 marzano_messenger.emit uses marzano_core.api✕
- Connections
- 2 pairs of types, where a type in marzano_messenger.emit uses a type in marzano_core.api.
- The types involved
marzano_messenger.emit.Messager→marzano_core.api.MatchResultmarzano_messenger.emit.emit$module→marzano_core.api.MatchResult
- Direction
- marzano_messenger.emit uses marzano_core.api, so a change to marzano_core.api can break marzano_messenger.emit, while a change to marzano_messenger.emit can't break marzano_core.api.
- Position
- Below the diagonal: marzano_messenger.emit uses a module listed above it, which is the healthy direction.
28→6 grit_pattern_matcher.pattern.variable uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_util.ranges.
- The types involved
grit_pattern_matcher.pattern.variable.VariableSource→grit_util.ranges.ByteRange
- Direction
- grit_pattern_matcher.pattern.variable uses grit_util.ranges, so a change to grit_util.ranges can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_util.ranges.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.variable uses a module listed above it, which is the healthy direction.
28→11 grit_pattern_matcher.pattern.variable uses grit_util.language✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.pattern.variable.Variable→grit_util.language.Languagegrit_pattern_matcher.pattern.variable.variable$module→grit_util.language.Language
- Direction
- grit_pattern_matcher.pattern.variable uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.variable uses a module listed above it, which is the healthy direction.
28→25 grit_pattern_matcher.pattern.variable uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.variable.Variable→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.variable uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.variable uses a module listed above it, which is the healthy direction.
28→29 grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.pattern.state part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.variable.Variable→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.variable.variable$module→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_pattern_matcher.pattern.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→31 grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.variable.Variable→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→33 grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.variable.Variable→grit_pattern_matcher.pattern.patterns.Matchergrit_pattern_matcher.pattern.variable.Variable→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_pattern_matcher.pattern.patterns.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→37 grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.variable.Variable→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→39 grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.binding part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.variable uses a type in grit_pattern_matcher.binding.
- The types involved
grit_pattern_matcher.pattern.variable.VariableMirror→grit_pattern_matcher.binding.Binding
- Direction
- grit_pattern_matcher.pattern.variable uses grit_pattern_matcher.binding, so a change to grit_pattern_matcher.binding can break grit_pattern_matcher.pattern.variable, while a change to grit_pattern_matcher.pattern.variable can't break grit_pattern_matcher.binding.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→10 grit_pattern_matcher.pattern.state uses grit_util.code_range✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.state uses a type in grit_util.code_range.
- The types involved
grit_pattern_matcher.pattern.state.state$module→grit_util.code_range.CodeRange
- Direction
- grit_pattern_matcher.pattern.state uses grit_util.code_range, so a change to grit_util.code_range can break grit_pattern_matcher.pattern.state, while a change to grit_pattern_matcher.pattern.state can't break grit_util.code_range.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.state uses a module listed above it, which is the healthy direction.
29→11 grit_pattern_matcher.pattern.state uses grit_util.language✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.state uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.pattern.state.State→grit_util.language.Languagegrit_pattern_matcher.pattern.state.state$module→grit_util.language.Language
- Direction
- grit_pattern_matcher.pattern.state uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.pattern.state, while a change to grit_pattern_matcher.pattern.state can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.state uses a module listed above it, which is the healthy direction.
29→25 grit_pattern_matcher.pattern.state uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.state uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.state.state$module→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.state uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.state, while a change to grit_pattern_matcher.pattern.state can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.state uses a module listed above it, which is the healthy direction.
29→28 grit_pattern_matcher.pattern.state uses grit_pattern_matcher.pattern.variable✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.state uses a type in grit_pattern_matcher.pattern.variable.
- The types involved
grit_pattern_matcher.pattern.state.State→grit_pattern_matcher.pattern.variable.Variablegrit_pattern_matcher.pattern.state.State→grit_pattern_matcher.pattern.variable.VariableScope
- Direction
- grit_pattern_matcher.pattern.state uses grit_pattern_matcher.pattern.variable, so a change to grit_pattern_matcher.pattern.variable can break grit_pattern_matcher.pattern.state, while a change to grit_pattern_matcher.pattern.state can't break grit_pattern_matcher.pattern.variable.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.state uses a module listed above it, which is the healthy direction.
29→30 grit_pattern_matcher.pattern.state uses grit_pattern_matcher.effects part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.state uses a type in grit_pattern_matcher.effects.
- The types involved
grit_pattern_matcher.pattern.state.EffectRange→grit_pattern_matcher.effects.Effectgrit_pattern_matcher.pattern.state.State→grit_pattern_matcher.effects.Effect
- Direction
- grit_pattern_matcher.pattern.state uses grit_pattern_matcher.effects, so a change to grit_pattern_matcher.effects can break grit_pattern_matcher.pattern.state, while a change to grit_pattern_matcher.pattern.state can't break grit_pattern_matcher.effects.
- 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→29 grit_pattern_matcher.effects uses grit_pattern_matcher.pattern.state✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.effects uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.effects.effects$module→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.effects uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.effects, while a change to grit_pattern_matcher.effects can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.effects uses a module listed above it, which is the healthy direction.
30→31 grit_pattern_matcher.effects uses grit_pattern_matcher.pattern.resolved_pattern part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.effects uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.effects.Effect→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPatterngrit_pattern_matcher.effects.effects$module→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.effects uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.effects, while a change to grit_pattern_matcher.effects can't break grit_pattern_matcher.pattern.resolved_pattern.
- 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→37 grit_pattern_matcher.effects uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.effects uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.effects.effects$module→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.effects uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.effects, while a change to grit_pattern_matcher.effects can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→39 grit_pattern_matcher.effects uses grit_pattern_matcher.binding part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.effects uses a type in grit_pattern_matcher.binding.
- The types involved
grit_pattern_matcher.effects.Effect→grit_pattern_matcher.binding.Binding
- Direction
- grit_pattern_matcher.effects uses grit_pattern_matcher.binding, so a change to grit_pattern_matcher.binding can break grit_pattern_matcher.effects, while a change to grit_pattern_matcher.effects can't break grit_pattern_matcher.binding.
- 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→6 grit_pattern_matcher.pattern.resolved_pattern uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_util.ranges.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_util.ranges.ByteRange
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_util.ranges, so a change to grit_util.ranges can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_util.ranges.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→8 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.pattern.range.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.range.Range
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→11 grit_pattern_matcher.pattern.resolved_pattern uses grit_util.language✕
- Connections
- 5 pairs of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.File→grit_util.language.Languagegrit_pattern_matcher.pattern.resolved_pattern.JoinFn→grit_util.language.Languagegrit_pattern_matcher.pattern.resolved_pattern.LazyBuiltIn→grit_util.language.Languagegrit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_util.language.Languagegrit_pattern_matcher.pattern.resolved_pattern.ResolvedSnippet→grit_util.language.Language
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→12 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.accessor✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.pattern.accessor.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.accessor.Accessor
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.accessor, so a change to grit_pattern_matcher.pattern.accessor can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.pattern.accessor.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→13 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.list_index✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.pattern.list_index.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.list_index.ListIndex
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.list_index, so a change to grit_pattern_matcher.pattern.list_index can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.pattern.list_index.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→25 grit_pattern_matcher.pattern.resolved_pattern uses grit_util.analysis_logs✕
- Connections
- 4 pairs of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.JoinFn→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.resolved_pattern.LazyBuiltIn→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.resolved_pattern.ResolvedSnippet→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→29 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.state✕
- Connections
- 8 pairs of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.File→grit_pattern_matcher.pattern.state.FileRegistrygrit_pattern_matcher.pattern.resolved_pattern.JoinFn→grit_pattern_matcher.pattern.state.FileRegistrygrit_pattern_matcher.pattern.resolved_pattern.LazyBuiltIn→grit_pattern_matcher.pattern.state.FileRegistrygrit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.state.FilePtrgrit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.state.FileRegistrygrit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.resolved_pattern.ResolvedSnippet→grit_pattern_matcher.pattern.state.FileRegistrygrit_pattern_matcher.pattern.resolved_pattern.ResolvedSnippet→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→30 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.effects✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.effects.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.effects.Effect
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.effects, so a change to grit_pattern_matcher.effects can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.effects.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.resolved_pattern uses a module listed above it, which is the healthy direction.
31→32 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.dynamic_snippet part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.pattern.dynamic_snippet.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.dynamic_snippet.DynamicPatterngrit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.dynamic_snippet.DynamicSnippet
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.dynamic_snippet, so a change to grit_pattern_matcher.pattern.dynamic_snippet can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.pattern.dynamic_snippet.
- 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→33 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.pattern.patterns.
- 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→37 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.context part of a loop✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→39 grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.binding part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.resolved_pattern uses a type in grit_pattern_matcher.binding.
- The types involved
grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern→grit_pattern_matcher.binding.Bindinggrit_pattern_matcher.pattern.resolved_pattern.ResolvedSnippet→grit_pattern_matcher.binding.Binding
- Direction
- grit_pattern_matcher.pattern.resolved_pattern uses grit_pattern_matcher.binding, so a change to grit_pattern_matcher.binding can break grit_pattern_matcher.pattern.resolved_pattern, while a change to grit_pattern_matcher.pattern.resolved_pattern can't break grit_pattern_matcher.binding.
- 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→3 grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.iter_pattern✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.dynamic_snippet uses a type in grit_pattern_matcher.pattern.iter_pattern.
- The types involved
grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicate
- Direction
- grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.iter_pattern, so a change to grit_pattern_matcher.pattern.iter_pattern can break grit_pattern_matcher.pattern.dynamic_snippet, while a change to grit_pattern_matcher.pattern.dynamic_snippet can't break grit_pattern_matcher.pattern.iter_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.dynamic_snippet uses a module listed above it, which is the healthy direction.
32→25 grit_pattern_matcher.pattern.dynamic_snippet uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.dynamic_snippet uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.dynamic_snippet uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.dynamic_snippet, while a change to grit_pattern_matcher.pattern.dynamic_snippet can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.dynamic_snippet uses a module listed above it, which is the healthy direction.
32→29 grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.state✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.dynamic_snippet uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.dynamic_snippet, while a change to grit_pattern_matcher.pattern.dynamic_snippet can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.dynamic_snippet uses a module listed above it, which is the healthy direction.
32→31 grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.resolved_pattern✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.dynamic_snippet uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.dynamic_snippet, while a change to grit_pattern_matcher.pattern.dynamic_snippet can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.dynamic_snippet uses a module listed above it, which is the healthy direction.
32→33 grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.patterns part of a loop✕
- Connections
- 3 pairs of types, where a type in grit_pattern_matcher.pattern.dynamic_snippet uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.pattern.patterns.Matchergrit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.pattern.patterns.PatternNamegrit_pattern_matcher.pattern.dynamic_snippet.DynamicSnippet→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.dynamic_snippet, while a change to grit_pattern_matcher.pattern.dynamic_snippet can't break grit_pattern_matcher.pattern.patterns.
- 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→37 grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.context part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.dynamic_snippet uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern→grit_pattern_matcher.context.StaticDefinitions
- Direction
- grit_pattern_matcher.pattern.dynamic_snippet uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.dynamic_snippet, while a change to grit_pattern_matcher.pattern.dynamic_snippet can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→3 grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.iter_pattern✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.patterns uses a type in grit_pattern_matcher.pattern.iter_pattern.
- The types involved
grit_pattern_matcher.pattern.patterns.Pattern→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicategrit_pattern_matcher.pattern.patterns.Pattern→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicateIterator
- Direction
- grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.iter_pattern, so a change to grit_pattern_matcher.pattern.iter_pattern can break grit_pattern_matcher.pattern.patterns, while a change to grit_pattern_matcher.pattern.patterns can't break grit_pattern_matcher.pattern.iter_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.patterns uses a module listed above it, which is the healthy direction.
33→25 grit_pattern_matcher.pattern.patterns uses grit_util.analysis_logs✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.patterns uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.patterns.Matcher→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.patterns.Pattern→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.patterns uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.patterns, while a change to grit_pattern_matcher.pattern.patterns can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.patterns uses a module listed above it, which is the healthy direction.
33→29 grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.state✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.patterns uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.patterns.Matcher→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.patterns.Pattern→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.patterns, while a change to grit_pattern_matcher.pattern.patterns can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.patterns uses a module listed above it, which is the healthy direction.
33→31 grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.resolved_pattern✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.patterns uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.patterns.Matcher→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPatterngrit_pattern_matcher.pattern.patterns.Pattern→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.patterns, while a change to grit_pattern_matcher.pattern.patterns can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.patterns uses a module listed above it, which is the healthy direction.
33→32 grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.dynamic_snippet✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.patterns uses a type in grit_pattern_matcher.pattern.dynamic_snippet.
- The types involved
grit_pattern_matcher.pattern.patterns.CodeSnippet→grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern
- Direction
- grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.pattern.dynamic_snippet, so a change to grit_pattern_matcher.pattern.dynamic_snippet can break grit_pattern_matcher.pattern.patterns, while a change to grit_pattern_matcher.pattern.patterns can't break grit_pattern_matcher.pattern.dynamic_snippet.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.patterns uses a module listed above it, which is the healthy direction.
33→37 grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.context part of a loop✕
- Connections
- 3 pairs of types, where a type in grit_pattern_matcher.pattern.patterns uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.patterns.Matcher→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.patterns.Pattern→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.patterns.Pattern→grit_pattern_matcher.context.StaticDefinitions
- Direction
- grit_pattern_matcher.pattern.patterns uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.patterns, while a change to grit_pattern_matcher.pattern.patterns can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→19 grit_pattern_matcher.pattern.functions uses marzano_core.marzano_context✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.functions uses a type in marzano_core.marzano_context.
- The types involved
grit_pattern_matcher.pattern.functions.CallForeignFunction→marzano_core.marzano_context.MarzanoContext
- Direction
- grit_pattern_matcher.pattern.functions uses marzano_core.marzano_context, so a change to marzano_core.marzano_context can break grit_pattern_matcher.pattern.functions, while a change to grit_pattern_matcher.pattern.functions can't break marzano_core.marzano_context.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.functions uses a module listed above it, which is the healthy direction.
34→25 grit_pattern_matcher.pattern.functions uses grit_util.analysis_logs✕
- Connections
- 4 pairs of types, where a type in grit_pattern_matcher.pattern.functions uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.functions.CallForeignFunction→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.functions.CallFunction→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.functions.Evaluator→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.functions.GritCall→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.functions uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.functions, while a change to grit_pattern_matcher.pattern.functions can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.functions uses a module listed above it, which is the healthy direction.
34→29 grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.pattern.state✕
- Connections
- 4 pairs of types, where a type in grit_pattern_matcher.pattern.functions uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.functions.CallForeignFunction→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.functions.CallFunction→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.functions.Evaluator→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.functions.GritCall→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.functions, while a change to grit_pattern_matcher.pattern.functions can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.functions uses a module listed above it, which is the healthy direction.
34→31 grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.pattern.resolved_pattern✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.functions uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.pattern.functions.FuncEvaluation→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.pattern.functions, while a change to grit_pattern_matcher.pattern.functions can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.functions uses a module listed above it, which is the healthy direction.
34→33 grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.pattern.patterns✕
- Connections
- 4 pairs of types, where a type in grit_pattern_matcher.pattern.functions uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.functions.CallForeignFunction→grit_pattern_matcher.pattern.patterns.Patterngrit_pattern_matcher.pattern.functions.CallForeignFunction→grit_pattern_matcher.pattern.patterns.PatternNamegrit_pattern_matcher.pattern.functions.CallFunction→grit_pattern_matcher.pattern.patterns.Patterngrit_pattern_matcher.pattern.functions.CallFunction→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.functions, while a change to grit_pattern_matcher.pattern.functions can't break grit_pattern_matcher.pattern.patterns.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.functions uses a module listed above it, which is the healthy direction.
34→37 grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.context part of a loop✕
- Connections
- 3 pairs of types, where a type in grit_pattern_matcher.pattern.functions uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.functions.CallFunction→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.functions.Evaluator→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.functions.GritCall→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.functions uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.functions, while a change to grit_pattern_matcher.pattern.functions can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→3 grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.iter_pattern✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.predicates uses a type in grit_pattern_matcher.pattern.iter_pattern.
- The types involved
grit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicategrit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicateIterator
- Direction
- grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.iter_pattern, so a change to grit_pattern_matcher.pattern.iter_pattern can break grit_pattern_matcher.pattern.predicates, while a change to grit_pattern_matcher.pattern.predicates can't break grit_pattern_matcher.pattern.iter_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.predicates uses a module listed above it, which is the healthy direction.
35→25 grit_pattern_matcher.pattern.predicates uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicates uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.predicates.Predicate→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.predicates uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.predicates, while a change to grit_pattern_matcher.pattern.predicates can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.predicates uses a module listed above it, which is the healthy direction.
35→29 grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.state✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicates uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.predicates, while a change to grit_pattern_matcher.pattern.predicates can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.predicates uses a module listed above it, which is the healthy direction.
35→33 grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.patterns✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicates uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.pattern.predicates, while a change to grit_pattern_matcher.pattern.predicates can't break grit_pattern_matcher.pattern.patterns.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.predicates uses a module listed above it, which is the healthy direction.
35→34 grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.functions✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.predicates uses a type in grit_pattern_matcher.pattern.functions.
- The types involved
grit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.pattern.functions.Evaluator
- Direction
- grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.pattern.functions, so a change to grit_pattern_matcher.pattern.functions can break grit_pattern_matcher.pattern.predicates, while a change to grit_pattern_matcher.pattern.predicates can't break grit_pattern_matcher.pattern.functions.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.predicates uses a module listed above it, which is the healthy direction.
35→37 grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.context part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.predicates uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.predicates.Predicate→grit_pattern_matcher.context.StaticDefinitions
- Direction
- grit_pattern_matcher.pattern.predicates uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.predicates, while a change to grit_pattern_matcher.pattern.predicates can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→25 grit_pattern_matcher.pattern.function_definition uses grit_util.analysis_logs✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.function_definition uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.pattern.function_definition.FunctionDefinition→grit_util.analysis_logs.AnalysisLogsgrit_pattern_matcher.pattern.function_definition.GritFunctionDefinition→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.pattern.function_definition uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.pattern.function_definition, while a change to grit_pattern_matcher.pattern.function_definition can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.function_definition uses a module listed above it, which is the healthy direction.
36→29 grit_pattern_matcher.pattern.function_definition uses grit_pattern_matcher.pattern.state✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.function_definition uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.pattern.function_definition.FunctionDefinition→grit_pattern_matcher.pattern.state.Stategrit_pattern_matcher.pattern.function_definition.GritFunctionDefinition→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.pattern.function_definition uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.pattern.function_definition, while a change to grit_pattern_matcher.pattern.function_definition can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.function_definition uses a module listed above it, which is the healthy direction.
36→35 grit_pattern_matcher.pattern.function_definition uses grit_pattern_matcher.pattern.predicates✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.pattern.function_definition uses a type in grit_pattern_matcher.pattern.predicates.
- The types involved
grit_pattern_matcher.pattern.function_definition.GritFunctionDefinition→grit_pattern_matcher.pattern.predicates.Predicate
- Direction
- grit_pattern_matcher.pattern.function_definition uses grit_pattern_matcher.pattern.predicates, so a change to grit_pattern_matcher.pattern.predicates can break grit_pattern_matcher.pattern.function_definition, while a change to grit_pattern_matcher.pattern.function_definition can't break grit_pattern_matcher.pattern.predicates.
- Position
- Below the diagonal: grit_pattern_matcher.pattern.function_definition uses a module listed above it, which is the healthy direction.
36→37 grit_pattern_matcher.pattern.function_definition uses grit_pattern_matcher.context part of a loop✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.pattern.function_definition uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.pattern.function_definition.FunctionDefinition→grit_pattern_matcher.context.ExecContextgrit_pattern_matcher.pattern.function_definition.GritFunctionDefinition→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.pattern.function_definition uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.pattern.function_definition, while a change to grit_pattern_matcher.pattern.function_definition can't break grit_pattern_matcher.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→4 grit_pattern_matcher.context uses grit_pattern_matcher.pattern.pattern_definition✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_pattern_matcher.pattern.pattern_definition.
- The types involved
grit_pattern_matcher.context.StaticDefinitions→grit_pattern_matcher.pattern.pattern_definition.PatternDefinition
- Direction
- grit_pattern_matcher.context uses grit_pattern_matcher.pattern.pattern_definition, so a change to grit_pattern_matcher.pattern.pattern_definition can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_pattern_matcher.pattern.pattern_definition.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→5 grit_pattern_matcher.context uses grit_pattern_matcher.pattern.predicate_definition✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_pattern_matcher.pattern.predicate_definition.
- The types involved
grit_pattern_matcher.context.StaticDefinitions→grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition
- Direction
- grit_pattern_matcher.context uses grit_pattern_matcher.pattern.predicate_definition, so a change to grit_pattern_matcher.pattern.predicate_definition can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_pattern_matcher.pattern.predicate_definition.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→11 grit_pattern_matcher.context uses grit_util.language✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.context.ExecContext→grit_util.language.Language
- Direction
- grit_pattern_matcher.context uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→25 grit_pattern_matcher.context uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.context.ExecContext→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.context uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→29 grit_pattern_matcher.context uses grit_pattern_matcher.pattern.state✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.context.ExecContext→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.context uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→31 grit_pattern_matcher.context uses grit_pattern_matcher.pattern.resolved_pattern✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.context uses a type in grit_pattern_matcher.pattern.resolved_pattern.
- The types involved
grit_pattern_matcher.context.ExecContext→grit_pattern_matcher.pattern.resolved_pattern.Filegrit_pattern_matcher.context.ExecContext→grit_pattern_matcher.pattern.resolved_pattern.ResolvedPattern
- Direction
- grit_pattern_matcher.context uses grit_pattern_matcher.pattern.resolved_pattern, so a change to grit_pattern_matcher.pattern.resolved_pattern can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_pattern_matcher.pattern.resolved_pattern.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→33 grit_pattern_matcher.context uses grit_pattern_matcher.pattern.patterns✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.context.ExecContext→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- grit_pattern_matcher.context uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_pattern_matcher.pattern.patterns.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
37→36 grit_pattern_matcher.context uses grit_pattern_matcher.pattern.function_definition✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.context uses a type in grit_pattern_matcher.pattern.function_definition.
- The types involved
grit_pattern_matcher.context.StaticDefinitions→grit_pattern_matcher.pattern.function_definition.GritFunctionDefinition
- Direction
- grit_pattern_matcher.context uses grit_pattern_matcher.pattern.function_definition, so a change to grit_pattern_matcher.pattern.function_definition can break grit_pattern_matcher.context, while a change to grit_pattern_matcher.context can't break grit_pattern_matcher.pattern.function_definition.
- Position
- Below the diagonal: grit_pattern_matcher.context uses a module listed above it, which is the healthy direction.
38→4 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.pattern_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.pattern_definition.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.pattern_definition.PatternDefinition
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.pattern_definition, so a change to grit_pattern_matcher.pattern.pattern_definition can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.pattern_definition.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→5 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.predicate_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.predicate_definition.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.predicate_definition.PredicateDefinition
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.predicate_definition, so a change to grit_pattern_matcher.pattern.predicate_definition can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.predicate_definition.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→6 marzano_core.pattern_compiler.builder uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_util.ranges.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_util.ranges.FileRange
- Direction
- marzano_core.pattern_compiler.builder uses grit_util.ranges, so a change to grit_util.ranges can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_util.ranges.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→14 marzano_core.pattern_compiler.builder uses marzano_language.language✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in marzano_language.language.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→marzano_language.language.Tree
- Direction
- marzano_core.pattern_compiler.builder uses marzano_language.language, so a change to marzano_language.language can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break marzano_language.language.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→16 marzano_core.pattern_compiler.builder uses marzano_language.target_language✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in marzano_language.target_language.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→marzano_language.target_language.TargetLanguage
- Direction
- marzano_core.pattern_compiler.builder uses marzano_language.target_language, so a change to marzano_language.target_language can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break marzano_language.target_language.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→20 marzano_core.pattern_compiler.builder uses marzano_core.built_in_functions✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in marzano_core.built_in_functions.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→marzano_core.built_in_functions.BuiltIns
- Direction
- marzano_core.pattern_compiler.builder uses marzano_core.built_in_functions, so a change to marzano_core.built_in_functions can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break marzano_core.built_in_functions.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→25 marzano_core.pattern_compiler.builder uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.pattern_compiler.builder uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_util.analysis_logs.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→28 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.variable✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.variable.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.variable.VariableSource
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.variable, so a change to grit_pattern_matcher.pattern.variable can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.variable.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→32 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.dynamic_snippet✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.dynamic_snippet.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.dynamic_snippet.DynamicPattern
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.dynamic_snippet, so a change to grit_pattern_matcher.pattern.dynamic_snippet can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.dynamic_snippet.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→33 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.patterns✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.patterns.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→35 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.predicates✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.predicates.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.predicates.Predicate
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.predicates, so a change to grit_pattern_matcher.pattern.predicates can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.predicates.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
38→36 marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.function_definition✕
- Connections
- 1 pair of types, where a type in marzano_core.pattern_compiler.builder uses a type in grit_pattern_matcher.pattern.function_definition.
- The types involved
marzano_core.pattern_compiler.builder.CompiledPatternBuilder→grit_pattern_matcher.pattern.function_definition.GritFunctionDefinition
- Direction
- marzano_core.pattern_compiler.builder uses grit_pattern_matcher.pattern.function_definition, so a change to grit_pattern_matcher.pattern.function_definition can break marzano_core.pattern_compiler.builder, while a change to marzano_core.pattern_compiler.builder can't break grit_pattern_matcher.pattern.function_definition.
- Position
- Below the diagonal: marzano_core.pattern_compiler.builder uses a module listed above it, which is the healthy direction.
39→6 grit_pattern_matcher.binding uses grit_util.ranges✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_util.ranges.
- The types involved
grit_pattern_matcher.binding.Binding→grit_util.ranges.ByteRange
- Direction
- grit_pattern_matcher.binding uses grit_util.ranges, so a change to grit_util.ranges can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_util.ranges.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→8 grit_pattern_matcher.binding uses grit_pattern_matcher.pattern.range✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_pattern_matcher.pattern.range.
- The types involved
grit_pattern_matcher.binding.Binding→grit_pattern_matcher.pattern.range.Range
- Direction
- grit_pattern_matcher.binding uses grit_pattern_matcher.pattern.range, so a change to grit_pattern_matcher.pattern.range can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_pattern_matcher.pattern.range.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→10 grit_pattern_matcher.binding uses grit_util.code_range✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_util.code_range.
- The types involved
grit_pattern_matcher.binding.Binding→grit_util.code_range.CodeRange
- Direction
- grit_pattern_matcher.binding uses grit_util.code_range, so a change to grit_util.code_range can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_util.code_range.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→11 grit_pattern_matcher.binding uses grit_util.language✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_util.language.
- The types involved
grit_pattern_matcher.binding.Binding→grit_util.language.Language
- Direction
- grit_pattern_matcher.binding uses grit_util.language, so a change to grit_util.language can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_util.language.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→25 grit_pattern_matcher.binding uses grit_util.analysis_logs✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_util.analysis_logs.
- The types involved
grit_pattern_matcher.binding.Binding→grit_util.analysis_logs.AnalysisLogs
- Direction
- grit_pattern_matcher.binding uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_util.analysis_logs.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→29 grit_pattern_matcher.binding uses grit_pattern_matcher.pattern.state✕
- Connections
- 2 pairs of types, where a type in grit_pattern_matcher.binding uses a type in grit_pattern_matcher.pattern.state.
- The types involved
grit_pattern_matcher.binding.Binding→grit_pattern_matcher.pattern.state.FileRegistrygrit_pattern_matcher.binding.Binding→grit_pattern_matcher.pattern.state.State
- Direction
- grit_pattern_matcher.binding uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→33 grit_pattern_matcher.binding uses grit_pattern_matcher.pattern.patterns✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
grit_pattern_matcher.binding.Binding→grit_pattern_matcher.pattern.patterns.Pattern
- Direction
- grit_pattern_matcher.binding uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_pattern_matcher.pattern.patterns.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
39→37 grit_pattern_matcher.binding uses grit_pattern_matcher.context✕
- Connections
- 1 pair of types, where a type in grit_pattern_matcher.binding uses a type in grit_pattern_matcher.context.
- The types involved
grit_pattern_matcher.binding.Binding→grit_pattern_matcher.context.ExecContext
- Direction
- grit_pattern_matcher.binding uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break grit_pattern_matcher.binding, while a change to grit_pattern_matcher.binding can't break grit_pattern_matcher.context.
- Position
- Below the diagonal: grit_pattern_matcher.binding uses a module listed above it, which is the healthy direction.
40→3 marzano_core.ast_node uses grit_pattern_matcher.pattern.iter_pattern✕
- Connections
- 1 pair of types, where a type in marzano_core.ast_node uses a type in grit_pattern_matcher.pattern.iter_pattern.
- The types involved
marzano_core.ast_node.ASTNode→grit_pattern_matcher.pattern.iter_pattern.PatternOrPredicate
- Direction
- marzano_core.ast_node uses grit_pattern_matcher.pattern.iter_pattern, so a change to grit_pattern_matcher.pattern.iter_pattern can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break grit_pattern_matcher.pattern.iter_pattern.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→9 marzano_core.ast_node uses marzano_util.node_with_source✕
- Connections
- 1 pair of types, where a type in marzano_core.ast_node uses a type in marzano_util.node_with_source.
- The types involved
marzano_core.ast_node.ASTNode→marzano_util.node_with_source.NodeWithSource
- Direction
- marzano_core.ast_node uses marzano_util.node_with_source, so a change to marzano_util.node_with_source can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break marzano_util.node_with_source.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→14 marzano_core.ast_node uses marzano_language.language✕
- Connections
- 1 pair of types, where a type in marzano_core.ast_node uses a type in marzano_language.language.
- The types involved
marzano_core.ast_node.AstLeafNode→marzano_language.language.LeafEquivalenceClass
- Direction
- marzano_core.ast_node uses marzano_language.language, so a change to marzano_language.language can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break marzano_language.language.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→18 marzano_core.ast_node uses marzano_core.marzano_resolved_pattern✕
- Connections
- 2 pairs of types, where a type in marzano_core.ast_node uses a type in marzano_core.marzano_resolved_pattern.
- The types involved
marzano_core.ast_node.ASTNode→marzano_core.marzano_resolved_pattern.MarzanoResolvedPatternmarzano_core.ast_node.AstLeafNode→marzano_core.marzano_resolved_pattern.MarzanoResolvedPattern
- Direction
- marzano_core.ast_node uses marzano_core.marzano_resolved_pattern, so a change to marzano_core.marzano_resolved_pattern can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break marzano_core.marzano_resolved_pattern.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→19 marzano_core.ast_node uses marzano_core.marzano_context✕
- Connections
- 2 pairs of types, where a type in marzano_core.ast_node uses a type in marzano_core.marzano_context.
- The types involved
marzano_core.ast_node.ASTNode→marzano_core.marzano_context.MarzanoContextmarzano_core.ast_node.AstLeafNode→marzano_core.marzano_context.MarzanoContext
- Direction
- marzano_core.ast_node uses marzano_core.marzano_context, so a change to marzano_core.marzano_context can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break marzano_core.marzano_context.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→25 marzano_core.ast_node uses grit_util.analysis_logs✕
- Connections
- 2 pairs of types, where a type in marzano_core.ast_node uses a type in grit_util.analysis_logs.
- The types involved
marzano_core.ast_node.ASTNode→grit_util.analysis_logs.AnalysisLogsmarzano_core.ast_node.AstLeafNode→grit_util.analysis_logs.AnalysisLogs
- Direction
- marzano_core.ast_node uses grit_util.analysis_logs, so a change to grit_util.analysis_logs can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break grit_util.analysis_logs.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→29 marzano_core.ast_node uses grit_pattern_matcher.pattern.state✕
- Connections
- 2 pairs of types, where a type in marzano_core.ast_node uses a type in grit_pattern_matcher.pattern.state.
- The types involved
marzano_core.ast_node.ASTNode→grit_pattern_matcher.pattern.state.Statemarzano_core.ast_node.AstLeafNode→grit_pattern_matcher.pattern.state.State
- Direction
- marzano_core.ast_node uses grit_pattern_matcher.pattern.state, so a change to grit_pattern_matcher.pattern.state can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break grit_pattern_matcher.pattern.state.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→33 marzano_core.ast_node uses grit_pattern_matcher.pattern.patterns✕
- Connections
- 4 pairs of types, where a type in marzano_core.ast_node uses a type in grit_pattern_matcher.pattern.patterns.
- The types involved
marzano_core.ast_node.ASTNode→grit_pattern_matcher.pattern.patterns.Matchermarzano_core.ast_node.ASTNode→grit_pattern_matcher.pattern.patterns.PatternNamemarzano_core.ast_node.AstLeafNode→grit_pattern_matcher.pattern.patterns.Matchermarzano_core.ast_node.AstLeafNode→grit_pattern_matcher.pattern.patterns.PatternName
- Direction
- marzano_core.ast_node uses grit_pattern_matcher.pattern.patterns, so a change to grit_pattern_matcher.pattern.patterns can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break grit_pattern_matcher.pattern.patterns.
- Position
- Below the diagonal: marzano_core.ast_node uses a module listed above it, which is the healthy direction.
40→37 marzano_core.ast_node uses grit_pattern_matcher.context✕
- Connections
- 1 pair of types, where a type in marzano_core.ast_node uses a type in grit_pattern_matcher.context.
- The types involved
marzano_core.ast_node.ASTNode→grit_pattern_matcher.context.StaticDefinitions
- Direction
- marzano_core.ast_node uses grit_pattern_matcher.context, so a change to grit_pattern_matcher.context can break marzano_core.ast_node, while a change to marzano_core.ast_node can't break grit_pattern_matcher.context.
- Position
- Below the diagonal: marzano_core.ast_node 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 — Domain Modelling
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 104 | High / Critical |
| A05:2025 — Injection | 16 | High / Critical |
Roadmap
First, address immediate stability and security risks by resolving skipped tests, enabling dependency review tooling, and updating end-of-life platform runtimes. Next, refine the public API surface by hiding internal implementation types to prevent breaking changes for consumers. Finally, establish architectural governance by documenting key decisions through Architecture Decision Records.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Skipped test finding(s) in Test Quality — start with napi.spec.mts. | +3.7 pts | Low | Test Quality |
| Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with Generator.csproj, REDACTED, rust-toolchain.toml. | +2.2 pts | Low | Platform End-of-Life |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.8 pts | Low | ADR Quality |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.8 pts | Medium | Security & performance tooling |
| Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +1.2 pts | Low | Dependency Hygiene |
| Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports; Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers. | +1.8 pts | Medium | Library API & versioning |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +1.4 pts | Medium | Nullable reference types |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.6 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/cli/src/result_formatting.rs | 5.7 | Mixed | Cyclomatic Complexity: FormattedResult::fmt (cyclomatic 25) |
| crates/cli/src/commands/apply_pattern.rs | 5.9 | Mixed | Cyclomatic Complexity: marzano_cli::commands::apply_pattern::run_apply_pattern (cyclomatic 39) |
| crates/language/src/js_like.rs | 6.3 | Mixed | Cyclomatic Complexity: marzano_language::js_like::jslike_check_replacements (cyclomatic 20) |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| crates/core/src/inline_snippets.rs | 7.0 | Mixed | Cyclomatic Complexity: marzano_core::inline_snippets::get_deletion_indices (cyclomatic 51) |
| crates/core/src/optimizer/hoist_files.rs | 7.0 | Mixed | Cyclomatic Complexity: marzano_core::optimizer::hoist_files::extract_filename_pattern (cyclomatic 35) |
| crates/core/src/pattern_compiler/auto_wrap.rs | 7.0 | Mixed | Cognitive Complexity: marzano_core::pattern_compiler::auto_wrap::auto_wrap_pattern (cognitive 24) |
| crates/core/src/pattern_compiler/compiler.rs | 7.0 | Mixed | Cognitive Complexity: marzano_core::pattern_compiler::compiler::filter_libs (cognitive 21) |
| crates/gritmodule/src/resolver.rs | 7.0 | Mixed | Cyclomatic Complexity: marzano_gritmodule::resolver::resolve_patterns (cyclomatic 18) |
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. 74 of 74 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 — 74 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, 575 of 596 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half measured 18.7% (bun:test via `npm install --ignore-scripts` (no lockfile) in js/gritql/; node:test in resources/language-metavariables/tree-sitter-c-sharp/: not run). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D10 Test 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 7 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 19 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — 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 reliability NOT SCORED: this repository's production source includes .rs, and the rust executor ran against the .rs half and never executed — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (bun:test via `npm install --ignore-scripts` (no lockfile) in js/gritql/ (6 tests); node:test via `npm ci --ignore-scripts` in resources/language-metavariables/tree-sitter-c-sharp/ (1 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
- D14 License Compliance — 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. This repository declares a Cargo manifest, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares REDACTED, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — 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. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D17 Explicit Debt — 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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .rs (62,896 lines, 90% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 67 task marker(s) (TODO/FIXME/HACK/XXX) across 44 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — 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.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — 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.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- 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), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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
36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was marzano_core::inline_snippets::get_deletion_indices at 51. A further 60 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 MarzanoCodeSnippet::execute at 57 — they are counted neither in the figure above nor in this dimension's score. 10 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: crates/core/src/marzano_code_snippet.rs (MarzanoCodeSnippet::execute at 57), crates/grit-pattern-matcher/src/pattern/iter_pattern.rs (Pattern::children at 56), crates/grit-pattern-matcher/src/pattern/patterns.rs (Pattern::execute at 54), crates/core/src/pattern_compiler/pattern_compiler.rs (PatternCompiler::from_node_with_rhs at 49), crates/gritmodule/src/patterns_directory.rs (PatternsDirectory::get_language_directory_mut at 25), and 5 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 36 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with marzano_core::inline_snippets::get_deletion_indices (cyclomatic 51), marzano_cli::commands::check::run_check (cyclomatic 44), marzano_cli::commands::run_command (cyclomatic 39). — 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 36 together lifts Cyclomatic Complexity from 6.7 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
71 method(s) exceeded the cognitive complexity threshold of 15; the worst was marzano_core::inline_snippets::get_deletion_indices at 113.
What to do
- Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with marzano_core::inline_snippets::get_deletion_indices (cognitive 113), marzano_gritmodule::formatting::format_temp_dir (cognitive 84), marzano_cli::commands::check::run_check (cognitive 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 5.1 to about 6.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
30 god class(es) detected.
What to do
- Resolve the 12 FunctionTooLong finding(s) in God Classes — start with testing.rs (2), apply_pattern.rs, check.rs. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 9 MethodTooLong finding(s) in God Classes — start with marzano_context.rs, contains.rs, notebooks.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 FileTooLong finding(s) in God Classes — start with marzano_resolved_pattern.rs, target_language.rs, api.rs. — One of this dimension's main actionable groups (7 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
88 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 12 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with compiler.rs (3), binding.rs (2), analysis.rs. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 10 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with match.rs (2), workflows_watch.rs, inline_snippets.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with auto_wrap.rs (2), marzano_resolved_pattern.rs, accumulate_compiler.rs. — One of this dimension's main actionable groups (7 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
32 production modules (Cargo+npm+Python), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 16 of the 32 (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 marzano-lsp 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)
2 of 109 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with result_formatting.rs, pattern_sdk.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1030 test methods: 854 unit, 176 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 7 `it`/`test` case(s) across 2 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 998 `#[test]` function(s) across 103 file(s) declaring at least one; its unit/integration split is Cargo's own — 15 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 7 test function(s) across 4 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 18 test case(s) across 7 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 7 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D10 · Test Quality
1 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 7 tests. Measured on the JavaScript/TypeScript suite only — at least 19 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 1 Skipped test finding(s) in Test Quality — start with napi.spec.mts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
1 outdated, 0 author-deprecated direct Go module(s), 7 pinning or checksum defect(s). 6 of 6 direct requirement(s) were graded against proxy.golang.org (0 not served there, 4 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 No go.sum committed (resources/language-metavariables/tree-sitter-java/b… finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No go.sum committed (resources/language-metavariables/tree-sitter-kotlin… finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- 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 29 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 29 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Cargo manifest, REDACTED and a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/cli/src/result_formatting.rs. Counted over 183 of the 340 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted debt markers + 0 dead symbols across 149 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .rs (90% of production source) was not read, and carries at least 67 uncounted task marker(s) in 44 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 36 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 9 high, 7 medium, 0 low. 1 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 7 file(s) — `crates/cli_bin/fixtures/concourse/foo.yaml`, `crates/cli_bin/fixtures/invalid_extensions/some_folder/file4.js.py` (line 1, line 2), `crates/cli_bin/fixtures/malformed.js` (line 1), `crates/cli_bin/fixtures/misc/many_problems.js` (line 2, line 3, line 6, …), `crates/cli_bin/fixtures/test_patterns/class_declaration/expected/class.js` (lines 1–3), … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 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).
D30 · Dependency Vulnerabilities
97 finding(s): 9 critical, 34 high, 52 medium, 2 low.
What to do
- Resolve the 34 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22), REDACTED (7), REDACTED (5). — One of this dimension's main actionable groups (34 issue-level).
- Resolve the 9 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 15 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (15 warning-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
183 of 183 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/core/src/test.rs. Counted over 183 of the 340 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 180 Orphaned file finding(s) in Knowledge Freshness — start with testing.rs (4), language.rs (3), patterns.rs (3). — One of this dimension's main actionable groups (180 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with test.rs, marzano_resolved_pattern.rs, resolver.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: apply_pattern.rs↔check.rs 67%; js_like.rs↔target_language.rs 54%; apply.rs↔plumbing.rs 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with apply_pattern.rs, js_like.rs, apply.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
3 end-of-life runtime(s) and 0 end-of-life framework(s), read from 22 platform declaration(s) and 6 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.
What to do
- Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with Generator.csproj, REDACTED, rust-toolchain.toml. — One of this dimension's main actionable groups (3 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
ES1 · Fold determinism
ES2 · Immutable events
GD1 · Unfinished & placeholder code
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 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- `prettier --version` invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:45
What to do
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P10 · Library API & versioning
- 136/155 types (88%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports; Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- Only 9/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `crates/cli_bin`, `docs`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
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
- `prep_query` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — js/gritql/src/search.rs:171
What to do
- Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
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
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 69% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by D12 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61% | Adequate — gated by D29, D30, D44 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Event Sourcing | 100% | Exemplary | Solid. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 8 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
- D18 Solution Shape — D18 scores the shape of a .NET solution, but this repository's production source is mostly .c, .cts, .kt, .mts, .py, .rs, .ts, .tsx — the .NET project files present are an immaterial minority — so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Go, Java, JavaScript, Kotlin, Python, Rust, TypeScript, html not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Rust surface was not measured.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D24 Comment Value — D24 reads C# and Visual Basic comments only; comments in this repository's .cts, .kt, .mts, .py, .rs, .ts, .tsx source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — .NET suite
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- 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 — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no async method does work a token could cancel
- 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 — 52 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 317 finding(s)
- marzano_core::inline_snippets::get_deletion_indices (cognitive 113) crates/core/src/inline_snippets.rs:518
- marzano_core::inline_snippets::update_comma_insertion_strings (cognitive 64) crates/core/src/inline_snippets.rs:418
- marzano_core::optimizer::hoist_text::extract_body_pattern (cognitive 37) crates/core/src/optimizer/hoist_text.rs:104
- marzano_core::inline_snippets::inline_sorted_snippets_with_offset (cognitive 33) crates/core/src/inline_snippets.rs:124
- marzano_core::smart_insert::calculate_padding (cognitive 31) crates/core/src/smart_insert.rs:4
- marzano_core::optimizer::hoist_files::extract_filename_pattern (cognitive 27) crates/core/src/optimizer/hoist_files.rs:13
- marzano_core::pattern_compiler::auto_wrap::auto_wrap_pattern (cognitive 24) crates/core/src/pattern_compiler/auto_wrap.rs:19
- marzano_core::built_in_functions::distinct_fn (cognitive 21) crates/core/src/built_in_functions.rs:445
- marzano_core::pattern_compiler::compiler::filter_libs (cognitive 21) crates/core/src/pattern_compiler/compiler.rs:570
- marzano_core::inline_snippets::filter_out_nested (cognitive 20) crates/core/src/inline_snippets.rs:11
- marzano_core::analysis::get_dependents_of_target_patterns_by_traversal_from_src (cognitive 19) crates/core/src/analysis.rs:112
- marzano_core::inline_snippets::delete_hanging_comma (cognitive 19) crates/core/src/inline_snippets.rs:301
- marzano_core::pattern_compiler::compiler::defs_to_filenames (cognitive 19) crates/core/src/pattern_compiler/compiler.rs:470
- marzano_core::marzano_binding::linearize_binding (cognitive 17) crates/core/src/marzano_binding.rs:59
- marzano_core::tree_sitter_serde::tree_sitter_node_to_json (cognitive 16) crates/core/src/tree_sitter_serde.rs:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: marzano_cli::commands::apply_pattern::run_apply_pattern crates/cli/src/commands/apply_pattern.rs:200
- FunctionTooLong: marzano_cli::commands::check::run_check crates/cli/src/commands/check.rs:76
- FunctionTooLong: marzano_cli::commands::plumbing::run_plumbing crates/cli/src/commands/plumbing.rs:129
- FunctionTooLong: marzano_lsp::testing::maybe_test_pattern crates/lsp/src/testing.rs:29
- FunctionTooLong: marzano_gritmodule::markdown::get_patterns_from_md crates/gritmodule/src/markdown.rs:57
- FunctionTooLong: marzano_cli::analyze::par_apply_pattern crates/cli/src/analyze.rs:144
- FunctionTooLong: marzano_cli::workflows::run_bin_workflow crates/cli/src/workflows.rs:59
- FunctionTooLong: marzano_gritmodule::testing::test_pattern_sample crates/gritmodule/src/testing.rs:196
- FunctionTooLong: marzano_cli::commands::run_command crates/cli/src/commands/mod.rs:354
- FunctionTooLong: marzano_core::optimizer::hoist_text::extract_body_pattern crates/core/src/optimizer/hoist_text.rs:104
- FunctionTooLong: gritql_napi::search::search_internal js/gritql/src/search.rs:351
- FunctionTooLong: marzano_gritmodule::formatting::format_temp_dir crates/gritmodule/src/formatting.rs:72
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) crates/core/src/analysis.rs:144
- Duplicated block (7 lines × 2) crates/core/src/marzano_resolved_pattern.rs:666
- Duplicated block (7 lines × 2) crates/core/src/pattern_compiler/any_compiler.rs:20
- Duplicated block (7 lines × 2) crates/core/src/pattern_compiler/compiler.rs:484
- Duplicated block (7 lines × 2) crates/core/src/pattern_compiler/compiler.rs:482
- Duplicated block (7 lines × 2) crates/core/src/pattern_compiler/compiler.rs:527
- Duplicated block (7 lines × 2) crates/core/src/pattern_compiler/if_compiler.rs:20
- Duplicated block (7 lines × 2) crates/core/src/sdk/binding.rs:77
- Duplicated block (7 lines × 2) crates/core/src/sdk/binding.rs:117
- Duplicated block (7 lines × 2) crates/grit-pattern-matcher/src/pattern/iter_pattern.rs:79
- Duplicated block (7 lines × 2) crates/grit-pattern-matcher/src/pattern/variable.rs:425
- Duplicated block (7 lines × 2) crates/core/src/pattern_compiler/back_tick_compiler.rs:21
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) crates/cli/src/commands/workflows_watch.rs:26
- Duplicated block (10 lines × 2) crates/core/src/inline_snippets.rs:445
- Duplicated block (10 lines × 2) crates/core/src/optimizer/hoist_files.rs:16
- Duplicated block (10 lines × 2) crates/core/src/pattern_compiler/step_compiler.rs:77
- Duplicated block (10 lines × 2) crates/grit-pattern-matcher/src/pattern/match.rs:59
- Duplicated block (10 lines × 2) crates/grit-pattern-matcher/src/pattern/match.rs:95
- Duplicated block (10 lines × 2) crates/gritmodule/src/resolver.rs:57
- Duplicated block (10 lines × 2) crates/language/src/css.rs:126
- Duplicated block (10 lines × 2) crates/language/src/markdown_block.rs:37
- Duplicated block (10 lines × 2) crates/core/src/pattern_compiler/as_compiler.rs:39
- marzano_cli::commands::check::run_check (cognitive 80) crates/cli/src/commands/check.rs:76
- marzano_cli::commands::apply_pattern::run_apply_pattern (cognitive 70) crates/cli/src/commands/apply_pattern.rs:200
- marzano_cli::analyze::par_apply_pattern (cognitive 54) crates/cli/src/analyze.rs:144
- marzano_cli::lister::list_applyables (cognitive 49) crates/cli/src/lister.rs:113
- marzano_cli::commands::patterns::run_patterns_describe (cognitive 33) crates/cli/src/commands/patterns.rs:68
- marzano_cli::commands::plumbing::run_plumbing (cognitive 31) crates/cli/src/commands/plumbing.rs:129
- marzano_cli::commands::run_command (cognitive 23) crates/cli/src/commands/mod.rs:354
- marzano_cli::workflows::run_bin_workflow (cognitive 23) crates/cli/src/workflows.rs:59
- marzano_cli::workflows::find_workflow_file_from (cognitive 18) crates/cli/src/workflows.rs:400
- MethodTooLong: MarzanoContext.exec_step crates/core/src/marzano_context.rs:192
- MethodTooLong: Contains.execute crates/grit-pattern-matcher/src/pattern/contains.rs:93
- MethodTooLong: MarzanoNotebookParser.parse_file_as_notebook crates/language/src/notebooks.rs:212
- MethodTooLong: Pattern.children crates/grit-pattern-matcher/src/pattern/iter_pattern.rs:248
- MethodTooLong: GritServer.execute_command crates/lsp/src/server.rs:503
- MethodTooLong: PatternCompiler.from_node_with_rhs crates/core/src/pattern_compiler/pattern_compiler.rs:173
- MethodTooLong: Messager.handle_results_inner crates/marzano_messenger/src/emit.rs:96
- MethodTooLong: MarzanoResolvedPattern.from_pattern crates/core/src/marzano_resolved_pattern.rs:494
- MethodTooLong: RewriteCompiler.from_node_with_rhs crates/core/src/pattern_compiler/rewrite_compiler.rs:17
- marzano_gritmodule::formatting::format_temp_dir (cognitive 84) crates/gritmodule/src/formatting.rs:72
- marzano_gritmodule::resolver::resolve_patterns (cognitive 57) crates/gritmodule/src/resolver.rs:276
- marzano_gritmodule::markdown::get_patterns_from_md (cognitive 49) crates/gritmodule/src/markdown.rs:57
- marzano_gritmodule::resolver::resolve_namespace_import (cognitive 44) crates/gritmodule/src/resolver.rs:449
- marzano_gritmodule::resolver::resolve_patterns_for_module (cognitive 30) crates/gritmodule/src/resolver.rs:582
- marzano_gritmodule::testing::test_pattern_sample (cognitive 28) crates/gritmodule/src/testing.rs:196
- marzano_gritmodule::dot_grit::get_patterns_from_grit (cognitive 20) crates/gritmodule/src/dot_grit.rs:15
- marzano_gritmodule::resolver::dir_has_config (cognitive 20) crates/gritmodule/src/resolver.rs:151
- FileTooLong: src/marzano_resolved_pattern.rs crates/core/src/marzano_resolved_pattern.rs
- FileTooLong: src/target_language.rs crates/language/src/target_language.rs
- FileTooLong: src/api.rs crates/core/src/api.rs
- FileTooLong: pattern_compiler/compiler.rs crates/core/src/pattern_compiler/compiler.rs
- FileTooLong: src/resolver.rs crates/gritmodule/src/resolver.rs
- FileTooLong: commands/mod.rs crates/cli/src/commands/mod.rs
- FileTooLong: src/server.rs crates/lsp/src/server.rs
- Duplicated block (9 lines × 2) crates/core/src/marzano_resolved_pattern.rs:468
- Duplicated block (9 lines × 2) crates/core/src/pattern_compiler/accumulate_compiler.rs:43
- Duplicated block (9 lines × 2) crates/core/src/pattern_compiler/auto_wrap.rs:88
- Duplicated block (9 lines × 2) crates/core/src/pattern_compiler/auto_wrap.rs:158
- Duplicated block (9 lines × 2) crates/grit-pattern-matcher/src/pattern/range.rs:45
- Duplicated block (9 lines × 2) crates/lsp/src/server.rs:530
- Duplicated block (9 lines × 2) crates/cli/src/workflows.rs:184
- marzano_cli::commands::check::run_check (cyclomatic 44) crates/cli/src/commands/check.rs:76
- marzano_cli::commands::run_command (cyclomatic 39) crates/cli/src/commands/mod.rs:354
- marzano_cli::commands::apply_pattern::run_apply_pattern (cyclomatic 39) crates/cli/src/commands/apply_pattern.rs:200
- marzano_cli::analyze::par_apply_pattern (cyclomatic 27) crates/cli/src/analyze.rs:144
- marzano_cli::lister::list_applyables (cyclomatic 24) crates/cli/src/lister.rs:113
- marzano_cli::commands::plumbing::run_plumbing (cyclomatic 20) crates/cli/src/commands/plumbing.rs:129
- Duplicated block (6 lines × 2) crates/cli/src/result_formatting.rs:291
- Duplicated block (6 lines × 2) crates/core/src/pattern_compiler/compiler.rs:491
- Duplicated block (6 lines × 2) crates/core/src/pattern_compiler/compiler.rs:500
- Duplicated block (6 lines × 2) crates/core/src/pattern_compiler/compiler.rs:499
- Duplicated block (6 lines × 2) crates/core/src/pattern_compiler/compiler.rs:506
- Duplicated block (6 lines × 2) crates/language/src/java.rs:38
- marzano_core::inline_snippets::get_deletion_indices (cyclomatic 51) crates/core/src/inline_snippets.rs:518
- marzano_core::optimizer::hoist_text::extract_body_pattern (cyclomatic 39) crates/core/src/optimizer/hoist_text.rs:104
- marzano_core::inline_snippets::update_comma_insertion_strings (cyclomatic 38) crates/core/src/inline_snippets.rs:418
- marzano_core::optimizer::hoist_files::extract_filename_pattern (cyclomatic 35) crates/core/src/optimizer/hoist_files.rs:13
- marzano_core::inline_snippets::inline_sorted_snippets_with_offset (cyclomatic 19) crates/core/src/inline_snippets.rs:124
- marzano_gritmodule::formatting::format_temp_dir (cyclomatic 35) crates/gritmodule/src/formatting.rs:72
- marzano_gritmodule::markdown::get_patterns_from_md (cyclomatic 29) crates/gritmodule/src/markdown.rs:57
- marzano_gritmodule::testing::test_pattern_sample (cyclomatic 21) crates/gritmodule/src/testing.rs:196
- marzano_gritmodule::resolver::resolve_patterns (cyclomatic 18) crates/gritmodule/src/resolver.rs:276
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) crates/core/src/marzano_resolved_pattern.rs:427
- Duplicated block (15 lines × 2) crates/core/src/optimizer/hoist_files.rs:256
- Duplicated block (15 lines × 2) crates/core/src/optimizer/hoist_files.rs:278
- Duplicated block (15 lines × 2) crates/grit-pattern-matcher/src/errors.rs:16
- Duplicated block (5 lines × 2) crates/cli/src/commands/parse.rs:97
- Duplicated block (5 lines × 2) crates/cli/src/result_formatting.rs:512
- Duplicated block (5 lines × 2) crates/core/src/pattern_compiler/ast_node_compiler.rs:118
- Duplicated block (5 lines × 2) crates/grit-pattern-matcher/src/pattern/float_constant.rs:33
- Dependency pinned to a stale untagged commit: github.com/smacker/go-tree-sitter
- Dependency pinned to a stale untagged commit: github.com/smacker/go-tree-sitter
- Dependency pinned to a stale untagged commit: github.com/smacker/go-tree-sitter
- grit_pattern_matcher::pattern::list::execute_assoc (cognitive 39) crates/grit-pattern-matcher/src/pattern/list.rs:57
- grit_pattern_matcher::pattern::contains::execute_until (cognitive 20) crates/grit-pattern-matcher/src/pattern/contains.rs:37
- grit_pattern_matcher::pattern::includes::execute (cognitive 19) crates/grit-pattern-matcher/src/pattern/includes.rs:30
- Change coupling: apply_pattern.rs ↔ check.rs crates/cli/src/commands/apply_pattern.rs:1
- Change coupling: js_like.rs ↔ target_language.rs crates/language/src/js_like.rs:1
- Change coupling: apply.rs ↔ plumbing.rs crates/cli/src/commands/apply.rs:1
- Duplicated block (11 lines × 2) crates/core/src/inline_snippets.rs:458
- Duplicated block (11 lines × 2) crates/grit-pattern-matcher/src/pattern/accessor.rs:150
- Duplicated block (11 lines × 2) crates/auth/src/auth0.rs:120
- Duplicated block (8 lines × 4) crates/core/src/optimizer/hoist_files.rs:320
- Duplicated block (8 lines × 4) crates/core/src/sdk/binding.rs:101
- Duplicated block (8 lines × 4) crates/gritmodule/src/formatting.rs:86
- Duplicated block (8 lines × 2) crates/cli/src/lister.rs:197
- Duplicated block (8 lines × 2) crates/grit-pattern-matcher/src/pattern/after.rs:68
- Duplicated block (8 lines × 2) crates/wasm-bindings/src/match_pattern.rs:195
- End-of-life runtime: .NET net6.0 resources/language-metavariables/tree-sitter-c-sharp/tools/highlight-test-generator/Generator.csproj:4
- End-of-life runtime: Node.js 10 js/gritql/package.json:45
- End-of-life runtime: Rust 1.82 rust-toolchain.toml:1
- Predicate::extract_body_pattern (cyclomatic 25) crates/core/src/optimizer/hoist_text.rs:317
- Predicate::extract_filename_pattern (cyclomatic 23) crates/core/src/optimizer/hoist_files.rs:205
- marzano_language::js_like::jslike_check_replacements (cyclomatic 20) crates/language/src/js_like.rs:170
- marzano_language::language::snippet_nodes_from_index (cyclomatic 16) crates/language/src/language.rs:564
- marzano_util::diff::parse_modified_ranges (cognitive 40) crates/util/src/diff.rs:70
- marzano_util::diff_standardizer::standardize_rewrite (cognitive 26) crates/util/src/diff_standardizer.rs:13
- Predicate::extract_body_pattern (cognitive 37) crates/core/src/optimizer/hoist_text.rs:317
- Predicate::extract_filename_pattern (cognitive 31) crates/core/src/optimizer/hoist_files.rs:205
- marzano_language::js_like::jslike_check_replacements (cognitive 37) crates/language/src/js_like.rs:170
- marzano_language::language::snippet_nodes_from_index (cognitive 27) crates/language/src/language.rs:564
- marzano_lsp::scan::collect_initial_diagnostics (cognitive 21) crates/lsp/src/scan.rs:36
- marzano_lsp::testing::maybe_test_pattern (cognitive 16) crates/lsp/src/testing.rs:29
- ClassTooLong: MarzanoResolvedPattern crates/core/src/marzano_resolved_pattern.rs:30
- ClassTooLong: GritServer crates/lsp/src/server.rs:44
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/core/src/pattern_compiler/function_definition_compiler.rs:24
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/core/src/sdk/binding.rs:94
- Duplicated block (17 lines × 2) crates/core/src/optimizer/hoist_files.rs:315
- Duplicated block (17 lines × 2) crates/core/src/pattern_compiler/not_compiler.rs:29
- Duplicated block (12 lines × 4) crates/core/src/optimizer/hoist_text.rs:80
- Duplicated block (12 lines × 4) crates/core/src/pattern_compiler/auto_wrap.rs:124
- Duplicated block (10–11 lines × 2) crates/core/src/pattern_compiler/function_definition_compiler.rs:25
- Duplicated block (10–11 lines × 2) crates/grit-pattern-matcher/src/pattern/variable.rs:290
- Duplicated block (8–9 lines × 5) crates/core/src/optimizer/hoist_files.rs:117
- Duplicated block (8–9 lines × 5) crates/core/src/pattern_compiler/auto_wrap.rs:128
- Duplicated block (8 lines × 5) crates/core/src/optimizer/hoist_files.rs:67
- Duplicated block (8 lines × 5) crates/core/src/optimizer/hoist_text.rs:178
- Off the main sequence: grit-util
- Off the main sequence: marzano-language
- Low cohesion: TransformedMessenger (LCOM4 6) crates/cli/src/result_formatting.rs:458
- Low cohesion: UncompiledPatternBuilder (LCOM4 4) crates/core/src/sdk/pattern_sdk.rs:68
- PatternLanguage::from_string (cyclomatic 37) crates/language/src/target_language.rs:218
- Contains::execute (cyclomatic 28) crates/grit-pattern-matcher/src/pattern/contains.rs:93
- Commands::fmt (cyclomatic 27) crates/cli/src/commands/mod.rs:188
- Messager::handle_results_inner (cyclomatic 26) crates/marzano_messenger/src/emit.rs:96
- FormattedResult::fmt (cyclomatic 25) crates/cli/src/result_formatting.rs:184
- GritServer::execute_command (cyclomatic 25) crates/lsp/src/server.rs:503
- MarzanoNotebookParser::parse_file_as_notebook (cyclomatic 22) crates/language/src/notebooks.rs:212
- Python::check_replacements (cyclomatic 21) crates/language/src/python.rs:80
- gritql_napi::search::search_internal (cyclomatic 21) js/gritql/src/search.rs:351
- grit_pattern_matcher::pattern::list::execute_assoc (cyclomatic 20) crates/grit-pattern-matcher/src/pattern/list.rs:57
- MarzanoResolvedPattern::extend (cyclomatic 17) crates/core/src/marzano_resolved_pattern.rs:116
- grit_wasm_bindings.debugString (cyclomatic 17) __generated__/grit-wasm-bindings/grit_wasm_bindings.js:121
- marzano_wasm_bindings.debugString (cyclomatic 17) __generated__/grit-wasm-bindings/marzano_wasm_bindings.js:121
- MarzanoContext::exec_step (cyclomatic 16) crates/core/src/marzano_context.rs:192
- Match::execute_func (cyclomatic 16) crates/grit-pattern-matcher/src/pattern/match.rs:34
- marzano_util::diff::parse_modified_ranges (cyclomatic 16) crates/util/src/diff.rs:70
- monaco-diff-editor.MonacoDiffEditor (cyclomatic 16) docs/src/components/editor/monaco-diff-editor.tsx:34
- Skipped test: can run inside a storage context js/gritql/__test__/napi.spec.mts:14
- No go.sum committed (resources/language-metavariables/tree-sitter-java/bindings/go/go.mod)
- No go.sum committed (resources/language-metavariables/tree-sitter-kotlin/go.mod)
- No go.sum committed (resources/language-metavariables/tree-sitter-toml/bindings/go/go.mod)
- No go.sum committed (resources/language-metavariables/tree-sitter-yaml/bindings/go/go.mod)
- gritql_napi::search::search_internal (cognitive 74) js/gritql/src/search.rs:351
- Messager::handle_results_inner (cognitive 73) crates/marzano_messenger/src/emit.rs:96
- Contains::execute (cognitive 66) crates/grit-pattern-matcher/src/pattern/contains.rs:93
- FormattedResult::fmt (cognitive 48) crates/cli/src/result_formatting.rs:184
- Python::check_replacements (cognitive 48) crates/language/src/python.rs:80
- GritServer::execute_command (cognitive 47) crates/lsp/src/server.rs:503
- MarzanoNotebookParser::parse_file_as_notebook (cognitive 45) crates/language/src/notebooks.rs:212
- MarzanoContext::exec_step (cognitive 39) crates/core/src/marzano_context.rs:192
- State::bindings_history_to_ranges (cognitive 39) crates/grit-pattern-matcher/src/pattern/state.rs:424
- Match::execute_func (cognitive 35) crates/grit-pattern-matcher/src/pattern/match.rs:34
- LocalRepo::remote (cognitive 31) REDACTED:126
- Range::execute (cognitive 27) crates/grit-pattern-matcher/src/pattern/range.rs:69
- RegexPattern::execute_matching (cognitive 25) crates/grit-pattern-matcher/src/pattern/regex.rs:35
- grit_util::ast_node_traversal::traverse_iterative (cognitive 25) crates/grit-util/src/ast_node_traversal.rs:57
- Problem::execute_paths (cognitive 23) crates/core/src/problem.rs:344
- grit_wasm_bindings.debugString (cognitive 23) __generated__/grit-wasm-bindings/grit_wasm_bindings.js:121
- marzano_wasm_bindings.debugString (cognitive 23) __generated__/grit-wasm-bindings/marzano_wasm_bindings.js:121
- Some::execute (cognitive 22) crates/grit-pattern-matcher/src/pattern/some.rs:27
- CallCompiler::from_node_with_rhs (cognitive 21) crates/core/src/pattern_compiler/call_compiler.rs:21
- Every::execute (cognitive 19) crates/grit-pattern-matcher/src/pattern/every.rs:27
- Or::execute (cognitive 19) crates/grit-pattern-matcher/src/pattern/or.rs:31
- Updater::check_for_update (cognitive 18) crates/cli/src/updater.rs:215
- MarzanoLanguage::align_padding (cognitive 17) crates/language/src/language.rs:318
- ASTNode::execute (cognitive 16) crates/core/src/ast_node.rs:55
- Within::execute (cognitive 16) crates/grit-pattern-matcher/src/pattern/within.rs:29
- marzano_messenger::format::get_extended_byte_range (cognitive 16) crates/marzano_messenger/src/format.rs:8
- grit_wasm_bindings.__wbg_load (cognitive 16) __generated__/grit-wasm-bindings/grit_wasm_bindings.js:376
- marzano_wasm_bindings.__wbg_load (cognitive 16) __generated__/grit-wasm-bindings/marzano_wasm_bindings.js:321
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member family (5 members, 23 shared lines) crates/core/src/pattern_compiler/auto_wrap.rs:79
- Near-duplicate member family (4 members, 23 shared lines) crates/core/src/optimizer/hoist_files.rs:299
- Near-duplicate member pair (52 shared lines) crates/core/src/optimizer/hoist_files.rs:205
- Members sharing a duplicated core (14 members, 50+ identical tokens) crates/language/src/csharp.rs:31
- Duplicated block (32 lines × 2) crates/core/src/optimizer/hoist_files.rs:107
- Duplicated block (27 lines × 2) crates/gritmodule/src/resolver.rs:539
- Duplicated block (22 lines × 2) crates/core/src/optimizer/hoist_files.rs:206
- Duplicated block (19–20 lines × 2) crates/core/src/sdk/binding.rs:140
- Duplicated block (18–19 lines × 2) crates/gritmodule/src/resolver.rs:239
- Duplicated block (17–18 lines × 2) crates/cli/src/commands/blueprints.rs:47
- Duplicated block (16 lines × 3) crates/core/src/pattern_compiler/auto_wrap.rs:180
- Duplicated block (16 lines × 2) crates/core/src/sdk/binding.rs:95
- Duplicated block (12–15 lines × 2) crates/grit-pattern-matcher/src/pattern/contains.rs:165
- Duplicated block (14 lines × 3) crates/core/src/optimizer/hoist_files.rs:309
- Duplicated block (13 lines × 3) crates/core/src/pattern_compiler/auto_wrap.rs:103
- Duplicated block (12 lines × 6) crates/core/src/pattern_compiler/auto_wrap.rs:110
- Duplicated block (12 lines × 5) crates/core/src/marzano_resolved_pattern.rs:583
- Duplicated block (11 lines × 14) crates/language/src/csharp.rs:32
- Duplicated block (11 lines × 5) crates/core/src/optimizer/hoist_files.rs:344
- Duplicated block (11 lines × 3) crates/language/src/javascript.rs:118
- Duplicated block (9–11 lines × 2) crates/core/src/analysis.rs:119
- Duplicated block (10 lines × 8) crates/core/src/pattern_compiler/accumulate_compiler.rs:57
- Duplicated block (10 lines × 5) crates/core/src/pattern_compiler/auto_wrap.rs:125
- Duplicated block (9–10 lines × 5) crates/gritmodule/src/formatting.rs:77
- Duplicated block (8–9 lines × 2) crates/core/src/pattern_compiler/accumulate_compiler.rs:76
- Duplicated block (7 lines × 3) crates/core/src/pattern_compiler/and_compiler.rs:43
- Duplicated block (5 lines × 3) crates/language/src/java.rs:37
- Duplicated block (6 lines × 4) crates/grit-pattern-matcher/src/pattern/add.rs:59
- Duplicated block (14 lines × 2) crates/language/src/tsx.rs:49
- Duplicated block (7 lines × 4) crates/core/src/pattern_compiler/function_definition_compiler.rs:28
- Unstable project marzano-lsp
- CI formatting step cannot fail REDACTED:45
- Sync-over-async blocking js/gritql/src/search.rs:171
Minor — 226 finding(s)
- Orphaned file crates/language/src/target_language.rs:1
- Orphaned file crates/core/src/pattern_compiler/compiler.rs:1
- Orphaned file crates/core/src/api.rs:1
- Orphaned file crates/util/src/diff.rs:1
- Orphaned file crates/lsp/src/server.rs:1
- Orphaned file crates/gritmodule/src/markdown.rs:1
- Orphaned file crates/cli/src/commands/mod.rs:1
- Orphaned file crates/core/src/inline_snippets.rs:1
- Orphaned file crates/cli/src/updater.rs:1
- Orphaned file crates/language/src/language.rs:1
- Orphaned file crates/core/src/built_in_functions.rs:1
- Orphaned file crates/core/src/marzano_binding.rs:1
- Orphaned file crates/wasm-bindings/src/match_pattern.rs:1
- Orphaned file crates/cli/src/result_formatting.rs:1
- Orphaned file crates/core/src/problem.rs:1
- Orphaned file REDACTED:1
- Orphaned file crates/core/src/pattern_compiler/pattern_compiler.rs:1
- Orphaned file crates/core/src/optimizer/hoist_text.rs:1
- Orphaned file crates/cli/src/commands/apply_pattern.rs:1
- Orphaned file crates/core/src/pattern_compiler/auto_wrap.rs:1
- Orphaned file js/gritql/src/search.rs:1
- Orphaned file crates/grit-pattern-matcher/src/pattern/state.rs:1
- Orphaned file crates/core/src/analysis.rs:1
- Orphaned file crates/cli/src/workflows.rs:1
- Orphaned file crates/grit-pattern-matcher/src/pattern/variable.rs:1
- Duplicated predicate resources/language-metavariables/tree-sitter-elixir/grammar.js:59
- Duplicated predicate __generated__/grit-wasm-bindings/grit_wasm_bindings.js:97
- Duplicated predicate __generated__/grit-wasm-bindings/grit_wasm_bindings.js:239
- Duplicated predicate __generated__/grit-wasm-bindings/grit_wasm_bindings.js:30
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/tree-sitter-markdown-inline/grammar.js:455
- Duplicated predicate resources/language-metavariables/tree-sitter-php/common/define-grammar.js:49
- Duplicated predicate resources/language-metavariables/tree-sitter-toml/docs/assets/tree-sitter-playground-0.19.3/playground.js:436
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:2
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:9
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:6
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:5
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:7
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:4
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:8
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:3
- Duplicated predicate resources/language-metavariables/tree-sitter-markdown/common/grammar.js:10
- Duplicated predicate resources/language-metavariables/tree-sitter-yaml/grammar.js:1372
- Duplicated predicate resources/language-metavariables/tree-sitter-toml/docs/assets/tree-sitter-playground-0.19.3/playground.js:316
- Duplicated predicate resources/language-metavariables/tree-sitter-toml/docs/assets/tree-sitter-playground-0.19.3/playground.js:107
- Duplicated predicate __generated__/grit-wasm-bindings/grit_wasm_bindings.js:949
- Duplicated predicate __generated__/grit-wasm-bindings/grit_wasm_bindings.js:140
- Duplicated predicate crates/language/src/javascript.rs:123
- Duplicated predicate crates/language/src/grit_parser.rs:72
- Duplicated predicate crates/core/src/analysis.rs:145
- Duplicated predicate crates/language/src/javascript.rs:159
- Silent fallback default on Err REDACTED:83
- Silent fallback default on Err crates/gritmodule/src/resolver.rs:409
- Silent fallback default on Err crates/lsp/src/patterns.rs:53
- Silent fallback default on Err crates/lsp/src/patterns.rs:74
- Silent fallback default on Err crates/lsp/src/watcher.rs:8
- Silent fallback default on Err crates/util/src/diff.rs:39
- Most significant orphaned file crates/core/src/test.rs:1
- Most significant orphaned file crates/core/src/marzano_resolved_pattern.rs:1
- Most significant orphaned file crates/gritmodule/src/resolver.rs:1
- REDACTED
- REDACTED
- Silent fallback default in catch __generated__/grit-wasm-bindings/grit_wasm_bindings.js:174
- Silent fallback default in catch __generated__/grit-wasm-bindings/marzano_wasm_bindings.js:174
- Off-boarding risk: anonymized user #1
- No ADRs found
- Concentrated knowledge decay
- REDACTED
- No ADRs
- Large public API surface
- Logging is not universal
- Nullable reference types not enabled everywhere
Minor — 1 finding(s)
- Outdated: github.com/tree-sitter/go-tree-sitter
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-087e83bb3e9e45af9d359891112cdaa9/history.json --exit-code 0 --source . | 1 | 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-087e83bb3e9e45af9d359891112cdaa9/tree.json --exit-code 0 --source . | 1 | 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 resources/language-metavariables/tree-sitter-c-sharp/tools/highlight-test-generator/obj --exclude resources/language-metavariables/tree-sitter-c-sharp --exclude resources/language-metavariables/tree-sitter-css --exclude resources/language-metavariables/tree-sitter-elixir/bindings --exclude resources/language-metavariables/tree-sitter-elixir/docs --exclude resources/language-metavariables/tree-sitter-elixir/queries --exclude resources/language-metavariables/tree-sitter-elixir/scripts --exclude resources/language-metavariables/tree-sitter-elixir/src/tree_sitter --exclude resources/language-metavariables/tree-sitter-elixir/test --exclude resources/language-metavariables/tree-sitter-go --exclude resources/language-metavariables/tree-sitter-hcl --exclude resources/language-metavariables/tree-sitter-html --exclude resources/language-metavariables/tree-sitter-java --exclude resources/language-metavariables/tree-sitter-javascript --exclude resources/language-metavariables/tree-sitter-json --exclude resources/language-metavariables/tree-sitter-kotlin --exclude resources/language-metavariables/tree-sitter-markdown --exclude resources/language-metavariables/tree-sitter-php/bindings --exclude resources/language-metavariables/tree-sitter-php/common --exclude resources/language-metavariables/tree-sitter-php/php/bindings --exclude resources/language-metavariables/tree-sitter-php/php/src --exclude resources/language-metavariables/tree-sitter-php/php_only/bindings --exclude resources/language-metavariables/tree-sitter-php/php_only/src --exclude resources/language-metavariables/tree-sitter-php/queries --exclude resources/language-metavariables/tree-sitter-php/script --exclude resources/language-metavariables/tree-sitter-python --exclude resources/language-metavariables/tree-sitter-ruby --exclude resources/language-metavariables/tree-sitter-rust --exclude resources/language-metavariables/tree-sitter-solidity --exclude resources/language-metavariables/tree-sitter-sql --exclude resources/language-metavariables/tree-sitter-toml --exclude resources/language-metavariables/tree-sitter-typescript/bindings --exclude resources/language-metavariables/tree-sitter-typescript/build --exclude resources/language-metavariables/tree-sitter-typescript/common --exclude resources/language-metavariables/tree-sitter-typescript/examples --exclude resources/language-metavariables/tree-sitter-typescript/queries --exclude resources/language-metavariables/tree-sitter-typescript/script --exclude resources/language-metavariables/tree-sitter-typescript/tsx/src --exclude resources/language-metavariables/tree-sitter-typescript/typescript/src --exclude resources/language-metavariables/tree-sitter-vue --exclude resources/language-metavariables/tree-sitter-yaml --exclude resources/metavariable-grammars --exclude resources/node-types . | 16 | 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 | 97 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 |