Executive summary
run-llama/llama-agents is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 58 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 53, is the weakest lens, level with Production Readiness, and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 5 points. Automating accessibility checks would lift Accessibility itself, worth about 3 points. Raising Accessibility to 70 would lift the score to about 62.
Forty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten settings leave the servers or containers unsafe, and six weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, correcting the unsafe settings and fixing the weaknesses the scanner points to would close these risks. Updating the vulnerable packages would fix the five packages with a known security hole, and limiting each secret to its own step would deal with the three secrets exposed to more of the pipeline than needed. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 51,104 lines, about €110,000 to rebuild.
If Accessibility rose from 53 to 70, the lowest score rated Strong, the score would rise from 58 to about 62.
New since the last survey: 4 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Forms & labels · <ThemeSelect> field component without a label docs/src/components/Header.astro
- Forms & labels · <LanguageSelect> field component without a label docs/src/components/Header.astro
Fixed since the last survey: 52 findings
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] pnpm-lock.yaml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] pnpm-lock.yaml
- Dependency Vulnerabilities · High CVE: [GHSA redacted] pnpm-lock.yaml
- Dependency Vulnerabilities · Medium CVE: GO-2026-6603 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: GO-2026-6094 REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Documentation (README) · README may be stale
- Exception handling · Swallowed exception (caught, then discarded) REDACTED
- Exception handling · Swallowed exception (caught, then discarded) REDACTED
- Exception handling · Swallowed exception (caught, then discarded) REDACTED
- Exception handling · Swallowed exception (caught, then discarded) operator/internal/controller/metrics.go
- Exception handling · Swallowed exception (caught, then discarded) operator/internal/controller/metrics.go
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-agentcore/src/llama_agents/agentcore/deploy.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-agentcore/src/llama_agents/agentcore/deploy.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-appserver/src/llama_agents/appserver/workflow_loader.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-appserver/src/llama_agents/appserver/workflow_loader.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-appserver/src/llama_agents/appserver/process_utils.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-appserver/src/llama_agents/appserver/configure_logging.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-appserver/src/llama_agents/appserver/routers/ui_proxy.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-appserver/src/llama_agents/appserver/routers/ui_proxy.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-client/src/llama_agents/client/client.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-core/src/llama_agents/core/client/manage_client.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/client/manage_client.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/client/manage_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-core/src/llama_agents/core/client/manage_client.py
- Exception handling · Swallowed exception (empty catch) packages/llama-agents-core/src/llama_agents/core/client/manage_client.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/git/git_util.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/git/git_util.py
- Exception handling · Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/git/git_util.py
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €37,000 to €180,000, for 613 to 1,943 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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: 51,104 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 llama-agents-appserver.src.llama_agents.appserver.settings | 2 llama-agents-control-plane.src.llama_agents.control_plane.manage_api.backup_service | 3 llama-agents-control-plane.src.llama_agents.control_plane.storage | 4 llama-agents-core.src.llama_agents.core.schema.base | 5 llama-agents-server.src.llama_agents.server._store.abstract_workflow_store | 6 llama-index-workflows.src.workflows.collect | 7 llama-index-workflows.src.workflows.context.context_types | 8 llama-index-workflows.src.workflows.context.serializers | 9 llama-index-workflows.src.workflows.events | 10 llama-index-workflows.src.workflows.runtime.types.step_id | 11 llamactl.src.llama_agents.cli | 12 llamactl.src.llama_agents.cli.config.schema | 13 llama-agents-appserver.src.llama_agents.appserver | 14 llama-agents-appserver.src.llama_agents.appserver.routers | 15 llama-agents-core.src.llama_agents.core.schema.deployments | 16 llama-agents-core.src.llama_agents.core.schema.public | 17 llama-agents-server.src.llama_agents.server._service | 18 llama-index-workflows.src.workflows | 19 llama-index-workflows.src.workflows.context.state_store | 20 llama-index-workflows.src.workflows.runtime.types.commands | 21 llama-index-workflows.src.workflows.runtime.types.results | 22 llama-index-workflows.src.workflows.workflow | 23 llamactl.src.llama_agents.cli.config.auth_service | 24 llama-agents-core.src.llama_agents.core.client.manage_client | 25 llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service | 26 llama-index-workflows.src.workflows.context | 27 llama-index-workflows.src.workflows.runtime.types.internal_state | 28 llama-index-workflows.src.workflows.runtime.types.step_function | 29 llamactl.src.llama_agents.cli.commands | 30 llama-index-workflows.src.workflows.runtime.types.plugin | 31 llama-index-workflows.src.workflows.context.external_context | 32 llama-index-workflows.src.workflows.context.internal_context | 33 llama-index-workflows.src.workflows.handler | 34 llama-index-workflows.src.workflows.runtime.control_loop | 35 llama-index-workflows.src.workflows.runtime.runtime_decorators | 36 llama-index-workflows.src.workflows.context.context | 37 llama-index-workflows.src.workflows.runtime.verbose | 38 llama-index-workflows.src.workflows.plugins.basic | 39 llama-index-workflows.src.workflows.runtime.control_loop.runner | 40 llama-index-workflows.src.workflows.runtime.types |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 llama-agents-appserver.src.llama_agents.appserver.settings | ||||||||||||||||||||||||||||||||||||||||
| 2 llama-agents-control-plane.src.llama_agents.control_plane.manage_api.backup_service | ||||||||||||||||||||||||||||||||||||||||
| 3 llama-agents-control-plane.src.llama_agents.control_plane.storage | ||||||||||||||||||||||||||||||||||||||||
| 4 llama-agents-core.src.llama_agents.core.schema.base | ||||||||||||||||||||||||||||||||||||||||
| 5 llama-agents-server.src.llama_agents.server._store.abstract_workflow_store | ||||||||||||||||||||||||||||||||||||||||
| 6 llama-index-workflows.src.workflows.collect | ||||||||||||||||||||||||||||||||||||||||
| 7 llama-index-workflows.src.workflows.context.context_types | ||||||||||||||||||||||||||||||||||||||||
| 8 llama-index-workflows.src.workflows.context.serializers | ||||||||||||||||||||||||||||||||||||||||
| 9 llama-index-workflows.src.workflows.events | ||||||||||||||||||||||||||||||||||||||||
| 10 llama-index-workflows.src.workflows.runtime.types.step_id | ||||||||||||||||||||||||||||||||||||||||
| 11 llamactl.src.llama_agents.cli | ||||||||||||||||||||||||||||||||||||||||
| 12 llamactl.src.llama_agents.cli.config.schema | ||||||||||||||||||||||||||||||||||||||||
| 13 llama-agents-appserver.src.llama_agents.appserver | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 llama-agents-appserver.src.llama_agents.appserver.routers | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 llama-agents-core.src.llama_agents.core.schema.deployments | 15 | |||||||||||||||||||||||||||||||||||||||
| 16 llama-agents-core.src.llama_agents.core.schema.public | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 llama-agents-server.src.llama_agents.server._service | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 llama-index-workflows.src.workflows | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 llama-index-workflows.src.workflows.context.state_store | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 llama-index-workflows.src.workflows.runtime.types.commands | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 llama-index-workflows.src.workflows.runtime.types.results | 3 | |||||||||||||||||||||||||||||||||||||||
| 22 llama-index-workflows.src.workflows.workflow | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 llamactl.src.llama_agents.cli.config.auth_service | 3 | |||||||||||||||||||||||||||||||||||||||
| 24 llama-agents-core.src.llama_agents.core.client.manage_client | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 llama-index-workflows.src.workflows.context | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 llama-index-workflows.src.workflows.runtime.types.internal_state | 1 | 1 | 1 | 3 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 28 llama-index-workflows.src.workflows.runtime.types.step_function | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 llamactl.src.llama_agents.cli.commands | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 llama-index-workflows.src.workflows.runtime.types.plugin | 1 | 2 | 4 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 31 llama-index-workflows.src.workflows.context.external_context | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 32 llama-index-workflows.src.workflows.context.internal_context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 llama-index-workflows.src.workflows.handler | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 llama-index-workflows.src.workflows.runtime.control_loop | 2 | 1 | 1 | 2 | 7 | 1 | ||||||||||||||||||||||||||||||||||
| 35 llama-index-workflows.src.workflows.runtime.runtime_decorators | 1 | 2 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 36 llama-index-workflows.src.workflows.context.context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 llama-index-workflows.src.workflows.runtime.verbose | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 llama-index-workflows.src.workflows.plugins.basic | 2 | 1 | 1 | 4 | 9 | 1 | ||||||||||||||||||||||||||||||||||
| 39 llama-index-workflows.src.workflows.runtime.control_loop.runner | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 llama-index-workflows.src.workflows.runtime.types | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | 1 |
13→1 llama-agents-appserver.src.llama_agents.appserver uses llama-agents-appserver.src.llama_agents.appserver.settings✕
- Connections
- 1 pair of types, where a type in llama-agents-appserver.src.llama_agents.appserver uses a type in llama-agents-appserver.src.llama_agents.appserver.settings.
- The types involved
packages.llama-agents-appserver.src.llama_agents.appserver.workflow_loader→packages.llama-agents-appserver.src.llama_agents.appserver.settings.ApiserverSettings
- Direction
- llama-agents-appserver.src.llama_agents.appserver uses llama-agents-appserver.src.llama_agents.appserver.settings, so a change to llama-agents-appserver.src.llama_agents.appserver.settings can break llama-agents-appserver.src.llama_agents.appserver, while a change to llama-agents-appserver.src.llama_agents.appserver can't break llama-agents-appserver.src.llama_agents.appserver.settings.
- Position
- Below the diagonal: llama-agents-appserver.src.llama_agents.appserver uses a module listed above it, which is the healthy direction.
14→1 llama-agents-appserver.src.llama_agents.appserver.routers uses llama-agents-appserver.src.llama_agents.appserver.settings✕
- Connections
- 1 pair of types, where a type in llama-agents-appserver.src.llama_agents.appserver.routers uses a type in llama-agents-appserver.src.llama_agents.appserver.settings.
- The types involved
packages.llama-agents-appserver.src.llama_agents.appserver.routers.ui_proxy→packages.llama-agents-appserver.src.llama_agents.appserver.settings.ApiserverSettings
- Direction
- llama-agents-appserver.src.llama_agents.appserver.routers uses llama-agents-appserver.src.llama_agents.appserver.settings, so a change to llama-agents-appserver.src.llama_agents.appserver.settings can break llama-agents-appserver.src.llama_agents.appserver.routers, while a change to llama-agents-appserver.src.llama_agents.appserver.routers can't break llama-agents-appserver.src.llama_agents.appserver.settings.
- Position
- Below the diagonal: llama-agents-appserver.src.llama_agents.appserver.routers uses a module listed above it, which is the healthy direction.
15→4 llama-agents-core.src.llama_agents.core.schema.deployments uses llama-agents-core.src.llama_agents.core.schema.base✕
- Connections
- 15 pairs of types, where a type in llama-agents-core.src.llama_agents.core.schema.deployments uses a type in llama-agents-core.src.llama_agents.core.schema.base.
- The types involved
packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentCreate→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentEvent→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentHistoryResponse→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentResponse→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentUpdate→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentUpdateResult→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentsListResponse→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.LlamaDeploymentCRD→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.LlamaDeploymentMetadata→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.LlamaDeploymentSpec→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.LlamaDeploymentStatus→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.LogEvent→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.ReleaseHistoryEntry→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.ReleaseHistoryItem→packages.llama-agents-core.src.llama_agents.core.schema.base.Basepackages.llama-agents-core.src.llama_agents.core.schema.deployments.RollbackRequest→packages.llama-agents-core.src.llama_agents.core.schema.base.Base
- Direction
- llama-agents-core.src.llama_agents.core.schema.deployments uses llama-agents-core.src.llama_agents.core.schema.base, so a change to llama-agents-core.src.llama_agents.core.schema.base can break llama-agents-core.src.llama_agents.core.schema.deployments, while a change to llama-agents-core.src.llama_agents.core.schema.deployments can't break llama-agents-core.src.llama_agents.core.schema.base.
- Position
- Below the diagonal: llama-agents-core.src.llama_agents.core.schema.deployments uses a module listed above it, which is the healthy direction.
16→4 llama-agents-core.src.llama_agents.core.schema.public uses llama-agents-core.src.llama_agents.core.schema.base✕
- Connections
- 1 pair of types, where a type in llama-agents-core.src.llama_agents.core.schema.public uses a type in llama-agents-core.src.llama_agents.core.schema.base.
- The types involved
packages.llama-agents-core.src.llama_agents.core.schema.public.VersionResponse→packages.llama-agents-core.src.llama_agents.core.schema.base.Base
- Direction
- llama-agents-core.src.llama_agents.core.schema.public uses llama-agents-core.src.llama_agents.core.schema.base, so a change to llama-agents-core.src.llama_agents.core.schema.base can break llama-agents-core.src.llama_agents.core.schema.public, while a change to llama-agents-core.src.llama_agents.core.schema.public can't break llama-agents-core.src.llama_agents.core.schema.base.
- Position
- Below the diagonal: llama-agents-core.src.llama_agents.core.schema.public uses a module listed above it, which is the healthy direction.
17→5 llama-agents-server.src.llama_agents.server._service uses llama-agents-server.src.llama_agents.server._store.abstract_workflow_store✕
- Connections
- 2 pairs of types, where a type in llama-agents-server.src.llama_agents.server._service uses a type in llama-agents-server.src.llama_agents.server._store.abstract_workflow_store.
- The types involved
packages.llama-agents-server.src.llama_agents.server._service._WorkflowService→packages.llama-agents-server.src.llama_agents.server._store.abstract_workflow_store.AbstractWorkflowStorepackages.llama-agents-server.src.llama_agents.server._service._WorkflowService→packages.llama-agents-server.src.llama_agents.server._store.abstract_workflow_store.HandlerQuery
- Direction
- llama-agents-server.src.llama_agents.server._service uses llama-agents-server.src.llama_agents.server._store.abstract_workflow_store, so a change to llama-agents-server.src.llama_agents.server._store.abstract_workflow_store can break llama-agents-server.src.llama_agents.server._service, while a change to llama-agents-server.src.llama_agents.server._service can't break llama-agents-server.src.llama_agents.server._store.abstract_workflow_store.
- Position
- Below the diagonal: llama-agents-server.src.llama_agents.server._service uses a module listed above it, which is the healthy direction.
18→6 llama-index-workflows.src.workflows uses llama-index-workflows.src.workflows.collect✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows uses a type in llama-index-workflows.src.workflows.collect.
- The types involved
packages.llama-index-workflows.src.workflows.utils→packages.llama-index-workflows.src.workflows.collect.Collect
- Direction
- llama-index-workflows.src.workflows uses llama-index-workflows.src.workflows.collect, so a change to llama-index-workflows.src.workflows.collect can break llama-index-workflows.src.workflows, while a change to llama-index-workflows.src.workflows can't break llama-index-workflows.src.workflows.collect.
- Position
- Below the diagonal: llama-index-workflows.src.workflows uses a module listed above it, which is the healthy direction.
18→9 llama-index-workflows.src.workflows uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows._event_summary→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.events→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows, while a change to llama-index-workflows.src.workflows can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows uses a module listed above it, which is the healthy direction.
19→8 llama-index-workflows.src.workflows.context.state_store uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 5 pairs of types, where a type in llama-index-workflows.src.workflows.context.state_store uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.context.state_store.StateCheckpoint→packages.llama-index-workflows.src.workflows.context.serializers.JsonSerializerpackages.llama-index-workflows.src.workflows.context.state_store.StateStoreFacade→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializerpackages.llama-index-workflows.src.workflows.context.state_store._PatchLocation→packages.llama-index-workflows.src.workflows.context.serializers.JsonSerializerpackages.llama-index-workflows.src.workflows.context.state_store._PayloadSeed→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializerpackages.llama-index-workflows.src.workflows.context.state_store._StateDiff→packages.llama-index-workflows.src.workflows.context.serializers.JsonSerializer
- Direction
- llama-index-workflows.src.workflows.context.state_store uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.context.state_store, while a change to llama-index-workflows.src.workflows.context.state_store can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.state_store uses a module listed above it, which is the healthy direction.
19→9 llama-index-workflows.src.workflows.context.state_store uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.state_store uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.context.state_store.DictState→packages.llama-index-workflows.src.workflows.events.DictLikeModel
- Direction
- llama-index-workflows.src.workflows.context.state_store uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.context.state_store, while a change to llama-index-workflows.src.workflows.context.state_store can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.state_store uses a module listed above it, which is the healthy direction.
20→9 llama-index-workflows.src.workflows.runtime.types.commands uses llama-index-workflows.src.workflows.events✕
- Connections
- 4 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.commands uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.commands.CommandCompleteRun→packages.llama-index-workflows.src.workflows.events.StopEventpackages.llama-index-workflows.src.workflows.runtime.types.commands.CommandPublishEvent→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.runtime.types.commands.CommandQueueEvent→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.runtime.types.commands.CommandRunWorker→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.types.commands uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.types.commands, while a change to llama-index-workflows.src.workflows.runtime.types.commands can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.commands uses a module listed above it, which is the healthy direction.
20→10 llama-index-workflows.src.workflows.runtime.types.commands uses llama-index-workflows.src.workflows.runtime.types.step_id✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.commands uses a type in llama-index-workflows.src.workflows.runtime.types.step_id.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.commands.CommandFailWorkflow→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepIdpackages.llama-index-workflows.src.workflows.runtime.types.commands.CommandRunWorker→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepIdpackages.llama-index-workflows.src.workflows.runtime.types.commands.CommandScheduleWaiterTimeout→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepId
- Direction
- llama-index-workflows.src.workflows.runtime.types.commands uses llama-index-workflows.src.workflows.runtime.types.step_id, so a change to llama-index-workflows.src.workflows.runtime.types.step_id can break llama-index-workflows.src.workflows.runtime.types.commands, while a change to llama-index-workflows.src.workflows.runtime.types.commands can't break llama-index-workflows.src.workflows.runtime.types.step_id.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.commands uses a module listed above it, which is the healthy direction.
21→9 llama-index-workflows.src.workflows.runtime.types.results uses llama-index-workflows.src.workflows.events✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.results uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.results.CollectionReleasePayload→packages.llama-index-workflows.src.workflows.events.CollectionReleaseEventpackages.llama-index-workflows.src.workflows.runtime.types.results.StepWorkerContext→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.runtime.types.results.StepWorkerWaiter→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.types.results uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.types.results, while a change to llama-index-workflows.src.workflows.runtime.types.results can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.results uses a module listed above it, which is the healthy direction.
22→9 llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.workflow uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.workflow.Workflow→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.workflow.Workflow→packages.llama-index-workflows.src.workflows.events.StartEvent
- Direction
- llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.workflow, while a change to llama-index-workflows.src.workflows.workflow can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.workflow uses a module listed above it, which is the healthy direction.
22→27 llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.runtime.types.internal_state part of a loop✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.workflow uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.workflow.Workflow→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerConfig
- Direction
- llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.workflow, while a change to llama-index-workflows.src.workflows.workflow can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→30 llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.runtime.types.plugin part of a loop✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.workflow uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.workflow.Workflow→packages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtime
- Direction
- llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.workflow, while a change to llama-index-workflows.src.workflows.workflow can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→33 llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.handler part of a loop✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.workflow uses a type in llama-index-workflows.src.workflows.handler.
- The types involved
packages.llama-index-workflows.src.workflows.workflow.Workflow→packages.llama-index-workflows.src.workflows.handler.WorkflowHandler
- Direction
- llama-index-workflows.src.workflows.workflow uses llama-index-workflows.src.workflows.handler, so a change to llama-index-workflows.src.workflows.handler can break llama-index-workflows.src.workflows.workflow, while a change to llama-index-workflows.src.workflows.workflow can't break llama-index-workflows.src.workflows.handler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→12 llamactl.src.llama_agents.cli.config.auth_service uses llamactl.src.llama_agents.cli.config.schema✕
- Connections
- 3 pairs of types, where a type in llamactl.src.llama_agents.cli.config.auth_service uses a type in llamactl.src.llama_agents.cli.config.schema.
- The types involved
packages.llamactl.src.llama_agents.cli.config.auth_service.AuthService→packages.llamactl.src.llama_agents.cli.config.schema.Authpackages.llamactl.src.llama_agents.cli.config.auth_service.AuthService→packages.llamactl.src.llama_agents.cli.config.schema.DeviceOIDCpackages.llamactl.src.llama_agents.cli.config.auth_service.AuthService→packages.llamactl.src.llama_agents.cli.config.schema.Environment
- Direction
- llamactl.src.llama_agents.cli.config.auth_service uses llamactl.src.llama_agents.cli.config.schema, so a change to llamactl.src.llama_agents.cli.config.schema can break llamactl.src.llama_agents.cli.config.auth_service, while a change to llamactl.src.llama_agents.cli.config.auth_service can't break llamactl.src.llama_agents.cli.config.schema.
- Position
- Below the diagonal: llamactl.src.llama_agents.cli.config.auth_service uses a module listed above it, which is the healthy direction.
24→15 llama-agents-core.src.llama_agents.core.client.manage_client uses llama-agents-core.src.llama_agents.core.schema.deployments✕
- Connections
- 4 pairs of types, where a type in llama-agents-core.src.llama_agents.core.client.manage_client uses a type in llama-agents-core.src.llama_agents.core.schema.deployments.
- The types involved
packages.llama-agents-core.src.llama_agents.core.client.manage_client.ProjectClient→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentCreatepackages.llama-agents-core.src.llama_agents.core.client.manage_client.ProjectClient→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentHistoryResponsepackages.llama-agents-core.src.llama_agents.core.client.manage_client.ProjectClient→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentResponsepackages.llama-agents-core.src.llama_agents.core.client.manage_client.ProjectClient→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentUpdate
- Direction
- llama-agents-core.src.llama_agents.core.client.manage_client uses llama-agents-core.src.llama_agents.core.schema.deployments, so a change to llama-agents-core.src.llama_agents.core.schema.deployments can break llama-agents-core.src.llama_agents.core.client.manage_client, while a change to llama-agents-core.src.llama_agents.core.client.manage_client can't break llama-agents-core.src.llama_agents.core.schema.deployments.
- Position
- Below the diagonal: llama-agents-core.src.llama_agents.core.client.manage_client uses a module listed above it, which is the healthy direction.
24→16 llama-agents-core.src.llama_agents.core.client.manage_client uses llama-agents-core.src.llama_agents.core.schema.public✕
- Connections
- 1 pair of types, where a type in llama-agents-core.src.llama_agents.core.client.manage_client uses a type in llama-agents-core.src.llama_agents.core.schema.public.
- The types involved
packages.llama-agents-core.src.llama_agents.core.client.manage_client.ControlPlaneClient→packages.llama-agents-core.src.llama_agents.core.schema.public.VersionResponse
- Direction
- llama-agents-core.src.llama_agents.core.client.manage_client uses llama-agents-core.src.llama_agents.core.schema.public, so a change to llama-agents-core.src.llama_agents.core.schema.public can break llama-agents-core.src.llama_agents.core.client.manage_client, while a change to llama-agents-core.src.llama_agents.core.client.manage_client can't break llama-agents-core.src.llama_agents.core.schema.public.
- Position
- Below the diagonal: llama-agents-core.src.llama_agents.core.client.manage_client uses a module listed above it, which is the healthy direction.
25→15 llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses llama-agents-core.src.llama_agents.core.schema.deployments✕
- Connections
- 6 pairs of types, where a type in llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses a type in llama-agents-core.src.llama_agents.core.schema.deployments.
- The types involved
packages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentCreatepackages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentHistoryResponsepackages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentResponsepackages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentUpdatepackages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.deployments.DeploymentsListResponsepackages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.deployments.RollbackRequest
- Direction
- llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses llama-agents-core.src.llama_agents.core.schema.deployments, so a change to llama-agents-core.src.llama_agents.core.schema.deployments can break llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service, while a change to llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service can't break llama-agents-core.src.llama_agents.core.schema.deployments.
- Position
- Below the diagonal: llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses a module listed above it, which is the healthy direction.
25→16 llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses llama-agents-core.src.llama_agents.core.schema.public✕
- Connections
- 1 pair of types, where a type in llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses a type in llama-agents-core.src.llama_agents.core.schema.public.
- The types involved
packages.llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service.AbstractPublicDeploymentsService→packages.llama-agents-core.src.llama_agents.core.schema.public.VersionResponse
- Direction
- llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses llama-agents-core.src.llama_agents.core.schema.public, so a change to llama-agents-core.src.llama_agents.core.schema.public can break llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service, while a change to llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service can't break llama-agents-core.src.llama_agents.core.schema.public.
- Position
- Below the diagonal: llama-agents-core.src.llama_agents.core.server.manage_api._abstract_deployments_service uses a module listed above it, which is the healthy direction.
26→8 llama-index-workflows.src.workflows.context uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.context uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.context.state_store→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializerpackages.llama-index-workflows.src.workflows.context.state_store→packages.llama-index-workflows.src.workflows.context.serializers.JsonSerializerpackages.llama-index-workflows.src.workflows.context.state_store_integration→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializer
- Direction
- llama-index-workflows.src.workflows.context uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.context, while a change to llama-index-workflows.src.workflows.context can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context uses a module listed above it, which is the healthy direction.
26→9 llama-index-workflows.src.workflows.context uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.context.state_store→packages.llama-index-workflows.src.workflows.events.DictLikeModel
- Direction
- llama-index-workflows.src.workflows.context uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.context, while a change to llama-index-workflows.src.workflows.context can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context uses a module listed above it, which is the healthy direction.
26→19 llama-index-workflows.src.workflows.context uses llama-index-workflows.src.workflows.context.state_store✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.context uses a type in llama-index-workflows.src.workflows.context.state_store.
- The types involved
packages.llama-index-workflows.src.workflows.context.state_store→packages.llama-index-workflows.src.workflows.context.state_store.DictStatepackages.llama-index-workflows.src.workflows.context.state_store→packages.llama-index-workflows.src.workflows.context.state_store.InMemorySerializedStatepackages.llama-index-workflows.src.workflows.context.state_store→packages.llama-index-workflows.src.workflows.context.state_store.StateRecord
- Direction
- llama-index-workflows.src.workflows.context uses llama-index-workflows.src.workflows.context.state_store, so a change to llama-index-workflows.src.workflows.context.state_store can break llama-index-workflows.src.workflows.context, while a change to llama-index-workflows.src.workflows.context can't break llama-index-workflows.src.workflows.context.state_store.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context uses a module listed above it, which is the healthy direction.
27→6 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.collect✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.collect.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.CollectionBinding→packages.llama-index-workflows.src.workflows.collect.Collect
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.collect, so a change to llama-index-workflows.src.workflows.collect can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.collect.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→7 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.context.context_types✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.context.context_types.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState→packages.llama-index-workflows.src.workflows.context.context_types.SerializedContext
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.context.context_types, so a change to llama-index-workflows.src.workflows.context.context_types can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.context.context_types.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→8 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializer
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→9 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.events✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.Delivery→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.runtime.types.internal_state.EventAttempt→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.runtime.types.internal_state.InProgressState→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→10 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.runtime.types.step_id✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.runtime.types.step_id.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerConfig→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepIdpackages.llama-index-workflows.src.workflows.runtime.types.internal_state.CollectionBinding→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepIdpackages.llama-index-workflows.src.workflows.runtime.types.internal_state.CollectionStreamInstance→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepId
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.runtime.types.step_id, so a change to llama-index-workflows.src.workflows.runtime.types.step_id can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.runtime.types.step_id.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→20 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.runtime.types.commands✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.runtime.types.commands.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.Delivery→packages.llama-index-workflows.src.workflows.runtime.types.commands.CommandQueueEvent
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.runtime.types.commands, so a change to llama-index-workflows.src.workflows.runtime.types.commands can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.runtime.types.commands.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→21 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.runtime.types.results✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.runtime.types.results.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.InProgressState→packages.llama-index-workflows.src.workflows.runtime.types.results.StepWorkerState
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.runtime.types.results, so a change to llama-index-workflows.src.workflows.runtime.types.results can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.runtime.types.results.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
27→22 llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.internal_state uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.types.internal_state uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.types.internal_state, while a change to llama-index-workflows.src.workflows.runtime.types.internal_state can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.internal_state uses a module listed above it, which is the healthy direction.
28→9 llama-index-workflows.src.workflows.runtime.types.step_function uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.step_function uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function.StepWorkerFunction→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.types.step_function uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.types.step_function, while a change to llama-index-workflows.src.workflows.runtime.types.step_function can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.step_function uses a module listed above it, which is the healthy direction.
28→21 llama-index-workflows.src.workflows.runtime.types.step_function uses llama-index-workflows.src.workflows.runtime.types.results✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.step_function uses a type in llama-index-workflows.src.workflows.runtime.types.results.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function.StepWorkerFunction→packages.llama-index-workflows.src.workflows.runtime.types.results.RetryAttemptpackages.llama-index-workflows.src.workflows.runtime.types.step_function.StepWorkerFunction→packages.llama-index-workflows.src.workflows.runtime.types.results.StepWorkerState
- Direction
- llama-index-workflows.src.workflows.runtime.types.step_function uses llama-index-workflows.src.workflows.runtime.types.results, so a change to llama-index-workflows.src.workflows.runtime.types.results can break llama-index-workflows.src.workflows.runtime.types.step_function, while a change to llama-index-workflows.src.workflows.runtime.types.step_function can't break llama-index-workflows.src.workflows.runtime.types.results.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.step_function uses a module listed above it, which is the healthy direction.
28→22 llama-index-workflows.src.workflows.runtime.types.step_function uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.step_function uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function.StepWorkerFunction→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.types.step_function uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.types.step_function, while a change to llama-index-workflows.src.workflows.runtime.types.step_function can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.step_function uses a module listed above it, which is the healthy direction.
29→12 llamactl.src.llama_agents.cli.commands uses llamactl.src.llama_agents.cli.config.schema✕
- Connections
- 4 pairs of types, where a type in llamactl.src.llama_agents.cli.commands uses a type in llamactl.src.llama_agents.cli.config.schema.
- The types involved
packages.llamactl.src.llama_agents.cli.commands.auth→packages.llamactl.src.llama_agents.cli.config.schema.Authpackages.llamactl.src.llama_agents.cli.commands.auth→packages.llamactl.src.llama_agents.cli.config.schema.DeviceOIDCpackages.llamactl.src.llama_agents.cli.commands.environments→packages.llamactl.src.llama_agents.cli.config.schema.Environmentpackages.llamactl.src.llama_agents.cli.commands.serve→packages.llamactl.src.llama_agents.cli.config.schema.Auth
- Direction
- llamactl.src.llama_agents.cli.commands uses llamactl.src.llama_agents.cli.config.schema, so a change to llamactl.src.llama_agents.cli.config.schema can break llamactl.src.llama_agents.cli.commands, while a change to llamactl.src.llama_agents.cli.commands can't break llamactl.src.llama_agents.cli.config.schema.
- Position
- Below the diagonal: llamactl.src.llama_agents.cli.commands uses a module listed above it, which is the healthy direction.
29→23 llamactl.src.llama_agents.cli.commands uses llamactl.src.llama_agents.cli.config.auth_service✕
- Connections
- 1 pair of types, where a type in llamactl.src.llama_agents.cli.commands uses a type in llamactl.src.llama_agents.cli.config.auth_service.
- The types involved
packages.llamactl.src.llama_agents.cli.commands.auth→packages.llamactl.src.llama_agents.cli.config.auth_service.AuthService
- Direction
- llamactl.src.llama_agents.cli.commands uses llamactl.src.llama_agents.cli.config.auth_service, so a change to llamactl.src.llama_agents.cli.config.auth_service can break llamactl.src.llama_agents.cli.commands, while a change to llamactl.src.llama_agents.cli.commands can't break llamactl.src.llama_agents.cli.config.auth_service.
- Position
- Below the diagonal: llamactl.src.llama_agents.cli.commands uses a module listed above it, which is the healthy direction.
30→8 llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.plugin uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtime→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializer
- Direction
- llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.runtime.types.plugin, while a change to llama-index-workflows.src.workflows.runtime.types.plugin can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.plugin uses a module listed above it, which is the healthy direction.
30→9 llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.plugin uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapter→packages.llama-index-workflows.src.workflows.events.StopEventpackages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapter→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.types.plugin, while a change to llama-index-workflows.src.workflows.runtime.types.plugin can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.plugin uses a module listed above it, which is the healthy direction.
30→22 llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 4 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.plugin uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.plugin.RegisteredWorkflow→packages.llama-index-workflows.src.workflows.workflow.Workflowpackages.llama-index-workflows.src.workflows.runtime.types.plugin.RunContext→packages.llama-index-workflows.src.workflows.workflow.Workflowpackages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtime→packages.llama-index-workflows.src.workflows.workflow.Workflowpackages.llama-index-workflows.src.workflows.runtime.types.plugin.WorkflowSet→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.types.plugin, while a change to llama-index-workflows.src.workflows.runtime.types.plugin can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.plugin uses a module listed above it, which is the healthy direction.
30→27 llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types.plugin uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtime→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.runtime.types.plugin.SnapshottableAdapter→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.runtime.types.plugin.WorkflowRunFunction→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState
- Direction
- llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.runtime.types.plugin, while a change to llama-index-workflows.src.workflows.runtime.types.plugin can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types.plugin uses a module listed above it, which is the healthy direction.
30→36 llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.context.context part of a loop✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types.plugin uses a type in llama-index-workflows.src.workflows.context.context.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.plugin.RunContext→packages.llama-index-workflows.src.workflows.context.context.Context
- Direction
- llama-index-workflows.src.workflows.runtime.types.plugin uses llama-index-workflows.src.workflows.context.context, so a change to llama-index-workflows.src.workflows.context.context can break llama-index-workflows.src.workflows.runtime.types.plugin, while a change to llama-index-workflows.src.workflows.runtime.types.plugin can't break llama-index-workflows.src.workflows.context.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→8 llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.external_context uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializer
- Direction
- llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.context.external_context, while a change to llama-index-workflows.src.workflows.context.external_context can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.external_context uses a module listed above it, which is the healthy direction.
31→9 llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.context.external_context uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.events.StopEvent
- Direction
- llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.context.external_context, while a change to llama-index-workflows.src.workflows.context.external_context can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.external_context uses a module listed above it, which is the healthy direction.
31→22 llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.external_context uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.context.external_context, while a change to llama-index-workflows.src.workflows.context.external_context can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.external_context uses a module listed above it, which is the healthy direction.
31→27 llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.external_context uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState
- Direction
- llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.context.external_context, while a change to llama-index-workflows.src.workflows.context.external_context can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.external_context uses a module listed above it, which is the healthy direction.
31→30 llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.context.external_context uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapterpackages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.runtime.types.plugin.SnapshottableAdapterpackages.llama-index-workflows.src.workflows.context.external_context.ExternalContext→packages.llama-index-workflows.src.workflows.runtime.types.plugin.V2RuntimeCompatibilityShim
- Direction
- llama-index-workflows.src.workflows.context.external_context uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.context.external_context, while a change to llama-index-workflows.src.workflows.context.external_context can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.external_context uses a module listed above it, which is the healthy direction.
32→9 llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.internal_context uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.context.internal_context.InternalContext→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.context.internal_context, while a change to llama-index-workflows.src.workflows.context.internal_context can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.internal_context uses a module listed above it, which is the healthy direction.
32→21 llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.runtime.types.results✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.internal_context uses a type in llama-index-workflows.src.workflows.runtime.types.results.
- The types involved
packages.llama-index-workflows.src.workflows.context.internal_context.InternalContext→packages.llama-index-workflows.src.workflows.runtime.types.results.StepWorkerContext
- Direction
- llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.runtime.types.results, so a change to llama-index-workflows.src.workflows.runtime.types.results can break llama-index-workflows.src.workflows.context.internal_context, while a change to llama-index-workflows.src.workflows.context.internal_context can't break llama-index-workflows.src.workflows.runtime.types.results.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.internal_context uses a module listed above it, which is the healthy direction.
32→22 llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.internal_context uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.context.internal_context.InternalContext→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.context.internal_context, while a change to llama-index-workflows.src.workflows.context.internal_context can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.internal_context uses a module listed above it, which is the healthy direction.
32→30 llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.internal_context uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.context.internal_context.InternalContext→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapter
- Direction
- llama-index-workflows.src.workflows.context.internal_context uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.context.internal_context, while a change to llama-index-workflows.src.workflows.context.internal_context can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.internal_context uses a module listed above it, which is the healthy direction.
33→9 llama-index-workflows.src.workflows.handler uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.handler uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.handler.WorkflowHandler→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.handler.WorkflowHandler→packages.llama-index-workflows.src.workflows.events.StopEvent
- Direction
- llama-index-workflows.src.workflows.handler uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.handler, while a change to llama-index-workflows.src.workflows.handler can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.handler uses a module listed above it, which is the healthy direction.
33→30 llama-index-workflows.src.workflows.handler uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.handler uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.handler.WorkflowHandler→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapter
- Direction
- llama-index-workflows.src.workflows.handler uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.handler, while a change to llama-index-workflows.src.workflows.handler can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.handler uses a module listed above it, which is the healthy direction.
33→36 llama-index-workflows.src.workflows.handler uses llama-index-workflows.src.workflows.context.context part of a loop✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.handler uses a type in llama-index-workflows.src.workflows.context.context.
- The types involved
packages.llama-index-workflows.src.workflows.handler.WorkflowHandler→packages.llama-index-workflows.src.workflows.context.context.Context
- Direction
- llama-index-workflows.src.workflows.handler uses llama-index-workflows.src.workflows.context.context, so a change to llama-index-workflows.src.workflows.context.context can break llama-index-workflows.src.workflows.handler, while a change to llama-index-workflows.src.workflows.handler can't break llama-index-workflows.src.workflows.context.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→9 llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.events.Eventpackages.llama-index-workflows.src.workflows.runtime.control_loop.runner→packages.llama-index-workflows.src.workflows.events.StopEvent
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.control_loop, while a change to llama-index-workflows.src.workflows.runtime.control_loop can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop uses a module listed above it, which is the healthy direction.
34→10 llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.step_id✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop uses a type in llama-index-workflows.src.workflows.runtime.types.step_id.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepId
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.step_id, so a change to llama-index-workflows.src.workflows.runtime.types.step_id can break llama-index-workflows.src.workflows.runtime.control_loop, while a change to llama-index-workflows.src.workflows.runtime.control_loop can't break llama-index-workflows.src.workflows.runtime.types.step_id.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop uses a module listed above it, which is the healthy direction.
34→20 llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.commands✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop uses a type in llama-index-workflows.src.workflows.runtime.types.commands.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.commands.CommandQueueEvent
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.commands, so a change to llama-index-workflows.src.workflows.runtime.types.commands can break llama-index-workflows.src.workflows.runtime.control_loop, while a change to llama-index-workflows.src.workflows.runtime.control_loop can't break llama-index-workflows.src.workflows.runtime.types.commands.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop uses a module listed above it, which is the healthy direction.
34→21 llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.results✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop uses a type in llama-index-workflows.src.workflows.runtime.types.results.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.results.EmissionKeypackages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.results.StepWorkerFailed
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.results, so a change to llama-index-workflows.src.workflows.runtime.types.results can break llama-index-workflows.src.workflows.runtime.control_loop, while a change to llama-index-workflows.src.workflows.runtime.control_loop can't break llama-index-workflows.src.workflows.runtime.types.results.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop uses a module listed above it, which is the healthy direction.
34→27 llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 7 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.EventAttemptpackages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.InProgressStatepackages.llama-index-workflows.src.workflows.runtime.control_loop.reduce→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.InternalStepWorkerStatepackages.llama-index-workflows.src.workflows.runtime.control_loop.streams→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.runtime.control_loop.streams→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.CollectionBindingpackages.llama-index-workflows.src.workflows.runtime.control_loop.streams→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.CollectionReleaseState
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.runtime.control_loop, while a change to llama-index-workflows.src.workflows.runtime.control_loop can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop uses a module listed above it, which is the healthy direction.
34→30 llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapter
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.runtime.control_loop, while a change to llama-index-workflows.src.workflows.runtime.control_loop can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop uses a module listed above it, which is the healthy direction.
35→8 llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.runtime_decorators uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializer
- Direction
- llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.runtime.runtime_decorators, while a change to llama-index-workflows.src.workflows.runtime.runtime_decorators can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.runtime_decorators uses a module listed above it, which is the healthy direction.
35→9 llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.runtime_decorators uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseExternalRunAdapterDecorator→packages.llama-index-workflows.src.workflows.events.StopEventpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseInternalRunAdapterDecorator→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.runtime_decorators, while a change to llama-index-workflows.src.workflows.runtime.runtime_decorators can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.runtime_decorators uses a module listed above it, which is the healthy direction.
35→22 llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.runtime_decorators uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.runtime_decorators, while a change to llama-index-workflows.src.workflows.runtime.runtime_decorators can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.runtime_decorators uses a module listed above it, which is the healthy direction.
35→27 llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.runtime_decorators uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState
- Direction
- llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.runtime.runtime_decorators, while a change to llama-index-workflows.src.workflows.runtime.runtime_decorators can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.runtime_decorators uses a module listed above it, which is the healthy direction.
35→30 llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 7 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.runtime_decorators uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseExternalRunAdapterDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapterpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseInternalRunAdapterDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapterpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseInternalRunAdapterDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.WaitForNextTaskResultpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapterpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapterpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.RegisteredWorkflowpackages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtime
- Direction
- llama-index-workflows.src.workflows.runtime.runtime_decorators uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.runtime.runtime_decorators, while a change to llama-index-workflows.src.workflows.runtime.runtime_decorators can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.runtime_decorators uses a module listed above it, which is the healthy direction.
36→9 llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.context uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.context.context.Context→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.context.context, while a change to llama-index-workflows.src.workflows.context.context can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.context uses a module listed above it, which is the healthy direction.
36→22 llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.context uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.context.context.Context→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.context.context, while a change to llama-index-workflows.src.workflows.context.context can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.context uses a module listed above it, which is the healthy direction.
36→30 llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.context uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.context.context.Context→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapter
- Direction
- llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.context.context, while a change to llama-index-workflows.src.workflows.context.context can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.context uses a module listed above it, which is the healthy direction.
36→33 llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.handler✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.context.context uses a type in llama-index-workflows.src.workflows.handler.
- The types involved
packages.llama-index-workflows.src.workflows.context.context.Context→packages.llama-index-workflows.src.workflows.handler.WorkflowHandler
- Direction
- llama-index-workflows.src.workflows.context.context uses llama-index-workflows.src.workflows.handler, so a change to llama-index-workflows.src.workflows.handler can break llama-index-workflows.src.workflows.context.context, while a change to llama-index-workflows.src.workflows.context.context can't break llama-index-workflows.src.workflows.handler.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.context.context uses a module listed above it, which is the healthy direction.
37→9 llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.verbose uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.verbose._VerboseInternalRunAdapter→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.verbose, while a change to llama-index-workflows.src.workflows.runtime.verbose can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.verbose uses a module listed above it, which is the healthy direction.
37→22 llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.verbose uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.verbose.VerboseDecorator→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.verbose, while a change to llama-index-workflows.src.workflows.runtime.verbose can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.verbose uses a module listed above it, which is the healthy direction.
37→30 llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.verbose uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.verbose.VerboseDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapterpackages.llama-index-workflows.src.workflows.runtime.verbose.VerboseDecorator→packages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtimepackages.llama-index-workflows.src.workflows.runtime.verbose._VerboseInternalRunAdapter→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapter
- Direction
- llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.runtime.verbose, while a change to llama-index-workflows.src.workflows.runtime.verbose can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.verbose uses a module listed above it, which is the healthy direction.
37→35 llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.runtime.runtime_decorators✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.verbose uses a type in llama-index-workflows.src.workflows.runtime.runtime_decorators.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.verbose.VerboseDecorator→packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseRuntimeDecoratorpackages.llama-index-workflows.src.workflows.runtime.verbose._VerboseInternalRunAdapter→packages.llama-index-workflows.src.workflows.runtime.runtime_decorators.BaseInternalRunAdapterDecorator
- Direction
- llama-index-workflows.src.workflows.runtime.verbose uses llama-index-workflows.src.workflows.runtime.runtime_decorators, so a change to llama-index-workflows.src.workflows.runtime.runtime_decorators can break llama-index-workflows.src.workflows.runtime.verbose, while a change to llama-index-workflows.src.workflows.runtime.verbose can't break llama-index-workflows.src.workflows.runtime.runtime_decorators.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.verbose uses a module listed above it, which is the healthy direction.
38→9 llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.events✕
- Connections
- 2 pairs of types, where a type in llama-index-workflows.src.workflows.plugins.basic uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.plugins.basic.ExternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.events.StopEventpackages.llama-index-workflows.src.workflows.plugins.basic.InternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.plugins.basic, while a change to llama-index-workflows.src.workflows.plugins.basic can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.plugins.basic uses a module listed above it, which is the healthy direction.
38→19 llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.context.state_store✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.plugins.basic uses a type in llama-index-workflows.src.workflows.context.state_store.
- The types involved
packages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.context.state_store.StateCheckpoint
- Direction
- llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.context.state_store, so a change to llama-index-workflows.src.workflows.context.state_store can break llama-index-workflows.src.workflows.plugins.basic, while a change to llama-index-workflows.src.workflows.plugins.basic can't break llama-index-workflows.src.workflows.context.state_store.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.plugins.basic uses a module listed above it, which is the healthy direction.
38→22 llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.plugins.basic uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.plugins.basic, while a change to llama-index-workflows.src.workflows.plugins.basic can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.plugins.basic uses a module listed above it, which is the healthy direction.
38→27 llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 4 pairs of types, where a type in llama-index-workflows.src.workflows.plugins.basic uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.plugins.basic.AsyncioAdapterQueues→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.plugins.basic.ExternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerStatepackages.llama-index-workflows.src.workflows.plugins.basic.InternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState
- Direction
- llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.plugins.basic, while a change to llama-index-workflows.src.workflows.plugins.basic can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.plugins.basic uses a module listed above it, which is the healthy direction.
38→30 llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 9 pairs of types, where a type in llama-index-workflows.src.workflows.plugins.basic uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapterpackages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapterpackages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.runtime.types.plugin.RegisteredWorkflowpackages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.runtime.types.plugin.Runtimepackages.llama-index-workflows.src.workflows.plugins.basic.ExternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapterpackages.llama-index-workflows.src.workflows.plugins.basic.ExternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.plugin.SnapshottableAdapterpackages.llama-index-workflows.src.workflows.plugins.basic.ExternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.plugin.V2RuntimeCompatibilityShimpackages.llama-index-workflows.src.workflows.plugins.basic.InternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapterpackages.llama-index-workflows.src.workflows.plugins.basic.InternalAsyncioAdapter→packages.llama-index-workflows.src.workflows.runtime.types.plugin.SnapshottableAdapter
- Direction
- llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.plugins.basic, while a change to llama-index-workflows.src.workflows.plugins.basic can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.plugins.basic uses a module listed above it, which is the healthy direction.
38→36 llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.context.context✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.plugins.basic uses a type in llama-index-workflows.src.workflows.context.context.
- The types involved
packages.llama-index-workflows.src.workflows.plugins.basic.BasicRuntime→packages.llama-index-workflows.src.workflows.context.context.Context
- Direction
- llama-index-workflows.src.workflows.plugins.basic uses llama-index-workflows.src.workflows.context.context, so a change to llama-index-workflows.src.workflows.context.context can break llama-index-workflows.src.workflows.plugins.basic, while a change to llama-index-workflows.src.workflows.plugins.basic can't break llama-index-workflows.src.workflows.context.context.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.plugins.basic uses a module listed above it, which is the healthy direction.
39→9 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.events.StopEvent
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
39→10 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.step_id✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.runtime.types.step_id.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepId
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.step_id, so a change to llama-index-workflows.src.workflows.runtime.types.step_id can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.runtime.types.step_id.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
39→20 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.commands✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.runtime.types.commands.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.runtime.types.commands.CommandRunWorker
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.commands, so a change to llama-index-workflows.src.workflows.runtime.types.commands can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.runtime.types.commands.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
39→22 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
39→27 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
39→30 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.runtime.types.plugin.InternalRunAdapter
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
39→36 llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.context.context✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.control_loop.runner uses a type in llama-index-workflows.src.workflows.context.context.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.control_loop.runner._ControlLoopRunner→packages.llama-index-workflows.src.workflows.context.context.Context
- Direction
- llama-index-workflows.src.workflows.runtime.control_loop.runner uses llama-index-workflows.src.workflows.context.context, so a change to llama-index-workflows.src.workflows.context.context can break llama-index-workflows.src.workflows.runtime.control_loop.runner, while a change to llama-index-workflows.src.workflows.runtime.control_loop.runner can't break llama-index-workflows.src.workflows.context.context.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.control_loop.runner uses a module listed above it, which is the healthy direction.
40→6 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.collect✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.collect.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.collect.Collect
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.collect, so a change to llama-index-workflows.src.workflows.collect can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.collect.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→7 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.context.context_types✕
- Connections
- 3 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.context.context_types.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.context.context_types.SerializedContextpackages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.context.context_types.SerializedEventAttemptpackages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.context.context_types.SerializedInProgressAttempt
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.context.context_types, so a change to llama-index-workflows.src.workflows.context.context_types can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.context.context_types.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→8 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.context.serializers✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.context.serializers.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.context.serializers.BaseSerializer
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.context.serializers, so a change to llama-index-workflows.src.workflows.context.serializers can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.context.serializers.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→9 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.events✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.events.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function→packages.llama-index-workflows.src.workflows.events.Event
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.events, so a change to llama-index-workflows.src.workflows.events can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.events.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→10 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.step_id✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.runtime.types.step_id.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.runtime.types.step_id.StepId
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.step_id, so a change to llama-index-workflows.src.workflows.runtime.types.step_id can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.runtime.types.step_id.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→22 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.workflow✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.workflow.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function→packages.llama-index-workflows.src.workflows.workflow.Workflow
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.workflow, so a change to llama-index-workflows.src.workflows.workflow can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.workflow.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→27 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.internal_state✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.runtime.types.internal_state.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.internal_state→packages.llama-index-workflows.src.workflows.runtime.types.internal_state.BrokerState
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.internal_state, so a change to llama-index-workflows.src.workflows.runtime.types.internal_state can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.runtime.types.internal_state.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→28 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.step_function✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.runtime.types.step_function.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function→packages.llama-index-workflows.src.workflows.runtime.types.step_function.StepWorkerFunction
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.step_function, so a change to llama-index-workflows.src.workflows.runtime.types.step_function can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.runtime.types.step_function.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→30 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.plugin✕
- Connections
- 4 pairs of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.runtime.types.plugin.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.plugin→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ExternalRunAdapterpackages.llama-index-workflows.src.workflows.runtime.types.plugin→packages.llama-index-workflows.src.workflows.runtime.types.plugin.RunContextpackages.llama-index-workflows.src.workflows.runtime.types.step_function→packages.llama-index-workflows.src.workflows.runtime.types.plugin.ControlLoopFunctionpackages.llama-index-workflows.src.workflows.runtime.types.step_function→packages.llama-index-workflows.src.workflows.runtime.types.plugin.WorkflowRunFunction
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.runtime.types.plugin, so a change to llama-index-workflows.src.workflows.runtime.types.plugin can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.runtime.types.plugin.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types uses a module listed above it, which is the healthy direction.
40→36 llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.context.context✕
- Connections
- 1 pair of types, where a type in llama-index-workflows.src.workflows.runtime.types uses a type in llama-index-workflows.src.workflows.context.context.
- The types involved
packages.llama-index-workflows.src.workflows.runtime.types.step_function→packages.llama-index-workflows.src.workflows.context.context.Context
- Direction
- llama-index-workflows.src.workflows.runtime.types uses llama-index-workflows.src.workflows.context.context, so a change to llama-index-workflows.src.workflows.context.context can break llama-index-workflows.src.workflows.runtime.types, while a change to llama-index-workflows.src.workflows.runtime.types can't break llama-index-workflows.src.workflows.context.context.
- Position
- Below the diagonal: llama-index-workflows.src.workflows.runtime.types 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 76 | High / Critical |
| A05:2025 — Injection | 69 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 18 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED; Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, 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; Resolve the 1 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. | +4.9 pts | Low | Secret Scanning |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.5 pts | Low | License Compliance |
| Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, 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. | +2.7 pts | Medium | A11y enforcement |
| Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker. | +2.1 pts | Medium | Outbound HTTP resilience |
| 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. | +1.8 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. | +1.7 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.6 pts | Medium | Forms & labels |
| Interpolated log message defeats structured logging | +1.5 pts | Medium | Structured logging |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.2 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 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 — 76 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, 457 of 485 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 READ here — but this repository measures it: a coverage step in CI (`pytest --cov=src --cov`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.py, .go), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`, or `go test -coverprofile=coverage.out ./...`) 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 `go test -coverprofile=coverage.out ./...`) 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.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 Go module (REDACTED/go.sum), but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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. `packages/llama-agents-control-plane/src/llama_agents/control_plane/build_api/build_app.py`, `packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.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.
- D41 Kernel & Syscall Confinement — 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. Charts/llama-agents/templates/deployment.yaml:2, charts/llama-agents/templates/operator-deployment.yaml:3 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- 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 packages/llama-index-workflows/src/workflows/runtime/types/plugin.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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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) — ------ REDACTED:28 -------------------- 26 | 27 | # Copy workspace configuration files 28 | >>> COPY REDACTED REDACTED README.md ./ 29 | 30 | ENV PATH=/app/.venv/bin:$PATH -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 66afbee0-1385-4ea2-82b6-d9d9ca34ec36::zdc6h32p8s1g9dhpgonwpijd6: "/REDACTED": not found; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X3 Exception handling — 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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
- X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
- 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 (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
41 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was build.get_workflow_representation at 48. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being workflow._get_node_color at 17 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with build.get_workflow_representation (cyclomatic 48), pytest_cmd.pytest_cmd (cyclomatic 43), deployment_config.read_deployment_config (cyclomatic 41). — 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 5 together lifts Cyclomatic Complexity from 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
81 method(s) exceeded the cognitive complexity threshold of 15; the worst was build.get_workflow_representation at 99.
What to do
- Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with build.get_workflow_representation (cognitive 99), pytest_cmd.pytest_cmd (cognitive 91), deployment_config.read_deployment_config (cognitive 86). — 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 5 together lifts Cognitive Complexity from 5.2 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
16 god class(es) detected.
What to do
- Resolve the 12 FileTooLong finding(s) in God Classes — start with deployment.py, reduce.py, k8s_client.py. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
30 duplicated block group(s) detected. 1 of the 30 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with postgres_workflow_store.py, auth.py, deployment.py. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with storage.py, idle_release_runtime.py, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with deployments.py, deployment.py. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
21 production modules (npm+Go+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 12 of the 21 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
2 of 81 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with abstract_workflow_store.py, plugin.py. — One of this dimension's main actionable groups (2 warning-level).
D9 · Test Distribution
2911 test methods: 2702 unit, 206 integration, 0 BDD, 3 e2e. The Python suite contributes 2815 test function(s) across 210 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 96 test case(s) across 8 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Python (12 distributions): measured (0 flaky).
D12 · Dependency Hygiene
8 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
1 of 119 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 31 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (88 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 10 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares package.json and a Go module (REDACTED/go.sum), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py (6×32=192); packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py (8×24=192); packages/llama-agents-server/src/llama_agents/server/_service.py (4×17=68)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with runner.py, reduce.py, _service.py. — One of this dimension's main actionable groups (4 warning-level).
D16 · Bus Factor
60 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py. Counted over 148 of the 261 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
8 deducted task-comment markers across 51104 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with context.py (3), handler.py, types.py. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with options.py. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 65 document(s) read across 14 unit(s).
What to do
- Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 13 build units (Python, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
85 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
69 finding(s): 0 critical, 55 high, 11 medium, 3 low. 41 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 21 file(s) — `charts/llama-agents-crds/templates/crds.yaml`, `charts/llama-agents/templates/controlplane-hpa.yaml`, `charts/llama-agents/templates/controlplane-s3-secret.yaml`, `charts/llama-agents/templates/deployment.yaml`, `charts/llama-agents/templates/networkpolicy.yaml`, … (+16 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 41 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (43 issue-level, 2 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
6 finding(s): 1 critical, 4 high, 1 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
76 finding(s): 1 critical, 9 high, 54 medium, 12 low.
What to do
- Resolve the 54 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (24), REDACTED (22), REDACTED (4). — One of this dimension's main actionable groups (54 warning-level).
- Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
2 of 148 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/llama-index-workflows/src/workflows/testing/runner.py. Counted over 148 of the 261 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D40 · Network Egress Confinement
Kubernetes workloads are covered by a network policy that restricts egress.
D41 · Kernel & Syscall Confinement
0/2 workload(s) run every container under a seccomp profile; 0/2 declare an AppArmor/SELinux profile.
What to do
- Resolve the 2 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D42 · Runtime Threat Enforcement
0/2 runtime-enforcement controls present (threat detection, admission control).
What to do
- Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 No admission-control policy finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 31 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
AC1 · Text alternatives
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 for> 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. (×2) — docs/src/components/Header.astro:31, docs/src/components/Header.astro:32
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. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — packages/llama-agents-server/src/llama_agents/server/static/index.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.
AC6 · Visual & motion safety
- `.DocSearch-Input` 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. (×2) — docs/api_docs/docs/css/algolia.css:212, docs/api_docs/docs/api_reference/_static/css/algolia.css:192
- `.DocSearch-Cancel` 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. (×2) — docs/api_docs/docs/css/algolia.css:740, docs/api_docs/docs/api_reference/_static/css/algolia.css:644
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 (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 8 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. — package.json:11
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, 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
AX5 · Architecture & structure
AX8 · Test isolation
C2 · Access Controls
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 1 of 16 have no README of their own, in their folder or in their family's project (`operator`).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 10/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:11
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — REDACTED:397, REDACTED:421, REDACTED:446
What to do
- Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations
PF3 · Async & latency hygiene
- `async_main` is async and calls subprocess.run — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — examples/dbos/server_replicas.py:157
What to do
- Python: await the async equivalent (asyncio.sleep, an async HTTP client such as httpx.AsyncClient or aiohttp, asyncio.create_subprocess_exec), or move the blocking call off the loop with `await asyncio.to_thread(...)`; never call asyncio.run inside a coroutine — await the coroutine.
S1 · Web-Security Posture
- `https://cdn.jsdelivr.net/npm/@llamaindex/workflow-debugger@0.2.42/dist/app.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — packages/llama-agents-server/src/llama_agents/server/static/index.html:7
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
- The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception. (×5) — packages/llama-index-workflows/src/workflows/context/context.py:703, packages/llama-index-workflows/src/workflows/context/context.py:706, packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:170, …
What to do
- Task from `asyncio.create_task` is not kept
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `wait_for_event` is public, takes a document from its caller (line 216) and hands it to `normalize`, which calls itself at line 119 (`normalize`) with a piece of `value` (and at line 123, line 125, line 128) — and nowhere in `normalize` 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 `normalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/llama-index-workflows/src/workflows/context/internal_context.py:119
- `serialize_value` is public and takes `value: Any` from its caller, and it calls itself at line 227 (`self.serialize_value`) with a piece of `value` (and at line 230) — and nowhere in `serialize_value` 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 `serialize_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:227
- `deserialize_value` is public and takes `data: Any` from its caller, and it calls itself at line 270 (`self.deserialize_value`) with a piece of `data` (and at line 272) — and nowhere in `deserialize_value` 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 `deserialize_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:270
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
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
- `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. (×16) — src/dev_cli/commands/pytest_cmd.py:47, packages/llamactl/src/llama_agents/cli/client.py:93, packages/llamactl/src/llama_agents/cli/utils/version.py:10, …
- 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. (×21) — packages/llamactl/src/llama_agents/cli/client.py:195, packages/llamactl/src/llama_agents/cli/local_context.py:84, packages/llamactl/src/llama_agents/cli/config/auth_service.py:74, …
- `except (Exception, SystemExit)` 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. — packages/llamactl/src/llama_agents/cli/param_types.py:20
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. (×2) — packages/llamactl/src/llama_agents/cli/auth/client.py:90, packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:259
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warning` at line 884 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:884
- `error` at line 431 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_api.py:431
- `error` at line 449 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_api.py:449
- `info` at line 245 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/server.py:245
- `info` at line 190 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:190
- `info` at line 229 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:229
- `info` at line 246 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:246
- `error` at line 356 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_runtime/persistence_runtime.py:356
- `error` at line 406 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_runtime/persistence_runtime.py:406
- `error` at line 217 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-server/src/llama_agents/server/_runtime/server_runtime.py:217
- `warning` at line 95 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:95
- `info` at line 256 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:256
- `info` at line 283 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:283
- `warning` at line 285 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:285
- `warning` at line 320 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:320
- `debug` at line 325 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:325
- `warning` at line 330 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:330
- `warning` at line 399 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:399
- `debug` at line 411 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:411
- `debug` at line 418 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:418
- `info` at line 438 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:438
- `error` at line 692 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:692
- `warning` at line 1356 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:1356
- `error` at line 313 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:313
- `info` at line 471 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:471
- `debug` at line 527 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:527
- `debug` at line 540 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:540
- `error` at line 544 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:544
- `error` at line 548 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:548
- `debug` at line 609 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:609
- `info` at line 622 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:622
- `warning` at line 627 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:627
- `warning` at line 630 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:630
- `warning` at line 633 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:633
- `debug` at line 650 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:650
- `warning` at line 653 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:653
- `info` at line 665 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:665
- `debug` at line 668 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:668
- `info` at line 769 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:769
- `error` at line 932 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:932
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| 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 |
| 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 | 64% | Adequate | Acceptable, with room to improve. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 76% | Strong | Solid. |
| Readiness | 53% | Adequate — gated by D13, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 74% | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 53% | Adequate | Largest drag on the score — prioritise here. |
| Performance | 85% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 42 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 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 Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:28 -------------------- 26 | 27 | # Copy workspace configuration files 28 | >>> COPY REDACTED REDACTED README.md ./ 29 | 30 | ENV PATH=/app/.venv/bin:$PATH -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 66afbee0-1385-4ea2-82b6-d9d9ca34ec36::zdc6h32p8s1g9dhpgonwpijd6: "/REDACTED": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~66338 lines of test source are present (.py, .go) 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.
- 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; Go, JavaScript, Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python 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. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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 (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 143 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- 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.
- 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 was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 73 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: psycopg
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 322 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) packages/llamactl/src/llama_agents/cli/client.py:195
- Swallowed exception (empty catch) packages/llamactl/src/llama_agents/cli/local_context.py:84
- Swallowed exception (empty catch) packages/llamactl/src/llama_agents/cli/config/auth_service.py:74
- Swallowed exception (empty catch) packages/llamactl/src/llama_agents/cli/commands/auth.py:492
- Swallowed exception (empty catch) packages/llamactl/src/llama_agents/cli/auth/client.py:90
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/handler.py:217
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/handler.py:225
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/runtime/types/step_function.py:95
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/runtime/types/step_function.py:371
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/runtime/types/step_function.py:375
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py:421
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py:434
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py:626
- Swallowed exception (empty catch) packages/llama-index-workflows/src/workflows/context/internal_context.py:129
- Swallowed exception (empty catch) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:888
- Swallowed exception (empty catch) packages/llama-agents-server/src/llama_agents/server/_service.py:372
- Swallowed exception (empty catch) packages/llama-agents-server/src/llama_agents/server/_service.py:376
- Swallowed exception (empty catch) packages/llama-agents-server/src/llama_agents/server/_service.py:385
- Swallowed exception (empty catch) packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:259
- Swallowed exception (empty catch) packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:239
- Swallowed exception (empty catch) packages/llama-agents-server/src/llama_agents/server/_runtime/persistence_runtime.py:428
- Swallowed exception (empty catch) packages/llama-agents-core/src/llama_agents/core/iter_utils.py:141
- Swallowed exception (empty catch) packages/llama-agents-core/src/llama_agents/core/iter_utils.py:146
- Swallowed exception (caught, then discarded) src/dev_cli/commands/pytest_cmd.py:47
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/client.py:93
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/param_types.py:20
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/utils/version.py:10
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/commands/config.py:81
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/commands/environments.py:183
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/commands/init.py:201
- Swallowed exception (caught, then discarded) packages/llamactl/src/llama_agents/cli/auth/client.py:109
- Swallowed exception (caught, then discarded) packages/llama-index-workflows/src/workflows/_event_summary.py:58
- Swallowed exception (caught, then discarded) packages/llama-index-workflows/src/workflows/runtime/types/step_function.py:270
- Swallowed exception (caught, then discarded) packages/llama-index-workflows/src/workflows/runtime/types/step_function.py:439
- Swallowed exception (caught, then discarded) packages/llama-index-workflows/src/workflows/context/state_store.py:1502
- Swallowed exception (caught, then discarded) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:721
- Swallowed exception (caught, then discarded) packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:196
- Swallowed exception (caught, then discarded) packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:536
- Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/git/git_util.py:443
- Swallowed exception (caught, then discarded) packages/llama-agents-core/src/llama_agents/core/git/git_util.py:448
- FileTooLong: commands/deployment.py packages/llamactl/src/llama_agents/cli/commands/deployment.py
- FileTooLong: control_loop/reduce.py packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py
- FileTooLong: control_plane/k8s_client.py packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py
- FileTooLong: context/state_store.py packages/llama-index-workflows/src/workflows/context/state_store.py
- FileTooLong: dbos/runtime.py packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py
- FileTooLong: controller/resources.go operator/internal/controller/resources.go
- FileTooLong: types/internal_state.py packages/llama-index-workflows/src/workflows/runtime/types/internal_state.py
- FileTooLong: git/_git_service.py packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py
- FileTooLong: workflow/__init__.py packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py
- FileTooLong: server/_api.py packages/llama-agents-server/src/llama_agents/server/_api.py
- FileTooLong: commands/auth.py packages/llamactl/src/llama_agents/cli/commands/auth.py
- FileTooLong: REDACTED REDACTED
- TodoComment packages/llama-index-workflows/src/workflows/handler.py:50
- TodoComment packages/llama-index-workflows/src/workflows/types.py:11
- TodoComment packages/llama-index-workflows/src/workflows/workflow.py:434
- TodoComment packages/llama-index-workflows/src/workflows/context/context.py:57
- TodoComment packages/llama-index-workflows/src/workflows/context/context.py:310
- TodoComment packages/llama-index-workflows/src/workflows/context/context.py:320
- TodoComment REDACTED:167
- Focus outline removed in CSS without a :focus replacement docs/api_docs/docs/css/algolia.css:212
- Focus outline removed in CSS without a :focus replacement docs/api_docs/docs/css/algolia.css:740
- Focus outline removed in CSS without a :focus replacement docs/api_docs/docs/api_reference/_static/css/algolia.css:192
- Focus outline removed in CSS without a :focus replacement docs/api_docs/docs/api_reference/_static/css/algolia.css:644
- Hotspot: packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py:440
- Hotspot: packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:827
- Hotspot: packages/llama-agents-server/src/llama_agents/server/_service.py packages/llama-agents-server/src/llama_agents/server/_service.py:192
- Hotspot: packages/llama-agents-client/src/llama_agents/client/protocol/serializable_events.py packages/llama-agents-client/src/llama_agents/client/protocol/serializable_events.py:130
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:656
- Duplicated block (8 lines × 2) packages/llamactl/src/llama_agents/cli/commands/auth.py:623
- Duplicated block (8 lines × 2) packages/llamactl/src/llama_agents/cli/commands/deployment.py:189
- Duplicated block (8 lines × 2) examples/client/base/workflow_server.py:35
- Off the main sequence: llama-agents-operator (npm)
- Off the main sequence: llama-agents-core
- Off the main sequence: llama-index-workflows (npm)
- Off the main sequence: llama-agents-appserver (npm)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) packages/llama-agents-control-plane/src/llama_agents/control_plane/backup/storage.py:37
- Duplicated block (9 lines × 2) packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:151
- Duplicated block (9 lines × 2) REDACTED:48
- Outbound HTTP without resilience REDACTED:397
- Outbound HTTP without resilience REDACTED:421
- Outbound HTTP without resilience REDACTED:446
- Recursive walk over a caller-supplied document has no depth cap packages/llama-index-workflows/src/workflows/context/internal_context.py:119
- Recursive walk over a caller-supplied document has no depth cap REDACTED:227
- Recursive walk over a caller-supplied document has no depth cap REDACTED:270
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: main.main REDACTED:66
- FunctionTooLong: ProtectedContent.ProtectedContent REDACTED:6
- Duplicated block (13 lines × 2) packages/llama-agents-appserver/src/llama_agents/appserver/routers/deployments.py:48
- Duplicated block (13 lines × 2) packages/llamactl/src/llama_agents/cli/commands/deployment.py:992
- Duplicated block (12 lines × 2) packages/llama-index-workflows/src/workflows/runtime/types/internal_state.py:334
- Duplicated block (12 lines × 2) packages/llamactl/src/llama_agents/cli/commands/pkg.py:56
- Duplicated block (8–9 lines × 2) packages/llama-agents-control-plane/src/llama_agents/control_plane/backup/storage.py:75
- Duplicated block (8–9 lines × 2) src/dev_cli/commands/pytest_cmd.py:416
- Duplicated block (7 lines × 2) packages/llama-agents-core/src/llama_agents/core/schema/deployments.py:224
- Duplicated block (7 lines × 2) REDACTED:41
- Duplicated block (5 lines × 2) packages/llama-agents-dbos/src/llama_agents/dbos/journal/crud.py:21
- Duplicated block (5 lines × 2) operator/internal/controller/resources.go:498
- Low cohesion: AbstractWorkflowStore (LCOM4 4) packages/llama-agents-server/src/llama_agents/server/_store/abstract_workflow_store.py:118
- Low cohesion: Runtime (LCOM4 4) packages/llama-index-workflows/src/workflows/runtime/types/plugin.py:494
- Task from `asyncio.create_task` is not kept packages/llama-index-workflows/src/workflows/context/context.py:703
- Task from `asyncio.create_task` is not kept packages/llama-agents-core/src/llama_agents/core/iter_utils.py:174
- Task from `asyncio.ensure_future` is not kept packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:170
- Task from `asyncio.ensure_future` is not kept packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:187
- <ThemeSelect> field component without a label docs/src/components/Header.astro:31
- <LanguageSelect> field component without a label docs/src/components/Header.astro:32
- Page without a main landmark packages/llama-agents-server/src/llama_agents/server/static/index.html:2
- Accessibility enforcement below the top rung package.json:11
- build.get_workflow_representation (cyclomatic 48) packages/llama-index-workflows/src/workflows/representation/build.py:167
- pytest_cmd.pytest_cmd (cyclomatic 43) src/dev_cli/commands/pytest_cmd.py:459
- deployment_config.read_deployment_config (cyclomatic 41) packages/llama-agents-core/src/llama_agents/core/deployment_config.py:29
- init._create (cyclomatic 33) packages/llamactl/src/llama_agents/cli/commands/init.py:66
- _ControlLoopRunner.run (cyclomatic 32) packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py:440
- LlamaDeploymentReconciler.Reconcile (cyclomatic 30) REDACTED:244
- LlamaDeploymentReconciler.reconcileBuild (cyclomatic 27) operator/internal/controller/resources.go:431
- GitService._check_github_access_type (cyclomatic 26) packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:251
- deployment._execute_deployment_operation (cyclomatic 26) packages/llamactl/src/llama_agents/cli/commands/deployment.py:1120
- main.main (cyclomatic 26) REDACTED:66
- LlamaDeploymentReconciler.determineDeploymentPhase (cyclomatic 26) REDACTED:237
- LlamaDeploymentReconciler.scaleDownFailingReplicaSet (cyclomatic 26) REDACTED:494
- LlamaDeploymentReconciler.applyTemplateOverlay (cyclomatic 26) operator/internal/controller/resources.go:1286
- reduce._apply_step_result (cyclomatic 24) packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:827
- LlamaDeploymentReconciler.applyBuildJobTemplateOverlay (cyclomatic 24) operator/internal/controller/resources.go:666
- DeploymentService.update_deployment (cyclomatic 23) packages/llama-agents-control-plane/src/llama_agents/control_plane/manage_api/deployments_service.py:290
- EventEnvelope.parse (cyclomatic 22) packages/llama-agents-client/src/llama_agents/client/protocol/serializable_events.py:130
- iter_utils.merge_generators (cyclomatic 22) packages/llama-agents-core/src/llama_agents/core/iter_utils.py:56
- utils.inspect_signature (cyclomatic 22) packages/llama-index-workflows/src/workflows/utils.py:63
- auth._run_device_authentication (cyclomatic 22) packages/llamactl/src/llama_agents/cli/commands/auth.py:436
- LlamaDeploymentReconciler.SetupWithManager (cyclomatic 21) REDACTED:629
- GitService._validate_github_application (cyclomatic 20) packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:697
- projects.use_project (cyclomatic 20) packages/llamactl/src/llama_agents/cli/commands/projects.py:95
- interactive._blessed_select (cyclomatic 20) packages/llamactl/src/llama_agents/cli/interactive.py:66
- deployments.apply_deployment_update (cyclomatic 19) packages/llama-agents-core/src/llama_agents/core/schema/deployments.py:431
- validate.build_step_graph (cyclomatic 19) packages/llama-index-workflows/src/workflows/representation/validate.py:57
- validate._validate_event_connectivity (cyclomatic 19) packages/llama-index-workflows/src/workflows/representation/validate.py:340
- workflow._render_pyvis (cyclomatic 18) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:108
- LlamaDeploymentReconciler.initializeStatus (cyclomatic 18) REDACTED:359
- build_gc._get_referenced_build_ids_from_replicasets (cyclomatic 17) packages/llama-agents-control-plane/src/llama_agents/control_plane/build_api/build_gc.py:26
- _WorkflowService.cancel_handler (cyclomatic 17) packages/llama-agents-server/src/llama_agents/server/_service.py:192
- pytest_cmd.extract_failed_test_names (cyclomatic 17) src/dev_cli/commands/pytest_cmd.py:118
- GitService.validate_repository (cyclomatic 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:135
- k8s_client._llamadeployment_to_response (cyclomatic 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:965
- DeploymentService.create_deployment (cyclomatic 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/manage_api/deployments_service.py:153
- git_util.clone_repo_sync (cyclomatic 16) packages/llama-agents-core/src/llama_agents/core/git/git_util.py:263
- _catch_error._collect_catch_error_handlers (cyclomatic 16) packages/llama-index-workflows/src/workflows/_catch_error.py:61
- validate.validate_graph (cyclomatic 16) packages/llama-index-workflows/src/workflows/representation/validate.py:162
- utils._event_list_element_types (cyclomatic 16) packages/llama-index-workflows/src/workflows/utils.py:199
- serve._maybe_inject_llama_cloud_credentials (cyclomatic 16) packages/llamactl/src/llama_agents/cli/commands/serve.py:208
- yaml_template.render (cyclomatic 16) packages/llamactl/src/llama_agents/cli/yaml_template.py:77
- HackComment packages/llamactl/src/llama_agents/cli/pkg/options.py:10
- build.get_workflow_representation (cognitive 99) packages/llama-index-workflows/src/workflows/representation/build.py:167
- pytest_cmd.pytest_cmd (cognitive 91) src/dev_cli/commands/pytest_cmd.py:459
- deployment_config.read_deployment_config (cognitive 86) packages/llama-agents-core/src/llama_agents/core/deployment_config.py:29
- _ControlLoopRunner.run (cognitive 71) packages/llama-index-workflows/src/workflows/runtime/control_loop/runner.py:440
- init._create (cognitive 65) packages/llamactl/src/llama_agents/cli/commands/init.py:66
- utils.inspect_signature (cognitive 47) packages/llama-index-workflows/src/workflows/utils.py:63
- LlamaDeploymentReconciler.applyTemplateOverlay (cognitive 46) operator/internal/controller/resources.go:1286
- iter_utils.merge_generators (cognitive 43) packages/llama-agents-core/src/llama_agents/core/iter_utils.py:56
- reduce._apply_step_result (cognitive 43) packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:827
- LlamaDeploymentReconciler.reconcileBuild (cognitive 42) operator/internal/controller/resources.go:431
- LlamaDeploymentReconciler.scaleDownFailingReplicaSet (cognitive 39) REDACTED:494
- workflow._render_pyvis (cognitive 38) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:108
- LlamaDeploymentReconciler.Reconcile (cognitive 36) REDACTED:244
- deployment._execute_deployment_operation (cognitive 35) packages/llamactl/src/llama_agents/cli/commands/deployment.py:1120
- interactive._blessed_select (cognitive 35) packages/llamactl/src/llama_agents/cli/interactive.py:66
- pytest_cmd.extract_failed_test_names (cognitive 35) src/dev_cli/commands/pytest_cmd.py:118
- LlamaDeploymentReconciler.initializeStatus (cognitive 35) REDACTED:359
- LlamaDeploymentReconciler.applyBuildJobTemplateOverlay (cognitive 34) operator/internal/controller/resources.go:666
- EventEnvelope.parse (cognitive 33) packages/llama-agents-client/src/llama_agents/client/protocol/serializable_events.py:130
- validate._validate_event_connectivity (cognitive 33) packages/llama-index-workflows/src/workflows/representation/validate.py:340
- auth._run_device_authentication (cognitive 33) packages/llamactl/src/llama_agents/cli/commands/auth.py:436
- main.main (cognitive 33) REDACTED:66
- projects.use_project (cognitive 30) packages/llamactl/src/llama_agents/cli/commands/projects.py:95
- build_gc._get_referenced_build_ids_from_replicasets (cognitive 29) packages/llama-agents-control-plane/src/llama_agents/control_plane/build_api/build_gc.py:26
- GitService._check_github_access_type (cognitive 28) packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:251
- validate.build_step_graph (cognitive 28) packages/llama-index-workflows/src/workflows/representation/validate.py:57
- validate.validate_graph (cognitive 28) packages/llama-index-workflows/src/workflows/representation/validate.py:162
- DeploymentService.stream_deployment_logs (cognitive 27) packages/llama-agents-control-plane/src/llama_agents/control_plane/manage_api/deployments_service.py:480
- process_utils._stream_source (cognitive 26) packages/llama-agents-appserver/src/llama_agents/appserver/process_utils.py:180
- reduce._route_to_accepting_steps (cognitive 26) packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:1639
- DeploymentService.update_deployment (cognitive 25) packages/llama-agents-control-plane/src/llama_agents/control_plane/manage_api/deployments_service.py:290
- _WorkflowService.cancel_handler (cognitive 25) packages/llama-agents-server/src/llama_agents/server/_service.py:192
- _catch_error._collect_catch_error_handlers (cognitive 25) packages/llama-index-workflows/src/workflows/_catch_error.py:61
- utils._event_list_element_types (cognitive 25) packages/llama-index-workflows/src/workflows/utils.py:199
- LlamaDeploymentReconciler.checkSecretExists (cognitive 25) REDACTED:153
- BackupService._restore_entries (cognitive 24) packages/llama-agents-control-plane/src/llama_agents/control_plane/manage_api/backup_service.py:168
- deployments.apply_deployment_update (cognitive 24) packages/llama-agents-core/src/llama_agents/core/schema/deployments.py:431
- skills_cmd.sync_skills (cognitive 24) src/dev_cli/commands/skills_cmd.py:30
- LlamaDeploymentReconciler.SetupWithManager (cognitive 24) REDACTED:629
- GitService._validate_github_application (cognitive 23) packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:697
- memory_workflow_store._matches_query (cognitive 23) packages/llama-agents-server/src/llama_agents/server/_store/memory_workflow_store.py:28
- k8s_client.update_deployment (cognitive 22) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:673
- workflow._process_tools_and_handoffs (cognitive 22) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:382
- LlamaDeploymentReconciler.determineDeploymentPhase (cognitive 22) REDACTED:237
- PersistenceDecorator._on_server_start (cognitive 21) packages/llama-agents-server/src/llama_agents/server/_runtime/persistence_runtime.py:329
- SerializedContext.from_v0 (cognitive 21) packages/llama-index-workflows/src/workflows/context/context_types.py:267
- internal_state._load_broker_from_serialized (cognitive 21) packages/llama-index-workflows/src/workflows/runtime/types/internal_state.py:475
- serve._maybe_inject_llama_cloud_credentials (cognitive 21) packages/llamactl/src/llama_agents/cli/commands/serve.py:208
- yaml_template.render (cognitive 21) packages/llamactl/src/llama_agents/cli/yaml_template.py:77
- controller.classifyPod (cognitive 21) REDACTED:458
- bootstrap.bootstrap_app_from_repo (cognitive 20) packages/llama-agents-appserver/src/llama_agents/appserver/bootstrap.py:210
- LlamaDeploymentReconciler.deleteOwnedResources (cognitive 20) REDACTED:490
- build_gc.gc_build_artifacts (cognitive 19) packages/llama-agents-control-plane/src/llama_agents/control_plane/build_api/build_gc.py:53
- GitService.validate_repository (cognitive 19) packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:135
- migrate.run_migrations (cognitive 19) packages/llama-agents-server/src/llama_agents/server/_store/sqlite/migrate.py:58
- JsonSerializer.__init__ (cognitive 19) REDACTED:109
- LlamaDeploymentReconciler.createDeploymentForLlama (cognitive 19) operator/internal/controller/resources.go:1049
- ui_proxy._ws_proxy (cognitive 18) packages/llama-agents-appserver/src/llama_agents/appserver/routers/ui_proxy.py:33
- workflow_loader._install_and_add_appserver_if_missing (cognitive 18) packages/llama-agents-appserver/src/llama_agents/appserver/workflow_loader.py:355
- k8s_client._llamadeployment_to_response (cognitive 18) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:965
- DeploymentService.rollback_deployment (cognitive 18) packages/llama-agents-control-plane/src/llama_agents/control_plane/manage_api/deployments_service.py:255
- workflow._get_workflow_classes_from_step (cognitive 18) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:540
- controller.isValidDNS1035Label (cognitive 18) operator/internal/controller/resources.go:339
- ProjectClient.stream_deployment_logs (cognitive 17) packages/llama-agents-core/src/llama_agents/core/client/manage_client.py:301
- git_util.clone_repo_sync (cognitive 17) packages/llama-agents-core/src/llama_agents/core/git/git_util.py:263
- DBOSRuntime._prepare_launch (cognitive 17) packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:851
- DBOSRuntime.destroy (cognitive 17) packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:1034
- SqliteWorkflowStore._build_filters (cognitive 17) packages/llama-agents-server/src/llama_agents/server/_store/sqlite/sqlite_workflow_store.py:356
- _catch_error.validate_catch_error_handlers (cognitive 17) packages/llama-index-workflows/src/workflows/_catch_error.py:12
- state_store.decode_state (cognitive 17) packages/llama-index-workflows/src/workflows/context/state_store.py:297
- state_store.apply_state_patch (cognitive 17) packages/llama-index-workflows/src/workflows/context/state_store.py:1679
- reduce._claim_emission (cognitive 17) packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:395
- projects.get_projects (cognitive 17) packages/llamactl/src/llama_agents/cli/commands/projects.py:42
- pytest_cmd._run_tests_verbose (cognitive 17) src/dev_cli/commands/pytest_cmd.py:387
- WorkflowClient.wait_for_handler (cognitive 16) packages/llama-agents-client/src/llama_agents/client/client.py:553
- k8s_client._create_k8s_secret (cognitive 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:490
- k8s_client._create_ingress (cognitive 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:552
- k8s_client._list_replicasets_for_deployment_sync (cognitive 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:1068
- k8s_client.get_replicaset_pods_for_deployment (cognitive 16) packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:1163
- workflow._render_mermaid (cognitive 16) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:248
- workflow._get_nested_workflow_representation (cognitive 16) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:594
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: LlamaDeploymentReconciler REDACTED:115
- MethodTooLong: LlamaDeploymentReconciler.createDeploymentForLlama operator/internal/controller/resources.go:1049
- REDACTED
- REDACTED
- Duplicated block (61–64 lines × 2) packages/llama-agents-server/src/llama_agents/server/_api.py:367
- Duplicated block (35 lines × 2) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:49
- Duplicated block (25 lines × 2) packages/llama-agents-client/src/llama_agents/client/client.py:286
- Duplicated block (22–23 lines × 2) packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:634
- Duplicated block (18 lines × 2) packages/llama-agents-server/src/llama_agents/server/_store/postgres_workflow_store.py:512
- Duplicated block (16 lines × 2) packages/llama-index-workflows/src/workflows/representation/build.py:319
- Duplicated block (14–16 lines × 2) packages/llamactl/src/llama_agents/cli/auth/client.py:279
- Duplicated block (14 lines × 2) packages/llama-index-workflows/src/workflows/representation/validate.py:278
- Duplicated block (5 lines × 3) packages/llama-agents-server/src/llama_agents/server/_store/memory_workflow_store.py:141
- Duplicated block (28 lines × 2) REDACTED:659
- Duplicated block (12–13 lines × 2) operator/internal/controller/resources.go:667
- Duplicated block (9–11 lines × 2) operator/internal/controller/resources.go:928
- Duplicated block (10 lines × 2) operator/internal/controller/resources.go:817
- Coverage collected but not gated
- Sync-over-async blocking examples/dbos/server_replicas.py:157
- Third-party script without Subresource Integrity packages/llama-agents-server/src/llama_agents/server/static/index.html:7
- Task from `loop.create_task` is not kept packages/llama-index-workflows/src/workflows/context/context.py:706
Minor — 82 finding(s)
- Interpolated log message defeats structured logging packages/llama-index-workflows/src/workflows/runtime/control_loop/reduce.py:884
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_api.py:431
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_api.py:449
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/server.py:245
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:190
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:229
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_runtime/idle_release_runtime.py:246
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_runtime/persistence_runtime.py:356
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_runtime/persistence_runtime.py:406
- Interpolated log message defeats structured logging packages/llama-agents-server/src/llama_agents/server/_runtime/server_runtime.py:217
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:95
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:256
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:283
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:285
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:320
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:325
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:330
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:399
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:411
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:418
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/idle_release.py:438
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:692
- Interpolated log message defeats structured logging packages/llama-agents-dbos/src/llama_agents/dbos/runtime.py:1356
- Interpolated log message defeats structured logging packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:313
- Interpolated log message defeats structured logging packages/llama-agents-control-plane/src/llama_agents/control_plane/k8s_client.py:471
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Documentation: no build, run or usage example packages/llama-agents-appserver/README.md:1
- Documentation: no build, run or usage example packages/llama-agents-control-plane/README.md:1
- Documentation: no build, run or usage example packages/llama-agents-core/README.md:1
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py:669
- Duplicated predicate packages/llama-agents-control-plane/src/llama_agents/control_plane/backup/storage.py:78
- Duplicated predicate packages/llama-index-workflows/src/workflows/_catch_error.py:81
- Silent fallback default in catch packages/llama-agents-agentcore/src/llama_agents/agentcore/deploy.py:627
- Silent fallback default in catch packages/llama-agents-core/src/llama_agents/core/client/manage_client.py:177
- Silent fallback default in catch packages/llama-index-utils-workflow/src/llama_index/utils/workflow/__init__.py:587
- Orphaned file packages/llama-index-workflows/src/workflows/testing/runner.py:1
- Orphaned file packages/llama-index-workflows/src/workflows/_event_matching.py:1
- No seccomp profile REDACTED:5
- No seccomp profile REDACTED:2
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No runtime threat detection
- No admission-control policy
- No ADRs
- Logging is not universal
- No dependency-update automation package.json:11
Minor — 8 finding(s)
- Outdated: github.com/onsi/ginkgo/v2
- Outdated: github.com/onsi/gomega
- Outdated: github.com/prometheus/client_golang
- Outdated: github.com/prometheus/client_model
- Outdated: k8s.io/api
- Outdated: k8s.io/apimachinery
- Outdated: k8s.io/client-go
- Outdated: sigs.k8s.io/controller-runtime
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-6ca0cf978d3d4212b9ec935754b4a4ea/history.json --exit-code 0 --source . | 2 | 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-6ca0cf978d3d4212b9ec935754b4a4ea/tree.json --exit-code 0 --source . | 2 | 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 . | 69 | 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/** . | 6 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 76 | 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 2 file(s) — `packages/llama-agents-control-plane/src/llama_agents/control_plane/build_api/build_app.py`, `packages/llama-agents-control-plane/src/llama_agents/control_plane/git/_git_service.py` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| 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 |