Executive summary
stanford-oval/storm falls short of our standard for production, in part because the project has no automated tests. It scores 45 out of 100 and is rated Weak, and nine of its 11 critical findings are security problems in the build pipeline.
Production Readiness, at 29, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 15 points. Fixing the package under a licence on your banned list comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 58.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and the project has no automated tests, so a change can break it without warning. Adding automated tests, pinning each tool to an exact version and limiting the secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 12,627 lines, about €11,000 to rebuild.
If Production Readiness rose from 29 to 70, the lowest score rated Strong, the score would rise from 45 to about 58.
New since the last survey: 6 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 6 findings
- Static Analysis (SAST) · High: watchdog-unpinned-package-install-in-run REDACTED
- Static Analysis (SAST) · High: watchdog-unpinned-package-install-in-run REDACTED
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-action-major-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-action-major-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-action-major-in-workflow REDACTED
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,700 to €19,000, for 62 to 197 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 45. 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 | Small: 12,627 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 frontend.demo_light | 2 frontend.demo_light.pages_util | 3 frontend.demo_light.stoc | 4 knowledge_storm | 5 knowledge_storm.collaborative_storm.modules.callback | 6 knowledge_storm.collaborative_storm.modules.expert_generation | 7 knowledge_storm.collaborative_storm.modules.simulate_user | 8 knowledge_storm.encoder | 9 knowledge_storm.lm | 10 knowledge_storm.logging_wrapper | 11 knowledge_storm.rm | 12 knowledge_storm.storm_wiki.modules | 13 knowledge_storm.storm_wiki.modules.callback | 14 knowledge_storm.storm_wiki.modules.persona_generator | 15 knowledge_storm.utils | 16 frontend.demo_light.demo_util | 17 knowledge_storm.collaborative_storm.modules.grounded_question_answering | 18 knowledge_storm.interface | 19 knowledge_storm.collaborative_storm.modules | 20 knowledge_storm.dataclass | 21 knowledge_storm.storm_wiki.modules.knowledge_curation | 22 knowledge_storm.storm_wiki.modules.storm_dataclass | 23 knowledge_storm.collaborative_storm.engine | 24 knowledge_storm.collaborative_storm.modules.article_generation | 25 knowledge_storm.collaborative_storm.modules.co_storm_agents | 26 knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator | 27 knowledge_storm.collaborative_storm.modules.grounded_question_generation | 28 knowledge_storm.collaborative_storm.modules.information_insertion_module | 29 knowledge_storm.collaborative_storm.modules.knowledge_base_summary | 30 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat | 31 knowledge_storm.storm_wiki.engine | 32 knowledge_storm.storm_wiki.modules.article_generation | 33 knowledge_storm.storm_wiki.modules.article_polish | 34 knowledge_storm.storm_wiki.modules.outline_generation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 frontend.demo_light | ||||||||||||||||||||||||||||||||||
| 2 frontend.demo_light.pages_util | ||||||||||||||||||||||||||||||||||
| 3 frontend.demo_light.stoc | ||||||||||||||||||||||||||||||||||
| 4 knowledge_storm | ||||||||||||||||||||||||||||||||||
| 5 knowledge_storm.collaborative_storm.modules.callback | ||||||||||||||||||||||||||||||||||
| 6 knowledge_storm.collaborative_storm.modules.expert_generation | ||||||||||||||||||||||||||||||||||
| 7 knowledge_storm.collaborative_storm.modules.simulate_user | ||||||||||||||||||||||||||||||||||
| 8 knowledge_storm.encoder | ||||||||||||||||||||||||||||||||||
| 9 knowledge_storm.lm | ||||||||||||||||||||||||||||||||||
| 10 knowledge_storm.logging_wrapper | ||||||||||||||||||||||||||||||||||
| 11 knowledge_storm.rm | ||||||||||||||||||||||||||||||||||
| 12 knowledge_storm.storm_wiki.modules | ||||||||||||||||||||||||||||||||||
| 13 knowledge_storm.storm_wiki.modules.callback | ||||||||||||||||||||||||||||||||||
| 14 knowledge_storm.storm_wiki.modules.persona_generator | ||||||||||||||||||||||||||||||||||
| 15 knowledge_storm.utils | ||||||||||||||||||||||||||||||||||
| 16 frontend.demo_light.demo_util | 1 | |||||||||||||||||||||||||||||||||
| 17 knowledge_storm.collaborative_storm.modules.grounded_question_answering | 1 | 1 | ||||||||||||||||||||||||||||||||
| 18 knowledge_storm.interface | 1 | |||||||||||||||||||||||||||||||||
| 19 knowledge_storm.collaborative_storm.modules | 1 | 2 | ||||||||||||||||||||||||||||||||
| 20 knowledge_storm.dataclass | 1 | 1 | ||||||||||||||||||||||||||||||||
| 21 knowledge_storm.storm_wiki.modules.knowledge_curation | 2 | 4 | ||||||||||||||||||||||||||||||||
| 22 knowledge_storm.storm_wiki.modules.storm_dataclass | 3 | |||||||||||||||||||||||||||||||||
| 23 knowledge_storm.collaborative_storm.engine | 2 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||
| 24 knowledge_storm.collaborative_storm.modules.article_generation | 2 | |||||||||||||||||||||||||||||||||
| 25 knowledge_storm.collaborative_storm.modules.co_storm_agents | 4 | 1 | 4 | 8 | 5 | |||||||||||||||||||||||||||||
| 26 knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 27 knowledge_storm.collaborative_storm.modules.grounded_question_generation | 2 | |||||||||||||||||||||||||||||||||
| 28 knowledge_storm.collaborative_storm.modules.information_insertion_module | 1 | 4 | ||||||||||||||||||||||||||||||||
| 29 knowledge_storm.collaborative_storm.modules.knowledge_base_summary | 1 | |||||||||||||||||||||||||||||||||
| 30 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat | 2 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||
| 31 knowledge_storm.storm_wiki.engine | 1 | 2 | 2 | |||||||||||||||||||||||||||||||
| 32 knowledge_storm.storm_wiki.modules.article_generation | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 33 knowledge_storm.storm_wiki.modules.article_polish | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 knowledge_storm.storm_wiki.modules.outline_generation | 2 | 1 | 1 |
16→13 frontend.demo_light.demo_util uses knowledge_storm.storm_wiki.modules.callback✕
- Connections
- 1 pair of types, where a type in frontend.demo_light.demo_util uses a type in knowledge_storm.storm_wiki.modules.callback.
- The types involved
frontend.demo_light.demo_util.StreamlitCallbackHandler→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandler
- Direction
- frontend.demo_light.demo_util uses knowledge_storm.storm_wiki.modules.callback, so a change to knowledge_storm.storm_wiki.modules.callback can break frontend.demo_light.demo_util, while a change to frontend.demo_light.demo_util can't break knowledge_storm.storm_wiki.modules.callback.
- Position
- Below the diagonal: frontend.demo_light.demo_util uses a module listed above it, which is the healthy direction.
17→5 knowledge_storm.collaborative_storm.modules.grounded_question_answering uses knowledge_storm.collaborative_storm.modules.callback✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.grounded_question_answering uses a type in knowledge_storm.collaborative_storm.modules.callback.
- The types involved
knowledge_storm.collaborative_storm.modules.grounded_question_answering.AnswerQuestionModule→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.collaborative_storm.modules.grounded_question_answering uses knowledge_storm.collaborative_storm.modules.callback, so a change to knowledge_storm.collaborative_storm.modules.callback can break knowledge_storm.collaborative_storm.modules.grounded_question_answering, while a change to knowledge_storm.collaborative_storm.modules.grounded_question_answering can't break knowledge_storm.collaborative_storm.modules.callback.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.grounded_question_answering uses a module listed above it, which is the healthy direction.
17→10 knowledge_storm.collaborative_storm.modules.grounded_question_answering uses knowledge_storm.logging_wrapper✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.grounded_question_answering uses a type in knowledge_storm.logging_wrapper.
- The types involved
knowledge_storm.collaborative_storm.modules.grounded_question_answering.AnswerQuestionModule→knowledge_storm.logging_wrapper.LoggingWrapper
- Direction
- knowledge_storm.collaborative_storm.modules.grounded_question_answering uses knowledge_storm.logging_wrapper, so a change to knowledge_storm.logging_wrapper can break knowledge_storm.collaborative_storm.modules.grounded_question_answering, while a change to knowledge_storm.collaborative_storm.modules.grounded_question_answering can't break knowledge_storm.logging_wrapper.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.grounded_question_answering uses a module listed above it, which is the healthy direction.
18→20 knowledge_storm.interface uses knowledge_storm.dataclass part of a loop✕
- Connections
- 1 pair of types, where a type in knowledge_storm.interface uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.interface.Agent→knowledge_storm.dataclass.KnowledgeBase
- Direction
- knowledge_storm.interface uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.interface, while a change to knowledge_storm.interface can't break knowledge_storm.dataclass.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→10 knowledge_storm.collaborative_storm.modules uses knowledge_storm.logging_wrapper✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules uses a type in knowledge_storm.logging_wrapper.
- The types involved
knowledge_storm.collaborative_storm.modules.collaborative_storm_utils→knowledge_storm.logging_wrapper.LoggingWrapper
- Direction
- knowledge_storm.collaborative_storm.modules uses knowledge_storm.logging_wrapper, so a change to knowledge_storm.logging_wrapper can break knowledge_storm.collaborative_storm.modules, while a change to knowledge_storm.collaborative_storm.modules can't break knowledge_storm.logging_wrapper.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules uses a module listed above it, which is the healthy direction.
19→18 knowledge_storm.collaborative_storm.modules uses knowledge_storm.interface✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.modules uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.collaborative_storm.modules.collaborative_storm_utils→knowledge_storm.interface.Informationknowledge_storm.collaborative_storm.modules.collaborative_storm_utils→knowledge_storm.interface.LMConfigs
- Direction
- knowledge_storm.collaborative_storm.modules uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.collaborative_storm.modules, while a change to knowledge_storm.collaborative_storm.modules can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules uses a module listed above it, which is the healthy direction.
20→8 knowledge_storm.dataclass uses knowledge_storm.encoder✕
- Connections
- 1 pair of types, where a type in knowledge_storm.dataclass uses a type in knowledge_storm.encoder.
- The types involved
knowledge_storm.dataclass.KnowledgeBase→knowledge_storm.encoder.Encoder
- Direction
- knowledge_storm.dataclass uses knowledge_storm.encoder, so a change to knowledge_storm.encoder can break knowledge_storm.dataclass, while a change to knowledge_storm.dataclass can't break knowledge_storm.encoder.
- Position
- Below the diagonal: knowledge_storm.dataclass uses a module listed above it, which is the healthy direction.
20→18 knowledge_storm.dataclass uses knowledge_storm.interface✕
- Connections
- 1 pair of types, where a type in knowledge_storm.dataclass uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.dataclass.KnowledgeBase→knowledge_storm.interface.Information
- Direction
- knowledge_storm.dataclass uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.dataclass, while a change to knowledge_storm.dataclass can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.dataclass uses a module listed above it, which is the healthy direction.
21→13 knowledge_storm.storm_wiki.modules.knowledge_curation uses knowledge_storm.storm_wiki.modules.callback✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.storm_wiki.modules.knowledge_curation uses a type in knowledge_storm.storm_wiki.modules.callback.
- The types involved
knowledge_storm.storm_wiki.modules.knowledge_curation.ConvSimulator→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandlerknowledge_storm.storm_wiki.modules.knowledge_curation.StormKnowledgeCurationModule→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.storm_wiki.modules.knowledge_curation uses knowledge_storm.storm_wiki.modules.callback, so a change to knowledge_storm.storm_wiki.modules.callback can break knowledge_storm.storm_wiki.modules.knowledge_curation, while a change to knowledge_storm.storm_wiki.modules.knowledge_curation can't break knowledge_storm.storm_wiki.modules.callback.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.knowledge_curation uses a module listed above it, which is the healthy direction.
21→18 knowledge_storm.storm_wiki.modules.knowledge_curation uses knowledge_storm.interface✕
- Connections
- 4 pairs of types, where a type in knowledge_storm.storm_wiki.modules.knowledge_curation uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.storm_wiki.modules.knowledge_curation.ConvSimulator→knowledge_storm.interface.Retrieverknowledge_storm.storm_wiki.modules.knowledge_curation.StormKnowledgeCurationModule→knowledge_storm.interface.KnowledgeCurationModuleknowledge_storm.storm_wiki.modules.knowledge_curation.StormKnowledgeCurationModule→knowledge_storm.interface.Retrieverknowledge_storm.storm_wiki.modules.knowledge_curation.TopicExpert→knowledge_storm.interface.Retriever
- Direction
- knowledge_storm.storm_wiki.modules.knowledge_curation uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.storm_wiki.modules.knowledge_curation, while a change to knowledge_storm.storm_wiki.modules.knowledge_curation can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.knowledge_curation uses a module listed above it, which is the healthy direction.
22→18 knowledge_storm.storm_wiki.modules.storm_dataclass uses knowledge_storm.interface✕
- Connections
- 3 pairs of types, where a type in knowledge_storm.storm_wiki.modules.storm_dataclass uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.storm_wiki.modules.storm_dataclass.StormArticle→knowledge_storm.interface.Articleknowledge_storm.storm_wiki.modules.storm_dataclass.StormArticle→knowledge_storm.interface.ArticleSectionNodeknowledge_storm.storm_wiki.modules.storm_dataclass.StormInformationTable→knowledge_storm.interface.InformationTable
- Direction
- knowledge_storm.storm_wiki.modules.storm_dataclass uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.storm_wiki.modules.storm_dataclass, while a change to knowledge_storm.storm_wiki.modules.storm_dataclass can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.storm_dataclass uses a module listed above it, which is the healthy direction.
23→5 knowledge_storm.collaborative_storm.engine uses knowledge_storm.collaborative_storm.modules.callback✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.engine uses a type in knowledge_storm.collaborative_storm.modules.callback.
- The types involved
knowledge_storm.collaborative_storm.engine.CoStormRunner→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandlerknowledge_storm.collaborative_storm.engine.DiscourseManager→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.collaborative_storm.engine uses knowledge_storm.collaborative_storm.modules.callback, so a change to knowledge_storm.collaborative_storm.modules.callback can break knowledge_storm.collaborative_storm.engine, while a change to knowledge_storm.collaborative_storm.engine can't break knowledge_storm.collaborative_storm.modules.callback.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.engine uses a module listed above it, which is the healthy direction.
23→8 knowledge_storm.collaborative_storm.engine uses knowledge_storm.encoder✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.engine uses a type in knowledge_storm.encoder.
- The types involved
knowledge_storm.collaborative_storm.engine.DiscourseManager→knowledge_storm.encoder.Encoder
- Direction
- knowledge_storm.collaborative_storm.engine uses knowledge_storm.encoder, so a change to knowledge_storm.encoder can break knowledge_storm.collaborative_storm.engine, while a change to knowledge_storm.collaborative_storm.engine can't break knowledge_storm.encoder.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.engine uses a module listed above it, which is the healthy direction.
23→10 knowledge_storm.collaborative_storm.engine uses knowledge_storm.logging_wrapper✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.engine uses a type in knowledge_storm.logging_wrapper.
- The types involved
knowledge_storm.collaborative_storm.engine.CoStormRunner→knowledge_storm.logging_wrapper.LoggingWrapperknowledge_storm.collaborative_storm.engine.DiscourseManager→knowledge_storm.logging_wrapper.LoggingWrapper
- Direction
- knowledge_storm.collaborative_storm.engine uses knowledge_storm.logging_wrapper, so a change to knowledge_storm.logging_wrapper can break knowledge_storm.collaborative_storm.engine, while a change to knowledge_storm.collaborative_storm.engine can't break knowledge_storm.logging_wrapper.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.engine uses a module listed above it, which is the healthy direction.
23→18 knowledge_storm.collaborative_storm.engine uses knowledge_storm.interface✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.engine uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.collaborative_storm.engine.CollaborativeStormLMConfigs→knowledge_storm.interface.LMConfigsknowledge_storm.collaborative_storm.engine.TurnPolicySpec→knowledge_storm.interface.Agent
- Direction
- knowledge_storm.collaborative_storm.engine uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.collaborative_storm.engine, while a change to knowledge_storm.collaborative_storm.engine can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.engine uses a module listed above it, which is the healthy direction.
23→20 knowledge_storm.collaborative_storm.engine uses knowledge_storm.dataclass✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.engine uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.engine.CoStormRunner→knowledge_storm.dataclass.ConversationTurn
- Direction
- knowledge_storm.collaborative_storm.engine uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.engine, while a change to knowledge_storm.collaborative_storm.engine can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.engine uses a module listed above it, which is the healthy direction.
24→20 knowledge_storm.collaborative_storm.modules.article_generation uses knowledge_storm.dataclass✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.article_generation uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.article_generation.ArticleGenerationModule→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.article_generation.ArticleGenerationModule→knowledge_storm.dataclass.KnowledgeNode
- Direction
- knowledge_storm.collaborative_storm.modules.article_generation uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.article_generation, while a change to knowledge_storm.collaborative_storm.modules.article_generation can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.article_generation uses a module listed above it, which is the healthy direction.
25→5 knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.collaborative_storm.modules.callback✕
- Connections
- 4 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.co_storm_agents uses a type in knowledge_storm.collaborative_storm.modules.callback.
- The types involved
knowledge_storm.collaborative_storm.modules.co_storm_agents.CoStormExpert→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandlerknowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandlerknowledge_storm.collaborative_storm.modules.co_storm_agents.PureRAGAgent→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandlerknowledge_storm.collaborative_storm.modules.co_storm_agents.SimulatedUser→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.collaborative_storm.modules.callback, so a change to knowledge_storm.collaborative_storm.modules.callback can break knowledge_storm.collaborative_storm.modules.co_storm_agents, while a change to knowledge_storm.collaborative_storm.modules.co_storm_agents can't break knowledge_storm.collaborative_storm.modules.callback.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.co_storm_agents uses a module listed above it, which is the healthy direction.
25→8 knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.encoder✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.co_storm_agents uses a type in knowledge_storm.encoder.
- The types involved
knowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.encoder.Encoder
- Direction
- knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.encoder, so a change to knowledge_storm.encoder can break knowledge_storm.collaborative_storm.modules.co_storm_agents, while a change to knowledge_storm.collaborative_storm.modules.co_storm_agents can't break knowledge_storm.encoder.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.co_storm_agents uses a module listed above it, which is the healthy direction.
25→10 knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.logging_wrapper✕
- Connections
- 4 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.co_storm_agents uses a type in knowledge_storm.logging_wrapper.
- The types involved
knowledge_storm.collaborative_storm.modules.co_storm_agents.CoStormExpert→knowledge_storm.logging_wrapper.LoggingWrapperknowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.logging_wrapper.LoggingWrapperknowledge_storm.collaborative_storm.modules.co_storm_agents.PureRAGAgent→knowledge_storm.logging_wrapper.LoggingWrapperknowledge_storm.collaborative_storm.modules.co_storm_agents.SimulatedUser→knowledge_storm.logging_wrapper.LoggingWrapper
- Direction
- knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.logging_wrapper, so a change to knowledge_storm.logging_wrapper can break knowledge_storm.collaborative_storm.modules.co_storm_agents, while a change to knowledge_storm.collaborative_storm.modules.co_storm_agents can't break knowledge_storm.logging_wrapper.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.co_storm_agents uses a module listed above it, which is the healthy direction.
25→18 knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.interface✕
- Connections
- 8 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.co_storm_agents uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.collaborative_storm.modules.co_storm_agents.CoStormExpert→knowledge_storm.interface.Agentknowledge_storm.collaborative_storm.modules.co_storm_agents.CoStormExpert→knowledge_storm.interface.LMConfigsknowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.interface.Agentknowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.interface.LMConfigsknowledge_storm.collaborative_storm.modules.co_storm_agents.PureRAGAgent→knowledge_storm.interface.Agentknowledge_storm.collaborative_storm.modules.co_storm_agents.PureRAGAgent→knowledge_storm.interface.LMConfigsknowledge_storm.collaborative_storm.modules.co_storm_agents.SimulatedUser→knowledge_storm.interface.Agentknowledge_storm.collaborative_storm.modules.co_storm_agents.SimulatedUser→knowledge_storm.interface.LMConfigs
- Direction
- knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.collaborative_storm.modules.co_storm_agents, while a change to knowledge_storm.collaborative_storm.modules.co_storm_agents can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.co_storm_agents uses a module listed above it, which is the healthy direction.
25→20 knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.dataclass✕
- Connections
- 5 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.co_storm_agents uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.co_storm_agents.CoStormExpert→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.dataclass.ConversationTurnknowledge_storm.collaborative_storm.modules.co_storm_agents.Moderator→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.co_storm_agents.PureRAGAgent→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.co_storm_agents.SimulatedUser→knowledge_storm.dataclass.KnowledgeBase
- Direction
- knowledge_storm.collaborative_storm.modules.co_storm_agents uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.co_storm_agents, while a change to knowledge_storm.collaborative_storm.modules.co_storm_agents can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.co_storm_agents uses a module listed above it, which is the healthy direction.
26→5 knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.collaborative_storm.modules.callback✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a type in knowledge_storm.collaborative_storm.modules.callback.
- The types involved
knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator.CoStormExpertUtteranceGenerationModule→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.collaborative_storm.modules.callback, so a change to knowledge_storm.collaborative_storm.modules.callback can break knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator, while a change to knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator can't break knowledge_storm.collaborative_storm.modules.callback.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a module listed above it, which is the healthy direction.
26→10 knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.logging_wrapper✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a type in knowledge_storm.logging_wrapper.
- The types involved
knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator.CoStormExpertUtteranceGenerationModule→knowledge_storm.logging_wrapper.LoggingWrapper
- Direction
- knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.logging_wrapper, so a change to knowledge_storm.logging_wrapper can break knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator, while a change to knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator can't break knowledge_storm.logging_wrapper.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a module listed above it, which is the healthy direction.
26→17 knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.collaborative_storm.modules.grounded_question_answering✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a type in knowledge_storm.collaborative_storm.modules.grounded_question_answering.
- The types involved
knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator.CoStormExpertUtteranceGenerationModule→knowledge_storm.collaborative_storm.modules.grounded_question_answering.AnswerQuestionModule
- Direction
- knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.collaborative_storm.modules.grounded_question_answering, so a change to knowledge_storm.collaborative_storm.modules.grounded_question_answering can break knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator, while a change to knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator can't break knowledge_storm.collaborative_storm.modules.grounded_question_answering.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a module listed above it, which is the healthy direction.
26→20 knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.dataclass✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator.CoStormExpertUtteranceGenerationModule→knowledge_storm.dataclass.ConversationTurn
- Direction
- knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator, while a change to knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.costorm_expert_utterance_generator uses a module listed above it, which is the healthy direction.
27→20 knowledge_storm.collaborative_storm.modules.grounded_question_generation uses knowledge_storm.dataclass✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.grounded_question_generation uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.grounded_question_generation.GroundedQuestionGenerationModule→knowledge_storm.dataclass.ConversationTurnknowledge_storm.collaborative_storm.modules.grounded_question_generation.GroundedQuestionGenerationModule→knowledge_storm.dataclass.KnowledgeBase
- Direction
- knowledge_storm.collaborative_storm.modules.grounded_question_generation uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.grounded_question_generation, while a change to knowledge_storm.collaborative_storm.modules.grounded_question_generation can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.grounded_question_generation uses a module listed above it, which is the healthy direction.
28→8 knowledge_storm.collaborative_storm.modules.information_insertion_module uses knowledge_storm.encoder✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.information_insertion_module uses a type in knowledge_storm.encoder.
- The types involved
knowledge_storm.collaborative_storm.modules.information_insertion_module.InsertInformationModule→knowledge_storm.encoder.Encoder
- Direction
- knowledge_storm.collaborative_storm.modules.information_insertion_module uses knowledge_storm.encoder, so a change to knowledge_storm.encoder can break knowledge_storm.collaborative_storm.modules.information_insertion_module, while a change to knowledge_storm.collaborative_storm.modules.information_insertion_module can't break knowledge_storm.encoder.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.information_insertion_module uses a module listed above it, which is the healthy direction.
28→20 knowledge_storm.collaborative_storm.modules.information_insertion_module uses knowledge_storm.dataclass✕
- Connections
- 4 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.information_insertion_module uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.information_insertion_module.ExpandNodeModule→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.information_insertion_module.ExpandNodeModule→knowledge_storm.dataclass.KnowledgeNodeknowledge_storm.collaborative_storm.modules.information_insertion_module.InsertInformationModule→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.information_insertion_module.InsertInformationModule→knowledge_storm.dataclass.KnowledgeNode
- Direction
- knowledge_storm.collaborative_storm.modules.information_insertion_module uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.information_insertion_module, while a change to knowledge_storm.collaborative_storm.modules.information_insertion_module can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.information_insertion_module uses a module listed above it, which is the healthy direction.
29→20 knowledge_storm.collaborative_storm.modules.knowledge_base_summary uses knowledge_storm.dataclass✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.knowledge_base_summary uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.knowledge_base_summary.KnowledgeBaseSummaryModule→knowledge_storm.dataclass.KnowledgeBase
- Direction
- knowledge_storm.collaborative_storm.modules.knowledge_base_summary uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.knowledge_base_summary, while a change to knowledge_storm.collaborative_storm.modules.knowledge_base_summary can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.knowledge_base_summary uses a module listed above it, which is the healthy direction.
30→5 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.collaborative_storm.modules.callback✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a type in knowledge_storm.collaborative_storm.modules.callback.
- The types involved
knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartConversation→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandlerknowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartModule→knowledge_storm.collaborative_storm.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.collaborative_storm.modules.callback, so a change to knowledge_storm.collaborative_storm.modules.callback can break knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat, while a change to knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat can't break knowledge_storm.collaborative_storm.modules.callback.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a module listed above it, which is the healthy direction.
30→6 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.collaborative_storm.modules.expert_generation✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a type in knowledge_storm.collaborative_storm.modules.expert_generation.
- The types involved
knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartConversation→knowledge_storm.collaborative_storm.modules.expert_generation.GenerateExpertModule
- Direction
- knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.collaborative_storm.modules.expert_generation, so a change to knowledge_storm.collaborative_storm.modules.expert_generation can break knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat, while a change to knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat can't break knowledge_storm.collaborative_storm.modules.expert_generation.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a module listed above it, which is the healthy direction.
30→10 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.logging_wrapper✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a type in knowledge_storm.logging_wrapper.
- The types involved
knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartConversation→knowledge_storm.logging_wrapper.LoggingWrapperknowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartModule→knowledge_storm.logging_wrapper.LoggingWrapper
- Direction
- knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.logging_wrapper, so a change to knowledge_storm.logging_wrapper can break knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat, while a change to knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat can't break knowledge_storm.logging_wrapper.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a module listed above it, which is the healthy direction.
30→17 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.collaborative_storm.modules.grounded_question_answering✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a type in knowledge_storm.collaborative_storm.modules.grounded_question_answering.
- The types involved
knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartConversation→knowledge_storm.collaborative_storm.modules.grounded_question_answering.AnswerQuestionModule
- Direction
- knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.collaborative_storm.modules.grounded_question_answering, so a change to knowledge_storm.collaborative_storm.modules.grounded_question_answering can break knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat, while a change to knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat can't break knowledge_storm.collaborative_storm.modules.grounded_question_answering.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a module listed above it, which is the healthy direction.
30→18 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.interface✕
- Connections
- 1 pair of types, where a type in knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartModule→knowledge_storm.interface.LMConfigs
- Direction
- knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat, while a change to knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a module listed above it, which is the healthy direction.
30→20 knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.dataclass✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a type in knowledge_storm.dataclass.
- The types involved
knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.ReportToConversation→knowledge_storm.dataclass.KnowledgeBaseknowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat.WarmStartModule→knowledge_storm.dataclass.KnowledgeBase
- Direction
- knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses knowledge_storm.dataclass, so a change to knowledge_storm.dataclass can break knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat, while a change to knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat can't break knowledge_storm.dataclass.
- Position
- Below the diagonal: knowledge_storm.collaborative_storm.modules.warmstart_hierarchical_chat uses a module listed above it, which is the healthy direction.
31→13 knowledge_storm.storm_wiki.engine uses knowledge_storm.storm_wiki.modules.callback✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.engine uses a type in knowledge_storm.storm_wiki.modules.callback.
- The types involved
knowledge_storm.storm_wiki.engine.STORMWikiRunner→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.storm_wiki.engine uses knowledge_storm.storm_wiki.modules.callback, so a change to knowledge_storm.storm_wiki.modules.callback can break knowledge_storm.storm_wiki.engine, while a change to knowledge_storm.storm_wiki.engine can't break knowledge_storm.storm_wiki.modules.callback.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.engine uses a module listed above it, which is the healthy direction.
31→18 knowledge_storm.storm_wiki.engine uses knowledge_storm.interface✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.storm_wiki.engine uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.storm_wiki.engine.STORMWikiLMConfigs→knowledge_storm.interface.LMConfigsknowledge_storm.storm_wiki.engine.STORMWikiRunner→knowledge_storm.interface.Engine
- Direction
- knowledge_storm.storm_wiki.engine uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.storm_wiki.engine, while a change to knowledge_storm.storm_wiki.engine can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.engine uses a module listed above it, which is the healthy direction.
31→22 knowledge_storm.storm_wiki.engine uses knowledge_storm.storm_wiki.modules.storm_dataclass✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.storm_wiki.engine uses a type in knowledge_storm.storm_wiki.modules.storm_dataclass.
- The types involved
knowledge_storm.storm_wiki.engine.STORMWikiRunner→knowledge_storm.storm_wiki.modules.storm_dataclass.StormArticleknowledge_storm.storm_wiki.engine.STORMWikiRunner→knowledge_storm.storm_wiki.modules.storm_dataclass.StormInformationTable
- Direction
- knowledge_storm.storm_wiki.engine uses knowledge_storm.storm_wiki.modules.storm_dataclass, so a change to knowledge_storm.storm_wiki.modules.storm_dataclass can break knowledge_storm.storm_wiki.engine, while a change to knowledge_storm.storm_wiki.engine can't break knowledge_storm.storm_wiki.modules.storm_dataclass.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.engine uses a module listed above it, which is the healthy direction.
32→13 knowledge_storm.storm_wiki.modules.article_generation uses knowledge_storm.storm_wiki.modules.callback✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.modules.article_generation uses a type in knowledge_storm.storm_wiki.modules.callback.
- The types involved
knowledge_storm.storm_wiki.modules.article_generation.StormArticleGenerationModule→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.storm_wiki.modules.article_generation uses knowledge_storm.storm_wiki.modules.callback, so a change to knowledge_storm.storm_wiki.modules.callback can break knowledge_storm.storm_wiki.modules.article_generation, while a change to knowledge_storm.storm_wiki.modules.article_generation can't break knowledge_storm.storm_wiki.modules.callback.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.article_generation uses a module listed above it, which is the healthy direction.
32→18 knowledge_storm.storm_wiki.modules.article_generation uses knowledge_storm.interface✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.modules.article_generation uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.storm_wiki.modules.article_generation.StormArticleGenerationModule→knowledge_storm.interface.ArticleGenerationModule
- Direction
- knowledge_storm.storm_wiki.modules.article_generation uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.storm_wiki.modules.article_generation, while a change to knowledge_storm.storm_wiki.modules.article_generation can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.article_generation uses a module listed above it, which is the healthy direction.
32→22 knowledge_storm.storm_wiki.modules.article_generation uses knowledge_storm.storm_wiki.modules.storm_dataclass✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.storm_wiki.modules.article_generation uses a type in knowledge_storm.storm_wiki.modules.storm_dataclass.
- The types involved
knowledge_storm.storm_wiki.modules.article_generation.StormArticleGenerationModule→knowledge_storm.storm_wiki.modules.storm_dataclass.StormArticleknowledge_storm.storm_wiki.modules.article_generation.StormArticleGenerationModule→knowledge_storm.storm_wiki.modules.storm_dataclass.StormInformationTable
- Direction
- knowledge_storm.storm_wiki.modules.article_generation uses knowledge_storm.storm_wiki.modules.storm_dataclass, so a change to knowledge_storm.storm_wiki.modules.storm_dataclass can break knowledge_storm.storm_wiki.modules.article_generation, while a change to knowledge_storm.storm_wiki.modules.article_generation can't break knowledge_storm.storm_wiki.modules.storm_dataclass.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.article_generation uses a module listed above it, which is the healthy direction.
33→18 knowledge_storm.storm_wiki.modules.article_polish uses knowledge_storm.interface✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.modules.article_polish uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.storm_wiki.modules.article_polish.StormArticlePolishingModule→knowledge_storm.interface.ArticlePolishingModule
- Direction
- knowledge_storm.storm_wiki.modules.article_polish uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.storm_wiki.modules.article_polish, while a change to knowledge_storm.storm_wiki.modules.article_polish can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.article_polish uses a module listed above it, which is the healthy direction.
33→22 knowledge_storm.storm_wiki.modules.article_polish uses knowledge_storm.storm_wiki.modules.storm_dataclass✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.modules.article_polish uses a type in knowledge_storm.storm_wiki.modules.storm_dataclass.
- The types involved
knowledge_storm.storm_wiki.modules.article_polish.StormArticlePolishingModule→knowledge_storm.storm_wiki.modules.storm_dataclass.StormArticle
- Direction
- knowledge_storm.storm_wiki.modules.article_polish uses knowledge_storm.storm_wiki.modules.storm_dataclass, so a change to knowledge_storm.storm_wiki.modules.storm_dataclass can break knowledge_storm.storm_wiki.modules.article_polish, while a change to knowledge_storm.storm_wiki.modules.article_polish can't break knowledge_storm.storm_wiki.modules.storm_dataclass.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.article_polish uses a module listed above it, which is the healthy direction.
34→13 knowledge_storm.storm_wiki.modules.outline_generation uses knowledge_storm.storm_wiki.modules.callback✕
- Connections
- 2 pairs of types, where a type in knowledge_storm.storm_wiki.modules.outline_generation uses a type in knowledge_storm.storm_wiki.modules.callback.
- The types involved
knowledge_storm.storm_wiki.modules.outline_generation.StormOutlineGenerationModule→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandlerknowledge_storm.storm_wiki.modules.outline_generation.WriteOutline→knowledge_storm.storm_wiki.modules.callback.BaseCallbackHandler
- Direction
- knowledge_storm.storm_wiki.modules.outline_generation uses knowledge_storm.storm_wiki.modules.callback, so a change to knowledge_storm.storm_wiki.modules.callback can break knowledge_storm.storm_wiki.modules.outline_generation, while a change to knowledge_storm.storm_wiki.modules.outline_generation can't break knowledge_storm.storm_wiki.modules.callback.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.outline_generation uses a module listed above it, which is the healthy direction.
34→18 knowledge_storm.storm_wiki.modules.outline_generation uses knowledge_storm.interface✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.modules.outline_generation uses a type in knowledge_storm.interface.
- The types involved
knowledge_storm.storm_wiki.modules.outline_generation.StormOutlineGenerationModule→knowledge_storm.interface.OutlineGenerationModule
- Direction
- knowledge_storm.storm_wiki.modules.outline_generation uses knowledge_storm.interface, so a change to knowledge_storm.interface can break knowledge_storm.storm_wiki.modules.outline_generation, while a change to knowledge_storm.storm_wiki.modules.outline_generation can't break knowledge_storm.interface.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.outline_generation uses a module listed above it, which is the healthy direction.
34→22 knowledge_storm.storm_wiki.modules.outline_generation uses knowledge_storm.storm_wiki.modules.storm_dataclass✕
- Connections
- 1 pair of types, where a type in knowledge_storm.storm_wiki.modules.outline_generation uses a type in knowledge_storm.storm_wiki.modules.storm_dataclass.
- The types involved
knowledge_storm.storm_wiki.modules.outline_generation.StormOutlineGenerationModule→knowledge_storm.storm_wiki.modules.storm_dataclass.StormInformationTable
- Direction
- knowledge_storm.storm_wiki.modules.outline_generation uses knowledge_storm.storm_wiki.modules.storm_dataclass, so a change to knowledge_storm.storm_wiki.modules.storm_dataclass can break knowledge_storm.storm_wiki.modules.outline_generation, while a change to knowledge_storm.storm_wiki.modules.outline_generation can't break knowledge_storm.storm_wiki.modules.storm_dataclass.
- Position
- Below the diagonal: knowledge_storm.storm_wiki.modules.outline_generation uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +14.6 pts | Low | Test Distribution |
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.7 pts | Low | License Compliance |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +14.6 pts | High | Code Coverage |
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +5.9 pts | Medium | Security & performance tooling |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with engine.py (2), article_generation.py (2), REDACTED. | +5.7 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.3 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +3.2 pts | Medium | Structured logging |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with rm.py, lm.py, dataclass.py. | +0.8 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| knowledge_storm/collaborative_storm/engine.py | 6.0 | Mixed | Explicit Debt: FixmeComment |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| knowledge_storm/rm.py | 7.1 | Mixed | Cognitive Complexity: SerperRM.forward (cognitive 26) |
| knowledge_storm/lm.py | 7.1 | Mixed | God Classes: FileTooLong: knowledge_storm/lm.py |
| examples/storm_examples/run_storm_wiki_claude.py | 7.1 | Mixed | Code Duplication: Near-duplicate member family (4 members, 29 shared lines) |
| knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py | 7.2 | Mixed | Cognitive Complexity: collaborative_storm_utils.format_search_results (cognitive 18) |
| examples/storm_examples/run_storm_wiki_mistral.py | 7.4 | Mixed | Code Duplication: Edited copy of a member (129 corresponding lines) |
| knowledge_storm/collaborative_storm/modules/information_insertion_module.py | 7.8 | Mixed | Cognitive Complexity: InsertInformationModule.layer_by_layer_navigation_placement (cognitive 16) |
| knowledge_storm/dataclass.py | 7.8 | Mixed | Cognitive Complexity: KnowledgeBase.insert_from_outline_string (cognitive 16) |
| knowledge_storm/storm_wiki/modules/storm_dataclass.py | 7.8 | Mixed | Cognitive Complexity: StormArticle.update_section (cognitive 16) |
| examples/costorm_examples/run_costorm_gpt.py | 7.8 | Mixed | Code Duplication: Duplicated block (21–28 lines × 3) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| examples/storm_examples/run_storm_wiki_gpt.py | 8.5 | Near-clean | Code Duplication: Duplicated block (30–32 lines × 2) |
| examples/storm_examples/run_storm_wiki_ollama.py | 8.5 | Near-clean | Code Duplication: Duplicated block (25–27 lines × 2) |
| examples/storm_examples/run_storm_wiki_deepseek.py | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
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 54 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 54 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, 115 of 131 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (setup.py), but 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.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- 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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala 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.
- 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 and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala 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.
- 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — 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 web-security 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 web-security controls.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X18 Disposal-pattern correctness — 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 JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X29 Per-element action decided by a fixed element — 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 JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- 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, and Kotlin 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: 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".
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was SerperRM.forward at 26.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with SerperRM.forward (cognitive 26), TavilySearchRM.forward (cognitive 22), CoStormRunner.step (cognitive 19). — 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 11 together lifts Cognitive Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with lm.py, rm.py, engine.py. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
23 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 14 of the 25 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 2 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with rm.py, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with lm.py, run_storm_wiki_deepseek.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with lm.py. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 52 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
4 outdated, 0 yanked pinned Python distributions. 6 of 22 shipped distributions were graded against pypi.org (0 not published there, 16 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 (poetry.lock, 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 155 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 22 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (133 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. 21 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 30 of the 40 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
1 deducted task-comment markers across 12627 LoC (0.0/KLoC) → score 10.0. 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 1 FixmeComment finding(s) in Explicit Debt — start with engine.py. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 1 build units (Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
77 % of calls cross a namespace and 0 % go through an interface, but 50 % 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 9 high, 6 medium, 0 low. 6 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
30 of 30 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is knowledge_storm/rm.py. Counted over 30 of the 40 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 27 Orphaned file finding(s) in Knowledge Freshness — start with engine.py (2), article_generation.py (2), REDACTED. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with rm.py, lm.py, dataclass.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
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 22 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`pytest` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `frontend/demo_light`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1780 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `except` 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. — knowledge_storm/rm.py:564
- `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. (×3) — REDACTED:443, REDACTED:764, REDACTED:791
- 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. (×2) — knowledge_storm/storm_wiki/modules/storm_dataclass.py:446, knowledge_storm/collaborative_storm/modules/information_insertion_module.py:171
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 420 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. — REDACTED:420
- `warning` at line 439 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:439
- `info` at line 502 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. — REDACTED:502
- `error` at line 535 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/lm.py:535
- `error` at line 72 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:72
- `error` at line 165 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:165
- `error` at line 402 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:402
- `error` at line 639 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:639
- `error` at line 723 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:723
- `error` at line 1094 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:1094
- `error` at line 1236 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/rm.py:1236
- `warning` at line 33 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:33
- `error` at line 79 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/storm_wiki/modules/article_generation.py:79
- `error` at line 236 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/storm_wiki/modules/knowledge_curation.py:236
- `error` at line 91 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.error("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.error("order moved", order_id=order_id, status=status)` with structlog. — knowledge_storm/storm_wiki/modules/persona_generator.py:91
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 47% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 29% | Weak — gated by D8, D9, D12, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 88% | Strong | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 2 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 evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not 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.
- 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in 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 — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 value object(s))
- 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 and Scala, 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 — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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 applicable: Python runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
- X16 Unfloored truncation loop — 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
- X18 Disposal-pattern correctness — 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
- 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.
- X29 Per-element action decided by a fixed element — 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
- 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 — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: unidecode
- REDACTED
- No automated tests
Serious — 56 finding(s)
- FileTooLong: knowledge_storm/lm.py knowledge_storm/lm.py
- FileTooLong: knowledge_storm/rm.py knowledge_storm/rm.py
- FileTooLong: collaborative_storm/engine.py knowledge_storm/collaborative_storm/engine.py
- FileTooLong: knowledge_storm/dataclass.py knowledge_storm/dataclass.py
- Swallowed exception (caught, then discarded) knowledge_storm/rm.py:564
- Swallowed exception (caught, then discarded) REDACTED:443
- Swallowed exception (caught, then discarded) REDACTED:764
- Swallowed exception (caught, then discarded) REDACTED:791
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (17 lines × 2) knowledge_storm/rm.py:839
- Duplicated block (17 lines × 2) REDACTED:169
- Duplicated block (15 lines × 2) knowledge_storm/lm.py:80
- Duplicated block (15 lines × 2) examples/storm_examples/run_storm_wiki_deepseek.py:44
- Swallowed exception (empty catch) knowledge_storm/storm_wiki/modules/storm_dataclass.py:446
- Swallowed exception (empty catch) knowledge_storm/collaborative_storm/modules/information_insertion_module.py:171
- FixmeComment knowledge_storm/collaborative_storm/engine.py:556
- SerperRM.forward (cognitive 26) knowledge_storm/rm.py:490
- TavilySearchRM.forward (cognitive 22) knowledge_storm/rm.py:920
- CoStormRunner.step (cognitive 19) knowledge_storm/collaborative_storm/engine.py:661
- collaborative_storm_utils.format_search_results (cognitive 18) knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py:36
- DuckDuckGoSearchRM.forward (cognitive 18) knowledge_storm/rm.py:802
- collaborative_storm_utils.clean_up_section (cognitive 17) knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py:194
- ArticleTextProcessing.clean_up_section (cognitive 17) REDACTED:506
- InsertInformationModule.layer_by_layer_navigation_placement (cognitive 16) knowledge_storm/collaborative_storm/modules/information_insertion_module.py:108
- KnowledgeBase.insert_from_outline_string (cognitive 16) knowledge_storm/dataclass.py:514
- StormArticle.update_section (cognitive 16) knowledge_storm/storm_wiki/modules/storm_dataclass.py:249
- StormArticle.from_outline_str (cognitive 16) knowledge_storm/storm_wiki/modules/storm_dataclass.py:438
- REDACTED
- REDACTED
- Duplicated block (20 lines × 2) knowledge_storm/lm.py:439
- Duplicated block (18–20 lines × 2) knowledge_storm/rm.py:159
- Duplicated block (17–18 lines × 2) knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py:209
- Duplicated block (12 lines × 2) knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py:229
- Duplicated block (11 lines × 2) knowledge_storm/lm.py:376
- Duplicated block (9–10 lines × 2) knowledge_storm/lm.py:94
- Duplicated block (8 lines × 2) knowledge_storm/collaborative_storm/modules/information_insertion_module.py:288
- Duplicated block (7 lines × 2) knowledge_storm/lm.py:103
- Near-duplicate member family (4 members, 29 shared lines) examples/storm_examples/run_storm_wiki_claude.py:41
- Edited copy of a member (129 corresponding lines) examples/storm_examples/run_storm_wiki_mistral.py:43
- Duplicated block (60 lines × 2) examples/storm_examples/run_storm_wiki_mistral.py:103
- Duplicated block (43–49 lines × 3) examples/storm_examples/run_storm_wiki_mistral.py:139
- Duplicated block (47–48 lines × 7) examples/storm_examples/run_storm_wiki_claude.py:71
- Duplicated block (38 lines × 2) examples/storm_examples/run_storm_wiki_claude.py:41
- Duplicated block (30–32 lines × 2) examples/storm_examples/run_storm_wiki_gpt.py:45
- Duplicated block (21–28 lines × 3) examples/costorm_examples/run_costorm_gpt.py:68
- Duplicated block (25–27 lines × 2) examples/storm_examples/run_storm_wiki_ollama.py:44
- Duplicated block (17 lines × 3) examples/storm_examples/run_storm_wiki_claude.py:117
- Duplicated block (13–16 lines × 10) examples/storm_examples/run_storm_wiki_claude.py:68
- Duplicated block (14 lines × 4) examples/storm_examples/run_storm_wiki_claude.py:121
- Duplicated block (9 lines × 8) examples/costorm_examples/run_costorm_gpt.py:145
Minor — 60 finding(s)
- Orphaned file knowledge_storm/collaborative_storm/engine.py:1
- Orphaned file REDACTED:1
- Orphaned file frontend/demo_light/demo_util.py:1
- Orphaned file REDACTED:1
- Orphaned file knowledge_storm/storm_wiki/modules/storm_dataclass.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/warmstart_hierarchical_chat.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/information_insertion_module.py:1
- Orphaned file knowledge_storm/storm_wiki/engine.py:1
- Orphaned file knowledge_storm/storm_wiki/modules/knowledge_curation.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/co_storm_agents.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py:1
- Orphaned file knowledge_storm/logging_wrapper.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/grounded_question_answering.py:1
- Orphaned file knowledge_storm/storm_wiki/modules/article_generation.py:1
- Orphaned file knowledge_storm/storm_wiki/modules/outline_generation.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/costorm_expert_utterance_generator.py:1
- Orphaned file knowledge_storm/encoder.py:1
- Orphaned file knowledge_storm/storm_wiki/modules/persona_generator.py:1
- Orphaned file frontend/demo_light/pages_util/CreateNewArticle.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/grounded_question_generation.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/article_generation.py:1
- Orphaned file knowledge_storm/collaborative_storm/modules/callback.py:1
- Orphaned file knowledge_storm/storm_wiki/modules/retriever.py:1
- Orphaned file knowledge_storm/storm_wiki/modules/article_polish.py:1
- Orphaned file frontend/demo_light/stoc.py:1
- Interpolated log message defeats structured logging REDACTED:420
- Interpolated log message defeats structured logging REDACTED:439
- Interpolated log message defeats structured logging REDACTED:502
- Interpolated log message defeats structured logging knowledge_storm/lm.py:535
- Interpolated log message defeats structured logging knowledge_storm/rm.py:72
- Interpolated log message defeats structured logging knowledge_storm/rm.py:165
- Interpolated log message defeats structured logging knowledge_storm/rm.py:402
- Interpolated log message defeats structured logging knowledge_storm/rm.py:639
- Interpolated log message defeats structured logging knowledge_storm/rm.py:723
- Interpolated log message defeats structured logging knowledge_storm/rm.py:1094
- Interpolated log message defeats structured logging knowledge_storm/rm.py:1236
- Interpolated log message defeats structured logging REDACTED:33
- Interpolated log message defeats structured logging knowledge_storm/storm_wiki/modules/article_generation.py:79
- Interpolated log message defeats structured logging knowledge_storm/storm_wiki/modules/knowledge_curation.py:236
- Interpolated log message defeats structured logging knowledge_storm/storm_wiki/modules/persona_generator.py:91
- Most significant orphaned file knowledge_storm/rm.py:1
- Most significant orphaned file knowledge_storm/lm.py:1
- Most significant orphaned file knowledge_storm/dataclass.py:1
- Duplicated predicate knowledge_storm/collaborative_storm/engine.py:165
- Duplicated predicate knowledge_storm/collaborative_storm/modules/collaborative_storm_utils.py:215
- Silent fallback default in catch REDACTED:764
- Silent fallback default in catch REDACTED:791
- Projects may be oversized for their cohesion
- Scattered collaborators
- Dormant codebase
- REDACTED
- No tests found
- No ADRs
- No architecture diagram/doc
- No src/ separation
- Logging is not universal
- No SAST REDACTED:4
- No changelog
Minor — 4 finding(s)
- Outdated: dspy-ai
- Outdated: extra-streamlit-components
- Outdated: st-pages
- Outdated: streamlit
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a9ff155da9cc4b3da30b7ce99bd25e4f/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a9ff155da9cc4b3da30b7ce99bd25e4f/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |