Executive summary
vortico/flama is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has controls that only work with a mouse. It scores 55 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 39, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 7 points. Recording design decisions comes next, worth about 4 points. Raising Accessibility to 70 would lift the score to about 67.
Twenty-one known security holes in the packages the code depends on can be used by attackers. Three controls can't be used without a mouse, and two weaknesses in the code could be used by an attacker. Making the controls work with a keyboard, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once.
The product code is 36,619 lines, about €81,000 to rebuild.
If Accessibility rose from 39 to 70, the lowest score rated Strong, the score would rise from 55 to about 67.
New since the last survey: 9 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flama/models/wire/dialect/llm/anthropic/parser.py
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flama/serialize/serializer.py
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 10 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flama/models/wire/dialect/llm/anthropic/parser.py
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) flama/serialize/serializer.py
- Secret Scanning · Leaked secret: hardcoded-credential flama/models/transport/input/llm/message.py
- Churn × Complexity Hotspots · Hotspot: flama/serialize/model_serializers/transformers.py flama/serialize/model_serializers/transformers.py
- Churn × Complexity Hotspots · Repeated repair: flama/injection/resolver.py flama/injection/resolver.py
- Churn × Complexity Hotspots · Repeated repair: flama/models/engine/backend/llm/_base.py flama/models/engine/backend/llm/_base.py
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €81,000 · Estimate
| Cost to rebuild | €27,000 to €140,000, for 449 to 1,423 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 36,619 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 flama._upgrade.source | 2 flama.codecs._base | 3 flama.context | 4 flama.http.data_structures | 5 flama.injection.components | 6 flama.models.transport.input.llm.message | 7 flama.models.transport.output.llm.event._base | 8 flama.serialize.data_structures | 9 flama.types.asgi | 10 flama.url | 11 lib.templates.src.apps.chatbot.components.message | 12 flama.codecs.compression.codec | 13 flama.codecs.http.codec | 14 flama.codecs.websockets.codec | 15 flama.http.requests.http | 16 flama.http.responses.response | 17 flama.middleware._base | 18 flama.models.engine.backend.llm._base | 19 flama.models.engine.backend.ml._base | 20 flama.models.transport.output.llm.event.start | 21 flama.models.transport.output.llm.event.stop | 22 flama.models.transport.output.llm.event.text | 23 flama.models.transport.output.llm.event.tool | 24 flama.types.applications | 25 flama.ddd.workers._base | 26 flama.debug.middleware | 27 flama.http.responses.sse | 28 flama.models.wire.dialect._base | 29 flama.modules | 30 flama.routing.routes._base | 31 flama.http.components | 32 flama.models.wire.dialect.llm.anthropic.renderer | 33 flama.models.wire.dialect.llm.native.renderer | 34 flama.models.wire.dialect.llm.ollama.renderer | 35 flama.models.wire.dialect.llm.openai.renderer | 36 flama.routing.routes.mount | 37 flama.schemas.components | 38 flama.schemas.modules | 39 flama.applications | 40 flama.routing.router |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 flama._upgrade.source | ||||||||||||||||||||||||||||||||||||||||
| 2 flama.codecs._base | ||||||||||||||||||||||||||||||||||||||||
| 3 flama.context | ||||||||||||||||||||||||||||||||||||||||
| 4 flama.http.data_structures | ||||||||||||||||||||||||||||||||||||||||
| 5 flama.injection.components | ||||||||||||||||||||||||||||||||||||||||
| 6 flama.models.transport.input.llm.message | ||||||||||||||||||||||||||||||||||||||||
| 7 flama.models.transport.output.llm.event._base | ||||||||||||||||||||||||||||||||||||||||
| 8 flama.serialize.data_structures | ||||||||||||||||||||||||||||||||||||||||
| 9 flama.types.asgi | ||||||||||||||||||||||||||||||||||||||||
| 10 flama.url | ||||||||||||||||||||||||||||||||||||||||
| 11 lib.templates.src.apps.chatbot.components.message | ||||||||||||||||||||||||||||||||||||||||
| 12 flama.codecs.compression.codec | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 flama.codecs.http.codec | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 flama.codecs.websockets.codec | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 flama.http.requests.http | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 16 flama.http.responses.response | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 17 flama.middleware._base | 6 | |||||||||||||||||||||||||||||||||||||||
| 18 flama.models.engine.backend.llm._base | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 flama.models.engine.backend.ml._base | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 flama.models.transport.output.llm.event.start | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 flama.models.transport.output.llm.event.stop | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 flama.models.transport.output.llm.event.text | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 flama.models.transport.output.llm.event.tool | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 flama.types.applications | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 flama.ddd.workers._base | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 flama.debug.middleware | 9 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 flama.http.responses.sse | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 flama.models.wire.dialect._base | 3 | 2 | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 29 flama.modules | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 flama.routing.routes._base | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 flama.http.components | 3 | 12 | 9 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 flama.models.wire.dialect.llm.anthropic.renderer | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 flama.models.wire.dialect.llm.native.renderer | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 flama.models.wire.dialect.llm.ollama.renderer | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 flama.models.wire.dialect.llm.openai.renderer | 3 | 3 | 3 | 3 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 36 flama.routing.routes.mount | 3 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 flama.schemas.components | 2 | 8 | 1 | 5 | 4 | |||||||||||||||||||||||||||||||||||
| 38 flama.schemas.modules | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 flama.applications | 2 | 3 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 flama.routing.router | 1 | 3 | 1 | 1 | 1 | 1 |
12→2 flama.codecs.compression.codec uses flama.codecs._base✕
- Connections
- 1 pair of types, where a type in flama.codecs.compression.codec uses a type in flama.codecs._base.
- The types involved
flama.codecs.compression.codec.CompressionCodec→flama.codecs._base.Codec
- Direction
- flama.codecs.compression.codec uses flama.codecs._base, so a change to flama.codecs._base can break flama.codecs.compression.codec, while a change to flama.codecs.compression.codec can't break flama.codecs._base.
- Position
- Below the diagonal: flama.codecs.compression.codec uses a module listed above it, which is the healthy direction.
13→2 flama.codecs.http.codec uses flama.codecs._base✕
- Connections
- 1 pair of types, where a type in flama.codecs.http.codec uses a type in flama.codecs._base.
- The types involved
flama.codecs.http.codec.HTTPCodec→flama.codecs._base.Codec
- Direction
- flama.codecs.http.codec uses flama.codecs._base, so a change to flama.codecs._base can break flama.codecs.http.codec, while a change to flama.codecs.http.codec can't break flama.codecs._base.
- Position
- Below the diagonal: flama.codecs.http.codec uses a module listed above it, which is the healthy direction.
14→2 flama.codecs.websockets.codec uses flama.codecs._base✕
- Connections
- 1 pair of types, where a type in flama.codecs.websockets.codec uses a type in flama.codecs._base.
- The types involved
flama.codecs.websockets.codec.WebsocketsCodec→flama.codecs._base.Codec
- Direction
- flama.codecs.websockets.codec uses flama.codecs._base, so a change to flama.codecs._base can break flama.codecs.websockets.codec, while a change to flama.codecs.websockets.codec can't break flama.codecs._base.
- Position
- Below the diagonal: flama.codecs.websockets.codec uses a module listed above it, which is the healthy direction.
15→4 flama.http.requests.http uses flama.http.data_structures✕
- Connections
- 1 pair of types, where a type in flama.http.requests.http uses a type in flama.http.data_structures.
- The types involved
flama.http.requests.http.Request→flama.http.data_structures.FormData
- Direction
- flama.http.requests.http uses flama.http.data_structures, so a change to flama.http.data_structures can break flama.http.requests.http, while a change to flama.http.requests.http can't break flama.http.data_structures.
- Position
- Below the diagonal: flama.http.requests.http uses a module listed above it, which is the healthy direction.
15→9 flama.http.requests.http uses flama.types.asgi✕
- Connections
- 7 pairs of types, where a type in flama.http.requests.http uses a type in flama.types.asgi.
- The types involved
flama.http.requests.http.Request→flama.types.asgi.Receiveflama.http.requests.http.Request→flama.types.asgi.Scopeflama.http.requests.http.Request→flama.types.asgi.Sendflama.http.requests.http._EmptyReceive→flama.types.asgi.Messageflama.http.requests.http._EmptyReceive→flama.types.asgi.Receiveflama.http.requests.http._EmptySend→flama.types.asgi.Messageflama.http.requests.http._EmptySend→flama.types.asgi.Send
- Direction
- flama.http.requests.http uses flama.types.asgi, so a change to flama.types.asgi can break flama.http.requests.http, while a change to flama.http.requests.http can't break flama.types.asgi.
- Position
- Below the diagonal: flama.http.requests.http uses a module listed above it, which is the healthy direction.
16→4 flama.http.responses.response uses flama.http.data_structures✕
- Connections
- 1 pair of types, where a type in flama.http.responses.response uses a type in flama.http.data_structures.
- The types involved
flama.http.responses.response.Response→flama.http.data_structures.MutableHeaders
- Direction
- flama.http.responses.response uses flama.http.data_structures, so a change to flama.http.data_structures can break flama.http.responses.response, while a change to flama.http.responses.response can't break flama.http.data_structures.
- Position
- Below the diagonal: flama.http.responses.response uses a module listed above it, which is the healthy direction.
16→9 flama.http.responses.response uses flama.types.asgi✕
- Connections
- 9 pairs of types, where a type in flama.http.responses.response uses a type in flama.types.asgi.
- The types involved
flama.http.responses.response.BufferedResponse→flama.types.asgi.Receiveflama.http.responses.response.BufferedResponse→flama.types.asgi.Scopeflama.http.responses.response.BufferedResponse→flama.types.asgi.Sendflama.http.responses.response.Response→flama.types.asgi.Receiveflama.http.responses.response.Response→flama.types.asgi.Scopeflama.http.responses.response.Response→flama.types.asgi.Sendflama.http.responses.response.StreamingResponse→flama.types.asgi.Receiveflama.http.responses.response.StreamingResponse→flama.types.asgi.Scopeflama.http.responses.response.StreamingResponse→flama.types.asgi.Send
- Direction
- flama.http.responses.response uses flama.types.asgi, so a change to flama.types.asgi can break flama.http.responses.response, while a change to flama.http.responses.response can't break flama.types.asgi.
- Position
- Below the diagonal: flama.http.responses.response uses a module listed above it, which is the healthy direction.
17→9 flama.middleware._base uses flama.types.asgi✕
- Connections
- 6 pairs of types, where a type in flama.middleware._base uses a type in flama.types.asgi.
- The types involved
flama.middleware._base.Middleware→flama.types.asgi.Receiveflama.middleware._base.Middleware→flama.types.asgi.Scopeflama.middleware._base.Middleware→flama.types.asgi.Sendflama.middleware._base.MiddlewareStack→flama.types.asgi.Receiveflama.middleware._base.MiddlewareStack→flama.types.asgi.Scopeflama.middleware._base.MiddlewareStack→flama.types.asgi.Send
- Direction
- flama.middleware._base uses flama.types.asgi, so a change to flama.types.asgi can break flama.middleware._base, while a change to flama.middleware._base can't break flama.types.asgi.
- Position
- Below the diagonal: flama.middleware._base uses a module listed above it, which is the healthy direction.
18→6 flama.models.engine.backend.llm._base uses flama.models.transport.input.llm.message✕
- Connections
- 3 pairs of types, where a type in flama.models.engine.backend.llm._base uses a type in flama.models.transport.input.llm.message.
- The types involved
flama.models.engine.backend.llm._base.TransformerLLMBackend→flama.models.transport.input.llm.message.Contentflama.models.engine.backend.llm._base.TransformerLLMBackend→flama.models.transport.input.llm.message.Messageflama.models.engine.backend.llm._base.TransformerLLMBackend→flama.models.transport.input.llm.message.ToolCall
- Direction
- flama.models.engine.backend.llm._base uses flama.models.transport.input.llm.message, so a change to flama.models.transport.input.llm.message can break flama.models.engine.backend.llm._base, while a change to flama.models.engine.backend.llm._base can't break flama.models.transport.input.llm.message.
- Position
- Below the diagonal: flama.models.engine.backend.llm._base uses a module listed above it, which is the healthy direction.
18→8 flama.models.engine.backend.llm._base uses flama.serialize.data_structures✕
- Connections
- 2 pairs of types, where a type in flama.models.engine.backend.llm._base uses a type in flama.serialize.data_structures.
- The types involved
flama.models.engine.backend.llm._base.LLMBackend→flama.serialize.data_structures.LLMModelCapabilitiesflama.models.engine.backend.llm._base.LLMBackend→flama.serialize.data_structures.ModelArtifact
- Direction
- flama.models.engine.backend.llm._base uses flama.serialize.data_structures, so a change to flama.serialize.data_structures can break flama.models.engine.backend.llm._base, while a change to flama.models.engine.backend.llm._base can't break flama.serialize.data_structures.
- Position
- Below the diagonal: flama.models.engine.backend.llm._base uses a module listed above it, which is the healthy direction.
19→8 flama.models.engine.backend.ml._base uses flama.serialize.data_structures✕
- Connections
- 1 pair of types, where a type in flama.models.engine.backend.ml._base uses a type in flama.serialize.data_structures.
- The types involved
flama.models.engine.backend.ml._base.MLBackend→flama.serialize.data_structures.ModelArtifact
- Direction
- flama.models.engine.backend.ml._base uses flama.serialize.data_structures, so a change to flama.serialize.data_structures can break flama.models.engine.backend.ml._base, while a change to flama.models.engine.backend.ml._base can't break flama.serialize.data_structures.
- Position
- Below the diagonal: flama.models.engine.backend.ml._base uses a module listed above it, which is the healthy direction.
20→7 flama.models.transport.output.llm.event.start uses flama.models.transport.output.llm.event._base✕
- Connections
- 1 pair of types, where a type in flama.models.transport.output.llm.event.start uses a type in flama.models.transport.output.llm.event._base.
- The types involved
flama.models.transport.output.llm.event.start.StartEvent→flama.models.transport.output.llm.event._base.Event
- Direction
- flama.models.transport.output.llm.event.start uses flama.models.transport.output.llm.event._base, so a change to flama.models.transport.output.llm.event._base can break flama.models.transport.output.llm.event.start, while a change to flama.models.transport.output.llm.event.start can't break flama.models.transport.output.llm.event._base.
- Position
- Below the diagonal: flama.models.transport.output.llm.event.start uses a module listed above it, which is the healthy direction.
21→7 flama.models.transport.output.llm.event.stop uses flama.models.transport.output.llm.event._base✕
- Connections
- 1 pair of types, where a type in flama.models.transport.output.llm.event.stop uses a type in flama.models.transport.output.llm.event._base.
- The types involved
flama.models.transport.output.llm.event.stop.StopEvent→flama.models.transport.output.llm.event._base.Event
- Direction
- flama.models.transport.output.llm.event.stop uses flama.models.transport.output.llm.event._base, so a change to flama.models.transport.output.llm.event._base can break flama.models.transport.output.llm.event.stop, while a change to flama.models.transport.output.llm.event.stop can't break flama.models.transport.output.llm.event._base.
- Position
- Below the diagonal: flama.models.transport.output.llm.event.stop uses a module listed above it, which is the healthy direction.
22→7 flama.models.transport.output.llm.event.text uses flama.models.transport.output.llm.event._base✕
- Connections
- 1 pair of types, where a type in flama.models.transport.output.llm.event.text uses a type in flama.models.transport.output.llm.event._base.
- The types involved
flama.models.transport.output.llm.event.text.TextEvent→flama.models.transport.output.llm.event._base.Event
- Direction
- flama.models.transport.output.llm.event.text uses flama.models.transport.output.llm.event._base, so a change to flama.models.transport.output.llm.event._base can break flama.models.transport.output.llm.event.text, while a change to flama.models.transport.output.llm.event.text can't break flama.models.transport.output.llm.event._base.
- Position
- Below the diagonal: flama.models.transport.output.llm.event.text uses a module listed above it, which is the healthy direction.
23→7 flama.models.transport.output.llm.event.tool uses flama.models.transport.output.llm.event._base✕
- Connections
- 1 pair of types, where a type in flama.models.transport.output.llm.event.tool uses a type in flama.models.transport.output.llm.event._base.
- The types involved
flama.models.transport.output.llm.event.tool.ToolEvent→flama.models.transport.output.llm.event._base.Event
- Direction
- flama.models.transport.output.llm.event.tool uses flama.models.transport.output.llm.event._base, so a change to flama.models.transport.output.llm.event._base can break flama.models.transport.output.llm.event.tool, while a change to flama.models.transport.output.llm.event.tool can't break flama.models.transport.output.llm.event._base.
- Position
- Below the diagonal: flama.models.transport.output.llm.event.tool uses a module listed above it, which is the healthy direction.
24→9 flama.types.applications uses flama.types.asgi✕
- Connections
- 3 pairs of types, where a type in flama.types.applications uses a type in flama.types.asgi.
- The types involved
flama.types.applications.App→flama.types.asgi.Receiveflama.types.applications.App→flama.types.asgi.Scopeflama.types.applications.App→flama.types.asgi.Send
- Direction
- flama.types.applications uses flama.types.asgi, so a change to flama.types.asgi can break flama.types.applications, while a change to flama.types.applications can't break flama.types.asgi.
- Position
- Below the diagonal: flama.types.applications uses a module listed above it, which is the healthy direction.
25→24 flama.ddd.workers._base uses flama.types.applications✕
- Connections
- 1 pair of types, where a type in flama.ddd.workers._base uses a type in flama.types.applications.
- The types involved
flama.ddd.workers._base.AbstractWorker→flama.types.applications.App
- Direction
- flama.ddd.workers._base uses flama.types.applications, so a change to flama.types.applications can break flama.ddd.workers._base, while a change to flama.ddd.workers._base can't break flama.types.applications.
- Position
- Below the diagonal: flama.ddd.workers._base uses a module listed above it, which is the healthy direction.
26→9 flama.debug.middleware uses flama.types.asgi✕
- Connections
- 9 pairs of types, where a type in flama.debug.middleware uses a type in flama.types.asgi.
- The types involved
flama.debug.middleware.BaseErrorMiddleware→flama.types.asgi.Receiveflama.debug.middleware.BaseErrorMiddleware→flama.types.asgi.Scopeflama.debug.middleware.BaseErrorMiddleware→flama.types.asgi.Sendflama.debug.middleware.ExceptionMiddleware→flama.types.asgi.Receiveflama.debug.middleware.ExceptionMiddleware→flama.types.asgi.Scopeflama.debug.middleware.ExceptionMiddleware→flama.types.asgi.Sendflama.debug.middleware.ServerErrorMiddleware→flama.types.asgi.Receiveflama.debug.middleware.ServerErrorMiddleware→flama.types.asgi.Scopeflama.debug.middleware.ServerErrorMiddleware→flama.types.asgi.Send
- Direction
- flama.debug.middleware uses flama.types.asgi, so a change to flama.types.asgi can break flama.debug.middleware, while a change to flama.debug.middleware can't break flama.types.asgi.
- Position
- Below the diagonal: flama.debug.middleware uses a module listed above it, which is the healthy direction.
26→16 flama.debug.middleware uses flama.http.responses.response✕
- Connections
- 2 pairs of types, where a type in flama.debug.middleware uses a type in flama.http.responses.response.
- The types involved
flama.debug.middleware.ExceptionMiddleware→flama.http.responses.response.Responseflama.debug.middleware.ServerErrorMiddleware→flama.http.responses.response.Response
- Direction
- flama.debug.middleware uses flama.http.responses.response, so a change to flama.http.responses.response can break flama.debug.middleware, while a change to flama.debug.middleware can't break flama.http.responses.response.
- Position
- Below the diagonal: flama.debug.middleware uses a module listed above it, which is the healthy direction.
26→17 flama.debug.middleware uses flama.middleware._base✕
- Connections
- 1 pair of types, where a type in flama.debug.middleware uses a type in flama.middleware._base.
- The types involved
flama.debug.middleware.BaseErrorMiddleware→flama.middleware._base.Middleware
- Direction
- flama.debug.middleware uses flama.middleware._base, so a change to flama.middleware._base can break flama.debug.middleware, while a change to flama.debug.middleware can't break flama.middleware._base.
- Position
- Below the diagonal: flama.debug.middleware uses a module listed above it, which is the healthy direction.
27→16 flama.http.responses.sse uses flama.http.responses.response✕
- Connections
- 1 pair of types, where a type in flama.http.responses.sse uses a type in flama.http.responses.response.
- The types involved
flama.http.responses.sse.ServerSentEventResponse→flama.http.responses.response.StreamingResponse
- Direction
- flama.http.responses.sse uses flama.http.responses.response, so a change to flama.http.responses.response can break flama.http.responses.sse, while a change to flama.http.responses.sse can't break flama.http.responses.response.
- Position
- Below the diagonal: flama.http.responses.sse uses a module listed above it, which is the healthy direction.
28→6 flama.models.wire.dialect._base uses flama.models.transport.input.llm.message✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect._base uses a type in flama.models.transport.input.llm.message.
- The types involved
flama.models.wire.dialect._base.Parser→flama.models.transport.input.llm.message.Contentflama.models.wire.dialect._base.Parser→flama.models.transport.input.llm.message.Messageflama.models.wire.dialect._base.Parser→flama.models.transport.input.llm.message.ToolCall
- Direction
- flama.models.wire.dialect._base uses flama.models.transport.input.llm.message, so a change to flama.models.transport.input.llm.message can break flama.models.wire.dialect._base, while a change to flama.models.wire.dialect._base can't break flama.models.transport.input.llm.message.
- Position
- Below the diagonal: flama.models.wire.dialect._base uses a module listed above it, which is the healthy direction.
28→20 flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.start✕
- Connections
- 2 pairs of types, where a type in flama.models.wire.dialect._base uses a type in flama.models.transport.output.llm.event.start.
- The types involved
flama.models.wire.dialect._base.Assembler→flama.models.transport.output.llm.event.start.StartEventflama.models.wire.dialect._base.Renderer→flama.models.transport.output.llm.event.start.StartEvent
- Direction
- flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.start, so a change to flama.models.transport.output.llm.event.start can break flama.models.wire.dialect._base, while a change to flama.models.wire.dialect._base can't break flama.models.transport.output.llm.event.start.
- Position
- Below the diagonal: flama.models.wire.dialect._base uses a module listed above it, which is the healthy direction.
28→21 flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.stop✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect._base uses a type in flama.models.transport.output.llm.event.stop.
- The types involved
flama.models.wire.dialect._base.Assembler→flama.models.transport.output.llm.event.stop.StopEventflama.models.wire.dialect._base.CoalescingRenderer→flama.models.transport.output.llm.event.stop.StopEventflama.models.wire.dialect._base.Renderer→flama.models.transport.output.llm.event.stop.StopEvent
- Direction
- flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.stop, so a change to flama.models.transport.output.llm.event.stop can break flama.models.wire.dialect._base, while a change to flama.models.wire.dialect._base can't break flama.models.transport.output.llm.event.stop.
- Position
- Below the diagonal: flama.models.wire.dialect._base uses a module listed above it, which is the healthy direction.
28→22 flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.text✕
- Connections
- 2 pairs of types, where a type in flama.models.wire.dialect._base uses a type in flama.models.transport.output.llm.event.text.
- The types involved
flama.models.wire.dialect._base.CoalescingRenderer→flama.models.transport.output.llm.event.text.TextEventflama.models.wire.dialect._base.Renderer→flama.models.transport.output.llm.event.text.TextEvent
- Direction
- flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.text, so a change to flama.models.transport.output.llm.event.text can break flama.models.wire.dialect._base, while a change to flama.models.wire.dialect._base can't break flama.models.transport.output.llm.event.text.
- Position
- Below the diagonal: flama.models.wire.dialect._base uses a module listed above it, which is the healthy direction.
28→23 flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.tool✕
- Connections
- 2 pairs of types, where a type in flama.models.wire.dialect._base uses a type in flama.models.transport.output.llm.event.tool.
- The types involved
flama.models.wire.dialect._base.CoalescingRenderer→flama.models.transport.output.llm.event.tool.ToolEventflama.models.wire.dialect._base.Renderer→flama.models.transport.output.llm.event.tool.ToolEvent
- Direction
- flama.models.wire.dialect._base uses flama.models.transport.output.llm.event.tool, so a change to flama.models.transport.output.llm.event.tool can break flama.models.wire.dialect._base, while a change to flama.models.wire.dialect._base can't break flama.models.transport.output.llm.event.tool.
- Position
- Below the diagonal: flama.models.wire.dialect._base uses a module listed above it, which is the healthy direction.
29→24 flama.modules uses flama.types.applications✕
- Connections
- 2 pairs of types, where a type in flama.modules uses a type in flama.types.applications.
- The types involved
flama.modules.Modules→flama.types.applications.Appflama.modules._BaseModule→flama.types.applications.App
- Direction
- flama.modules uses flama.types.applications, so a change to flama.types.applications can break flama.modules, while a change to flama.modules can't break flama.types.applications.
- Position
- Below the diagonal: flama.modules uses a module listed above it, which is the healthy direction.
30→9 flama.routing.routes._base uses flama.types.asgi✕
- Connections
- 6 pairs of types, where a type in flama.routing.routes._base uses a type in flama.types.asgi.
- The types involved
flama.routing.routes._base.BaseEndpointWrapper→flama.types.asgi.Receiveflama.routing.routes._base.BaseEndpointWrapper→flama.types.asgi.Scopeflama.routing.routes._base.BaseEndpointWrapper→flama.types.asgi.Sendflama.routing.routes._base.BaseRoute→flama.types.asgi.Receiveflama.routing.routes._base.BaseRoute→flama.types.asgi.Scopeflama.routing.routes._base.BaseRoute→flama.types.asgi.Send
- Direction
- flama.routing.routes._base uses flama.types.asgi, so a change to flama.types.asgi can break flama.routing.routes._base, while a change to flama.routing.routes._base can't break flama.types.asgi.
- Position
- Below the diagonal: flama.routing.routes._base uses a module listed above it, which is the healthy direction.
30→10 flama.routing.routes._base uses flama.url✕
- Connections
- 1 pair of types, where a type in flama.routing.routes._base uses a type in flama.url.
- The types involved
flama.routing.routes._base.BaseRoute→flama.url.URL
- Direction
- flama.routing.routes._base uses flama.url, so a change to flama.url can break flama.routing.routes._base, while a change to flama.routing.routes._base can't break flama.url.
- Position
- Below the diagonal: flama.routing.routes._base uses a module listed above it, which is the healthy direction.
30→24 flama.routing.routes._base uses flama.types.applications✕
- Connections
- 1 pair of types, where a type in flama.routing.routes._base uses a type in flama.types.applications.
- The types involved
flama.routing.routes._base.BaseRoute→flama.types.applications.App
- Direction
- flama.routing.routes._base uses flama.types.applications, so a change to flama.types.applications can break flama.routing.routes._base, while a change to flama.routing.routes._base can't break flama.types.applications.
- Position
- Below the diagonal: flama.routing.routes._base uses a module listed above it, which is the healthy direction.
31→4 flama.http.components uses flama.http.data_structures✕
- Connections
- 3 pairs of types, where a type in flama.http.components uses a type in flama.http.data_structures.
- The types involved
flama.http.components.CookiesComponent→flama.http.data_structures.Headersflama.http.components.HeadersComponent→flama.http.data_structures.Headersflama.http.components.QueryParamsComponent→flama.http.data_structures.QueryParams
- Direction
- flama.http.components uses flama.http.data_structures, so a change to flama.http.data_structures can break flama.http.components, while a change to flama.http.components can't break flama.http.data_structures.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
31→5 flama.http.components uses flama.injection.components✕
- Connections
- 12 pairs of types, where a type in flama.http.components uses a type in flama.injection.components.
- The types involved
flama.http.components.AppComponent→flama.injection.components.Componentflama.http.components.BodyComponent→flama.injection.components.Componentflama.http.components.CookiesComponent→flama.injection.components.Componentflama.http.components.HeadersComponent→flama.injection.components.Componentflama.http.components.MethodComponent→flama.injection.components.Componentflama.http.components.PathComponent→flama.injection.components.Componentflama.http.components.PathParamsComponent→flama.injection.components.Componentflama.http.components.QueryParamsComponent→flama.injection.components.Componentflama.http.components.QueryStringComponent→flama.injection.components.Componentflama.http.components.SchemeComponent→flama.injection.components.Componentflama.http.components.ServerComponent→flama.injection.components.Componentflama.http.components.URLComponent→flama.injection.components.Component
- Direction
- flama.http.components uses flama.injection.components, so a change to flama.injection.components can break flama.http.components, while a change to flama.http.components can't break flama.injection.components.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
31→9 flama.http.components uses flama.types.asgi✕
- Connections
- 9 pairs of types, where a type in flama.http.components uses a type in flama.types.asgi.
- The types involved
flama.http.components.AppComponent→flama.types.asgi.Scopeflama.http.components.BodyComponent→flama.types.asgi.Receiveflama.http.components.MethodComponent→flama.types.asgi.Scopeflama.http.components.PathComponent→flama.types.asgi.Scopeflama.http.components.PathParamsComponent→flama.types.asgi.Scopeflama.http.components.QueryStringComponent→flama.types.asgi.Scopeflama.http.components.SchemeComponent→flama.types.asgi.Scopeflama.http.components.ServerComponent→flama.types.asgi.Scopeflama.http.components.URLComponent→flama.types.asgi.Scope
- Direction
- flama.http.components uses flama.types.asgi, so a change to flama.types.asgi can break flama.http.components, while a change to flama.http.components can't break flama.types.asgi.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
31→10 flama.http.components uses flama.url✕
- Connections
- 2 pairs of types, where a type in flama.http.components uses a type in flama.url.
- The types involved
flama.http.components.PathComponent→flama.url.Pathflama.http.components.URLComponent→flama.url.URL
- Direction
- flama.http.components uses flama.url, so a change to flama.url can break flama.http.components, while a change to flama.http.components can't break flama.url.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
31→15 flama.http.components uses flama.http.requests.http✕
- Connections
- 1 pair of types, where a type in flama.http.components uses a type in flama.http.requests.http.
- The types involved
flama.http.components.HeadersComponent→flama.http.requests.http.Request
- Direction
- flama.http.components uses flama.http.requests.http, so a change to flama.http.requests.http can break flama.http.components, while a change to flama.http.components can't break flama.http.requests.http.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
31→24 flama.http.components uses flama.types.applications✕
- Connections
- 1 pair of types, where a type in flama.http.components uses a type in flama.types.applications.
- The types involved
flama.http.components.AppComponent→flama.types.applications.App
- Direction
- flama.http.components uses flama.types.applications, so a change to flama.types.applications can break flama.http.components, while a change to flama.http.components can't break flama.types.applications.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
31→30 flama.http.components uses flama.routing.routes._base✕
- Connections
- 1 pair of types, where a type in flama.http.components uses a type in flama.routing.routes._base.
- The types involved
flama.http.components.PathParamsComponent→flama.routing.routes._base.BaseRoute
- Direction
- flama.http.components uses flama.routing.routes._base, so a change to flama.routing.routes._base can break flama.http.components, while a change to flama.http.components can't break flama.routing.routes._base.
- Position
- Below the diagonal: flama.http.components uses a module listed above it, which is the healthy direction.
32→20 flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.start✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.anthropic.renderer uses a type in flama.models.transport.output.llm.event.start.
- The types involved
flama.models.wire.dialect.llm.anthropic.renderer.AnthropicRenderer→flama.models.transport.output.llm.event.start.StartEvent
- Direction
- flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.start, so a change to flama.models.transport.output.llm.event.start can break flama.models.wire.dialect.llm.anthropic.renderer, while a change to flama.models.wire.dialect.llm.anthropic.renderer can't break flama.models.transport.output.llm.event.start.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.anthropic.renderer uses a module listed above it, which is the healthy direction.
32→21 flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.stop✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.anthropic.renderer uses a type in flama.models.transport.output.llm.event.stop.
- The types involved
flama.models.wire.dialect.llm.anthropic.renderer.AnthropicRenderer→flama.models.transport.output.llm.event.stop.StopEvent
- Direction
- flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.stop, so a change to flama.models.transport.output.llm.event.stop can break flama.models.wire.dialect.llm.anthropic.renderer, while a change to flama.models.wire.dialect.llm.anthropic.renderer can't break flama.models.transport.output.llm.event.stop.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.anthropic.renderer uses a module listed above it, which is the healthy direction.
32→22 flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.text✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.anthropic.renderer uses a type in flama.models.transport.output.llm.event.text.
- The types involved
flama.models.wire.dialect.llm.anthropic.renderer.AnthropicRenderer→flama.models.transport.output.llm.event.text.TextEvent
- Direction
- flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.text, so a change to flama.models.transport.output.llm.event.text can break flama.models.wire.dialect.llm.anthropic.renderer, while a change to flama.models.wire.dialect.llm.anthropic.renderer can't break flama.models.transport.output.llm.event.text.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.anthropic.renderer uses a module listed above it, which is the healthy direction.
32→23 flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.tool✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.anthropic.renderer uses a type in flama.models.transport.output.llm.event.tool.
- The types involved
flama.models.wire.dialect.llm.anthropic.renderer.AnthropicRenderer→flama.models.transport.output.llm.event.tool.ToolEvent
- Direction
- flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.transport.output.llm.event.tool, so a change to flama.models.transport.output.llm.event.tool can break flama.models.wire.dialect.llm.anthropic.renderer, while a change to flama.models.wire.dialect.llm.anthropic.renderer can't break flama.models.transport.output.llm.event.tool.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.anthropic.renderer uses a module listed above it, which is the healthy direction.
32→27 flama.models.wire.dialect.llm.anthropic.renderer uses flama.http.responses.sse✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.anthropic.renderer uses a type in flama.http.responses.sse.
- The types involved
flama.models.wire.dialect.llm.anthropic.renderer.AnthropicRenderer→flama.http.responses.sse.ServerSentEvent
- Direction
- flama.models.wire.dialect.llm.anthropic.renderer uses flama.http.responses.sse, so a change to flama.http.responses.sse can break flama.models.wire.dialect.llm.anthropic.renderer, while a change to flama.models.wire.dialect.llm.anthropic.renderer can't break flama.http.responses.sse.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.anthropic.renderer uses a module listed above it, which is the healthy direction.
32→28 flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.wire.dialect._base✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.anthropic.renderer uses a type in flama.models.wire.dialect._base.
- The types involved
flama.models.wire.dialect.llm.anthropic.renderer.AnthropicRenderer→flama.models.wire.dialect._base.Renderer
- Direction
- flama.models.wire.dialect.llm.anthropic.renderer uses flama.models.wire.dialect._base, so a change to flama.models.wire.dialect._base can break flama.models.wire.dialect.llm.anthropic.renderer, while a change to flama.models.wire.dialect.llm.anthropic.renderer can't break flama.models.wire.dialect._base.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.anthropic.renderer uses a module listed above it, which is the healthy direction.
33→20 flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.start✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.native.renderer uses a type in flama.models.transport.output.llm.event.start.
- The types involved
flama.models.wire.dialect.llm.native.renderer.EventsRenderer→flama.models.transport.output.llm.event.start.StartEvent
- Direction
- flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.start, so a change to flama.models.transport.output.llm.event.start can break flama.models.wire.dialect.llm.native.renderer, while a change to flama.models.wire.dialect.llm.native.renderer can't break flama.models.transport.output.llm.event.start.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.native.renderer uses a module listed above it, which is the healthy direction.
33→21 flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.stop✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.native.renderer uses a type in flama.models.transport.output.llm.event.stop.
- The types involved
flama.models.wire.dialect.llm.native.renderer.EventsRenderer→flama.models.transport.output.llm.event.stop.StopEvent
- Direction
- flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.stop, so a change to flama.models.transport.output.llm.event.stop can break flama.models.wire.dialect.llm.native.renderer, while a change to flama.models.wire.dialect.llm.native.renderer can't break flama.models.transport.output.llm.event.stop.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.native.renderer uses a module listed above it, which is the healthy direction.
33→22 flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.text✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.native.renderer uses a type in flama.models.transport.output.llm.event.text.
- The types involved
flama.models.wire.dialect.llm.native.renderer.EventsRenderer→flama.models.transport.output.llm.event.text.TextEvent
- Direction
- flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.text, so a change to flama.models.transport.output.llm.event.text can break flama.models.wire.dialect.llm.native.renderer, while a change to flama.models.wire.dialect.llm.native.renderer can't break flama.models.transport.output.llm.event.text.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.native.renderer uses a module listed above it, which is the healthy direction.
33→23 flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.tool✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.native.renderer uses a type in flama.models.transport.output.llm.event.tool.
- The types involved
flama.models.wire.dialect.llm.native.renderer.EventsRenderer→flama.models.transport.output.llm.event.tool.ToolEvent
- Direction
- flama.models.wire.dialect.llm.native.renderer uses flama.models.transport.output.llm.event.tool, so a change to flama.models.transport.output.llm.event.tool can break flama.models.wire.dialect.llm.native.renderer, while a change to flama.models.wire.dialect.llm.native.renderer can't break flama.models.transport.output.llm.event.tool.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.native.renderer uses a module listed above it, which is the healthy direction.
33→27 flama.models.wire.dialect.llm.native.renderer uses flama.http.responses.sse✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.native.renderer uses a type in flama.http.responses.sse.
- The types involved
flama.models.wire.dialect.llm.native.renderer.EventsRenderer→flama.http.responses.sse.ServerSentEvent
- Direction
- flama.models.wire.dialect.llm.native.renderer uses flama.http.responses.sse, so a change to flama.http.responses.sse can break flama.models.wire.dialect.llm.native.renderer, while a change to flama.models.wire.dialect.llm.native.renderer can't break flama.http.responses.sse.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.native.renderer uses a module listed above it, which is the healthy direction.
33→28 flama.models.wire.dialect.llm.native.renderer uses flama.models.wire.dialect._base✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.native.renderer uses a type in flama.models.wire.dialect._base.
- The types involved
flama.models.wire.dialect.llm.native.renderer.EventsRenderer→flama.models.wire.dialect._base.Renderer
- Direction
- flama.models.wire.dialect.llm.native.renderer uses flama.models.wire.dialect._base, so a change to flama.models.wire.dialect._base can break flama.models.wire.dialect.llm.native.renderer, while a change to flama.models.wire.dialect.llm.native.renderer can't break flama.models.wire.dialect._base.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.native.renderer uses a module listed above it, which is the healthy direction.
34→20 flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.start✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.ollama.renderer uses a type in flama.models.transport.output.llm.event.start.
- The types involved
flama.models.wire.dialect.llm.ollama.renderer.OllamaRenderer→flama.models.transport.output.llm.event.start.StartEvent
- Direction
- flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.start, so a change to flama.models.transport.output.llm.event.start can break flama.models.wire.dialect.llm.ollama.renderer, while a change to flama.models.wire.dialect.llm.ollama.renderer can't break flama.models.transport.output.llm.event.start.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.ollama.renderer uses a module listed above it, which is the healthy direction.
34→21 flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.stop✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.ollama.renderer uses a type in flama.models.transport.output.llm.event.stop.
- The types involved
flama.models.wire.dialect.llm.ollama.renderer.OllamaRenderer→flama.models.transport.output.llm.event.stop.StopEvent
- Direction
- flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.stop, so a change to flama.models.transport.output.llm.event.stop can break flama.models.wire.dialect.llm.ollama.renderer, while a change to flama.models.wire.dialect.llm.ollama.renderer can't break flama.models.transport.output.llm.event.stop.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.ollama.renderer uses a module listed above it, which is the healthy direction.
34→22 flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.text✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.ollama.renderer uses a type in flama.models.transport.output.llm.event.text.
- The types involved
flama.models.wire.dialect.llm.ollama.renderer.OllamaRenderer→flama.models.transport.output.llm.event.text.TextEvent
- Direction
- flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.text, so a change to flama.models.transport.output.llm.event.text can break flama.models.wire.dialect.llm.ollama.renderer, while a change to flama.models.wire.dialect.llm.ollama.renderer can't break flama.models.transport.output.llm.event.text.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.ollama.renderer uses a module listed above it, which is the healthy direction.
34→23 flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.tool✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.ollama.renderer uses a type in flama.models.transport.output.llm.event.tool.
- The types involved
flama.models.wire.dialect.llm.ollama.renderer.OllamaRenderer→flama.models.transport.output.llm.event.tool.ToolEvent
- Direction
- flama.models.wire.dialect.llm.ollama.renderer uses flama.models.transport.output.llm.event.tool, so a change to flama.models.transport.output.llm.event.tool can break flama.models.wire.dialect.llm.ollama.renderer, while a change to flama.models.wire.dialect.llm.ollama.renderer can't break flama.models.transport.output.llm.event.tool.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.ollama.renderer uses a module listed above it, which is the healthy direction.
34→28 flama.models.wire.dialect.llm.ollama.renderer uses flama.models.wire.dialect._base✕
- Connections
- 1 pair of types, where a type in flama.models.wire.dialect.llm.ollama.renderer uses a type in flama.models.wire.dialect._base.
- The types involved
flama.models.wire.dialect.llm.ollama.renderer.OllamaRenderer→flama.models.wire.dialect._base.Renderer
- Direction
- flama.models.wire.dialect.llm.ollama.renderer uses flama.models.wire.dialect._base, so a change to flama.models.wire.dialect._base can break flama.models.wire.dialect.llm.ollama.renderer, while a change to flama.models.wire.dialect.llm.ollama.renderer can't break flama.models.wire.dialect._base.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.ollama.renderer uses a module listed above it, which is the healthy direction.
35→20 flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.start✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect.llm.openai.renderer uses a type in flama.models.transport.output.llm.event.start.
- The types involved
flama.models.wire.dialect.llm.openai.renderer.OpenAIRenderer→flama.models.transport.output.llm.event.start.StartEventflama.models.wire.dialect.llm.openai.renderer._ChatCompletionRenderer→flama.models.transport.output.llm.event.start.StartEventflama.models.wire.dialect.llm.openai.renderer._MessagesRenderer→flama.models.transport.output.llm.event.start.StartEvent
- Direction
- flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.start, so a change to flama.models.transport.output.llm.event.start can break flama.models.wire.dialect.llm.openai.renderer, while a change to flama.models.wire.dialect.llm.openai.renderer can't break flama.models.transport.output.llm.event.start.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.openai.renderer uses a module listed above it, which is the healthy direction.
35→21 flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.stop✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect.llm.openai.renderer uses a type in flama.models.transport.output.llm.event.stop.
- The types involved
flama.models.wire.dialect.llm.openai.renderer.OpenAIRenderer→flama.models.transport.output.llm.event.stop.StopEventflama.models.wire.dialect.llm.openai.renderer._ChatCompletionRenderer→flama.models.transport.output.llm.event.stop.StopEventflama.models.wire.dialect.llm.openai.renderer._MessagesRenderer→flama.models.transport.output.llm.event.stop.StopEvent
- Direction
- flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.stop, so a change to flama.models.transport.output.llm.event.stop can break flama.models.wire.dialect.llm.openai.renderer, while a change to flama.models.wire.dialect.llm.openai.renderer can't break flama.models.transport.output.llm.event.stop.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.openai.renderer uses a module listed above it, which is the healthy direction.
35→22 flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.text✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect.llm.openai.renderer uses a type in flama.models.transport.output.llm.event.text.
- The types involved
flama.models.wire.dialect.llm.openai.renderer.OpenAIRenderer→flama.models.transport.output.llm.event.text.TextEventflama.models.wire.dialect.llm.openai.renderer._ChatCompletionRenderer→flama.models.transport.output.llm.event.text.TextEventflama.models.wire.dialect.llm.openai.renderer._MessagesRenderer→flama.models.transport.output.llm.event.text.TextEvent
- Direction
- flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.text, so a change to flama.models.transport.output.llm.event.text can break flama.models.wire.dialect.llm.openai.renderer, while a change to flama.models.wire.dialect.llm.openai.renderer can't break flama.models.transport.output.llm.event.text.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.openai.renderer uses a module listed above it, which is the healthy direction.
35→23 flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.tool✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect.llm.openai.renderer uses a type in flama.models.transport.output.llm.event.tool.
- The types involved
flama.models.wire.dialect.llm.openai.renderer.OpenAIRenderer→flama.models.transport.output.llm.event.tool.ToolEventflama.models.wire.dialect.llm.openai.renderer._ChatCompletionRenderer→flama.models.transport.output.llm.event.tool.ToolEventflama.models.wire.dialect.llm.openai.renderer._MessagesRenderer→flama.models.transport.output.llm.event.tool.ToolEvent
- Direction
- flama.models.wire.dialect.llm.openai.renderer uses flama.models.transport.output.llm.event.tool, so a change to flama.models.transport.output.llm.event.tool can break flama.models.wire.dialect.llm.openai.renderer, while a change to flama.models.wire.dialect.llm.openai.renderer can't break flama.models.transport.output.llm.event.tool.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.openai.renderer uses a module listed above it, which is the healthy direction.
35→27 flama.models.wire.dialect.llm.openai.renderer uses flama.http.responses.sse✕
- Connections
- 2 pairs of types, where a type in flama.models.wire.dialect.llm.openai.renderer uses a type in flama.http.responses.sse.
- The types involved
flama.models.wire.dialect.llm.openai.renderer._ChatCompletionRenderer→flama.http.responses.sse.ServerSentEventflama.models.wire.dialect.llm.openai.renderer._MessagesRenderer→flama.http.responses.sse.ServerSentEvent
- Direction
- flama.models.wire.dialect.llm.openai.renderer uses flama.http.responses.sse, so a change to flama.http.responses.sse can break flama.models.wire.dialect.llm.openai.renderer, while a change to flama.models.wire.dialect.llm.openai.renderer can't break flama.http.responses.sse.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.openai.renderer uses a module listed above it, which is the healthy direction.
35→28 flama.models.wire.dialect.llm.openai.renderer uses flama.models.wire.dialect._base✕
- Connections
- 3 pairs of types, where a type in flama.models.wire.dialect.llm.openai.renderer uses a type in flama.models.wire.dialect._base.
- The types involved
flama.models.wire.dialect.llm.openai.renderer.OpenAIRenderer→flama.models.wire.dialect._base.Rendererflama.models.wire.dialect.llm.openai.renderer._ChatCompletionRenderer→flama.models.wire.dialect._base.Rendererflama.models.wire.dialect.llm.openai.renderer._MessagesRenderer→flama.models.wire.dialect._base.Renderer
- Direction
- flama.models.wire.dialect.llm.openai.renderer uses flama.models.wire.dialect._base, so a change to flama.models.wire.dialect._base can break flama.models.wire.dialect.llm.openai.renderer, while a change to flama.models.wire.dialect.llm.openai.renderer can't break flama.models.wire.dialect._base.
- Position
- Below the diagonal: flama.models.wire.dialect.llm.openai.renderer uses a module listed above it, which is the healthy direction.
36→9 flama.routing.routes.mount uses flama.types.asgi✕
- Connections
- 3 pairs of types, where a type in flama.routing.routes.mount uses a type in flama.types.asgi.
- The types involved
flama.routing.routes.mount.Mount→flama.types.asgi.Receiveflama.routing.routes.mount.Mount→flama.types.asgi.Scopeflama.routing.routes.mount.Mount→flama.types.asgi.Send
- Direction
- flama.routing.routes.mount uses flama.types.asgi, so a change to flama.types.asgi can break flama.routing.routes.mount, while a change to flama.routing.routes.mount can't break flama.types.asgi.
- Position
- Below the diagonal: flama.routing.routes.mount uses a module listed above it, which is the healthy direction.
36→10 flama.routing.routes.mount uses flama.url✕
- Connections
- 1 pair of types, where a type in flama.routing.routes.mount uses a type in flama.url.
- The types involved
flama.routing.routes.mount.Mount→flama.url.URL
- Direction
- flama.routing.routes.mount uses flama.url, so a change to flama.url can break flama.routing.routes.mount, while a change to flama.routing.routes.mount can't break flama.url.
- Position
- Below the diagonal: flama.routing.routes.mount uses a module listed above it, which is the healthy direction.
36→24 flama.routing.routes.mount uses flama.types.applications✕
- Connections
- 1 pair of types, where a type in flama.routing.routes.mount uses a type in flama.types.applications.
- The types involved
flama.routing.routes.mount.Mount→flama.types.applications.App
- Direction
- flama.routing.routes.mount uses flama.types.applications, so a change to flama.types.applications can break flama.routing.routes.mount, while a change to flama.routing.routes.mount can't break flama.types.applications.
- Position
- Below the diagonal: flama.routing.routes.mount uses a module listed above it, which is the healthy direction.
36→30 flama.routing.routes.mount uses flama.routing.routes._base✕
- Connections
- 2 pairs of types, where a type in flama.routing.routes.mount uses a type in flama.routing.routes._base.
- The types involved
flama.routing.routes.mount.Mount→flama.routing.routes._base.Matchflama.routing.routes.mount.Mount→flama.routing.routes._base.RouteTableParams
- Direction
- flama.routing.routes.mount uses flama.routing.routes._base, so a change to flama.routing.routes._base can break flama.routing.routes.mount, while a change to flama.routing.routes.mount can't break flama.routing.routes._base.
- Position
- Below the diagonal: flama.routing.routes.mount uses a module listed above it, which is the healthy direction.
37→4 flama.schemas.components uses flama.http.data_structures✕
- Connections
- 2 pairs of types, where a type in flama.schemas.components uses a type in flama.http.data_structures.
- The types involved
flama.schemas.components.FileParamComponent→flama.http.data_structures.UploadFileflama.schemas.components.ValidateQueryParamsComponent→flama.http.data_structures.QueryParams
- Direction
- flama.schemas.components uses flama.http.data_structures, so a change to flama.http.data_structures can break flama.schemas.components, while a change to flama.schemas.components can't break flama.http.data_structures.
- Position
- Below the diagonal: flama.schemas.components uses a module listed above it, which is the healthy direction.
37→5 flama.schemas.components uses flama.injection.components✕
- Connections
- 8 pairs of types, where a type in flama.schemas.components uses a type in flama.injection.components.
- The types involved
flama.schemas.components.CompositeParamComponent→flama.injection.components.Componentflama.schemas.components.FileParamComponent→flama.injection.components.Componentflama.schemas.components.PrimitiveParamComponent→flama.injection.components.Componentflama.schemas.components.RequestDataComponent→flama.injection.components.Componentflama.schemas.components.ValidatePathParamsComponent→flama.injection.components.Componentflama.schemas.components.ValidateQueryParamsComponent→flama.injection.components.Componentflama.schemas.components.ValidateRequestDataComponent→flama.injection.components.Componentflama.schemas.components.WebSocketMessageDataComponent→flama.injection.components.Component
- Direction
- flama.schemas.components uses flama.injection.components, so a change to flama.injection.components can break flama.schemas.components, while a change to flama.schemas.components can't break flama.injection.components.
- Position
- Below the diagonal: flama.schemas.components uses a module listed above it, which is the healthy direction.
37→9 flama.schemas.components uses flama.types.asgi✕
- Connections
- 1 pair of types, where a type in flama.schemas.components uses a type in flama.types.asgi.
- The types involved
flama.schemas.components.WebSocketMessageDataComponent→flama.types.asgi.Message
- Direction
- flama.schemas.components uses flama.types.asgi, so a change to flama.types.asgi can break flama.schemas.components, while a change to flama.schemas.components can't break flama.types.asgi.
- Position
- Below the diagonal: flama.schemas.components uses a module listed above it, which is the healthy direction.
37→15 flama.schemas.components uses flama.http.requests.http✕
- Connections
- 5 pairs of types, where a type in flama.schemas.components uses a type in flama.http.requests.http.
- The types involved
flama.schemas.components.CompositeParamComponent→flama.http.requests.http.Requestflama.schemas.components.RequestDataComponent→flama.http.requests.http.Requestflama.schemas.components.ValidatePathParamsComponent→flama.http.requests.http.Requestflama.schemas.components.ValidateQueryParamsComponent→flama.http.requests.http.Requestflama.schemas.components.ValidateRequestDataComponent→flama.http.requests.http.Request
- Direction
- flama.schemas.components uses flama.http.requests.http, so a change to flama.http.requests.http can break flama.schemas.components, while a change to flama.schemas.components can't break flama.http.requests.http.
- Position
- Below the diagonal: flama.schemas.components uses a module listed above it, which is the healthy direction.
37→30 flama.schemas.components uses flama.routing.routes._base✕
- Connections
- 4 pairs of types, where a type in flama.schemas.components uses a type in flama.routing.routes._base.
- The types involved
flama.schemas.components.CompositeParamComponent→flama.routing.routes._base.BaseRouteflama.schemas.components.ValidatePathParamsComponent→flama.routing.routes._base.BaseRouteflama.schemas.components.ValidateQueryParamsComponent→flama.routing.routes._base.BaseRouteflama.schemas.components.ValidateRequestDataComponent→flama.routing.routes._base.BaseRoute
- Direction
- flama.schemas.components uses flama.routing.routes._base, so a change to flama.routing.routes._base can break flama.schemas.components, while a change to flama.schemas.components can't break flama.routing.routes._base.
- Position
- Below the diagonal: flama.schemas.components uses a module listed above it, which is the healthy direction.
38→29 flama.schemas.modules uses flama.modules✕
- Connections
- 1 pair of types, where a type in flama.schemas.modules uses a type in flama.modules.
- The types involved
flama.schemas.modules.SchemaModule→flama.modules.Module
- Direction
- flama.schemas.modules uses flama.modules, so a change to flama.modules can break flama.schemas.modules, while a change to flama.schemas.modules can't break flama.modules.
- Position
- Below the diagonal: flama.schemas.modules uses a module listed above it, which is the healthy direction.
39→5 flama.applications uses flama.injection.components✕
- Connections
- 2 pairs of types, where a type in flama.applications uses a type in flama.injection.components.
- The types involved
flama.applications.Flama→flama.injection.components.Componentflama.applications.Flama→flama.injection.components.Components
- Direction
- flama.applications uses flama.injection.components, so a change to flama.injection.components can break flama.applications, while a change to flama.applications can't break flama.injection.components.
- Position
- Below the diagonal: flama.applications uses a module listed above it, which is the healthy direction.
39→9 flama.applications uses flama.types.asgi✕
- Connections
- 3 pairs of types, where a type in flama.applications uses a type in flama.types.asgi.
- The types involved
flama.applications.Flama→flama.types.asgi.Receiveflama.applications.Flama→flama.types.asgi.Scopeflama.applications.Flama→flama.types.asgi.Send
- Direction
- flama.applications uses flama.types.asgi, so a change to flama.types.asgi can break flama.applications, while a change to flama.applications can't break flama.types.asgi.
- Position
- Below the diagonal: flama.applications uses a module listed above it, which is the healthy direction.
39→10 flama.applications uses flama.url✕
- Connections
- 1 pair of types, where a type in flama.applications uses a type in flama.url.
- The types involved
flama.applications.Flama→flama.url.URL
- Direction
- flama.applications uses flama.url, so a change to flama.url can break flama.applications, while a change to flama.applications can't break flama.url.
- Position
- Below the diagonal: flama.applications uses a module listed above it, which is the healthy direction.
39→24 flama.applications uses flama.types.applications✕
- Connections
- 2 pairs of types, where a type in flama.applications uses a type in flama.types.applications.
- The types involved
flama.applications.Flama→flama.types.applications.Appflama.applications.Flama→flama.types.applications.AppStatus
- Direction
- flama.applications uses flama.types.applications, so a change to flama.types.applications can break flama.applications, while a change to flama.applications can't break flama.types.applications.
- Position
- Below the diagonal: flama.applications uses a module listed above it, which is the healthy direction.
39→36 flama.applications uses flama.routing.routes.mount✕
- Connections
- 1 pair of types, where a type in flama.applications uses a type in flama.routing.routes.mount.
- The types involved
flama.applications.Flama→flama.routing.routes.mount.Mount
- Direction
- flama.applications uses flama.routing.routes.mount, so a change to flama.routing.routes.mount can break flama.applications, while a change to flama.applications can't break flama.routing.routes.mount.
- Position
- Below the diagonal: flama.applications uses a module listed above it, which is the healthy direction.
39→38 flama.applications uses flama.schemas.modules✕
- Connections
- 1 pair of types, where a type in flama.applications uses a type in flama.schemas.modules.
- The types involved
flama.applications.Flama→flama.schemas.modules.SchemaModule
- Direction
- flama.applications uses flama.schemas.modules, so a change to flama.schemas.modules can break flama.applications, while a change to flama.applications can't break flama.schemas.modules.
- Position
- Below the diagonal: flama.applications uses a module listed above it, which is the healthy direction.
40→5 flama.routing.router uses flama.injection.components✕
- Connections
- 1 pair of types, where a type in flama.routing.router uses a type in flama.injection.components.
- The types involved
flama.routing.router.Router→flama.injection.components.Component
- Direction
- flama.routing.router uses flama.injection.components, so a change to flama.injection.components can break flama.routing.router, while a change to flama.routing.router can't break flama.injection.components.
- Position
- Below the diagonal: flama.routing.router uses a module listed above it, which is the healthy direction.
40→9 flama.routing.router uses flama.types.asgi✕
- Connections
- 3 pairs of types, where a type in flama.routing.router uses a type in flama.types.asgi.
- The types involved
flama.routing.router.Router→flama.types.asgi.Receiveflama.routing.router.Router→flama.types.asgi.Scopeflama.routing.router.Router→flama.types.asgi.Send
- Direction
- flama.routing.router uses flama.types.asgi, so a change to flama.types.asgi can break flama.routing.router, while a change to flama.routing.router can't break flama.types.asgi.
- Position
- Below the diagonal: flama.routing.router uses a module listed above it, which is the healthy direction.
40→10 flama.routing.router uses flama.url✕
- Connections
- 1 pair of types, where a type in flama.routing.router uses a type in flama.url.
- The types involved
flama.routing.router.Router→flama.url.URL
- Direction
- flama.routing.router uses flama.url, so a change to flama.url can break flama.routing.router, while a change to flama.routing.router can't break flama.url.
- Position
- Below the diagonal: flama.routing.router uses a module listed above it, which is the healthy direction.
40→24 flama.routing.router uses flama.types.applications✕
- Connections
- 1 pair of types, where a type in flama.routing.router uses a type in flama.types.applications.
- The types involved
flama.routing.router.Router→flama.types.applications.App
- Direction
- flama.routing.router uses flama.types.applications, so a change to flama.types.applications can break flama.routing.router, while a change to flama.routing.router can't break flama.types.applications.
- Position
- Below the diagonal: flama.routing.router uses a module listed above it, which is the healthy direction.
40→30 flama.routing.router uses flama.routing.routes._base✕
- Connections
- 1 pair of types, where a type in flama.routing.router uses a type in flama.routing.routes._base.
- The types involved
flama.routing.router.Router→flama.routing.routes._base.BaseRoute
- Direction
- flama.routing.router uses flama.routing.routes._base, so a change to flama.routing.routes._base can break flama.routing.router, while a change to flama.routing.router can't break flama.routing.routes._base.
- Position
- Below the diagonal: flama.routing.router uses a module listed above it, which is the healthy direction.
40→36 flama.routing.router uses flama.routing.routes.mount✕
- Connections
- 1 pair of types, where a type in flama.routing.router uses a type in flama.routing.routes.mount.
- The types involved
flama.routing.router.Router→flama.routing.routes.mount.Mount
- Direction
- flama.routing.router uses flama.routing.routes.mount, so a change to flama.routing.routes.mount can break flama.routing.router, while a change to flama.routing.router can't break flama.routing.routes.mount.
- Position
- Below the diagonal: flama.routing.router uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 37 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | Medium |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 1 No ADRs found finding(s) in ADR Quality; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +7.4 pts | Medium | Keyboard semantics |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.6 pts | Low | ADR Quality |
| 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. | +3.6 pts | Medium | Architecture documentation |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +3.3 pts | Medium | A11y enforcement |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.9 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.2 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.7 pts | Medium | Forms & labels |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.7 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| flama/pagination/paginators/limit_offset.py | 7.0 | Mixed | Code Duplication: Duplicated block (26 lines × 2) |
| flama/models/wire/dialect/llm/anthropic/parser.py | 7.1 | Mixed | Cyclomatic Complexity: AnthropicParser._expand_assistant (cyclomatic 17) |
| flama/schemas/openapi.py | 7.2 | Mixed | Cognitive Complexity: SchemaGenerator.get_endpoints (cognitive 28) |
| flama/serialize/serializer.py | 7.2 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| flama/models/resources/serving/llm/anthropic.py | 7.2 | Mixed | Code Duplication: Duplicated block (28–30 lines × 3) |
| flama/models/resources/serving/llm/openai.py | 7.2 | Mixed | Code Duplication: Duplicated block (13 lines × 2) |
| flama/models/resources/serving/llm/ollama.py | 7.2 | Mixed | Code Duplication: Duplicated block (11–12 lines × 2) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| flama/models/wire/dialect/_base.py | 7.8 | Mixed | Cyclomatic Complexity: Parser._parse_message (cyclomatic 22) |
| lib/core/src/json_encoder.rs | 7.8 | Mixed | Cyclomatic Complexity: JsonEncoder::encode_special (cyclomatic 22) |
| lib/templates/src/apps/chatbot/components/conversation/Conversation.tsx | 7.8 | Mixed | Cyclomatic Complexity: Conversation.Conversation (cyclomatic 21) |
| lib/templates/src/apps/chatbot/context/chat/reducer.ts | 7.8 | Mixed | Cyclomatic Complexity: reducer.reducer (cyclomatic 19) |
| lib/core/src/url.rs | 7.8 | Mixed | Cyclomatic Complexity: PathMatcher::match_path_raw (cyclomatic 17) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 80 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, 176 of 191 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py, .rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`, or lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`, or lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py, .rs) and this repository declares a Python test suite (repository root, 201 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python REDACTED/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (8 contributor(s) across 693 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 7 hold 1.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `flama/models/engine/llm/decoder/parsers.py` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in flama/injection/injector.py, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — [0m - InvalidDefaultArgInFrom: Default value for ARG python:${PYTHON_VERSION}-slim results in empty or invalid base image name (line 3) REDACTED:3 -------------------- 1 | ARG PYTHON_VERSION 2 | 3 | >>> FROM python:${PYTHON_VERSION}-slim 4 | 5 | ARG SCHEMAS_LIB -------------------- ERROR: failed to solve: failed to parse stage name "python:-slim": invalid reference format; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C3 Audit Trail — 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. 'sqlalchemy' is imported (flama/sqlalchemy.py:9), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'sqlalchemy' is imported (flama/sqlalchemy.py:9), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'sqlalchemy' is imported (flama/sqlalchemy.py:9), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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 this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Parser._parse_message at 22.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Parser._parse_message (cyclomatic 22), JsonEncoder::encode_special (cyclomatic 22), Conversation.Conversation (cyclomatic 21). — 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 9 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
25 method(s) exceeded the cognitive complexity threshold of 15; the worst was PathMatcher::match_path_raw at 29.
What to do
- Bring the 25 bodies over 15 down to 15 or less in Cognitive Complexity — start with PathMatcher::match_path_raw (cognitive 29), SchemaGenerator.get_endpoints (cognitive 28), JsonEncoder::encode_special (cognitive 25). — 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 25 together lifts Cognitive Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with openapi.py. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
30 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.
What to do
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with parser.py, adapter.py, v1.py. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with parser.py, serializer.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with http.py, serializer.py. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
3 production modules (Cargo+npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 122 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with mount.py. — One of this dimension's main actionable groups (1 warning-level).
D9 · Test Distribution
1976 test methods: 1976 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 55 `#[test]` function(s) across 8 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 1921 test function(s) across 201 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D12 · Dependency Hygiene
1 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 102 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python REDACTED/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 36619 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 35 judged comments only repeat the code they sit on (0.0 %).
D26 · Project Cohesion
1 of 3 build units (Cargo, npm) 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
57 % of calls cross a namespace and 0 % go through an interface, but 39 % 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)
9 finding(s): 0 critical, 3 high, 6 medium, 0 low. semgrep hit a parse error in 1 file(s) — `flama/models/engine/llm/decoder/parsers.py` (lines 296–334, lines 344–347) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
34 finding(s): 4 critical, 17 high, 8 medium, 5 low.
What to do
- Resolve the 17 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
3 finding(s): 0 critical, 0 high, 2 medium, 1 low.
What to do
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
1 of 178 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is flama/ddd/repositories/http.py. Counted over 178 of the 401 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: limit_offset.py↔page_number.py 83%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with limit_offset.py. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 2 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
AC2 · Forms & labels
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — lib/templates/src/apps/chatbot/components/PromptInput.tsx:61
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — lib/templates/src/pages/chatbot/chat.html:2, lib/templates/src/pages/debug/error_404.html:2, lib/templates/src/pages/debug/error_500.html:2, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — lib/templates/src/apps/debug/components/ErrorTraceback.tsx:81, lib/templates/src/apps/debug/components/URLTree.tsx:60, lib/templates/src/ui/components/Menu.tsx:38
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — lib/templates/src/ui/components/Menu.tsx:92
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.prompt-field :has(> label > textarea)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — lib/templates/src/apps/chatbot/styles/chat.css:12
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 38 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — lib/templates/package.json:16
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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
AX9 · CQS / query purity
C2 · Access Controls
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 2 of 2 have no README of their own, in their folder or in their family's project (`lib/core`, `lib/templates`).
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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add 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 5 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. — .github/workflows/ci_pull_request.yaml: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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- lib/templates/src/apps/chatbot/components/message/Thought.tsx:9 · lib/templates/src/apps/chatbot/components/message/Tool.tsx:8 — the two spans are one implementation copied and then locally edited — 283 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/templates/src/apps/chatbot/components/message/Thought.tsx:9
- lib/templates/src/apps/debug/error_404.tsx:19 · lib/templates/src/apps/debug/error_500.tsx:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/templates/src/apps/debug/error_404.tsx:19
- lib/templates/src/apps/chatbot/context/chat/useChat.ts:50 · lib/templates/src/apps/chatbot/context/chat/useChat.ts:68 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — lib/templates/src/apps/chatbot/context/chat/useChat.ts:50
- lib/templates/src/apps/debug/components/URLTree.tsx:85 · lib/templates/src/apps/debug/components/URLTree.tsx:93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — lib/templates/src/apps/debug/components/URLTree.tsx:85
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- reducer has cyclomatic complexity 14 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/templates/src/apps/chatbot/context/chat/reducer.ts:75
- buildBlock has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/templates/src/apps/chatbot/context/chat/reducer.ts:28
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
R6 · Tooling
- test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) as package.json scripts and run them in CI.
R7 · Dead Code
- 2 file(s) (~66 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
R8 · Dependency Hygiene
- Declared in lib/templates/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `header_size` is read from the bytes being parsed at line 256 (`struct.unpack("<Q")`), then passed as the size of `read` at line 257 — and nowhere in its function is `header_size` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: the call reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB (a 64-bit one for more than any machine has), and the reservation either raises `MemoryError` out of a parser whose failure path was written for malformed input, not for hostile input, or succeeds and holds gigabytes for a few bytes on the wire. Bound `header_size` against the bytes actually remaining and a maximum the format allows before reading. — flama/serialize/model_serializers/transformers.py:257
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `to_dict` is public and takes `obj: t.Any` from its caller, and it calls itself at line 439 (`self.to_dict`) with a piece of `obj` (and at line 442) — and nowhere in `to_dict` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `to_dict` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — flama/schemas/openapi.py:439
- `from_app` is public and takes `app: t.Any` from its caller, and it calls itself at line 163 (`self.from_app`) with a piece of `app` — and nowhere in `from_app` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `from_app` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — flama/debug/data_structures.py:163
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
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
- `svg` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:92
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. (×4) — lib/templates/src/apps/chatbot/context/chat/parseEvent.ts:32, REDACTED:76, flama/concurrency.py:328, …
- `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. (×24) — flama/telemetry/data_structures.py:87, flama/telemetry/data_structures.py:92, flama/serialize/model_serializers/pytorch.py:14, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 68% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 69% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 87% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 39% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'sqlalchemy' (flama/sqlalchemy.py:9) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and MongoEngine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'sqlalchemy' (flama/sqlalchemy.py:9) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, SQL schemas). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'sqlalchemy' (flama/sqlalchemy.py:9) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 46 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — [0m - InvalidDefaultArgInFrom: Default value for ARG python:${PYTHON_VERSION}-slim results in empty or invalid base image name (line 3) REDACTED:3 -------------------- 1 | ARG PYTHON_VERSION 2 | 3 | >>> FROM python:${PYTHON_VERSION}-slim 4 | 5 | ARG SCHEMAS_LIB -------------------- ERROR: failed to solve: failed to parse stage name "python:-slim": invalid reference format; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~44728 lines of test source are present (.py, .rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .py suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python, Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (flama), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 5 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 223 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- 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'.
- P8 Schema migrations — SQLAlchemy is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (45 production file(s)) has no JavaScript/TypeScript test, but it is 5.57% of this repository's production source and the other 94.43% carries 44,728 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were 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; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <li> lib/templates/src/apps/debug/components/ErrorTraceback.tsx:81
- Click handler on a non-interactive <li> lib/templates/src/ui/components/Menu.tsx:38
- Click handler on a non-interactive <div> lib/templates/src/apps/debug/components/URLTree.tsx:60
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 135 finding(s)
- Swallowed exception (caught, then discarded) flama/telemetry/data_structures.py:87
- Swallowed exception (caught, then discarded) flama/telemetry/data_structures.py:92
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/pytorch.py:14
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/tensorflow.py:14
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/tensorflow.py:19
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/transformers.py:23
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/transformers.py:301
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/transformers.py:324
- Swallowed exception (caught, then discarded) flama/serialize/model_serializers/transformers.py:335
- Swallowed exception (caught, then discarded) flama/routing/routes/http.py:36
- Swallowed exception (caught, then discarded) flama/resources/data_structures.py:10
- Swallowed exception (caught, then discarded) flama/models/_base.py:247
- Swallowed exception (caught, then discarded) REDACTED:416
- Swallowed exception (caught, then discarded) flama/models/engine/backend/ml/pytorch.py:8
- Swallowed exception (caught, then discarded) flama/models/engine/backend/ml/sklearn.py:8
- Swallowed exception (caught, then discarded) flama/models/engine/backend/ml/tensorflow.py:8
- Swallowed exception (caught, then discarded) flama/models/engine/backend/ml/tensorflow.py:13
- Swallowed exception (caught, then discarded) flama/models/engine/backend/ml/transformers.py:8
- Swallowed exception (caught, then discarded) flama/models/engine/backend/llm/_base.py:616
- Swallowed exception (caught, then discarded) flama/models/engine/backend/llm/mlx.py:22
- Swallowed exception (caught, then discarded) flama/models/engine/backend/llm/mlx.py:31
- Swallowed exception (caught, then discarded) flama/models/engine/backend/llm/vllm.py:18
- Swallowed exception (caught, then discarded) flama/models/engine/backend/llm/vllm.py:133
- Swallowed exception (caught, then discarded) flama/ddd/workers/_base.py:115
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark lib/templates/src/pages/chatbot/chat.html:2
- Page without a main landmark lib/templates/src/pages/debug/error_404.html:2
- Page without a main landmark lib/templates/src/pages/debug/error_500.html:2
- Page without a main landmark lib/templates/src/pages/schemas/docs.html:2
- Swallowed exception (empty catch) lib/templates/src/apps/chatbot/context/chat/parseEvent.ts:32
- Swallowed exception (empty catch) REDACTED:76
- Swallowed exception (empty catch) flama/concurrency.py:328
- Swallowed exception (empty catch) flama/serialize/model_serializers/tensorflow.py:63
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) flama/models/wire/dialect/llm/anthropic/parser.py:160
- Duplicated block (5 lines × 2) flama/schemas/_libs/marshmallow/adapter.py:121
- Duplicated block (5 lines × 2) flama/serialize/protocols/v1.py:257
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) flama/models/wire/dialect/llm/anthropic/parser.py:114
- Members sharing a duplicated core (4 members, 50+ identical tokens) flama/serialize/serializer.py:147
- Duplicated block (17 lines × 2) flama/routing/routes/http.py:59
- Duplicated block (17 lines × 2) flama/serialize/serializer.py:315
- Duplicated block (10 lines × 4) flama/models/resources/serving/llm/anthropic.py:62
- Duplicated block (10 lines × 4) flama/models/wire/dialect/llm/anthropic/parser.py:114
- Duplicated block (10 lines × 2) flama/models/resources/serving/llm/ollama.py:51
- Duplicated block (10 lines × 2) flama/models/resources/serving/llm/ollama.py:177
- Duplicated block (9 lines × 2) flama/models/resources/llm.py:113
- Duplicated block (9 lines × 2) flama/models/resources/serving/llm/ollama.py:94
- Duplicated block (7 lines × 2) flama/ddd/repositories/http.py:184
- Duplicated block (7 lines × 2) flama/models/streams.py:312
- Duplicated block (6 lines × 2) flama/models/resources/serving/llm/openai.py:126
- Duplicated block (6 lines × 2) flama/resources/crud.py:323
- Recursive walk over a caller-supplied document has no depth cap flama/schemas/openapi.py:439
- Recursive walk over a caller-supplied document has no depth cap flama/debug/data_structures.py:163
- <TextArea> field component without a label lib/templates/src/apps/chatbot/components/PromptInput.tsx:61
- Modal dialog does not manage focus lib/templates/src/ui/components/Menu.tsx:92
- Focus outline removed in CSS without a :focus replacement lib/templates/src/apps/chatbot/styles/chat.css:12
- Accessibility enforcement below the top rung lib/templates/package.json:16
- Parser._parse_message (cyclomatic 22) flama/models/wire/dialect/_base.py:134
- JsonEncoder::encode_special (cyclomatic 22) lib/core/src/json_encoder.rs:266
- Conversation.Conversation (cyclomatic 21) lib/templates/src/apps/chatbot/components/conversation/Conversation.tsx:23
- reducer.reducer (cyclomatic 19) lib/templates/src/apps/chatbot/context/chat/reducer.ts:75
- AnthropicParser._expand_assistant (cyclomatic 17) flama/models/wire/dialect/llm/anthropic/parser.py:206
- PathMatcher::match_path_raw (cyclomatic 17) lib/core/src/url.rs:73
- AnthropicAssembler.envelope (cyclomatic 16) flama/models/wire/dialect/llm/anthropic/assembler.py:45
- NativeParser._parse_part (cyclomatic 16) flama/models/wire/dialect/llm/native/parser.py:31
- ModelSerializer.detect_capabilities (cyclomatic 16) flama/serialize/model_serializers/transformers.py:121
- PathMatcher::match_path_raw (cognitive 29) lib/core/src/url.rs:73
- SchemaGenerator.get_endpoints (cognitive 28) flama/schemas/openapi.py:633
- JsonEncoder::encode_special (cognitive 25) lib/core/src/json_encoder.rs:266
- MLXBackend.generate (cognitive 24) flama/models/engine/backend/llm/mlx.py:276
- Parser._parse_message (cognitive 24) flama/models/wire/dialect/_base.py:134
- AnthropicParser._parse_part (cognitive 22) flama/models/wire/dialect/llm/anthropic/parser.py:113
- Conversation.Conversation (cognitive 22) lib/templates/src/apps/chatbot/components/conversation/Conversation.tsx:23
- AnthropicAssembler.envelope (cognitive 21) flama/models/wire/dialect/llm/anthropic/assembler.py:45
- RouteTable::resolve_inner (cognitive 20) lib/core/src/route_table.rs:57
- WorkerType.__new__ (cognitive 19) flama/ddd/workers/_base.py:103
- TransformerLLMBackend.prepare_input (cognitive 19) flama/models/engine/backend/llm/_base.py:538
- ModelSerializer.detect_capabilities (cognitive 19) flama/serialize/model_serializers/transformers.py:121
- Decoder._iter_marker_bodies (cognitive 18) flama/models/engine/llm/decoder/decoder.py:267
- Filters.build (cognitive 18) flama/resources/filtering.py:170
- reducer.reducer (cognitive 18) lib/templates/src/apps/chatbot/context/chat/reducer.ts:75
- Message.AssistantMessage (cognitive 18) lib/templates/src/apps/chatbot/components/message/Message.tsx:19
- EventBuffer.__anext__ (cognitive 17) flama/models/transport/output/llm/buffer.py:84
- ResourceType._get_attribute (cognitive 17) flama/resources/resource.py:51
- OpenAPISchemaRegistry._get_schema_references_from_schema (cognitive 17) flama/schemas/openapi.py:453
- flama_core::multipart::drain_field (cognitive 17) lib/core/src/multipart.rs:173
- AnthropicParser._expand_assistant (cognitive 16) flama/models/wire/dialect/llm/anthropic/parser.py:206
- OpenAIParser._parse_part (cognitive 16) flama/models/wire/dialect/llm/openai/parser.py:30
- Parameter.__post_init__ (cognitive 16) flama/schemas/data_structures.py:272
- OpenAPISchemaRegistry._get_schema_references_from_operation_request_body (cognitive 16) flama/schemas/openapi.py:528
- Path.__init__ (cognitive 16) flama/url.py:186
- REDACTED
- FileTooLong: schemas/openapi.py flama/schemas/openapi.py
- Change coupling: limit_offset.py ↔ page_number.py flama/pagination/paginators/limit_offset.py:1
- Duplicated block (37–42 lines × 2) flama/models/_base.py:380
- Duplicated block (28–30 lines × 3) flama/models/resources/serving/llm/anthropic.py:180
- Duplicated block (26 lines × 2) flama/pagination/paginators/limit_offset.py:110
- Duplicated block (20–22 lines × 2) flama/models/wire/dialect/llm/openai/assembler.py:78
- Duplicated block (16 lines × 3) flama/models/resources/serving/llm/anthropic.py:95
- Duplicated block (16 lines × 2) flama/models/wire/dialect/llm/native/parser.py:34
- Duplicated block (14 lines × 3) flama/serialize/serializer.py:238
- Duplicated block (13 lines × 3) flama/models/resources/serving/llm/anthropic.py:56
- Duplicated block (13 lines × 2) flama/models/resources/serving/llm/openai.py:130
- Duplicated block (12 lines × 2) flama/models/resources/llm.py:48
- Duplicated block (11–12 lines × 2) flama/models/resources/serving/llm/ollama.py:196
- Duplicated block (10 lines × 3) flama/models/resources/serving/llm/openai.py:45
- Duplicated block (9 lines × 4) flama/serialize/serializer.py:178
- Duplicated block (9 lines × 3) flama/models/resources/serving/llm/openai.py:88
- Duplicated block (8 lines × 2) flama/ddd/repositories/http.py:77
- Low cohesion: Mount (LCOM4 4) flama/routing/routes/mount.py:12
- Duplicated block with local edits (39 matched lines × 2 locations) lib/templates/src/apps/chatbot/components/message/Thought.tsx:9
- Duplicated block (23 lines × 2 locations) lib/templates/src/apps/debug/error_404.tsx:19
- Duplicated block with local edits (9 matched lines × 2 locations) lib/templates/src/apps/chatbot/context/chat/useChat.ts:50
- Duplicated block (8 lines × 2 locations) lib/templates/src/apps/debug/components/URLTree.tsx:85
- Complex function reducer (cyclomatic 14, cognitive 9) lib/templates/src/apps/chatbot/context/chat/reducer.ts:75
- Complex function buildBlock (cyclomatic 11, cognitive 13) lib/templates/src/apps/chatbot/context/chat/reducer.ts:28
- No test script
- Unused dependency '@heroicons/react'
- Unused dependency 'core-js'
- Unused dependency 'cssnano'
- Length read from the parsed input is spent without ever being bounded flama/serialize/model_serializers/transformers.py:257
- Untrusted text written into markup unescaped REDACTED:92
Minor — 28 finding(s)
- Duplicated predicate lib/templates/src/apps/chatbot/components/message/Message.tsx:27
- Duplicated predicate flama/models/wire/dialect/llm/native/renderer.py:144
- Duplicated predicate flama/schemas/_libs/marshmallow/adapter.py:175
- Duplicated predicate flama/schemas/_libs/marshmallow/adapter.py:172
- Duplicated predicate flama/models/wire/dialect/llm/ollama/assembler.py:86
- Duplicated predicate flama/routing/routes/http.py:131
- Duplicated predicate flama/models/wire/dialect/llm/native/parser.py:48
- Duplicated predicate flama/_upgrade/operations/calls.py:125
- Duplicated predicate flama/models/wire/dialect/llm/anthropic/parser.py:114
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- Projects may be oversized for their cohesion
- Scattered collaborators
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file flama/ddd/repositories/http.py:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST .github/workflows/ci_pull_request.yaml:4
- Strict null checking is not enabled everywhere the repository type-checks
- Silent fallback default on parse failure flama/mcp/data_structures.py:162
Minor — 1 finding(s)
- Outdated: flate2
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-39db70f2b27b445ca5345cff58d9e2df/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-39db70f2b27b445ca5345cff58d9e2df/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 . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 34 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `flama/models/engine/llm/decoder/parsers.py` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |