Executive summary
RasaHQ/rasa is rated At risk because critical security findings are open. It scores 55.9 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 42.5, is the weakest lens and counts most in the score. The best first steps are protecting outgoing calls with timeouts and moving to versioned database migrations, each worth about 3.4 points. Raising Production Readiness to 70 would lift the score to about 66.6.
Thirty-one known security holes in the packages the code depends on can be used by attackers. Ten pipeline steps run downloads nobody checks, and ten secrets can leak from the build pipeline. Updating the vulnerable packages, checking each download against a checksum and limiting each secret to its own step would close these risks. The ten unsafe settings in infrastructure or container files need changing to safe values. The eight pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions.
The product code is 70,104 lines, about €140,000 to rebuild.
If Production Readiness rose from 42.5 to 70, the lowest score rated Strong, the score would rise from 55.9 to about 66.6.
New since the last survey: 31 findings
- Code Duplication · Edited copy of a member (55 corresponding lines) rasa/core/featurizers/tracker_featurizers.py
- Code Duplication · Edited copies of one member (3 members, 32+ corresponding lines) rasa/shared/nlu/training_data/formats/rasa_yaml.py
- Code Duplication · Edited copy of a member (21 corresponding lines) rasa/server.py
- Code Duplication · Edited copy of a member (31 corresponding lines) rasa/validator.py
- Code Duplication · Edited copy of a member (36 corresponding lines) rasa/cli/shell.py
- Code Duplication · Edited copy of a member (38 corresponding lines) rasa/core/featurizers/tracker_featurizers.py
- Code Duplication · Edited copy of a member (23 corresponding lines) rasa/core/lock_store.py
- Code Duplication · Edited copy of a member (17 corresponding lines) rasa/shared/nlu/training_data/message.py
- Code Duplication · Edited copy of a member (17 corresponding lines) rasa/engine/graph.py
- Code Duplication · Edited copy of a member (33 corresponding lines) rasa/nlu/featurizers/dense_featurizer/convert_featurizer.py
- Code Duplication · Edited copy of a member (18 corresponding lines) rasa/nlu/classifiers/diet_classifier.py
- Code Duplication · Edited copy of a member (15 corresponding lines) rasa/nlu/classifiers/keyword_intent_classifier.py
- Code Duplication · Edited copy of a member (30 corresponding lines) rasa/core/policies/ted_policy.py
- Code Duplication · Edited copy of a member (43 corresponding lines) rasa/core/featurizers/tracker_featurizers.py
- Code Duplication · Edited copy of a member (13 corresponding lines) rasa/nlu/tokenizers/tokenizer.py
- Code Duplication · Edited copy of a member (13 corresponding lines) rasa/shared/nlu/training_data/formats/rasa_yaml.py
- Code Duplication · Edited copy of a member (13 corresponding lines) rasa/core/channels/mattermost.py
- Code Duplication · Edited copy of a member (12 corresponding lines) rasa/core/nlg/generator.py
- Code Duplication · Edited copy of a member (19 corresponding lines) .github/scripts/mr_generate_summary.py
- Code Duplication · Edited copy of a member (15 corresponding lines) rasa/nlu/extractors/regex_entity_extractor.py
- Code Duplication · Edited copy of a member (9 corresponding lines) rasa/nlu/extractors/crf_entity_extractor.py
- Code Duplication · Edited copy of a member (16 corresponding lines) rasa/cli/export.py
- Code Duplication · Edited copy of a member (7 corresponding lines) rasa/shared/importers/importer.py
- Code Duplication · Edited copy of a member (10 corresponding lines) rasa/core/policies/ted_policy.py
- Code Duplication · Edited copy of a member (6 corresponding lines) rasa/nlu/classifiers/diet_classifier.py
- Code Duplication · Edited copy of a member (4 corresponding lines) .github/scripts/validate_cpu.py
- Code Duplication · Edited copy of a member (2 corresponding lines) rasa/core/channels/channel.py
- Code Duplication · Edited copy of a member (16 corresponding lines) scripts/prepare_nightly_release.py
- Code Duplication · Edited copy of a member (25 corresponding lines) data/test_classes/custom_graph_components/nlu_dense.py
- Code Duplication · Edited copy of a member (23 corresponding lines) rasa/nlu/test.py
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 32 findings
- Code Duplication · Duplicated block (12 lines × 2) rasa/graph_components/validators/default_recipe_validator.py
- Code Duplication · Duplicated block (8 lines × 4) rasa/core/channels/facebook.py
- REDACTED Scanning · Leaked secret: signing-key examples/moodbot/credentials.yml
- REDACTED Scanning · Leaked secret: signing-key examples/moodbot/credentials.yml
- REDACTED Scanning · Leaked secret: high-entropy-secret examples/moodbot/credentials.yml
- REDACTED Scanning · Leaked secret: private-key docs/docs/deploy/deploy-rasa.mdx
- Secrets (history) · High secret: WD-SECRET-0005 docs-requirements.txt
- Secrets (history) · REDACTED: REDACTED docs/channels.rst
- Secrets (history) · REDACTED: REDACTED docs/channels.rst
- Secrets (history) · REDACTED: REDACTED docs/connectors.rst
- Secrets (history) · REDACTED: REDACTED docs/connectors.rst
- Secrets (history) · REDACTED: REDACTED docs/connectors/messenger.rst
- Secrets (history) · REDACTED: REDACTED docs/connectors/messenger.rst
- Secrets (history) · REDACTED: REDACTED docs/core/connectors.rst
- Secrets (history) · REDACTED: REDACTED docs/core/connectors.rst
- Secrets (history) · REDACTED: REDACTED docs/core/migrations.rst
- Secrets (history) · REDACTED: REDACTED docs/core/migrations.rst
- Secrets (history) · REDACTED: REDACTED docs/core/quickstart.rst
- Secrets (history) · REDACTED: REDACTED docs/core/quickstart.rst
- Secrets (history) · REDACTED: http-authorization-credential docs/core/server.rst
- Secrets (history) · REDACTED: REDACTED docs/migrations.rst
- Secrets (history) · REDACTED: REDACTED docs/migrations.rst
- Secrets (history) · REDACTED: REDACTED docs/quickstart.rst
- Secrets (history) · REDACTED: REDACTED docs/quickstart.rst
- Secrets (history) · REDACTED: http-authorization-credential docs/server.rst
- Secrets (history) · REDACTED: REDACTED examples/facebook/credentials.yml
- Secrets (history) · REDACTED: REDACTED examples/moodbot/credentials.yml
- Secrets (history) · REDACTED: REDACTED examples/moodbot/credentials.yml
- Secrets (history) · REDACTED: REDACTED examples/moodbot/credentials.yml
- Secrets (history) · REDACTED: REDACTED examples/responseselectorbot/credentials.yml
- Secrets (history) · REDACTED: REDACTED examples/responseselectorbot/credentials.yml
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] REDACTED
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €46,000 to €230,000, for 773 to 2,454 hours of work, about 1.0 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. 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,104 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 core.channels.channel | 2 shared.core.events | 3 shared.exceptions | 4 shared.nlu.training_data.message | 5 shared.nlu.training_data.training_data | 6 utils.endpoints | 7 utils.tensorflow.model_data | 8 core.brokers.broker | 9 engine.storage.resource | 10 shared.core.domain | 11 engine.graph | 12 shared.core.trackers | 13 shared.core.training_data.structures | 14 core.actions.forms | 15 core.featurizers.tracker_featurizers | 16 core.tracker_store | 17 engine.storage.storage | 18 shared.importers.importer | 19 core.agent | 20 core.featurizers.precomputation | 21 core.policies.policy | 22 graph_components.validators.default_recipe_validator | 23 nlu.classifiers.mitie_intent_classifier | 24 nlu.featurizers.dense_featurizer.mitie_featurizer | 25 nlu.tokenizers.tokenizer | 26 rasa | 27 core.actions.action | 28 core.policies.ensemble | 29 core.policies.memoization | 30 core.policies.ted_policy | 31 core.training | 32 nlu.extractors.extractor | 33 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer | 34 core | 35 core.policies.rule_policy | 36 core.policies.unexpected_intent_policy | 37 core.processor | 38 nlu.classifiers.diet_classifier | 39 nlu.extractors.mitie_entity_extractor | 40 nlu.selectors.response_selector |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.channels.channel | ||||||||||||||||||||||||||||||||||||||||
| 2 shared.core.events | ||||||||||||||||||||||||||||||||||||||||
| 3 shared.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 4 shared.nlu.training_data.message | ||||||||||||||||||||||||||||||||||||||||
| 5 shared.nlu.training_data.training_data | ||||||||||||||||||||||||||||||||||||||||
| 6 utils.endpoints | ||||||||||||||||||||||||||||||||||||||||
| 7 utils.tensorflow.model_data | ||||||||||||||||||||||||||||||||||||||||
| 8 core.brokers.broker | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 engine.storage.resource | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 shared.core.domain | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 engine.graph | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 shared.core.trackers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 shared.core.training_data.structures | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 core.actions.forms | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 core.featurizers.tracker_featurizers | 1 | 1 | 4 | 3 | ||||||||||||||||||||||||||||||||||||
| 16 core.tracker_store | 1 | 1 | 7 | 11 | ||||||||||||||||||||||||||||||||||||
| 17 engine.storage.storage | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 shared.importers.importer | 5 | 5 | 5 | |||||||||||||||||||||||||||||||||||||
| 19 core.agent | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 core.featurizers.precomputation | 1 | 1 | 2 | 2 | 4 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 21 core.policies.policy | 1 | 1 | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 22 graph_components.validators.default_recipe_validator | 1 | 1 | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 23 nlu.classifiers.mitie_intent_classifier | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 24 nlu.featurizers.dense_featurizer.mitie_featurizer | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 25 nlu.tokenizers.tokenizer | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 26 rasa | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 27 core.actions.action | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 core.policies.ensemble | 1 | 1 | 2 | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 29 core.policies.memoization | 1 | 2 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 30 core.policies.ted_policy | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 31 core.training | 2 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 nlu.extractors.extractor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 core | 2 | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 35 core.policies.rule_policy | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 36 core.policies.unexpected_intent_policy | 2 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 37 core.processor | 2 | 2 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 nlu.classifiers.diet_classifier | 1 | 1 | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 nlu.extractors.mitie_entity_extractor | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 nlu.selectors.response_selector | 1 | 1 | 1 | 1 | 1 | 1 | 3 |
8→6 core.brokers.broker uses utils.endpoints✕
- Connections
- 1 pair of types, where a type in core.brokers.broker uses a type in utils.endpoints.
- The types involved
rasa.core.brokers.broker.EventBroker→rasa.utils.endpoints.EndpointConfig
- Direction
- core.brokers.broker uses utils.endpoints, so a change to utils.endpoints can break core.brokers.broker, while a change to core.brokers.broker can't break utils.endpoints.
- Position
- Below the diagonal: core.brokers.broker uses a module listed above it, which is the healthy direction.
9→17 engine.storage.resource uses engine.storage.storage part of a loop✕
- Connections
- 1 pair of types, where a type in engine.storage.resource uses a type in engine.storage.storage.
- The types involved
rasa.engine.storage.resource.Resource→rasa.engine.storage.storage.ModelStorage
- Direction
- engine.storage.resource uses engine.storage.storage, so a change to engine.storage.storage can break engine.storage.resource, while a change to engine.storage.resource can't break engine.storage.storage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 shared.core.domain uses shared.core.events✕
- Connections
- 1 pair of types, where a type in shared.core.domain uses a type in shared.core.events.
- The types involved
rasa.shared.core.domain.Domain→rasa.shared.core.events.UserUttered
- Direction
- shared.core.domain uses shared.core.events, so a change to shared.core.events can break shared.core.domain, while a change to shared.core.domain can't break shared.core.events.
- Position
- Below the diagonal: shared.core.domain uses a module listed above it, which is the healthy direction.
10→3 shared.core.domain uses shared.exceptions✕
- Connections
- 2 pairs of types, where a type in shared.core.domain uses a type in shared.exceptions.
- The types involved
rasa.shared.core.domain.ActionNotFoundException→rasa.shared.exceptions.RasaExceptionrasa.shared.core.domain.InvalidDomain→rasa.shared.exceptions.RasaException
- Direction
- shared.core.domain uses shared.exceptions, so a change to shared.exceptions can break shared.core.domain, while a change to shared.core.domain can't break shared.exceptions.
- Position
- Below the diagonal: shared.core.domain uses a module listed above it, which is the healthy direction.
11→9 engine.graph uses engine.storage.resource✕
- Connections
- 2 pairs of types, where a type in engine.graph uses a type in engine.storage.resource.
- The types involved
rasa.engine.graph.GraphComponent→rasa.engine.storage.resource.Resourcerasa.engine.graph.GraphNode→rasa.engine.storage.resource.Resource
- Direction
- engine.graph uses engine.storage.resource, so a change to engine.storage.resource can break engine.graph, while a change to engine.graph can't break engine.storage.resource.
- Position
- Below the diagonal: engine.graph uses a module listed above it, which is the healthy direction.
11→17 engine.graph uses engine.storage.storage part of a loop✕
- Connections
- 2 pairs of types, where a type in engine.graph uses a type in engine.storage.storage.
- The types involved
rasa.engine.graph.GraphComponent→rasa.engine.storage.storage.ModelStoragerasa.engine.graph.GraphNode→rasa.engine.storage.storage.ModelStorage
- Direction
- engine.graph uses engine.storage.storage, so a change to engine.storage.storage can break engine.graph, while a change to engine.graph can't break engine.storage.storage.
- Position
- Above the diagonal, so 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→2 shared.core.trackers uses shared.core.events✕
- Connections
- 1 pair of types, where a type in shared.core.trackers uses a type in shared.core.events.
- The types involved
rasa.shared.core.trackers.DialogueStateTracker→rasa.shared.core.events.Event
- Direction
- shared.core.trackers uses shared.core.events, so a change to shared.core.events can break shared.core.trackers, while a change to shared.core.trackers can't break shared.core.events.
- Position
- Below the diagonal: shared.core.trackers uses a module listed above it, which is the healthy direction.
12→10 shared.core.trackers uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in shared.core.trackers uses a type in shared.core.domain.
- The types involved
rasa.shared.core.trackers.DialogueStateTracker→rasa.shared.core.domain.Domain
- Direction
- shared.core.trackers uses shared.core.domain, so a change to shared.core.domain can break shared.core.trackers, while a change to shared.core.trackers can't break shared.core.domain.
- Position
- Below the diagonal: shared.core.trackers uses a module listed above it, which is the healthy direction.
13→2 shared.core.training_data.structures uses shared.core.events✕
- Connections
- 3 pairs of types, where a type in shared.core.training_data.structures uses a type in shared.core.events.
- The types involved
rasa.shared.core.training_data.structures.RuleStep→rasa.shared.core.events.Eventrasa.shared.core.training_data.structures.StoryStep→rasa.shared.core.events.Eventrasa.shared.core.training_data.structures.StoryStep→rasa.shared.core.events.UserUttered
- Direction
- shared.core.training_data.structures uses shared.core.events, so a change to shared.core.events can break shared.core.training_data.structures, while a change to shared.core.training_data.structures can't break shared.core.events.
- Position
- Below the diagonal: shared.core.training_data.structures uses a module listed above it, which is the healthy direction.
13→3 shared.core.training_data.structures uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in shared.core.training_data.structures uses a type in shared.exceptions.
- The types involved
rasa.shared.core.training_data.structures.EventTypeError→rasa.shared.exceptions.RasaCoreException
- Direction
- shared.core.training_data.structures uses shared.exceptions, so a change to shared.exceptions can break shared.core.training_data.structures, while a change to shared.core.training_data.structures can't break shared.exceptions.
- Position
- Below the diagonal: shared.core.training_data.structures uses a module listed above it, which is the healthy direction.
13→10 shared.core.training_data.structures uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in shared.core.training_data.structures uses a type in shared.core.domain.
- The types involved
rasa.shared.core.training_data.structures.Story→rasa.shared.core.domain.Domainrasa.shared.core.training_data.structures.StoryStep→rasa.shared.core.domain.Domain
- Direction
- shared.core.training_data.structures uses shared.core.domain, so a change to shared.core.domain can break shared.core.training_data.structures, while a change to shared.core.training_data.structures can't break shared.core.domain.
- Position
- Below the diagonal: shared.core.training_data.structures uses a module listed above it, which is the healthy direction.
14→1 core.actions.forms uses core.channels.channel✕
- Connections
- 1 pair of types, where a type in core.actions.forms uses a type in core.channels.channel.
- The types involved
rasa.core.actions.forms.FormAction→rasa.core.channels.channel.OutputChannel
- Direction
- core.actions.forms uses core.channels.channel, so a change to core.channels.channel can break core.actions.forms, while a change to core.actions.forms can't break core.channels.channel.
- Position
- Below the diagonal: core.actions.forms uses a module listed above it, which is the healthy direction.
14→2 core.actions.forms uses shared.core.events✕
- Connections
- 1 pair of types, where a type in core.actions.forms uses a type in shared.core.events.
- The types involved
rasa.core.actions.forms.FormAction→rasa.shared.core.events.SlotSet
- Direction
- core.actions.forms uses shared.core.events, so a change to shared.core.events can break core.actions.forms, while a change to core.actions.forms can't break shared.core.events.
- Position
- Below the diagonal: core.actions.forms uses a module listed above it, which is the healthy direction.
14→10 core.actions.forms uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in core.actions.forms uses a type in shared.core.domain.
- The types involved
rasa.core.actions.forms.FormAction→rasa.shared.core.domain.Domain
- Direction
- core.actions.forms uses shared.core.domain, so a change to shared.core.domain can break core.actions.forms, while a change to core.actions.forms can't break shared.core.domain.
- Position
- Below the diagonal: core.actions.forms uses a module listed above it, which is the healthy direction.
14→12 core.actions.forms uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.actions.forms uses a type in shared.core.trackers.
- The types involved
rasa.core.actions.forms.FormAction→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.actions.forms uses shared.core.trackers, so a change to shared.core.trackers can break core.actions.forms, while a change to core.actions.forms can't break shared.core.trackers.
- Position
- Below the diagonal: core.actions.forms uses a module listed above it, which is the healthy direction.
15→2 core.featurizers.tracker_featurizers uses shared.core.events✕
- Connections
- 1 pair of types, where a type in core.featurizers.tracker_featurizers uses a type in shared.core.events.
- The types involved
rasa.core.featurizers.tracker_featurizers.TrackerFeaturizer→rasa.shared.core.events.UserUttered
- Direction
- core.featurizers.tracker_featurizers uses shared.core.events, so a change to shared.core.events can break core.featurizers.tracker_featurizers, while a change to core.featurizers.tracker_featurizers can't break shared.core.events.
- Position
- Below the diagonal: core.featurizers.tracker_featurizers uses a module listed above it, which is the healthy direction.
15→3 core.featurizers.tracker_featurizers uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in core.featurizers.tracker_featurizers uses a type in shared.exceptions.
- The types involved
rasa.core.featurizers.tracker_featurizers.InvalidStory→rasa.shared.exceptions.RasaException
- Direction
- core.featurizers.tracker_featurizers uses shared.exceptions, so a change to shared.exceptions can break core.featurizers.tracker_featurizers, while a change to core.featurizers.tracker_featurizers can't break shared.exceptions.
- Position
- Below the diagonal: core.featurizers.tracker_featurizers uses a module listed above it, which is the healthy direction.
15→10 core.featurizers.tracker_featurizers uses shared.core.domain✕
- Connections
- 4 pairs of types, where a type in core.featurizers.tracker_featurizers uses a type in shared.core.domain.
- The types involved
rasa.core.featurizers.tracker_featurizers.FullDialogueTrackerFeaturizer→rasa.shared.core.domain.Domainrasa.core.featurizers.tracker_featurizers.IntentMaxHistoryTrackerFeaturizer→rasa.shared.core.domain.Domainrasa.core.featurizers.tracker_featurizers.MaxHistoryTrackerFeaturizer→rasa.shared.core.domain.Domainrasa.core.featurizers.tracker_featurizers.TrackerFeaturizer→rasa.shared.core.domain.Domain
- Direction
- core.featurizers.tracker_featurizers uses shared.core.domain, so a change to shared.core.domain can break core.featurizers.tracker_featurizers, while a change to core.featurizers.tracker_featurizers can't break shared.core.domain.
- Position
- Below the diagonal: core.featurizers.tracker_featurizers uses a module listed above it, which is the healthy direction.
15→12 core.featurizers.tracker_featurizers uses shared.core.trackers✕
- Connections
- 3 pairs of types, where a type in core.featurizers.tracker_featurizers uses a type in shared.core.trackers.
- The types involved
rasa.core.featurizers.tracker_featurizers.IntentMaxHistoryTrackerFeaturizer→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.featurizers.tracker_featurizers.MaxHistoryTrackerFeaturizer→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.featurizers.tracker_featurizers.TrackerFeaturizer→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.featurizers.tracker_featurizers uses shared.core.trackers, so a change to shared.core.trackers can break core.featurizers.tracker_featurizers, while a change to core.featurizers.tracker_featurizers can't break shared.core.trackers.
- Position
- Below the diagonal: core.featurizers.tracker_featurizers uses a module listed above it, which is the healthy direction.
16→3 core.tracker_store uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in core.tracker_store uses a type in shared.exceptions.
- The types involved
rasa.core.tracker_store.TrackerDeserialisationException→rasa.shared.exceptions.RasaException
- Direction
- core.tracker_store uses shared.exceptions, so a change to shared.exceptions can break core.tracker_store, while a change to core.tracker_store can't break shared.exceptions.
- Position
- Below the diagonal: core.tracker_store uses a module listed above it, which is the healthy direction.
16→8 core.tracker_store uses core.brokers.broker✕
- Connections
- 1 pair of types, where a type in core.tracker_store uses a type in core.brokers.broker.
- The types involved
rasa.core.tracker_store.TrackerStore→rasa.core.brokers.broker.EventBroker
- Direction
- core.tracker_store uses core.brokers.broker, so a change to core.brokers.broker can break core.tracker_store, while a change to core.tracker_store can't break core.brokers.broker.
- Position
- Below the diagonal: core.tracker_store uses a module listed above it, which is the healthy direction.
16→10 core.tracker_store uses shared.core.domain✕
- Connections
- 7 pairs of types, where a type in core.tracker_store uses a type in shared.core.domain.
- The types involved
rasa.core.tracker_store.AwaitableTrackerStore→rasa.shared.core.domain.Domainrasa.core.tracker_store.DynamoTrackerStore→rasa.shared.core.domain.Domainrasa.core.tracker_store.FailSafeTrackerStore→rasa.shared.core.domain.Domainrasa.core.tracker_store.InMemoryTrackerStore→rasa.shared.core.domain.Domainrasa.core.tracker_store.MongoTrackerStore→rasa.shared.core.domain.Domainrasa.core.tracker_store.RedisTrackerStore→rasa.shared.core.domain.Domainrasa.core.tracker_store.TrackerStore→rasa.shared.core.domain.Domain
- Direction
- core.tracker_store uses shared.core.domain, so a change to shared.core.domain can break core.tracker_store, while a change to core.tracker_store can't break shared.core.domain.
- Position
- Below the diagonal: core.tracker_store uses a module listed above it, which is the healthy direction.
16→12 core.tracker_store uses shared.core.trackers✕
- Connections
- 11 pairs of types, where a type in core.tracker_store uses a type in shared.core.trackers.
- The types involved
rasa.core.tracker_store.AwaitableTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.DynamoTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.FailSafeTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.InMemoryTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.MongoTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.RedisTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.SQLTrackerStore→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.SerializedTrackerAsDict→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.SerializedTrackerAsText→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.SerializedTrackerRepresentation→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.tracker_store.TrackerStore→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.tracker_store uses shared.core.trackers, so a change to shared.core.trackers can break core.tracker_store, while a change to core.tracker_store can't break shared.core.trackers.
- Position
- Below the diagonal: core.tracker_store uses a module listed above it, which is the healthy direction.
17→9 engine.storage.storage uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in engine.storage.storage uses a type in engine.storage.resource.
- The types involved
rasa.engine.storage.storage.ModelStorage→rasa.engine.storage.resource.Resource
- Direction
- engine.storage.storage uses engine.storage.resource, so a change to engine.storage.resource can break engine.storage.storage, while a change to engine.storage.storage can't break engine.storage.resource.
- Position
- Below the diagonal: engine.storage.storage uses a module listed above it, which is the healthy direction.
17→10 engine.storage.storage uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in engine.storage.storage uses a type in shared.core.domain.
- The types involved
rasa.engine.storage.storage.ModelMetadata→rasa.shared.core.domain.Domainrasa.engine.storage.storage.ModelStorage→rasa.shared.core.domain.Domain
- Direction
- engine.storage.storage uses shared.core.domain, so a change to shared.core.domain can break engine.storage.storage, while a change to engine.storage.storage can't break shared.core.domain.
- Position
- Below the diagonal: engine.storage.storage uses a module listed above it, which is the healthy direction.
17→11 engine.storage.storage uses engine.graph✕
- Connections
- 2 pairs of types, where a type in engine.storage.storage uses a type in engine.graph.
- The types involved
rasa.engine.storage.storage.ModelMetadata→rasa.engine.graph.GraphSchemarasa.engine.storage.storage.ModelStorage→rasa.engine.graph.GraphModelConfiguration
- Direction
- engine.storage.storage uses engine.graph, so a change to engine.graph can break engine.storage.storage, while a change to engine.storage.storage can't break engine.graph.
- Position
- Below the diagonal: engine.storage.storage uses a module listed above it, which is the healthy direction.
18→5 shared.importers.importer uses shared.nlu.training_data.training_data✕
- Connections
- 5 pairs of types, where a type in shared.importers.importer uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.shared.importers.importer.CombinedDataImporter→rasa.shared.nlu.training_data.training_data.TrainingDatarasa.shared.importers.importer.E2EImporter→rasa.shared.nlu.training_data.training_data.TrainingDatarasa.shared.importers.importer.NluDataImporter→rasa.shared.nlu.training_data.training_data.TrainingDatarasa.shared.importers.importer.ResponsesSyncImporter→rasa.shared.nlu.training_data.training_data.TrainingDatarasa.shared.importers.importer.TrainingDataImporter→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- shared.importers.importer uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break shared.importers.importer, while a change to shared.importers.importer can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: shared.importers.importer uses a module listed above it, which is the healthy direction.
18→10 shared.importers.importer uses shared.core.domain✕
- Connections
- 5 pairs of types, where a type in shared.importers.importer uses a type in shared.core.domain.
- The types involved
rasa.shared.importers.importer.CombinedDataImporter→rasa.shared.core.domain.Domainrasa.shared.importers.importer.E2EImporter→rasa.shared.core.domain.Domainrasa.shared.importers.importer.NluDataImporter→rasa.shared.core.domain.Domainrasa.shared.importers.importer.ResponsesSyncImporter→rasa.shared.core.domain.Domainrasa.shared.importers.importer.TrainingDataImporter→rasa.shared.core.domain.Domain
- Direction
- shared.importers.importer uses shared.core.domain, so a change to shared.core.domain can break shared.importers.importer, while a change to shared.importers.importer can't break shared.core.domain.
- Position
- Below the diagonal: shared.importers.importer uses a module listed above it, which is the healthy direction.
18→13 shared.importers.importer uses shared.core.training_data.structures✕
- Connections
- 5 pairs of types, where a type in shared.importers.importer uses a type in shared.core.training_data.structures.
- The types involved
rasa.shared.importers.importer.CombinedDataImporter→rasa.shared.core.training_data.structures.StoryGraphrasa.shared.importers.importer.E2EImporter→rasa.shared.core.training_data.structures.StoryGraphrasa.shared.importers.importer.NluDataImporter→rasa.shared.core.training_data.structures.StoryGraphrasa.shared.importers.importer.ResponsesSyncImporter→rasa.shared.core.training_data.structures.StoryGraphrasa.shared.importers.importer.TrainingDataImporter→rasa.shared.core.training_data.structures.StoryGraph
- Direction
- shared.importers.importer uses shared.core.training_data.structures, so a change to shared.core.training_data.structures can break shared.importers.importer, while a change to shared.importers.importer can't break shared.core.training_data.structures.
- Position
- Below the diagonal: shared.importers.importer uses a module listed above it, which is the healthy direction.
19→1 core.agent uses core.channels.channel✕
- Connections
- 2 pairs of types, where a type in core.agent uses a type in core.channels.channel.
- The types involved
rasa.core.agent.Agent→rasa.core.channels.channel.OutputChannelrasa.core.agent.Agent→rasa.core.channels.channel.UserMessage
- Direction
- core.agent uses core.channels.channel, so a change to core.channels.channel can break core.agent, while a change to core.agent can't break core.channels.channel.
- Position
- Below the diagonal: core.agent uses a module listed above it, which is the healthy direction.
19→10 core.agent uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in core.agent uses a type in shared.core.domain.
- The types involved
rasa.core.agent.Agent→rasa.shared.core.domain.Domain
- Direction
- core.agent uses shared.core.domain, so a change to shared.core.domain can break core.agent, while a change to core.agent can't break shared.core.domain.
- Position
- Below the diagonal: core.agent uses a module listed above it, which is the healthy direction.
19→12 core.agent uses shared.core.trackers✕
- Connections
- 2 pairs of types, where a type in core.agent uses a type in shared.core.trackers.
- The types involved
rasa.core.agent.Agent→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.agent.Agent→rasa.shared.core.trackers.EventVerbosity
- Direction
- core.agent uses shared.core.trackers, so a change to shared.core.trackers can break core.agent, while a change to core.agent can't break shared.core.trackers.
- Position
- Below the diagonal: core.agent uses a module listed above it, which is the healthy direction.
19→16 core.agent uses core.tracker_store✕
- Connections
- 1 pair of types, where a type in core.agent uses a type in core.tracker_store.
- The types involved
rasa.core.agent.Agent→rasa.core.tracker_store.TrackerStore
- Direction
- core.agent uses core.tracker_store, so a change to core.tracker_store can break core.agent, while a change to core.agent can't break core.tracker_store.
- Position
- Below the diagonal: core.agent uses a module listed above it, which is the healthy direction.
20→4 core.featurizers.precomputation uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in core.featurizers.precomputation uses a type in shared.nlu.training_data.message.
- The types involved
rasa.core.featurizers.precomputation.MessageContainerForCoreFeaturization→rasa.shared.nlu.training_data.message.Message
- Direction
- core.featurizers.precomputation uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→5 core.featurizers.precomputation uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in core.featurizers.precomputation uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- core.featurizers.precomputation uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→9 core.featurizers.precomputation uses engine.storage.resource✕
- Connections
- 2 pairs of types, where a type in core.featurizers.precomputation uses a type in engine.storage.resource.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationCollector→rasa.engine.storage.resource.Resourcerasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.engine.storage.resource.Resource
- Direction
- core.featurizers.precomputation uses engine.storage.resource, so a change to engine.storage.resource can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break engine.storage.resource.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→10 core.featurizers.precomputation uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in core.featurizers.precomputation uses a type in shared.core.domain.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.shared.core.domain.Domainrasa.core.featurizers.precomputation.MessageContainerForCoreFeaturization→rasa.shared.core.domain.Domain
- Direction
- core.featurizers.precomputation uses shared.core.domain, so a change to shared.core.domain can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break shared.core.domain.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→11 core.featurizers.precomputation uses engine.graph✕
- Connections
- 4 pairs of types, where a type in core.featurizers.precomputation uses a type in engine.graph.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationCollector→rasa.engine.graph.ExecutionContextrasa.core.featurizers.precomputation.CoreFeaturizationCollector→rasa.engine.graph.GraphComponentrasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.engine.graph.ExecutionContextrasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.engine.graph.GraphComponent
- Direction
- core.featurizers.precomputation uses engine.graph, so a change to engine.graph can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break engine.graph.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→12 core.featurizers.precomputation uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.featurizers.precomputation uses a type in shared.core.trackers.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.featurizers.precomputation uses shared.core.trackers, so a change to shared.core.trackers can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break shared.core.trackers.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→13 core.featurizers.precomputation uses shared.core.training_data.structures✕
- Connections
- 1 pair of types, where a type in core.featurizers.precomputation uses a type in shared.core.training_data.structures.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.shared.core.training_data.structures.StoryGraph
- Direction
- core.featurizers.precomputation uses shared.core.training_data.structures, so a change to shared.core.training_data.structures can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break shared.core.training_data.structures.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
20→17 core.featurizers.precomputation uses engine.storage.storage✕
- Connections
- 2 pairs of types, where a type in core.featurizers.precomputation uses a type in engine.storage.storage.
- The types involved
rasa.core.featurizers.precomputation.CoreFeaturizationCollector→rasa.engine.storage.storage.ModelStoragerasa.core.featurizers.precomputation.CoreFeaturizationInputConverter→rasa.engine.storage.storage.ModelStorage
- Direction
- core.featurizers.precomputation uses engine.storage.storage, so a change to engine.storage.storage can break core.featurizers.precomputation, while a change to core.featurizers.precomputation can't break engine.storage.storage.
- Position
- Below the diagonal: core.featurizers.precomputation uses a module listed above it, which is the healthy direction.
21→3 core.policies.policy uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in core.policies.policy uses a type in shared.exceptions.
- The types involved
rasa.core.policies.policy.InvalidPolicyConfig→rasa.shared.exceptions.RasaException
- Direction
- core.policies.policy uses shared.exceptions, so a change to shared.exceptions can break core.policies.policy, while a change to core.policies.policy can't break shared.exceptions.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
21→9 core.policies.policy uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in core.policies.policy uses a type in engine.storage.resource.
- The types involved
rasa.core.policies.policy.Policy→rasa.engine.storage.resource.Resource
- Direction
- core.policies.policy uses engine.storage.resource, so a change to engine.storage.resource can break core.policies.policy, while a change to core.policies.policy can't break engine.storage.resource.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
21→10 core.policies.policy uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in core.policies.policy uses a type in shared.core.domain.
- The types involved
rasa.core.policies.policy.Policy→rasa.shared.core.domain.Domainrasa.core.policies.policy.PolicyPrediction→rasa.shared.core.domain.Domain
- Direction
- core.policies.policy uses shared.core.domain, so a change to shared.core.domain can break core.policies.policy, while a change to core.policies.policy can't break shared.core.domain.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
21→11 core.policies.policy uses engine.graph✕
- Connections
- 2 pairs of types, where a type in core.policies.policy uses a type in engine.graph.
- The types involved
rasa.core.policies.policy.Policy→rasa.engine.graph.ExecutionContextrasa.core.policies.policy.Policy→rasa.engine.graph.GraphComponent
- Direction
- core.policies.policy uses engine.graph, so a change to engine.graph can break core.policies.policy, while a change to core.policies.policy can't break engine.graph.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
21→12 core.policies.policy uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.policies.policy uses a type in shared.core.trackers.
- The types involved
rasa.core.policies.policy.Policy→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.policies.policy uses shared.core.trackers, so a change to shared.core.trackers can break core.policies.policy, while a change to core.policies.policy can't break shared.core.trackers.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
21→15 core.policies.policy uses core.featurizers.tracker_featurizers✕
- Connections
- 2 pairs of types, where a type in core.policies.policy uses a type in core.featurizers.tracker_featurizers.
- The types involved
rasa.core.policies.policy.Policy→rasa.core.featurizers.tracker_featurizers.MaxHistoryTrackerFeaturizerrasa.core.policies.policy.Policy→rasa.core.featurizers.tracker_featurizers.TrackerFeaturizer
- Direction
- core.policies.policy uses core.featurizers.tracker_featurizers, so a change to core.featurizers.tracker_featurizers can break core.policies.policy, while a change to core.policies.policy can't break core.featurizers.tracker_featurizers.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
21→17 core.policies.policy uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in core.policies.policy uses a type in engine.storage.storage.
- The types involved
rasa.core.policies.policy.Policy→rasa.engine.storage.storage.ModelStorage
- Direction
- core.policies.policy uses engine.storage.storage, so a change to engine.storage.storage can break core.policies.policy, while a change to core.policies.policy can't break engine.storage.storage.
- Position
- Below the diagonal: core.policies.policy uses a module listed above it, which is the healthy direction.
22→5 graph_components.validators.default_recipe_validator uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in graph_components.validators.default_recipe_validator uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- graph_components.validators.default_recipe_validator uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
22→9 graph_components.validators.default_recipe_validator uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in graph_components.validators.default_recipe_validator uses a type in engine.storage.resource.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.engine.storage.resource.Resource
- Direction
- graph_components.validators.default_recipe_validator uses engine.storage.resource, so a change to engine.storage.resource can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break engine.storage.resource.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
22→10 graph_components.validators.default_recipe_validator uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in graph_components.validators.default_recipe_validator uses a type in shared.core.domain.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.shared.core.domain.Domain
- Direction
- graph_components.validators.default_recipe_validator uses shared.core.domain, so a change to shared.core.domain can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break shared.core.domain.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
22→11 graph_components.validators.default_recipe_validator uses engine.graph✕
- Connections
- 3 pairs of types, where a type in graph_components.validators.default_recipe_validator uses a type in engine.graph.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.engine.graph.ExecutionContextrasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.engine.graph.GraphComponentrasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.engine.graph.GraphSchema
- Direction
- graph_components.validators.default_recipe_validator uses engine.graph, so a change to engine.graph can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break engine.graph.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
22→13 graph_components.validators.default_recipe_validator uses shared.core.training_data.structures✕
- Connections
- 1 pair of types, where a type in graph_components.validators.default_recipe_validator uses a type in shared.core.training_data.structures.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.shared.core.training_data.structures.StoryGraph
- Direction
- graph_components.validators.default_recipe_validator uses shared.core.training_data.structures, so a change to shared.core.training_data.structures can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break shared.core.training_data.structures.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
22→17 graph_components.validators.default_recipe_validator uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in graph_components.validators.default_recipe_validator uses a type in engine.storage.storage.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.engine.storage.storage.ModelStorage
- Direction
- graph_components.validators.default_recipe_validator uses engine.storage.storage, so a change to engine.storage.storage can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break engine.storage.storage.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
22→18 graph_components.validators.default_recipe_validator uses shared.importers.importer✕
- Connections
- 1 pair of types, where a type in graph_components.validators.default_recipe_validator uses a type in shared.importers.importer.
- The types involved
rasa.graph_components.validators.default_recipe_validator.DefaultV1RecipeValidator→rasa.shared.importers.importer.TrainingDataImporter
- Direction
- graph_components.validators.default_recipe_validator uses shared.importers.importer, so a change to shared.importers.importer can break graph_components.validators.default_recipe_validator, while a change to graph_components.validators.default_recipe_validator can't break shared.importers.importer.
- Position
- Below the diagonal: graph_components.validators.default_recipe_validator uses a module listed above it, which is the healthy direction.
23→4 nlu.classifiers.mitie_intent_classifier uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.mitie_intent_classifier uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.classifiers.mitie_intent_classifier.MitieIntentClassifier→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.classifiers.mitie_intent_classifier uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.classifiers.mitie_intent_classifier, while a change to nlu.classifiers.mitie_intent_classifier can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.classifiers.mitie_intent_classifier uses a module listed above it, which is the healthy direction.
23→5 nlu.classifiers.mitie_intent_classifier uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.mitie_intent_classifier uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.classifiers.mitie_intent_classifier.MitieIntentClassifier→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.classifiers.mitie_intent_classifier uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.classifiers.mitie_intent_classifier, while a change to nlu.classifiers.mitie_intent_classifier can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.classifiers.mitie_intent_classifier uses a module listed above it, which is the healthy direction.
23→9 nlu.classifiers.mitie_intent_classifier uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.mitie_intent_classifier uses a type in engine.storage.resource.
- The types involved
rasa.nlu.classifiers.mitie_intent_classifier.MitieIntentClassifier→rasa.engine.storage.resource.Resource
- Direction
- nlu.classifiers.mitie_intent_classifier uses engine.storage.resource, so a change to engine.storage.resource can break nlu.classifiers.mitie_intent_classifier, while a change to nlu.classifiers.mitie_intent_classifier can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.classifiers.mitie_intent_classifier uses a module listed above it, which is the healthy direction.
23→11 nlu.classifiers.mitie_intent_classifier uses engine.graph✕
- Connections
- 2 pairs of types, where a type in nlu.classifiers.mitie_intent_classifier uses a type in engine.graph.
- The types involved
rasa.nlu.classifiers.mitie_intent_classifier.MitieIntentClassifier→rasa.engine.graph.ExecutionContextrasa.nlu.classifiers.mitie_intent_classifier.MitieIntentClassifier→rasa.engine.graph.GraphComponent
- Direction
- nlu.classifiers.mitie_intent_classifier uses engine.graph, so a change to engine.graph can break nlu.classifiers.mitie_intent_classifier, while a change to nlu.classifiers.mitie_intent_classifier can't break engine.graph.
- Position
- Below the diagonal: nlu.classifiers.mitie_intent_classifier uses a module listed above it, which is the healthy direction.
23→17 nlu.classifiers.mitie_intent_classifier uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.mitie_intent_classifier uses a type in engine.storage.storage.
- The types involved
rasa.nlu.classifiers.mitie_intent_classifier.MitieIntentClassifier→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.classifiers.mitie_intent_classifier uses engine.storage.storage, so a change to engine.storage.storage can break nlu.classifiers.mitie_intent_classifier, while a change to nlu.classifiers.mitie_intent_classifier can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.classifiers.mitie_intent_classifier uses a module listed above it, which is the healthy direction.
24→4 nlu.featurizers.dense_featurizer.mitie_featurizer uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.dense_featurizer.mitie_featurizer uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.featurizers.dense_featurizer.mitie_featurizer.MitieFeaturizer→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.featurizers.dense_featurizer.mitie_featurizer uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.featurizers.dense_featurizer.mitie_featurizer, while a change to nlu.featurizers.dense_featurizer.mitie_featurizer can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.featurizers.dense_featurizer.mitie_featurizer uses a module listed above it, which is the healthy direction.
24→5 nlu.featurizers.dense_featurizer.mitie_featurizer uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.dense_featurizer.mitie_featurizer uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.featurizers.dense_featurizer.mitie_featurizer.MitieFeaturizer→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.featurizers.dense_featurizer.mitie_featurizer uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.featurizers.dense_featurizer.mitie_featurizer, while a change to nlu.featurizers.dense_featurizer.mitie_featurizer can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.featurizers.dense_featurizer.mitie_featurizer uses a module listed above it, which is the healthy direction.
24→9 nlu.featurizers.dense_featurizer.mitie_featurizer uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.dense_featurizer.mitie_featurizer uses a type in engine.storage.resource.
- The types involved
rasa.nlu.featurizers.dense_featurizer.mitie_featurizer.MitieFeaturizer→rasa.engine.storage.resource.Resource
- Direction
- nlu.featurizers.dense_featurizer.mitie_featurizer uses engine.storage.resource, so a change to engine.storage.resource can break nlu.featurizers.dense_featurizer.mitie_featurizer, while a change to nlu.featurizers.dense_featurizer.mitie_featurizer can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.featurizers.dense_featurizer.mitie_featurizer uses a module listed above it, which is the healthy direction.
24→11 nlu.featurizers.dense_featurizer.mitie_featurizer uses engine.graph✕
- Connections
- 2 pairs of types, where a type in nlu.featurizers.dense_featurizer.mitie_featurizer uses a type in engine.graph.
- The types involved
rasa.nlu.featurizers.dense_featurizer.mitie_featurizer.MitieFeaturizer→rasa.engine.graph.ExecutionContextrasa.nlu.featurizers.dense_featurizer.mitie_featurizer.MitieFeaturizer→rasa.engine.graph.GraphComponent
- Direction
- nlu.featurizers.dense_featurizer.mitie_featurizer uses engine.graph, so a change to engine.graph can break nlu.featurizers.dense_featurizer.mitie_featurizer, while a change to nlu.featurizers.dense_featurizer.mitie_featurizer can't break engine.graph.
- Position
- Below the diagonal: nlu.featurizers.dense_featurizer.mitie_featurizer uses a module listed above it, which is the healthy direction.
24→17 nlu.featurizers.dense_featurizer.mitie_featurizer uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.dense_featurizer.mitie_featurizer uses a type in engine.storage.storage.
- The types involved
rasa.nlu.featurizers.dense_featurizer.mitie_featurizer.MitieFeaturizer→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.featurizers.dense_featurizer.mitie_featurizer uses engine.storage.storage, so a change to engine.storage.storage can break nlu.featurizers.dense_featurizer.mitie_featurizer, while a change to nlu.featurizers.dense_featurizer.mitie_featurizer can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.featurizers.dense_featurizer.mitie_featurizer uses a module listed above it, which is the healthy direction.
25→4 nlu.tokenizers.tokenizer uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.tokenizers.tokenizer uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.tokenizers.tokenizer.Tokenizer→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.tokenizers.tokenizer uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.tokenizers.tokenizer, while a change to nlu.tokenizers.tokenizer can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.tokenizers.tokenizer uses a module listed above it, which is the healthy direction.
25→5 nlu.tokenizers.tokenizer uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.tokenizers.tokenizer uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.tokenizers.tokenizer.Tokenizer→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.tokenizers.tokenizer uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.tokenizers.tokenizer, while a change to nlu.tokenizers.tokenizer can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.tokenizers.tokenizer uses a module listed above it, which is the healthy direction.
25→9 nlu.tokenizers.tokenizer uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.tokenizers.tokenizer uses a type in engine.storage.resource.
- The types involved
rasa.nlu.tokenizers.tokenizer.Tokenizer→rasa.engine.storage.resource.Resource
- Direction
- nlu.tokenizers.tokenizer uses engine.storage.resource, so a change to engine.storage.resource can break nlu.tokenizers.tokenizer, while a change to nlu.tokenizers.tokenizer can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.tokenizers.tokenizer uses a module listed above it, which is the healthy direction.
25→11 nlu.tokenizers.tokenizer uses engine.graph✕
- Connections
- 2 pairs of types, where a type in nlu.tokenizers.tokenizer uses a type in engine.graph.
- The types involved
rasa.nlu.tokenizers.tokenizer.Tokenizer→rasa.engine.graph.ExecutionContextrasa.nlu.tokenizers.tokenizer.Tokenizer→rasa.engine.graph.GraphComponent
- Direction
- nlu.tokenizers.tokenizer uses engine.graph, so a change to engine.graph can break nlu.tokenizers.tokenizer, while a change to nlu.tokenizers.tokenizer can't break engine.graph.
- Position
- Below the diagonal: nlu.tokenizers.tokenizer uses a module listed above it, which is the healthy direction.
25→17 nlu.tokenizers.tokenizer uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.tokenizers.tokenizer uses a type in engine.storage.storage.
- The types involved
rasa.nlu.tokenizers.tokenizer.Tokenizer→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.tokenizers.tokenizer uses engine.storage.storage, so a change to engine.storage.storage can break nlu.tokenizers.tokenizer, while a change to nlu.tokenizers.tokenizer can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.tokenizers.tokenizer uses a module listed above it, which is the healthy direction.
26→1 rasa uses core.channels.channel✕
- Connections
- 1 pair of types, where a type in rasa uses a type in core.channels.channel.
- The types involved
rasa.server→rasa.core.channels.channel.OutputChannel
- Direction
- rasa uses core.channels.channel, so a change to core.channels.channel can break rasa, while a change to rasa can't break core.channels.channel.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→5 rasa uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in rasa uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.model_testing→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- rasa uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break rasa, while a change to rasa can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→10 rasa uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in rasa uses a type in shared.core.domain.
- The types involved
rasa.model_training→rasa.shared.core.domain.Domainrasa.server→rasa.shared.core.domain.Domain
- Direction
- rasa uses shared.core.domain, so a change to shared.core.domain can break rasa, while a change to rasa can't break shared.core.domain.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→12 rasa uses shared.core.trackers✕
- Connections
- 2 pairs of types, where a type in rasa uses a type in shared.core.trackers.
- The types involved
rasa.server→rasa.shared.core.trackers.DialogueStateTrackerrasa.server→rasa.shared.core.trackers.EventVerbosity
- Direction
- rasa uses shared.core.trackers, so a change to shared.core.trackers can break rasa, while a change to rasa can't break shared.core.trackers.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→13 rasa uses shared.core.training_data.structures✕
- Connections
- 1 pair of types, where a type in rasa uses a type in shared.core.training_data.structures.
- The types involved
rasa.model_training→rasa.shared.core.training_data.structures.StoryGraph
- Direction
- rasa uses shared.core.training_data.structures, so a change to shared.core.training_data.structures can break rasa, while a change to rasa can't break shared.core.training_data.structures.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→17 rasa uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in rasa uses a type in engine.storage.storage.
- The types involved
rasa.model_training→rasa.engine.storage.storage.ModelStorage
- Direction
- rasa uses engine.storage.storage, so a change to engine.storage.storage can break rasa, while a change to rasa can't break engine.storage.storage.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→18 rasa uses shared.importers.importer✕
- Connections
- 1 pair of types, where a type in rasa uses a type in shared.importers.importer.
- The types involved
rasa.model_training→rasa.shared.importers.importer.TrainingDataImporter
- Direction
- rasa uses shared.importers.importer, so a change to shared.importers.importer can break rasa, while a change to rasa can't break shared.importers.importer.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
26→19 rasa uses core.agent✕
- Connections
- 1 pair of types, where a type in rasa uses a type in core.agent.
- The types involved
rasa.server→rasa.core.agent.Agent
- Direction
- rasa uses core.agent, so a change to core.agent can break rasa, while a change to rasa can't break core.agent.
- Position
- Below the diagonal: rasa uses a module listed above it, which is the healthy direction.
27→2 core.actions.action uses shared.core.events✕
- Connections
- 2 pairs of types, where a type in core.actions.action uses a type in shared.core.events.
- The types involved
rasa.core.actions.action.Action→rasa.shared.core.events.ActionExecutedrasa.core.actions.action.ActionEndToEndResponse→rasa.shared.core.events.ActionExecuted
- Direction
- core.actions.action uses shared.core.events, so a change to shared.core.events can break core.actions.action, while a change to core.actions.action can't break shared.core.events.
- Position
- Below the diagonal: core.actions.action uses a module listed above it, which is the healthy direction.
27→3 core.actions.action uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in core.actions.action uses a type in shared.exceptions.
- The types involved
rasa.core.actions.action.ActionExecutionRejection→rasa.shared.exceptions.RasaException
- Direction
- core.actions.action uses shared.exceptions, so a change to shared.exceptions can break core.actions.action, while a change to core.actions.action can't break shared.exceptions.
- Position
- Below the diagonal: core.actions.action uses a module listed above it, which is the healthy direction.
27→21 core.actions.action uses core.policies.policy✕
- Connections
- 2 pairs of types, where a type in core.actions.action uses a type in core.policies.policy.
- The types involved
rasa.core.actions.action.Action→rasa.core.policies.policy.PolicyPredictionrasa.core.actions.action.ActionEndToEndResponse→rasa.core.policies.policy.PolicyPrediction
- Direction
- core.actions.action uses core.policies.policy, so a change to core.policies.policy can break core.actions.action, while a change to core.actions.action can't break core.policies.policy.
- Position
- Below the diagonal: core.actions.action uses a module listed above it, which is the healthy direction.
28→3 core.policies.ensemble uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in core.policies.ensemble uses a type in shared.exceptions.
- The types involved
rasa.core.policies.ensemble.InvalidPolicyEnsembleConfig→rasa.shared.exceptions.RasaException
- Direction
- core.policies.ensemble uses shared.exceptions, so a change to shared.exceptions can break core.policies.ensemble, while a change to core.policies.ensemble can't break shared.exceptions.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
28→9 core.policies.ensemble uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in core.policies.ensemble uses a type in engine.storage.resource.
- The types involved
rasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.engine.storage.resource.Resource
- Direction
- core.policies.ensemble uses engine.storage.resource, so a change to engine.storage.resource can break core.policies.ensemble, while a change to core.policies.ensemble can't break engine.storage.resource.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
28→10 core.policies.ensemble uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in core.policies.ensemble uses a type in shared.core.domain.
- The types involved
rasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.shared.core.domain.Domainrasa.core.policies.ensemble.PolicyPredictionEnsemble→rasa.shared.core.domain.Domain
- Direction
- core.policies.ensemble uses shared.core.domain, so a change to shared.core.domain can break core.policies.ensemble, while a change to core.policies.ensemble can't break shared.core.domain.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
28→11 core.policies.ensemble uses engine.graph✕
- Connections
- 2 pairs of types, where a type in core.policies.ensemble uses a type in engine.graph.
- The types involved
rasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.engine.graph.ExecutionContextrasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.engine.graph.GraphComponent
- Direction
- core.policies.ensemble uses engine.graph, so a change to engine.graph can break core.policies.ensemble, while a change to core.policies.ensemble can't break engine.graph.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
28→12 core.policies.ensemble uses shared.core.trackers✕
- Connections
- 2 pairs of types, where a type in core.policies.ensemble uses a type in shared.core.trackers.
- The types involved
rasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.policies.ensemble.PolicyPredictionEnsemble→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.policies.ensemble uses shared.core.trackers, so a change to shared.core.trackers can break core.policies.ensemble, while a change to core.policies.ensemble can't break shared.core.trackers.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
28→17 core.policies.ensemble uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in core.policies.ensemble uses a type in engine.storage.storage.
- The types involved
rasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.engine.storage.storage.ModelStorage
- Direction
- core.policies.ensemble uses engine.storage.storage, so a change to engine.storage.storage can break core.policies.ensemble, while a change to core.policies.ensemble can't break engine.storage.storage.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
28→21 core.policies.ensemble uses core.policies.policy✕
- Connections
- 2 pairs of types, where a type in core.policies.ensemble uses a type in core.policies.policy.
- The types involved
rasa.core.policies.ensemble.DefaultPolicyPredictionEnsemble→rasa.core.policies.policy.PolicyPredictionrasa.core.policies.ensemble.PolicyPredictionEnsemble→rasa.core.policies.policy.PolicyPrediction
- Direction
- core.policies.ensemble uses core.policies.policy, so a change to core.policies.policy can break core.policies.ensemble, while a change to core.policies.ensemble can't break core.policies.policy.
- Position
- Below the diagonal: core.policies.ensemble uses a module listed above it, which is the healthy direction.
29→9 core.policies.memoization uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in core.policies.memoization uses a type in engine.storage.resource.
- The types involved
rasa.core.policies.memoization.MemoizationPolicy→rasa.engine.storage.resource.Resource
- Direction
- core.policies.memoization uses engine.storage.resource, so a change to engine.storage.resource can break core.policies.memoization, while a change to core.policies.memoization can't break engine.storage.resource.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
29→10 core.policies.memoization uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in core.policies.memoization uses a type in shared.core.domain.
- The types involved
rasa.core.policies.memoization.AugmentedMemoizationPolicy→rasa.shared.core.domain.Domainrasa.core.policies.memoization.MemoizationPolicy→rasa.shared.core.domain.Domain
- Direction
- core.policies.memoization uses shared.core.domain, so a change to shared.core.domain can break core.policies.memoization, while a change to core.policies.memoization can't break shared.core.domain.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
29→11 core.policies.memoization uses engine.graph✕
- Connections
- 1 pair of types, where a type in core.policies.memoization uses a type in engine.graph.
- The types involved
rasa.core.policies.memoization.MemoizationPolicy→rasa.engine.graph.ExecutionContext
- Direction
- core.policies.memoization uses engine.graph, so a change to engine.graph can break core.policies.memoization, while a change to core.policies.memoization can't break engine.graph.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
29→12 core.policies.memoization uses shared.core.trackers✕
- Connections
- 2 pairs of types, where a type in core.policies.memoization uses a type in shared.core.trackers.
- The types involved
rasa.core.policies.memoization.AugmentedMemoizationPolicy→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.policies.memoization.MemoizationPolicy→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.policies.memoization uses shared.core.trackers, so a change to shared.core.trackers can break core.policies.memoization, while a change to core.policies.memoization can't break shared.core.trackers.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
29→15 core.policies.memoization uses core.featurizers.tracker_featurizers✕
- Connections
- 1 pair of types, where a type in core.policies.memoization uses a type in core.featurizers.tracker_featurizers.
- The types involved
rasa.core.policies.memoization.MemoizationPolicy→rasa.core.featurizers.tracker_featurizers.MaxHistoryTrackerFeaturizer
- Direction
- core.policies.memoization uses core.featurizers.tracker_featurizers, so a change to core.featurizers.tracker_featurizers can break core.policies.memoization, while a change to core.policies.memoization can't break core.featurizers.tracker_featurizers.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
29→17 core.policies.memoization uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in core.policies.memoization uses a type in engine.storage.storage.
- The types involved
rasa.core.policies.memoization.MemoizationPolicy→rasa.engine.storage.storage.ModelStorage
- Direction
- core.policies.memoization uses engine.storage.storage, so a change to engine.storage.storage can break core.policies.memoization, while a change to core.policies.memoization can't break engine.storage.storage.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
29→21 core.policies.memoization uses core.policies.policy✕
- Connections
- 2 pairs of types, where a type in core.policies.memoization uses a type in core.policies.policy.
- The types involved
rasa.core.policies.memoization.MemoizationPolicy→rasa.core.policies.policy.Policyrasa.core.policies.memoization.MemoizationPolicy→rasa.core.policies.policy.PolicyPrediction
- Direction
- core.policies.memoization uses core.policies.policy, so a change to core.policies.policy can break core.policies.memoization, while a change to core.policies.memoization can't break core.policies.policy.
- Position
- Below the diagonal: core.policies.memoization uses a module listed above it, which is the healthy direction.
30→7 core.policies.ted_policy uses utils.tensorflow.model_data✕
- Connections
- 2 pairs of types, where a type in core.policies.ted_policy uses a type in utils.tensorflow.model_data.
- The types involved
rasa.core.policies.ted_policy.TED→rasa.utils.tensorflow.model_data.RasaModelDatarasa.core.policies.ted_policy.TEDPolicy→rasa.utils.tensorflow.model_data.RasaModelData
- Direction
- core.policies.ted_policy uses utils.tensorflow.model_data, so a change to utils.tensorflow.model_data can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break utils.tensorflow.model_data.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→9 core.policies.ted_policy uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in engine.storage.resource.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.engine.storage.resource.Resource
- Direction
- core.policies.ted_policy uses engine.storage.resource, so a change to engine.storage.resource can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break engine.storage.resource.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→10 core.policies.ted_policy uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in shared.core.domain.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.shared.core.domain.Domain
- Direction
- core.policies.ted_policy uses shared.core.domain, so a change to shared.core.domain can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break shared.core.domain.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→11 core.policies.ted_policy uses engine.graph✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in engine.graph.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.engine.graph.ExecutionContext
- Direction
- core.policies.ted_policy uses engine.graph, so a change to engine.graph can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break engine.graph.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→12 core.policies.ted_policy uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in shared.core.trackers.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.policies.ted_policy uses shared.core.trackers, so a change to shared.core.trackers can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break shared.core.trackers.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→15 core.policies.ted_policy uses core.featurizers.tracker_featurizers✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in core.featurizers.tracker_featurizers.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.core.featurizers.tracker_featurizers.TrackerFeaturizer
- Direction
- core.policies.ted_policy uses core.featurizers.tracker_featurizers, so a change to core.featurizers.tracker_featurizers can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break core.featurizers.tracker_featurizers.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→17 core.policies.ted_policy uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in engine.storage.storage.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.engine.storage.storage.ModelStorage
- Direction
- core.policies.ted_policy uses engine.storage.storage, so a change to engine.storage.storage can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break engine.storage.storage.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→20 core.policies.ted_policy uses core.featurizers.precomputation✕
- Connections
- 1 pair of types, where a type in core.policies.ted_policy uses a type in core.featurizers.precomputation.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.core.featurizers.precomputation.MessageContainerForCoreFeaturization
- Direction
- core.policies.ted_policy uses core.featurizers.precomputation, so a change to core.featurizers.precomputation can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break core.featurizers.precomputation.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
30→21 core.policies.ted_policy uses core.policies.policy✕
- Connections
- 2 pairs of types, where a type in core.policies.ted_policy uses a type in core.policies.policy.
- The types involved
rasa.core.policies.ted_policy.TEDPolicy→rasa.core.policies.policy.Policyrasa.core.policies.ted_policy.TEDPolicy→rasa.core.policies.policy.PolicyPrediction
- Direction
- core.policies.ted_policy uses core.policies.policy, so a change to core.policies.policy can break core.policies.ted_policy, while a change to core.policies.ted_policy can't break core.policies.policy.
- Position
- Below the diagonal: core.policies.ted_policy uses a module listed above it, which is the healthy direction.
31→2 core.training uses shared.core.events✕
- Connections
- 2 pairs of types, where a type in core.training uses a type in shared.core.events.
- The types involved
rasa.core.training.interactive→rasa.shared.core.events.BotUtteredrasa.core.training.story_conflict→rasa.shared.core.events.Event
- Direction
- core.training uses shared.core.events, so a change to shared.core.events can break core.training, while a change to core.training can't break shared.core.events.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
31→4 core.training uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in core.training uses a type in shared.nlu.training_data.message.
- The types involved
rasa.core.training.interactive→rasa.shared.nlu.training_data.message.Message
- Direction
- core.training uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break core.training, while a change to core.training can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
31→6 core.training uses utils.endpoints✕
- Connections
- 1 pair of types, where a type in core.training uses a type in utils.endpoints.
- The types involved
rasa.core.training.interactive→rasa.utils.endpoints.EndpointConfig
- Direction
- core.training uses utils.endpoints, so a change to utils.endpoints can break core.training, while a change to core.training can't break utils.endpoints.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
31→10 core.training uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in core.training uses a type in shared.core.domain.
- The types involved
rasa.core.training.interactive→rasa.shared.core.domain.Domainrasa.core.training.story_conflict→rasa.shared.core.domain.Domain
- Direction
- core.training uses shared.core.domain, so a change to shared.core.domain can break core.training, while a change to core.training can't break shared.core.domain.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
31→12 core.training uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.training uses a type in shared.core.trackers.
- The types involved
rasa.core.training.interactive→rasa.shared.core.trackers.EventVerbosity
- Direction
- core.training uses shared.core.trackers, so a change to shared.core.trackers can break core.training, while a change to core.training can't break shared.core.trackers.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
31→18 core.training uses shared.importers.importer✕
- Connections
- 1 pair of types, where a type in core.training uses a type in shared.importers.importer.
- The types involved
rasa.core.training.interactive→rasa.shared.importers.importer.TrainingDataImporter
- Direction
- core.training uses shared.importers.importer, so a change to shared.importers.importer can break core.training, while a change to core.training can't break shared.importers.importer.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
31→25 core.training uses nlu.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in core.training uses a type in nlu.tokenizers.tokenizer.
- The types involved
rasa.core.training.story_conflict→rasa.nlu.tokenizers.tokenizer.Tokenizer
- Direction
- core.training uses nlu.tokenizers.tokenizer, so a change to nlu.tokenizers.tokenizer can break core.training, while a change to core.training can't break nlu.tokenizers.tokenizer.
- Position
- Below the diagonal: core.training uses a module listed above it, which is the healthy direction.
32→5 nlu.extractors.extractor uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.extractors.extractor uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.extractors.extractor.EntityExtractorMixin→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.extractors.extractor uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.extractors.extractor, while a change to nlu.extractors.extractor can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.extractors.extractor uses a module listed above it, which is the healthy direction.
32→25 nlu.extractors.extractor uses nlu.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in nlu.extractors.extractor uses a type in nlu.tokenizers.tokenizer.
- The types involved
rasa.nlu.extractors.extractor.EntityExtractorMixin→rasa.nlu.tokenizers.tokenizer.Token
- Direction
- nlu.extractors.extractor uses nlu.tokenizers.tokenizer, so a change to nlu.tokenizers.tokenizer can break nlu.extractors.extractor, while a change to nlu.extractors.extractor can't break nlu.tokenizers.tokenizer.
- Position
- Below the diagonal: nlu.extractors.extractor uses a module listed above it, which is the healthy direction.
33→4 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer, while a change to nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a module listed above it, which is the healthy direction.
33→5 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer, while a change to nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a module listed above it, which is the healthy direction.
33→9 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a type in engine.storage.resource.
- The types involved
rasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.engine.storage.resource.Resource
- Direction
- nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses engine.storage.resource, so a change to engine.storage.resource can break nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer, while a change to nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a module listed above it, which is the healthy direction.
33→11 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses engine.graph✕
- Connections
- 2 pairs of types, where a type in nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a type in engine.graph.
- The types involved
rasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.engine.graph.ExecutionContextrasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.engine.graph.GraphComponent
- Direction
- nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses engine.graph, so a change to engine.graph can break nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer, while a change to nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer can't break engine.graph.
- Position
- Below the diagonal: nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a module listed above it, which is the healthy direction.
33→17 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a type in engine.storage.storage.
- The types involved
rasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses engine.storage.storage, so a change to engine.storage.storage can break nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer, while a change to nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a module listed above it, which is the healthy direction.
33→25 nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses nlu.tokenizers.tokenizer✕
- Connections
- 1 pair of types, where a type in nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a type in nlu.tokenizers.tokenizer.
- The types involved
rasa.nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer.LexicalSyntacticFeaturizer→rasa.nlu.tokenizers.tokenizer.Token
- Direction
- nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses nlu.tokenizers.tokenizer, so a change to nlu.tokenizers.tokenizer can break nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer, while a change to nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer can't break nlu.tokenizers.tokenizer.
- Position
- Below the diagonal: nlu.featurizers.sparse_featurizer.lexical_syntactic_featurizer uses a module listed above it, which is the healthy direction.
34→2 core uses shared.core.events✕
- Connections
- 2 pairs of types, where a type in core uses a type in shared.core.events.
- The types involved
rasa.core.test→rasa.shared.core.events.ActionExecutedrasa.core.test→rasa.shared.core.events.UserUttered
- Direction
- core uses shared.core.events, so a change to shared.core.events can break core, while a change to core can't break shared.core.events.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→6 core uses utils.endpoints✕
- Connections
- 3 pairs of types, where a type in core uses a type in utils.endpoints.
- The types involved
rasa.core.agent→rasa.utils.endpoints.EndpointConfigrasa.core.lock_store→rasa.utils.endpoints.EndpointConfigrasa.core.tracker_store→rasa.utils.endpoints.EndpointConfig
- Direction
- core uses utils.endpoints, so a change to utils.endpoints can break core, while a change to core can't break utils.endpoints.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→10 core uses shared.core.domain✕
- Connections
- 2 pairs of types, where a type in core uses a type in shared.core.domain.
- The types involved
rasa.core.test→rasa.shared.core.domain.Domainrasa.core.tracker_store→rasa.shared.core.domain.Domain
- Direction
- core uses shared.core.domain, so a change to shared.core.domain can break core, while a change to core can't break shared.core.domain.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→12 core uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core uses a type in shared.core.trackers.
- The types involved
rasa.core.test→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core uses shared.core.trackers, so a change to shared.core.trackers can break core, while a change to core can't break shared.core.trackers.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→13 core uses shared.core.training_data.structures✕
- Connections
- 1 pair of types, where a type in core uses a type in shared.core.training_data.structures.
- The types involved
rasa.core.test→rasa.shared.core.training_data.structures.StoryStep
- Direction
- core uses shared.core.training_data.structures, so a change to shared.core.training_data.structures can break core, while a change to core can't break shared.core.training_data.structures.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→16 core uses core.tracker_store✕
- Connections
- 1 pair of types, where a type in core uses a type in core.tracker_store.
- The types involved
rasa.core.tracker_store→rasa.core.tracker_store.TrackerStore
- Direction
- core uses core.tracker_store, so a change to core.tracker_store can break core, while a change to core can't break core.tracker_store.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→18 core uses shared.importers.importer✕
- Connections
- 1 pair of types, where a type in core uses a type in shared.importers.importer.
- The types involved
rasa.core.train→rasa.shared.importers.importer.TrainingDataImporter
- Direction
- core uses shared.importers.importer, so a change to shared.importers.importer can break core, while a change to core can't break shared.importers.importer.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→19 core uses core.agent✕
- Connections
- 1 pair of types, where a type in core uses a type in core.agent.
- The types involved
rasa.core.run→rasa.core.agent.Agent
- Direction
- core uses core.agent, so a change to core.agent can break core, while a change to core can't break core.agent.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→21 core uses core.policies.policy✕
- Connections
- 1 pair of types, where a type in core uses a type in core.policies.policy.
- The types involved
rasa.core.test→rasa.core.policies.policy.PolicyPrediction
- Direction
- core uses core.policies.policy, so a change to core.policies.policy can break core, while a change to core can't break core.policies.policy.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
34→27 core uses core.actions.action✕
- Connections
- 1 pair of types, where a type in core uses a type in core.actions.action.
- The types involved
rasa.core.test→rasa.core.actions.action.Action
- Direction
- core uses core.actions.action, so a change to core.actions.action can break core, while a change to core can't break core.actions.action.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
35→3 core.policies.rule_policy uses shared.exceptions✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in shared.exceptions.
- The types involved
rasa.core.policies.rule_policy.InvalidRule→rasa.shared.exceptions.RasaException
- Direction
- core.policies.rule_policy uses shared.exceptions, so a change to shared.exceptions can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break shared.exceptions.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→9 core.policies.rule_policy uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in engine.storage.resource.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.engine.storage.resource.Resource
- Direction
- core.policies.rule_policy uses engine.storage.resource, so a change to engine.storage.resource can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break engine.storage.resource.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→10 core.policies.rule_policy uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in shared.core.domain.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.shared.core.domain.Domain
- Direction
- core.policies.rule_policy uses shared.core.domain, so a change to shared.core.domain can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break shared.core.domain.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→11 core.policies.rule_policy uses engine.graph✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in engine.graph.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.engine.graph.ExecutionContext
- Direction
- core.policies.rule_policy uses engine.graph, so a change to engine.graph can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break engine.graph.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→12 core.policies.rule_policy uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in shared.core.trackers.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.policies.rule_policy uses shared.core.trackers, so a change to shared.core.trackers can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break shared.core.trackers.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→17 core.policies.rule_policy uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in engine.storage.storage.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.engine.storage.storage.ModelStorage
- Direction
- core.policies.rule_policy uses engine.storage.storage, so a change to engine.storage.storage can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break engine.storage.storage.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→21 core.policies.rule_policy uses core.policies.policy✕
- Connections
- 2 pairs of types, where a type in core.policies.rule_policy uses a type in core.policies.policy.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.core.policies.policy.PolicyPredictionrasa.core.policies.rule_policy.RulePolicy→rasa.core.policies.policy.SupportedData
- Direction
- core.policies.rule_policy uses core.policies.policy, so a change to core.policies.policy can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break core.policies.policy.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
35→29 core.policies.rule_policy uses core.policies.memoization✕
- Connections
- 1 pair of types, where a type in core.policies.rule_policy uses a type in core.policies.memoization.
- The types involved
rasa.core.policies.rule_policy.RulePolicy→rasa.core.policies.memoization.MemoizationPolicy
- Direction
- core.policies.rule_policy uses core.policies.memoization, so a change to core.policies.memoization can break core.policies.rule_policy, while a change to core.policies.rule_policy can't break core.policies.memoization.
- Position
- Below the diagonal: core.policies.rule_policy uses a module listed above it, which is the healthy direction.
36→7 core.policies.unexpected_intent_policy uses utils.tensorflow.model_data✕
- Connections
- 2 pairs of types, where a type in core.policies.unexpected_intent_policy uses a type in utils.tensorflow.model_data.
- The types involved
rasa.core.policies.unexpected_intent_policy.IntentTED→rasa.utils.tensorflow.model_data.RasaModelDatarasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.utils.tensorflow.model_data.RasaModelData
- Direction
- core.policies.unexpected_intent_policy uses utils.tensorflow.model_data, so a change to utils.tensorflow.model_data can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break utils.tensorflow.model_data.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→9 core.policies.unexpected_intent_policy uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in core.policies.unexpected_intent_policy uses a type in engine.storage.resource.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.engine.storage.resource.Resource
- Direction
- core.policies.unexpected_intent_policy uses engine.storage.resource, so a change to engine.storage.resource can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break engine.storage.resource.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→10 core.policies.unexpected_intent_policy uses shared.core.domain✕
- Connections
- 1 pair of types, where a type in core.policies.unexpected_intent_policy uses a type in shared.core.domain.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.shared.core.domain.Domain
- Direction
- core.policies.unexpected_intent_policy uses shared.core.domain, so a change to shared.core.domain can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break shared.core.domain.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→11 core.policies.unexpected_intent_policy uses engine.graph✕
- Connections
- 1 pair of types, where a type in core.policies.unexpected_intent_policy uses a type in engine.graph.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.engine.graph.ExecutionContext
- Direction
- core.policies.unexpected_intent_policy uses engine.graph, so a change to engine.graph can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break engine.graph.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→12 core.policies.unexpected_intent_policy uses shared.core.trackers✕
- Connections
- 1 pair of types, where a type in core.policies.unexpected_intent_policy uses a type in shared.core.trackers.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.shared.core.trackers.DialogueStateTracker
- Direction
- core.policies.unexpected_intent_policy uses shared.core.trackers, so a change to shared.core.trackers can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break shared.core.trackers.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→15 core.policies.unexpected_intent_policy uses core.featurizers.tracker_featurizers✕
- Connections
- 2 pairs of types, where a type in core.policies.unexpected_intent_policy uses a type in core.featurizers.tracker_featurizers.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.core.featurizers.tracker_featurizers.IntentMaxHistoryTrackerFeaturizerrasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.core.featurizers.tracker_featurizers.TrackerFeaturizer
- Direction
- core.policies.unexpected_intent_policy uses core.featurizers.tracker_featurizers, so a change to core.featurizers.tracker_featurizers can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break core.featurizers.tracker_featurizers.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→17 core.policies.unexpected_intent_policy uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in core.policies.unexpected_intent_policy uses a type in engine.storage.storage.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.engine.storage.storage.ModelStorage
- Direction
- core.policies.unexpected_intent_policy uses engine.storage.storage, so a change to engine.storage.storage can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break engine.storage.storage.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→21 core.policies.unexpected_intent_policy uses core.policies.policy✕
- Connections
- 1 pair of types, where a type in core.policies.unexpected_intent_policy uses a type in core.policies.policy.
- The types involved
rasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.core.policies.policy.PolicyPrediction
- Direction
- core.policies.unexpected_intent_policy uses core.policies.policy, so a change to core.policies.policy can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break core.policies.policy.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
36→30 core.policies.unexpected_intent_policy uses core.policies.ted_policy✕
- Connections
- 2 pairs of types, where a type in core.policies.unexpected_intent_policy uses a type in core.policies.ted_policy.
- The types involved
rasa.core.policies.unexpected_intent_policy.IntentTED→rasa.core.policies.ted_policy.TEDrasa.core.policies.unexpected_intent_policy.UnexpecTEDIntentPolicy→rasa.core.policies.ted_policy.TEDPolicy
- Direction
- core.policies.unexpected_intent_policy uses core.policies.ted_policy, so a change to core.policies.ted_policy can break core.policies.unexpected_intent_policy, while a change to core.policies.unexpected_intent_policy can't break core.policies.ted_policy.
- Position
- Below the diagonal: core.policies.unexpected_intent_policy uses a module listed above it, which is the healthy direction.
37→1 core.processor uses core.channels.channel✕
- Connections
- 2 pairs of types, where a type in core.processor uses a type in core.channels.channel.
- The types involved
rasa.core.processor.MessageProcessor→rasa.core.channels.channel.OutputChannelrasa.core.processor.MessageProcessor→rasa.core.channels.channel.UserMessage
- Direction
- core.processor uses core.channels.channel, so a change to core.channels.channel can break core.processor, while a change to core.processor can't break core.channels.channel.
- Position
- Below the diagonal: core.processor uses a module listed above it, which is the healthy direction.
37→2 core.processor uses shared.core.events✕
- Connections
- 2 pairs of types, where a type in core.processor uses a type in shared.core.events.
- The types involved
rasa.core.processor.MessageProcessor→rasa.shared.core.events.Eventrasa.core.processor.MessageProcessor→rasa.shared.core.events.ReminderScheduled
- Direction
- core.processor uses shared.core.events, so a change to shared.core.events can break core.processor, while a change to core.processor can't break shared.core.events.
- Position
- Below the diagonal: core.processor uses a module listed above it, which is the healthy direction.
37→12 core.processor uses shared.core.trackers✕
- Connections
- 2 pairs of types, where a type in core.processor uses a type in shared.core.trackers.
- The types involved
rasa.core.processor.MessageProcessor→rasa.shared.core.trackers.DialogueStateTrackerrasa.core.processor.MessageProcessor→rasa.shared.core.trackers.EventVerbosity
- Direction
- core.processor uses shared.core.trackers, so a change to shared.core.trackers can break core.processor, while a change to core.processor can't break shared.core.trackers.
- Position
- Below the diagonal: core.processor uses a module listed above it, which is the healthy direction.
37→16 core.processor uses core.tracker_store✕
- Connections
- 1 pair of types, where a type in core.processor uses a type in core.tracker_store.
- The types involved
rasa.core.processor.MessageProcessor→rasa.core.tracker_store.TrackerStore
- Direction
- core.processor uses core.tracker_store, so a change to core.tracker_store can break core.processor, while a change to core.processor can't break core.tracker_store.
- Position
- Below the diagonal: core.processor uses a module listed above it, which is the healthy direction.
37→21 core.processor uses core.policies.policy✕
- Connections
- 1 pair of types, where a type in core.processor uses a type in core.policies.policy.
- The types involved
rasa.core.processor.MessageProcessor→rasa.core.policies.policy.PolicyPrediction
- Direction
- core.processor uses core.policies.policy, so a change to core.policies.policy can break core.processor, while a change to core.processor can't break core.policies.policy.
- Position
- Below the diagonal: core.processor uses a module listed above it, which is the healthy direction.
37→27 core.processor uses core.actions.action✕
- Connections
- 1 pair of types, where a type in core.processor uses a type in core.actions.action.
- The types involved
rasa.core.processor.MessageProcessor→rasa.core.actions.action.Action
- Direction
- core.processor uses core.actions.action, so a change to core.actions.action can break core.processor, while a change to core.processor can't break core.actions.action.
- Position
- Below the diagonal: core.processor uses a module listed above it, which is the healthy direction.
38→4 nlu.classifiers.diet_classifier uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.diet_classifier uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.classifiers.diet_classifier uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
38→5 nlu.classifiers.diet_classifier uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.diet_classifier uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.classifiers.diet_classifier uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
38→7 nlu.classifiers.diet_classifier uses utils.tensorflow.model_data✕
- Connections
- 2 pairs of types, where a type in nlu.classifiers.diet_classifier uses a type in utils.tensorflow.model_data.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIET→rasa.utils.tensorflow.model_data.RasaModelDatarasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.utils.tensorflow.model_data.RasaModelData
- Direction
- nlu.classifiers.diet_classifier uses utils.tensorflow.model_data, so a change to utils.tensorflow.model_data can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break utils.tensorflow.model_data.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
38→9 nlu.classifiers.diet_classifier uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.diet_classifier uses a type in engine.storage.resource.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.engine.storage.resource.Resource
- Direction
- nlu.classifiers.diet_classifier uses engine.storage.resource, so a change to engine.storage.resource can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
38→11 nlu.classifiers.diet_classifier uses engine.graph✕
- Connections
- 2 pairs of types, where a type in nlu.classifiers.diet_classifier uses a type in engine.graph.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.engine.graph.ExecutionContextrasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.engine.graph.GraphComponent
- Direction
- nlu.classifiers.diet_classifier uses engine.graph, so a change to engine.graph can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break engine.graph.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
38→17 nlu.classifiers.diet_classifier uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.diet_classifier uses a type in engine.storage.storage.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.classifiers.diet_classifier uses engine.storage.storage, so a change to engine.storage.storage can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
38→32 nlu.classifiers.diet_classifier uses nlu.extractors.extractor✕
- Connections
- 1 pair of types, where a type in nlu.classifiers.diet_classifier uses a type in nlu.extractors.extractor.
- The types involved
rasa.nlu.classifiers.diet_classifier.DIETClassifier→rasa.nlu.extractors.extractor.EntityExtractorMixin
- Direction
- nlu.classifiers.diet_classifier uses nlu.extractors.extractor, so a change to nlu.extractors.extractor can break nlu.classifiers.diet_classifier, while a change to nlu.classifiers.diet_classifier can't break nlu.extractors.extractor.
- Position
- Below the diagonal: nlu.classifiers.diet_classifier uses a module listed above it, which is the healthy direction.
39→4 nlu.extractors.mitie_entity_extractor uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.extractors.mitie_entity_extractor uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.extractors.mitie_entity_extractor uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.extractors.mitie_entity_extractor, while a change to nlu.extractors.mitie_entity_extractor can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.extractors.mitie_entity_extractor uses a module listed above it, which is the healthy direction.
39→5 nlu.extractors.mitie_entity_extractor uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.extractors.mitie_entity_extractor uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.extractors.mitie_entity_extractor uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.extractors.mitie_entity_extractor, while a change to nlu.extractors.mitie_entity_extractor can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.extractors.mitie_entity_extractor uses a module listed above it, which is the healthy direction.
39→9 nlu.extractors.mitie_entity_extractor uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.extractors.mitie_entity_extractor uses a type in engine.storage.resource.
- The types involved
rasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.engine.storage.resource.Resource
- Direction
- nlu.extractors.mitie_entity_extractor uses engine.storage.resource, so a change to engine.storage.resource can break nlu.extractors.mitie_entity_extractor, while a change to nlu.extractors.mitie_entity_extractor can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.extractors.mitie_entity_extractor uses a module listed above it, which is the healthy direction.
39→11 nlu.extractors.mitie_entity_extractor uses engine.graph✕
- Connections
- 2 pairs of types, where a type in nlu.extractors.mitie_entity_extractor uses a type in engine.graph.
- The types involved
rasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.engine.graph.ExecutionContextrasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.engine.graph.GraphComponent
- Direction
- nlu.extractors.mitie_entity_extractor uses engine.graph, so a change to engine.graph can break nlu.extractors.mitie_entity_extractor, while a change to nlu.extractors.mitie_entity_extractor can't break engine.graph.
- Position
- Below the diagonal: nlu.extractors.mitie_entity_extractor uses a module listed above it, which is the healthy direction.
39→17 nlu.extractors.mitie_entity_extractor uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.extractors.mitie_entity_extractor uses a type in engine.storage.storage.
- The types involved
rasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.extractors.mitie_entity_extractor uses engine.storage.storage, so a change to engine.storage.storage can break nlu.extractors.mitie_entity_extractor, while a change to nlu.extractors.mitie_entity_extractor can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.extractors.mitie_entity_extractor uses a module listed above it, which is the healthy direction.
39→32 nlu.extractors.mitie_entity_extractor uses nlu.extractors.extractor✕
- Connections
- 1 pair of types, where a type in nlu.extractors.mitie_entity_extractor uses a type in nlu.extractors.extractor.
- The types involved
rasa.nlu.extractors.mitie_entity_extractor.MitieEntityExtractor→rasa.nlu.extractors.extractor.EntityExtractorMixin
- Direction
- nlu.extractors.mitie_entity_extractor uses nlu.extractors.extractor, so a change to nlu.extractors.extractor can break nlu.extractors.mitie_entity_extractor, while a change to nlu.extractors.mitie_entity_extractor can't break nlu.extractors.extractor.
- Position
- Below the diagonal: nlu.extractors.mitie_entity_extractor uses a module listed above it, which is the healthy direction.
40→4 nlu.selectors.response_selector uses shared.nlu.training_data.message✕
- Connections
- 1 pair of types, where a type in nlu.selectors.response_selector uses a type in shared.nlu.training_data.message.
- The types involved
rasa.nlu.selectors.response_selector.ResponseSelector→rasa.shared.nlu.training_data.message.Message
- Direction
- nlu.selectors.response_selector uses shared.nlu.training_data.message, so a change to shared.nlu.training_data.message can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break shared.nlu.training_data.message.
- Position
- Below the diagonal: nlu.selectors.response_selector uses a module listed above it, which is the healthy direction.
40→5 nlu.selectors.response_selector uses shared.nlu.training_data.training_data✕
- Connections
- 1 pair of types, where a type in nlu.selectors.response_selector uses a type in shared.nlu.training_data.training_data.
- The types involved
rasa.nlu.selectors.response_selector.ResponseSelector→rasa.shared.nlu.training_data.training_data.TrainingData
- Direction
- nlu.selectors.response_selector uses shared.nlu.training_data.training_data, so a change to shared.nlu.training_data.training_data can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break shared.nlu.training_data.training_data.
- Position
- Below the diagonal: nlu.selectors.response_selector uses a module listed above it, which is the healthy direction.
40→7 nlu.selectors.response_selector uses utils.tensorflow.model_data✕
- Connections
- 1 pair of types, where a type in nlu.selectors.response_selector uses a type in utils.tensorflow.model_data.
- The types involved
rasa.nlu.selectors.response_selector.ResponseSelector→rasa.utils.tensorflow.model_data.RasaModelData
- Direction
- nlu.selectors.response_selector uses utils.tensorflow.model_data, so a change to utils.tensorflow.model_data can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break utils.tensorflow.model_data.
- Position
- Below the diagonal: nlu.selectors.response_selector uses a module listed above it, which is the healthy direction.
40→9 nlu.selectors.response_selector uses engine.storage.resource✕
- Connections
- 1 pair of types, where a type in nlu.selectors.response_selector uses a type in engine.storage.resource.
- The types involved
rasa.nlu.selectors.response_selector.ResponseSelector→rasa.engine.storage.resource.Resource
- Direction
- nlu.selectors.response_selector uses engine.storage.resource, so a change to engine.storage.resource can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break engine.storage.resource.
- Position
- Below the diagonal: nlu.selectors.response_selector uses a module listed above it, which is the healthy direction.
40→11 nlu.selectors.response_selector uses engine.graph✕
- Connections
- 1 pair of types, where a type in nlu.selectors.response_selector uses a type in engine.graph.
- The types involved
rasa.nlu.selectors.response_selector.ResponseSelector→rasa.engine.graph.ExecutionContext
- Direction
- nlu.selectors.response_selector uses engine.graph, so a change to engine.graph can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break engine.graph.
- Position
- Below the diagonal: nlu.selectors.response_selector uses a module listed above it, which is the healthy direction.
40→17 nlu.selectors.response_selector uses engine.storage.storage✕
- Connections
- 1 pair of types, where a type in nlu.selectors.response_selector uses a type in engine.storage.storage.
- The types involved
rasa.nlu.selectors.response_selector.ResponseSelector→rasa.engine.storage.storage.ModelStorage
- Direction
- nlu.selectors.response_selector uses engine.storage.storage, so a change to engine.storage.storage can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break engine.storage.storage.
- Position
- Below the diagonal: nlu.selectors.response_selector uses a module listed above it, which is the healthy direction.
40→38 nlu.selectors.response_selector uses nlu.classifiers.diet_classifier✕
- Connections
- 3 pairs of types, where a type in nlu.selectors.response_selector uses a type in nlu.classifiers.diet_classifier.
- The types involved
rasa.nlu.selectors.response_selector.DIET2BOW→rasa.nlu.classifiers.diet_classifier.DIETrasa.nlu.selectors.response_selector.DIET2DIET→rasa.nlu.classifiers.diet_classifier.DIETrasa.nlu.selectors.response_selector.ResponseSelector→rasa.nlu.classifiers.diet_classifier.DIETClassifier
- Direction
- nlu.selectors.response_selector uses nlu.classifiers.diet_classifier, so a change to nlu.classifiers.diet_classifier can break nlu.selectors.response_selector, while a change to nlu.selectors.response_selector can't break nlu.classifiers.diet_classifier.
- Position
- Below the diagonal: nlu.selectors.response_selector 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 65 | High / Critical |
| A02:2025 — Security Misconfiguration | 51 | High / Critical |
| A05:2025 — Injection | 46 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker; Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pyproject.toml.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker. | +3.4 pts | Medium | Outbound HTTP resilience |
| Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly. | +3.4 pts | Medium | Schema migrations |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pyproject.toml. | +1.6 pts | Low | ADR Quality |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. | +0.9 pts | Low | Platform End-of-Life |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +1.2 pts | Medium | Web-Security Posture |
| Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +0.5 pts | Low | Secrets (history) |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
| Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.4 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.6 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.6 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 58 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 635 of 647 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Python half could not be measured — the pytest suite could not be run in the analyzer image (its dependency install could not be served by 172.31.7.1 (pip: No matching distribution found for rasa-sdk<3.7.0,>=3.6.2), so its suite was not run against dependencies it does not declare). Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`coverage xml`) shows coverage is measured in your own CI.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py) and this repository declares a Python test suite (repository root, 207 test files), but it was not re-run: its dependency install could not be served by 172.31.7.1 (pip: No matching distribution found for rasa-sdk<3.7.0,>=3.6.2), so its suite was not run against dependencies it does not declare. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Python distribution 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.
- D16 Bus Factor — 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. All 204 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 199 of the 311 production source files in this repository: 107 are under the ~2,400-byte size floor this dimension measures over, and the remaining 5 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (tests_deployment/docker-compose.integration.yml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-11-17T00:01:18Z" level=warning msg="The \"RABBITMQ_USER\" variable is not set. Defaulting to a blank string." time="2026-11-17T00:01:18Z" level=warning msg="The \"RABBITMQ_PASSWORD\" variable is not set. Defaulting to a blank string." container tests_deployment-postgres-1 exited (1); runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 218 further occurrence(s) are not listed individually; the score already reflects all 258.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- 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 REDACTED Scanning: REDACTED 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.
- 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TrainingDataGenerator._generate at 29.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TrainingDataGenerator._generate (cyclomatic 29), migrate.migrate_domain_format (cyclomatic 26), visualization.visualize_neighborhood (cyclomatic 20). — 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 Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
38 method(s) exceeded the cognitive complexity threshold of 15; the worst was TrainingDataGenerator._generate at 64.
What to do
- Bring the 38 bodies over 15 down to 15 or less in Cognitive Complexity — start with TrainingDataGenerator._generate (cognitive 64), Policy.format_tracker_states (cognitive 47), StoryGraph.with_cycles_removed (cognitive 46). — 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 38 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
32 god class(es) detected.
What to do
- Resolve the 23 FileTooLong finding(s) in God Classes — start with ted_policy.py, diet_classifier.py, domain.py. — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 9 TooManyMethods finding(s) in God Classes — start with domain.py, trackers.py, rule_policy.py. — One of this dimension's main actionable groups (9 warning-level).
D4 · Code Duplication
22 duplicated block group(s) detected. 2.1 % of the production lines (1,506 of 70,104) are in a reported copy. A further 32 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 5 of the 54 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with tokenizer.py, rasa_yaml.py, mattermost.py. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with botframework.py, callback.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (23 corresponding lines) finding(s) in Code Duplication — start with lock_store.py, test.py. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
2 of 183 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with domain.py, training_data.py. — One of this dimension's main actionable groups (2 warning-level).
D12 · Dependency Hygiene
2 outdated, 0 yanked pinned Python distributions. 3 of 70 shipped distributions were graded against pypi.org (0 not published there, 67 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (REDACTED, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 189 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 70 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (119 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 20 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
60 deducted task-comment markers across 70104 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 31 TodoComment finding(s) in Explicit Debt — start with nlu_component_skeleton.py (5), single_state_featurizer.py (2), model.py (2). — One of this dimension's main actionable groups (31 warning-level).
- Resolve the 29 FixmeComment finding(s) in Explicit Debt — start with test_evaluation.py (5), yaml_story_writer.py (3), slots.py (2). — One of this dimension's main actionable groups (29 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 118 document(s) read across 2 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 — start with pyproject.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Python, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with pyproject.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
77 % of calls cross a namespace and 0 % go through an interface, but 30 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
46 finding(s): 0 critical, 30 high, 15 medium, 1 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 6 file(s) — `REDACTED`, `data/test_domains/invalid_format.yml`, `data/test_wrong_yaml_stories/wrong_yaml.yml`, `scripts/poetry-version.sh` (lines 3–22), `scripts/read_tensorflow_version.sh` (lines 3–22), … (+1 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 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (3). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
D30 · Dependency Vulnerabilities
45 finding(s): 7 critical, 24 high, 14 medium, 0 low.
What to do
- Resolve the 24 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (24). — One of this dimension's main actionable groups (24 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
51 finding(s): 0 critical, 10 high, 26 medium, 15 low.
What to do
- Resolve the 26 Medium IaC finding(s) in IaC & Container Security — start with REDACTED.full (4), REDACTED.pretrained_embeddings_mitie_en (4), REDACTED (3). — One of this dimension's main actionable groups (26 warning-level).
- Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED.base-builder (3), REDACTED.base (2), REDACTED.base-mitie (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 15 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3), REDACTED.base. — One of this dimension's main actionable groups (15 recommendation-level).
D34 · Knowledge Freshness
204 of 204 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is rasa/core/policies/ted_policy.py. Counted over 204 of the 311 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 201 Orphaned file finding(s) in Knowledge Freshness — start with constants.py (5), test.py (4), REDACTED (3). — One of this dimension's main actionable groups (201 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with domain.py, ted_policy.py, diet_classifier.py. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: hangouts.py↔rest.py 54%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with hangouts.py. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 13 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (security.txt) 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
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 70 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 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C2 · Access Controls
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
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
- docs/docs/custom-graph-components.mdx names Python 3.7, but pyproject.toml:91 requires `python = ">=3.8,<3.11"`: the package does not install on Python 3.7. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/docs/custom-graph-components.mdx:22
What to do
- Reconcile the README with reality: docs/docs/custom-graph-components.mdx names Python 3.7, but pyproject.toml:91 requires `python = ">=3.8,<3.11"`: the package does not install on Python 3.7.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it. — REDACTED:1229
- Job `deploy_runner_gpu` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it. — REDACTED:238
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
- Run the production rollout in a protected environment, behind a manual approval, or after the tests it must pass, so a bad push is stopped before users get it.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `aiohttp.ClientSession(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — rasa/cli/x.py:141, rasa/core/http_interpreter.py:23, rasa/server.py:579
- `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — rasa/core/channels/botframework.py:74, rasa/core/channels/botframework.py:113, rasa/core/channels/mattermost.py:27, …
- `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — rasa/core/channels/botframework.py:210, rasa/core/channels/botframework.py:216
What to do
- Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations
- SQLAlchemy create_all() builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Alembic (`alembic revision --autogenerate` + `alembic upgrade head`), so every schema change is a versioned file applied the same way in every environment. (×3) — rasa/engine/caching.py:208, REDACTED:1098, rasa/core/brokers/sql.py:55
What to do
- Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly.
PF3 · Async & latency hygiene
- `_get_headers` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — rasa/core/channels/botframework.py:62
- `send` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — rasa/core/channels/botframework.py:108
What to do
- Python: await the async equivalent (asyncio.sleep, an async HTTP client such as httpx.AsyncClient or aiohttp, asyncio.create_subprocess_exec), or move the blocking call off the loop with `await asyncio.to_thread(...)`; never call asyncio.run inside a coroutine — await the coroutine.
S1 · Web-Security Posture
- `https://dagrejs.github.io/project/dagre-d3/latest/dagre-d3.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 4 such include(s) across the repository's markup. — rasa/shared/core/training_data/visualization.html:6
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — docs/netlify.toml:1
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X17 · Uncapped recursion over a caller-supplied document
- `all_subclasses` is public and takes `cls: Any` from its caller, and it calls itself at line 57 (`all_subclasses`) with a piece of `cls` — and nowhere in `all_subclasses` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `all_subclasses` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — rasa/shared/utils/common.py:57
- `convert_to_ordered_dict` is public and takes `obj: Any` from its caller, and it calls itself at line 464 (`convert_to_ordered_dict`) with a piece of `obj` (and at line 470) — and nowhere in `convert_to_ordered_dict` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `convert_to_ordered_dict` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:464
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 683 is called with an argument built by `newline.join(number_of_examples_for_each_intent)` (line 683), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — rasa/shared/nlu/training_data/training_data.py:683
- `debug` at line 111 is called with an argument built by `json.dumps(entity)` (line 112), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — rasa/shared/nlu/training_data/util.py:111
- `debug` at line 52 is called with an argument built by `"…".join(["…" i "…" for i in self._imports])` (line 53), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — rasa/shared/importers/multi_project.py:52
- `debug` at line 84 is called with an argument built by `json.dumps(body)` (line 87), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — rasa/core/nlg/callback.py:84
- `debug` at line 94 is called with an argument built by `json.dumps(response)` (line 94), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — rasa/core/nlg/callback.py:94
What to do
- In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — rasa/telemetry.py:921, rasa/nlu/utils/__init__.py:30
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — rasa/core/channels/facebook.py:408
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 90 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/model.py:90
- `info` at line 335 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/model_testing.py:335
- `debug` at line 330 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/server.py:330
- `info` at line 1220 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/server.py:1220
- `debug` at line 1360 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/server.py:1360
- `debug` at line 1370 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/server.py:1370
- `debug` at line 161 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/telemetry.py:161
- `exception` at line 208 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — rasa/telemetry.py:208
- `debug` at line 417 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/telemetry.py:417
- `debug` at line 424 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/telemetry.py:424
- `debug` at line 541 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/telemetry.py:541
- `debug` at line 559 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/telemetry.py:559
- `debug` at line 157 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/common.py:157
- `warning` at line 387 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/common.py:387
- `info` at line 121 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/plotting.py:121
- `info` at line 123 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/plotting.py:123
- `info` at line 362 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/plotting.py:362
- `debug` at line 69 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/tensorflow/callback.py:69
- `debug` at line 431 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/utils/tensorflow/models.py:431
- `warning` at line 190 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/utils/common.py:190
- `info` at line 237 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/utils/validation.py:237
- `debug` at line 58 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/entities_parser.py:58
- `debug` at line 135 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/loading.py:135
- `info` at line 676 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:676
- `debug` at line 683 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:683
- `info` at line 686 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:686
- `info` at line 687 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:687
- `info` at line 691 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:691
- `info` at line 696 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:696
- `info` at line 698 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:698
- `info` at line 700 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/training_data.py:700
- `debug` at line 111 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/nlu/training_data/util.py:111
- `warning` at line 196 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/importers/importer.py:196
- `debug` at line 547 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/importers/importer.py:547
- `warning` at line 366 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:366
- `warning` at line 2013 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — REDACTED:2013
- `debug` at line 349 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/core/generator.py:349
- `debug` at line 383 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/core/generator.py:383
- `debug` at line 408 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/core/generator.py:408
- `debug` at line 479 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — rasa/shared/core/generator.py:479
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 68.6 | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87.7 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 65.3 | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 42.5 | Weak — gated by D12, P7, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63.7 | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100.0 | Exemplary | Strongest area. |
| Performance | 70.0 | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (14 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-11-17T00:01:18Z" level=warning msg="The \"RABBITMQ_USER\" variable is not set. Defaulting to a blank string." time="2026-11-17T00:01:18Z" level=warning msg="The \"RABBITMQ_PASSWORD\" variable is not set. Defaulting to a blank string." container tests_deployment-postgres-1 exited (1); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~68215 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .py suite was found but not re-run
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (rasa), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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.
- 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.
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — Python suite
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — python (70,104 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 73 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 287 finding(s)
- TodoComment tests/nlu/test_train.py:149
- TodoComment rasa/core/featurizers/single_state_featurizer.py:74
- TodoComment rasa/core/featurizers/single_state_featurizer.py:302
- TodoComment tests/engine/recipes/test_default_recipe.py:349
- TodoComment tests/cli/test_rasa_test.py:201
- TodoComment rasa/model.py:16
- TodoComment rasa/server.py:1012
- TodoComment rasa/utils/common.py:54
- TodoComment rasa/utils/tensorflow/layers.py:5
- TodoComment rasa/utils/tensorflow/transformer.py:6
- TodoComment REDACTED:543
- TodoComment rasa/shared/core/generator.py:817
- TodoComment rasa/shared/core/slots.py:82
- TodoComment rasa/nlu/model.py:10
- TodoComment rasa/nlu/classifiers/classifier.py:4
- TodoComment rasa/nlu/classifiers/regex_message_handler.py:36
- TodoComment rasa/graph_components/validators/default_recipe_validator.py:47
- TodoComment rasa/graph_components/validators/default_recipe_validator.py:49
- TodoComment rasa/engine/validation.py:354
- TodoComment rasa/core/agent.py:90
- TodoComment REDACTED:928
- TodoComment rasa/core/training/story_conflict.py:312
- TodoComment rasa/core/policies/ted_policy.py:803
- TodoComment rasa/core/policies/ted_policy.py:1418
- TodoComment rasa/core/featurizers/precomputation.py:19
- FixmeComment tests/conftest.py:681
- FixmeComment tests/nlu/test_evaluation.py:509
- FixmeComment tests/nlu/test_evaluation.py:556
- FixmeComment tests/nlu/test_evaluation.py:605
- FixmeComment tests/nlu/test_evaluation.py:688
- FixmeComment tests/nlu/classifiers/test_diet_classifier.py:889
- FixmeComment tests/core/test_evaluation.py:352
- FixmeComment tests/core/test_processor.py:1519
- FixmeComment tests/core/test_test.py:109
- FixmeComment tests/cli/test_rasa_shell.py:68
- FixmeComment rasa/server.py:1378
- FixmeComment rasa/shared/core/domain.py:1385
- FixmeComment rasa/shared/core/trackers.py:918
- FixmeComment REDACTED:1660
- FixmeComment rasa/shared/core/slots.py:290
- FixmeComment rasa/shared/core/slots.py:299
- FixmeComment rasa/shared/core/training_data/story_writer/yaml_story_writer.py:217
- FixmeComment rasa/shared/core/training_data/story_writer/yaml_story_writer.py:248
- FixmeComment rasa/shared/core/training_data/story_writer/yaml_story_writer.py:292
- FixmeComment rasa/nlu/utils/hugging_face/transformers_pre_post_processors.py:27
- FixmeComment rasa/nlu/featurizers/sparse_featurizer/lexical_syntactic_featurizer.py:440
- FixmeComment rasa/core/test.py:877
- FixmeComment rasa/core/actions/action.py:935
- FixmeComment rasa/core/actions/action.py:1000
- FixmeComment rasa/core/policies/rule_policy.py:431
- 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
- FileTooLong: policies/ted_policy.py rasa/core/policies/ted_policy.py
- FileTooLong: classifiers/diet_classifier.py rasa/nlu/classifiers/diet_classifier.py
- FileTooLong: core/domain.py rasa/shared/core/domain.py
- FileTooLong: REDACTED REDACTED
- FileTooLong: REDACTED REDACTED
- FileTooLong: rasa/server.py rasa/server.py
- FileTooLong: REDACTED REDACTED
- FileTooLong: actions/action.py rasa/core/actions/action.py
- FileTooLong: recipes/default_recipe.py rasa/engine/recipes/default_recipe.py
- FileTooLong: policies/rule_policy.py rasa/core/policies/rule_policy.py
- FileTooLong: tensorflow/layers.py rasa/utils/tensorflow/layers.py
- FileTooLong: core/processor.py rasa/core/processor.py
- FileTooLong: featurizers/tracker_featurizers.py rasa/core/featurizers/tracker_featurizers.py
- FileTooLong: selectors/response_selector.py rasa/nlu/selectors/response_selector.py
- FileTooLong: story_reader/yaml_story_reader.py rasa/shared/core/training_data/story_reader/yaml_story_reader.py
- FileTooLong: rasa/telemetry.py rasa/telemetry.py
- FileTooLong: core/generator.py rasa/shared/core/generator.py
- FileTooLong: sparse_featurizer/count_vectors_featurizer.py rasa/nlu/featurizers/sparse_featurizer/count_vectors_featurizer.py
- FileTooLong: tensorflow/rasa_layers.py rasa/utils/tensorflow/rasa_layers.py
- FileTooLong: policies/unexpected_intent_policy.py rasa/core/policies/unexpected_intent_policy.py
- FileTooLong: training_data/structures.py rasa/shared/core/training_data/structures.py
- FileTooLong: core/trackers.py rasa/shared/core/trackers.py
- FileTooLong: tensorflow/models.py rasa/utils/tensorflow/models.py
- 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
- TooManyMethods: Domain rasa/shared/core/domain.py:160
- TooManyMethods: DialogueStateTracker rasa/shared/core/trackers.py:125
- TooManyMethods: RulePolicy rasa/core/policies/rule_policy.py:99
- TooManyMethods: MessageProcessor rasa/core/processor.py:84
- TooManyMethods: CountVectorsFeaturizer rasa/nlu/featurizers/sparse_featurizer/count_vectors_featurizer.py:38
- TooManyMethods: TrainingData rasa/shared/nlu/training_data/training_data.py:35
- TooManyMethods: DIETClassifier rasa/nlu/classifiers/diet_classifier.py:133
- TooManyMethods: YAMLStoryReader rasa/shared/core/training_data/story_reader/yaml_story_reader.py:79
- TooManyMethods: RasaModelData rasa/utils/tensorflow/model_data.py:64
- Outbound HTTP without resilience rasa/cli/x.py:141
- Outbound HTTP without resilience rasa/core/channels/botframework.py:74
- Outbound HTTP without resilience rasa/core/channels/botframework.py:113
- Outbound HTTP without resilience rasa/core/channels/botframework.py:210
- Outbound HTTP without resilience rasa/core/channels/botframework.py:216
- Outbound HTTP without resilience rasa/core/channels/mattermost.py:27
- Outbound HTTP without resilience rasa/core/channels/mattermost.py:52
- Outbound HTTP without resilience rasa/core/http_interpreter.py:23
- Outbound HTTP without resilience rasa/server.py:579
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (13 corresponding lines) rasa/nlu/tokenizers/tokenizer.py:125
- Edited copy of a member (13 corresponding lines) rasa/shared/nlu/training_data/formats/rasa_yaml.py:450
- Edited copy of a member (13 corresponding lines) rasa/core/channels/mattermost.py:186
- Schema created by SQLAlchemy create_all() (no migration path) rasa/engine/caching.py:208
- Schema created by SQLAlchemy create_all() (no migration path) REDACTED:1098
- Schema created by SQLAlchemy create_all() (no migration path) rasa/core/brokers/sql.py:55
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) rasa/core/channels/botframework.py:289
- Members sharing a duplicated core (4 members, 50+ identical tokens) rasa/core/channels/callback.py:64
- Edited copy of a member (23 corresponding lines) rasa/core/lock_store.py:212
- Edited copy of a member (23 corresponding lines) rasa/nlu/test.py:755
- Edited copy of a member (17 corresponding lines) rasa/shared/nlu/training_data/message.py:373
- Edited copy of a member (17 corresponding lines) rasa/engine/graph.py:517
- Edited copy of a member (15 corresponding lines) rasa/nlu/classifiers/keyword_intent_classifier.py:174
- Edited copy of a member (15 corresponding lines) rasa/nlu/extractors/regex_entity_extractor.py:97
- Edited copy of a member (16 corresponding lines) rasa/cli/export.py:30
- Edited copy of a member (16 corresponding lines) scripts/prepare_nightly_release.py:48
- Duplicated block (12 lines × 2) rasa/core/policies/ted_policy.py:1074
- Duplicated block (12 lines × 2) rasa/nlu/selectors/response_selector.py:704
- Duplicated block (8 lines × 2) rasa/core/channels/rocketchat.py:146
- Duplicated block (8 lines × 2) scripts/prepare_nightly_release.py:57
- Low cohesion: Domain (LCOM4 7) rasa/shared/core/domain.py:160
- Low cohesion: TrainingData (LCOM4 5) rasa/shared/nlu/training_data/training_data.py:35
- Sync-over-async blocking rasa/core/channels/botframework.py:62
- Sync-over-async blocking rasa/core/channels/botframework.py:108
- Recursive walk over a caller-supplied document has no depth cap rasa/shared/utils/common.py:57
- Recursive walk over a caller-supplied document has no depth cap REDACTED:464
- Swallowed exception (caught, then discarded) rasa/telemetry.py:921
- Swallowed exception (caught, then discarded) rasa/nlu/utils/__init__.py:30
- TrainingDataGenerator._generate (cyclomatic 29) rasa/shared/core/generator.py:345
- migrate.migrate_domain_format (cyclomatic 26) rasa/core/migrate.py:280
- visualization.visualize_neighborhood (cyclomatic 20) rasa/shared/core/training_data/visualization.py:423
- DefaultV1RecipeValidator._warn_if_some_training_data_is_unused (cyclomatic 19) rasa/graph_components/validators/default_recipe_validator.py:122
- interactive.format_bot_output (cyclomatic 17) REDACTED:271
- YAMLStoryWriter.process_user_utterance (cyclomatic 17) rasa/shared/core/training_data/story_writer/yaml_story_writer.py:191
- RasaModelData.balanced_data (cyclomatic 17) rasa/utils/tensorflow/model_data.py:509
- TrainingDataGenerator._process_step (cyclomatic 16) rasa/shared/core/generator.py:663
- TrainingDataGenerator._generate (cognitive 64) rasa/shared/core/generator.py:345
- Policy.format_tracker_states (cognitive 47) rasa/core/policies/policy.py:438
- StoryGraph.with_cycles_removed (cognitive 46) rasa/shared/core/training_data/structures.py:487
- YAMLStoryWriter.process_user_utterance (cognitive 42) rasa/shared/core/training_data/story_writer/yaml_story_writer.py:191
- RasaModelData.balanced_data (cognitive 42) rasa/utils/tensorflow/model_data.py:509
- migrate.migrate_domain_format (cognitive 41) rasa/core/migrate.py:280
- ActionExtractSlots.run (cognitive 35) rasa/core/actions/action.py:1231
- TrainingDataGenerator._process_step (cognitive 35) rasa/shared/core/generator.py:663
- visualization.visualize_neighborhood (cognitive 34) rasa/shared/core/training_data/visualization.py:423
- Domain.slots_for_entities (cognitive 31) rasa/shared/core/domain.py:1396
- visualization._merge_equivalent_nodes (cognitive 30) rasa/shared/core/training_data/visualization.py:217
- RulePolicy._run_prediction_on_trackers (cognitive 28) rasa/core/policies/rule_policy.py:609
- Domain.collect_entity_properties (cognitive 28) rasa/shared/core/domain.py:602
- FullDialogueTrackerFeaturizer.training_states_labels_and_entities (cognitive 26) rasa/core/featurizers/tracker_featurizers.py:572
- RasaDataGenerator.prepare_batch (cognitive 25) rasa/utils/tensorflow/data_generator.py:75
- model_data_utils._extract_features (cognitive 24) rasa/utils/tensorflow/model_data_utils.py:430
- DefaultV1RecipeValidator._warn_if_some_training_data_is_unused (cognitive 23) rasa/graph_components/validators/default_recipe_validator.py:122
- StoryStep.as_story_string (cognitive 23) rasa/shared/core/training_data/structures.py:196
- YAMLStoryReader._parse_or_statement (cognitive 22) rasa/shared/core/training_data/story_reader/yaml_story_reader.py:349
- Validator.verify_utterances_in_stories (cognitive 22) rasa/validator.py:175
- console.record_messages (cognitive 21) rasa/core/channels/console.py:188
- Marker.evaluate_trackers (cognitive 21) rasa/core/evaluation/marker_base.py:597
- interactive.record_messages (cognitive 21) REDACTED:1474
- DIET._check_data (cognitive 21) rasa/nlu/classifiers/diet_classifier.py:1364
- Domain.states_for_tracker_history (cognitive 21) rasa/shared/core/domain.py:1333
- CRFEntityExtractor._create_features_for_token (cognitive 20) rasa/nlu/extractors/crf_entity_extractor.py:495
- interactive.format_bot_output (cognitive 19) REDACTED:271
- EntityExtractorMixin.convert_predictions_into_entities (cognitive 19) rasa/nlu/extractors/extractor.py:156
- RegexFeaturizer._features_for_patterns (cognitive 19) rasa/nlu/featurizers/sparse_featurizer/regex_featurizer.py:169
- Features.combine (cognitive 19) rasa/shared/nlu/training_data/features.py:359
- TrainingDataGenerator._issue_unused_checkpoint_notification (cognitive 18) rasa/shared/core/generator.py:837
- Validator.verify_actions_in_stories_rules (cognitive 18) rasa/validator.py:253
- ActionExtractSlots._matches_mapping_conditions (cognitive 16) rasa/core/actions/action.py:1057
- KafkaEventBroker.publish (cognitive 16) rasa/core/brokers/kafka.py:109
- GraphNode.__call__ (cognitive 16) rasa/engine/graph.py:440
- DIET._update_metrics_to_log (cognitive 16) rasa/nlu/classifiers/diet_classifier.py:1429
- RasaModel.batch_to_model_data_format (cognitive 16) rasa/utils/tensorflow/models.py:458
- Validator.verify_slot_mappings (cognitive 16) rasa/validator.py:359
- REDACTED
- REDACTED
- Change coupling: hangouts.py ↔ rest.py rasa/core/channels/hangouts.py:1
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (55 corresponding lines) rasa/core/featurizers/tracker_featurizers.py:793
- Edited copies of one member (3 members, 32+ corresponding lines) rasa/shared/nlu/training_data/formats/rasa_yaml.py:216
- Edited copy of a member (21 corresponding lines) rasa/server.py:1457
- Edited copy of a member (31 corresponding lines) rasa/validator.py:176
- Edited copy of a member (36 corresponding lines) rasa/cli/shell.py:65
- Edited copy of a member (38 corresponding lines) rasa/core/featurizers/tracker_featurizers.py:856
- Edited copy of a member (33 corresponding lines) rasa/nlu/featurizers/dense_featurizer/convert_featurizer.py:338
- Edited copy of a member (18 corresponding lines) rasa/nlu/classifiers/diet_classifier.py:1284
- Edited copy of a member (30 corresponding lines) rasa/core/policies/ted_policy.py:437
- Edited copy of a member (43 corresponding lines) rasa/core/featurizers/tracker_featurizers.py:913
- Edited copy of a member (12 corresponding lines) rasa/core/nlg/generator.py:76
- Edited copy of a member (19 corresponding lines) .github/scripts/mr_generate_summary.py:14
- Edited copy of a member (9 corresponding lines) rasa/nlu/extractors/crf_entity_extractor.py:303
- Edited copy of a member (7 corresponding lines) rasa/shared/importers/importer.py:271
- Edited copy of a member (10 corresponding lines) rasa/core/policies/ted_policy.py:1150
- Edited copy of a member (6 corresponding lines) rasa/nlu/classifiers/diet_classifier.py:1305
- Edited copy of a member (4 corresponding lines) .github/scripts/validate_cpu.py:7
- Edited copy of a member (2 corresponding lines) rasa/core/channels/channel.py:376
- Duplicated block (24 lines × 2) rasa/core/featurizers/tracker_featurizers.py:812
- Duplicated block (21 lines × 2) rasa/cli/shell.py:70
- Duplicated block (20 lines × 2) rasa/server.py:899
- Duplicated block (19 lines × 2) rasa/nlu/classifiers/diet_classifier.py:1791
- Duplicated block (15 lines × 3) rasa/shared/nlu/training_data/formats/rasa_yaml.py:235
- Duplicated block (14 lines × 2) rasa/core/policies/ted_policy.py:1037
- Duplicated block (9–14 lines × 2) rasa/nlu/classifiers/diet_classifier.py:1872
- Duplicated block (12–13 lines × 2) rasa/core/policies/ted_policy.py:835
- Duplicated block (13 lines × 2) rasa/server.py:1465
- Duplicated block (12 lines × 3) rasa/server.py:733
- Duplicated block (7–10 lines × 2) rasa/nlu/featurizers/sparse_featurizer/count_vectors_featurizer.py:753
- Duplicated block (10 lines × 2) rasa/server.py:743
- Duplicated block (8–9 lines × 4) rasa/core/channels/botframework.py:290
- Duplicated block (8 lines × 4) rasa/core/channels/callback.py:64
- Duplicated block (6 lines × 2) rasa/nlu/selectors/response_selector.py:718
- Duplicated block (7 lines × 2) rasa/core/lock_store.py:255
- Duplicated block (5 lines × 2) rasa/nlu/selectors/response_selector.py:697
- Edited copy of a member (25 corresponding lines) data/test_classes/custom_graph_components/nlu_dense.py:107
- Duplicated block (42–43 lines × 2) rasa/nlu/test.py:458
- End-of-life runtime: Node.js 12 docs/package.json:127
- Third-party script without Subresource Integrity rasa/shared/core/training_data/visualization.html:6
- Swallowed exception (empty catch) rasa/core/channels/facebook.py:408
Minor — 285 finding(s)
- Orphaned file rasa/nlu/test.py:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file rasa/utils/tensorflow/layers.py:1
- Orphaned file REDACTED:1
- Orphaned file rasa/server.py:1
- Orphaned file rasa/core/policies/rule_policy.py:1
- Orphaned file rasa/utils/tensorflow/rasa_layers.py:1
- Orphaned file rasa/core/test.py:1
- Orphaned file rasa/core/featurizers/tracker_featurizers.py:1
- Orphaned file rasa/core/actions/action.py:1
- Orphaned file rasa/engine/recipes/default_recipe.py:1
- Orphaned file rasa/core/processor.py:1
- Orphaned file rasa/core/policies/unexpected_intent_policy.py:1
- Orphaned file rasa/nlu/selectors/response_selector.py:1
- Orphaned file rasa/core/evaluation/marker_base.py:1
- Orphaned file rasa/telemetry.py:1
- Orphaned file rasa/utils/tensorflow/models.py:1
- Orphaned file rasa/shared/core/generator.py:1
- Orphaned file rasa/nlu/featurizers/sparse_featurizer/count_vectors_featurizer.py:1
- Orphaned file rasa/shared/core/trackers.py:1
- Orphaned file rasa/shared/core/training_data/story_reader/yaml_story_reader.py:1
- Orphaned file rasa/nlu/featurizers/dense_featurizer/lm_featurizer.py:1
- Orphaned file rasa/shared/core/training_data/structures.py:1
- Orphaned file rasa/shared/nlu/training_data/training_data.py:1
- Interpolated log message defeats structured logging rasa/model.py:90
- Interpolated log message defeats structured logging rasa/model_testing.py:335
- Interpolated log message defeats structured logging rasa/server.py:330
- Interpolated log message defeats structured logging rasa/server.py:1220
- Interpolated log message defeats structured logging rasa/server.py:1360
- Interpolated log message defeats structured logging rasa/server.py:1370
- Interpolated log message defeats structured logging rasa/telemetry.py:161
- Interpolated log message defeats structured logging rasa/telemetry.py:208
- Interpolated log message defeats structured logging rasa/telemetry.py:417
- Interpolated log message defeats structured logging rasa/telemetry.py:424
- Interpolated log message defeats structured logging rasa/telemetry.py:541
- Interpolated log message defeats structured logging rasa/telemetry.py:559
- Interpolated log message defeats structured logging rasa/utils/common.py:157
- Interpolated log message defeats structured logging rasa/utils/common.py:387
- Interpolated log message defeats structured logging rasa/utils/plotting.py:121
- Interpolated log message defeats structured logging rasa/utils/plotting.py:123
- Interpolated log message defeats structured logging rasa/utils/plotting.py:362
- Interpolated log message defeats structured logging rasa/utils/tensorflow/callback.py:69
- Interpolated log message defeats structured logging rasa/utils/tensorflow/models.py:431
- Interpolated log message defeats structured logging rasa/shared/utils/common.py:190
- Interpolated log message defeats structured logging rasa/shared/utils/validation.py:237
- Interpolated log message defeats structured logging rasa/shared/nlu/training_data/entities_parser.py:58
- Interpolated log message defeats structured logging rasa/shared/nlu/training_data/loading.py:135
- Interpolated log message defeats structured logging rasa/shared/nlu/training_data/training_data.py:676
- Interpolated log message defeats structured logging rasa/shared/nlu/training_data/training_data.py:683
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Diagnostic log message is built whether or not it is wanted rasa/shared/nlu/training_data/training_data.py:683
- Diagnostic log message is built whether or not it is wanted rasa/shared/nlu/training_data/util.py:111
- Diagnostic log message is built whether or not it is wanted rasa/shared/importers/multi_project.py:52
- Diagnostic log message is built whether or not it is wanted rasa/core/nlg/callback.py:84
- Diagnostic log message is built whether or not it is wanted rasa/core/nlg/callback.py:94
- Most significant orphaned file rasa/shared/core/domain.py:1
- Most significant orphaned file rasa/core/policies/ted_policy.py:1
- Most significant orphaned file rasa/nlu/classifiers/diet_classifier.py:1
- Duplicated predicate rasa/cli/interactive.py:158
- Duplicated predicate rasa/shared/core/generator.py:720
- Duplicated predicate rasa/core/lock_store.py:255
- No ADRs found pyproject.toml:230
- Projects may be oversized for their cohesion pyproject.toml:1
- Scattered collaborators
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift docs/docs/custom-graph-components.mdx:22
- Dependabot does not watch npm REDACTED:2
- No release approval gate REDACTED:1229
- Irreversible deploy step: production deploy on every push REDACTED:238
- No security response headers detected docs/netlify.toml:1
- Silent fallback default on parse failure rasa/core/evaluation/marker.py:152
- Silent fallback default in catch rasa/utils/common.py:140
Minor — 2 finding(s)
- Outdated: dnspython
- Outdated: skops
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-1866320f258b43b1943a1e65476f8a96/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-1866320f258b43b1943a1e65476f8a96/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-1866320f258b43b1943a1e65476f8a96/history-2.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=12800" --report-format json --report-path /tmp/watchdog-gitleaks-1866320f258b43b1943a1e65476f8a96/history-3.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=17000 --max-count=16027" --report-format json --report-path /tmp/watchdog-gitleaks-1866320f258b43b1943a1e65476f8a96/history-4.json --exit-code 0 --source . | 26 | artifacts/raw/gitleaks-history-4.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1866320f258b43b1943a1e65476f8a96/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs/static/js . | 46 | 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/** . | 45 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 51 | 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/** . | 0 | artifacts/raw/trivy-fs.json |