Executive summary
teaql/teaql-agent-kit falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 52 out of 100 and is rated Adequate, and ten of its 14 critical findings are security problems.
Production Readiness, at 31, is the weakest lens and counts most in the score. The best first steps are adding an automated build and test pipeline and adding automated security scanning, each worth about 5 points. Raising Production Readiness to 70 would lift the score to about 69.
Nine passwords or keys are open to anyone who can read the repository. One known security hole in a package the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks. The four uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 5,520 lines, about €8,700 to rebuild.
If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 52 to about 69.
New since the last survey: 116 findings
- Cyclomatic Complexity · context-markers.loadPlan (cyclomatic 35) packages/agent-context-kit/src/context-markers.ts
- Cyclomatic Complexity · pi-policy-feedback.registerPiPolicyFeedback (cyclomatic 35) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts
- Cyclomatic Complexity · FileAccessPolicy.checkMutation (cyclomatic 32) packages/agent-context-kit/src/file-policy.ts
- Cyclomatic Complexity · controlled-tasks.renderDiagnostics.diagnostics (cyclomatic 27) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · pi-progress.registerPiProgressRecovery (cyclomatic 25) packages/agent-context-kit/src/adapters/pi-progress.ts
- Cyclomatic Complexity · pi-completion.createPiCompletionGuard (cyclomatic 25) packages/agent-context-kit/src/adapters/pi-completion.ts
- Cyclomatic Complexity · pi-host-tools.loadPiHostTools (cyclomatic 25) packages/agent-context-kit/src/adapters/pi-host-tools.ts
- Cyclomatic Complexity · model_provenance.codex_actor (cyclomatic 24) skills/build-teaql-app/scripts/model_provenance.py
- Cyclomatic Complexity · TaskProtocol.parse (cyclomatic 23) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · ContextFiles.grep (cyclomatic 21) REDACTED
- Cyclomatic Complexity · controlled-tasks.runControlledTask (cyclomatic 21) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · pi-cli.createPiContextMutationTools (cyclomatic 21) packages/agent-context-kit/src/adapters/pi-cli.ts
- Cyclomatic Complexity · createTeaqlTools::execute (cyclomatic 21) integrations/pi-teaql/tools.mjs
- Cyclomatic Complexity · controlled-tasks.snapshotTaskCommand (cyclomatic 20) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · agent_context_kit._pre_tool_call (cyclomatic 18) packages/agent-context-kit/integrations/hermes/agent_context_kit.py
- Cyclomatic Complexity · context-access.checkContextAccess (cyclomatic 17) packages/agent-context-kit/src/context-access.ts
- Cyclomatic Complexity · context-loading.loadContextPolicyFiles (cyclomatic 17) packages/agent-context-kit/src/context-loading.ts
- Cyclomatic Complexity · context-read.inspectContextRead (cyclomatic 17) packages/agent-context-kit/src/context-read.ts
- Cyclomatic Complexity · parser.parseMarkdown (cyclomatic 17) packages/agent-context-kit/src/parser.ts
- Cyclomatic Complexity · opencode-context.createOpenCodeContextPolicyTools (cyclomatic 17) packages/agent-context-kit/src/adapters/opencode-context.ts
- Cyclomatic Complexity · opencode-context.createOpenCodeContextPolicyPlugin.setup (cyclomatic 17) packages/agent-context-kit/src/adapters/opencode-context.ts
- Cyclomatic Complexity · main._policy_map (cyclomatic 17) REDACTED
- Cyclomatic Complexity · agent_context_kit._load_guard (cyclomatic 16) packages/agent-context-kit/integrations/hermes/agent_context_kit.py
- Cognitive Complexity · FileAccessPolicy.checkMutation (cognitive 48) packages/agent-context-kit/src/file-policy.ts
- Cognitive Complexity · pi-policy-feedback.registerPiPolicyFeedback (cognitive 40) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts
- Cognitive Complexity · model_provenance.codex_actor (cognitive 34) skills/build-teaql-app/scripts/model_provenance.py
- Cognitive Complexity · ContextFiles.grep (cognitive 33) REDACTED
- Cognitive Complexity · controlled-tasks.runControlledTask (cognitive 33) packages/agent-context-kit/src/controlled-tasks.ts
- Cognitive Complexity · parser.parseMarkdown (cognitive 33) packages/agent-context-kit/src/parser.ts
- Cognitive Complexity · context-loading.loadContextPolicyFiles (cognitive 31) packages/agent-context-kit/src/context-loading.ts
- Cognitive Complexity · pi-completion.createPiCompletionGuard (cognitive 31) packages/agent-context-kit/src/adapters/pi-completion.ts
- Cognitive Complexity · createTeaqlTools::execute (cognitive 31) integrations/pi-teaql/tools.mjs
- Cognitive Complexity · agent_context_kit._pre_tool_call (cognitive 30) packages/agent-context-kit/integrations/hermes/agent_context_kit.py
- Cognitive Complexity · context-markers.loadPlan (cognitive 29) packages/agent-context-kit/src/context-markers.ts
- Cognitive Complexity · OctopContextMiddleware._project (cognitive 29) REDACTED
- Cognitive Complexity · pi-host-tools.loadPiHostTools (cognitive 25) packages/agent-context-kit/src/adapters/pi-host-tools.ts
- Cognitive Complexity · controlled-tasks.renderDiagnostics.diagnostics (cognitive 24) packages/agent-context-kit/src/controlled-tasks.ts
- Cognitive Complexity · context-read.inspectContextRead (cognitive 24) packages/agent-context-kit/src/context-read.ts
- Cognitive Complexity · agent_context_kit._parse_source (cognitive 24) packages/agent-context-kit/integrations/hermes/agent_context_kit.py
- Cognitive Complexity · main._policy_map (cognitive 24) REDACTED
- Cognitive Complexity · context-markers.validateTargets (cognitive 23) packages/agent-context-kit/src/context-markers.ts
- Cognitive Complexity · OctopContextMiddleware.before_model (cognitive 22) REDACTED
- Cognitive Complexity · opencode-context.createOpenCodeContextPolicyTools (cognitive 21) packages/agent-context-kit/src/adapters/opencode-context.ts
- Cognitive Complexity · parseRustMakeOutput (cognitive 21) integrations/pi-teaql/rust-make.mjs
- Cognitive Complexity · context-markers.applyPlan (cognitive 20) packages/agent-context-kit/src/context-markers.ts
- Cognitive Complexity · pi-cli.createPiContextMutationTools (cognitive 20) packages/agent-context-kit/src/adapters/pi-cli.ts
- Cognitive Complexity · pi-progress.registerPiProgressRecovery (cognitive 19) packages/agent-context-kit/src/adapters/pi-progress.ts
- Cognitive Complexity · TaskProtocol.parse (cognitive 18) packages/agent-context-kit/src/controlled-tasks.ts
- Cognitive Complexity · controlled-tasks.snapshotTaskCommand (cognitive 18) packages/agent-context-kit/src/controlled-tasks.ts
- Cognitive Complexity · opencode-context.createOpenCodeContextPolicyPlugin.setup (cognitive 18) packages/agent-context-kit/src/adapters/opencode-context.ts
- Cognitive Complexity · context-access.checkContextAccess (cognitive 17) packages/agent-context-kit/src/context-access.ts
- Cognitive Complexity · read-guard.pathInputs (cognitive 17) packages/agent-context-kit/src/read-guard.ts
- Cognitive Complexity · LifecycleSession.buildContextView (cognitive 17) packages/agent-context-kit/src/session.ts
- Cognitive Complexity · agent_context_kit._load_guard (cognitive 16) packages/agent-context-kit/integrations/hermes/agent_context_kit.py
- Cognitive Complexity · policy.read_denial (cognitive 16) packages/agent-context-kit/integrations/octop/policy.py
- God Classes · FunctionTooLong: parser.parseMarkdown packages/agent-context-kit/src/parser.ts
- God Classes · FunctionTooLong: pi-runtime-trace.runPiRuntimeTrace packages/agent-context-kit/scripts/pi-runtime-trace.ts
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Code Duplication · Duplicated block (41 lines × 2 locations) packages/agent-context-kit/src/adapters/mimocode.ts
- Code Duplication · Duplicated block (16 lines × 2 locations) packages/agent-context-kit/src/adapters/mimocode.ts
- Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/agent-context-kit/scripts/build-command-hook.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/agent-context-kit/src/adapters/pi.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) packages/agent-context-kit/src/adapters/workspace-runtime.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/agent-context-kit/src/session.ts
- Code Duplication · Duplicated block (7 lines × 3 locations) packages/agent-context-kit/src/adapters/deepseek-harness.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) packages/agent-context-kit/src/adapters/deepseek-harness.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) packages/agent-context-kit/src/adapters/mimocode.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) packages/agent-context-kit/src/adapters/pi-cli.ts
- Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/agent-context-kit/src/adapters/cline.ts
- Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) packages/agent-context-kit/src/adapters/pi-completion.ts
- Import Boundaries · Boundary violation [package:test-cross-package-internals] tests/context-runtime/skill-contract.test.mjs
- Cyclomatic Complexity · Complex function checkMutation (cyclomatic 32, cognitive 50) packages/agent-context-kit/src/file-policy.ts
- Cyclomatic Complexity · Complex function loadPlan (cyclomatic 28, cognitive 31) packages/agent-context-kit/src/context-markers.ts
- Cyclomatic Complexity · Complex function loadPiHostTools (cyclomatic 25, cognitive 27) packages/agent-context-kit/src/adapters/pi-host-tools.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 30) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 25) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · Complex function parse (cyclomatic 23, cognitive 19) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · Complex function grep (cyclomatic 21, cognitive 35) REDACTED
- Cyclomatic Complexity · Complex function execute (cyclomatic 21, cognitive 31) integrations/pi-teaql/tools.mjs
- Cyclomatic Complexity · Complex function snapshotTaskCommand (cyclomatic 21, cognitive 22) packages/agent-context-kit/src/controlled-tasks.ts
- Cyclomatic Complexity · Complex function parseMarkdown (cyclomatic 18, cognitive 34) packages/agent-context-kit/src/parser.ts
- Cyclomatic Complexity · Complex function loadContextPolicyFiles (cyclomatic 17, cognitive 31) packages/agent-context-kit/src/context-loading.ts
- Cyclomatic Complexity · Complex function inspectContextRead (cyclomatic 17, cognitive 24) packages/agent-context-kit/src/context-read.ts
- Cyclomatic Complexity · Complex function checkContextAccess (cyclomatic 16, cognitive 17) packages/agent-context-kit/src/context-access.ts
- Cyclomatic Complexity · Complex function parseReadGuardConfig (cyclomatic 14, cognitive 11) packages/agent-context-kit/src/read-guard.ts
- Cyclomatic Complexity · Complex function applyPlan (cyclomatic 13, cognitive 21) packages/agent-context-kit/src/context-markers.ts
- Cyclomatic Complexity · Complex function execute (cyclomatic 13, cognitive 14) packages/agent-context-kit/src/adapters/opencode-context.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 14) packages/agent-context-kit/src/adapters/pi-completion.ts
- Cyclomatic Complexity · Complex function evaluate (cyclomatic 13, cognitive 12) packages/agent-context-kit/src/read-guard.ts
- Cyclomatic Complexity · Complex function handleCommandHook (cyclomatic 13, cognitive 10) packages/agent-context-kit/src/adapters/command-hook.ts
- Test Coverage · No test reaches this file packages/agent-context-kit/scripts/build-command-hook.ts
- Test Coverage · No test reaches this file packages/agent-context-kit/src/adapters/gemini-cli-hook.ts
- Test Coverage · No test reaches this file packages/agent-context-kit/scripts/pi-context-cli.mjs
Fixed since the last survey: 1 finding
- Cognitive Complexity · teaql_workspace.resolve (cognitive 24) tools/teaql_workspace.py
Rebuild cost: about €8,700 · Estimate
| Cost to rebuild | €2,900 to €14,000, for 48 to 153 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,520 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 integrations.pi-teaql | 2 packages.agent-context-kit.integrations.hermes.agent_context_kit | 3 packages.agent-context-kit.integrations.octop.main | 4 packages.agent-context-kit.scripts.pi-runtime-trace | 5 packages.agent-context-kit.src.adapters.command-hook | 6 packages.agent-context-kit.src.adapters.pi-cli | 7 packages.agent-context-kit.src.adapters.pi-progress | 8 packages.agent-context-kit.src.context-access | 9 packages.agent-context-kit.src.context-read | 10 packages.agent-context-kit.src.controlled-tasks | 11 packages.agent-context-kit.src.parser | 12 packages.agent-context-kit.src.read-guard | 13 packages.agent-context-kit.src.types | 14 skills.build-teaql-app.scripts | 15 tools | 16 packages.agent-context-kit.integrations.hermes | 17 packages.agent-context-kit.integrations.octop | 18 packages.agent-context-kit.src.adapters.cline | 19 packages.agent-context-kit.src.adapters.gemini-cli | 20 packages.agent-context-kit.src.adapters.mimocode | 21 packages.agent-context-kit.src.adapters.opencode | 22 packages.agent-context-kit.src.adapters.opencode-context | 23 packages.agent-context-kit.src.adapters.pi-context | 24 packages.agent-context-kit.src.context-files | 25 packages.agent-context-kit.src.context-markers | 26 packages.agent-context-kit.src.file-policy | 27 packages.agent-context-kit.src.session | 28 packages.agent-context-kit.src | 29 packages.agent-context-kit.src.adapters.deepseek-harness | 30 packages.agent-context-kit.src.adapters.pi | 31 packages.agent-context-kit.src.adapters.workspace-runtime | 32 packages.agent-context-kit.src.workspace-files | 33 packages.agent-context-kit.scripts | 34 packages.agent-context-kit.src.adapters |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 integrations.pi-teaql | ||||||||||||||||||||||||||||||||||
| 2 packages.agent-context-kit.integrations.hermes.agent_context_kit | ||||||||||||||||||||||||||||||||||
| 3 packages.agent-context-kit.integrations.octop.main | ||||||||||||||||||||||||||||||||||
| 4 packages.agent-context-kit.scripts.pi-runtime-trace | ||||||||||||||||||||||||||||||||||
| 5 packages.agent-context-kit.src.adapters.command-hook | ||||||||||||||||||||||||||||||||||
| 6 packages.agent-context-kit.src.adapters.pi-cli | ||||||||||||||||||||||||||||||||||
| 7 packages.agent-context-kit.src.adapters.pi-progress | ||||||||||||||||||||||||||||||||||
| 8 packages.agent-context-kit.src.context-access | ||||||||||||||||||||||||||||||||||
| 9 packages.agent-context-kit.src.context-read | ||||||||||||||||||||||||||||||||||
| 10 packages.agent-context-kit.src.controlled-tasks | ||||||||||||||||||||||||||||||||||
| 11 packages.agent-context-kit.src.parser | ||||||||||||||||||||||||||||||||||
| 12 packages.agent-context-kit.src.read-guard | ||||||||||||||||||||||||||||||||||
| 13 packages.agent-context-kit.src.types | ||||||||||||||||||||||||||||||||||
| 14 skills.build-teaql-app.scripts | ||||||||||||||||||||||||||||||||||
| 15 tools | ||||||||||||||||||||||||||||||||||
| 16 packages.agent-context-kit.integrations.hermes | 1 | |||||||||||||||||||||||||||||||||
| 17 packages.agent-context-kit.integrations.octop | 1 | |||||||||||||||||||||||||||||||||
| 18 packages.agent-context-kit.src.adapters.cline | 1 | |||||||||||||||||||||||||||||||||
| 19 packages.agent-context-kit.src.adapters.gemini-cli | 2 | |||||||||||||||||||||||||||||||||
| 20 packages.agent-context-kit.src.adapters.mimocode | 1 | |||||||||||||||||||||||||||||||||
| 21 packages.agent-context-kit.src.adapters.opencode | 1 | |||||||||||||||||||||||||||||||||
| 22 packages.agent-context-kit.src.adapters.opencode-context | 1 | |||||||||||||||||||||||||||||||||
| 23 packages.agent-context-kit.src.adapters.pi-context | 1 | |||||||||||||||||||||||||||||||||
| 24 packages.agent-context-kit.src.context-files | 1 | |||||||||||||||||||||||||||||||||
| 25 packages.agent-context-kit.src.context-markers | 1 | |||||||||||||||||||||||||||||||||
| 26 packages.agent-context-kit.src.file-policy | 1 | |||||||||||||||||||||||||||||||||
| 27 packages.agent-context-kit.src.session | 5 | |||||||||||||||||||||||||||||||||
| 28 packages.agent-context-kit.src | 2 | 4 | 1 | 1 | 3 | 1 | 3 | |||||||||||||||||||||||||||
| 29 packages.agent-context-kit.src.adapters.deepseek-harness | 1 | |||||||||||||||||||||||||||||||||
| 30 packages.agent-context-kit.src.adapters.pi | 1 | 1 | ||||||||||||||||||||||||||||||||
| 31 packages.agent-context-kit.src.adapters.workspace-runtime | 1 | 2 | ||||||||||||||||||||||||||||||||
| 32 packages.agent-context-kit.src.workspace-files | 1 | 3 | ||||||||||||||||||||||||||||||||
| 33 packages.agent-context-kit.scripts | 3 | 1 | 1 | |||||||||||||||||||||||||||||||
| 34 packages.agent-context-kit.src.adapters | 2 | 1 | 1 | 1 | 1 | 2 | 3 | 1 | 2 | 4 | 3 | 1 | 4 | 2 | 2 |
16→2 packages.agent-context-kit.integrations.hermes uses packages.agent-context-kit.integrations.hermes.agent_context_kit✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.integrations.hermes uses a type in packages.agent-context-kit.integrations.hermes.agent_context_kit.
- The types involved
packages.agent-context-kit.integrations.hermes.agent_context_kit→packages.agent-context-kit.integrations.hermes.agent_context_kit.SessionState
- Direction
- packages.agent-context-kit.integrations.hermes uses packages.agent-context-kit.integrations.hermes.agent_context_kit, so a change to packages.agent-context-kit.integrations.hermes.agent_context_kit can break packages.agent-context-kit.integrations.hermes, while a change to packages.agent-context-kit.integrations.hermes can't break packages.agent-context-kit.integrations.hermes.agent_context_kit.
- Position
- Below the diagonal: packages.agent-context-kit.integrations.hermes uses a module listed above it, which is the healthy direction.
17→3 packages.agent-context-kit.integrations.octop uses packages.agent-context-kit.integrations.octop.main✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.integrations.octop uses a type in packages.agent-context-kit.integrations.octop.main.
- The types involved
packages.agent-context-kit.integrations.octop.main→packages.agent-context-kit.integrations.octop.main.Lifecycle
- Direction
- packages.agent-context-kit.integrations.octop uses packages.agent-context-kit.integrations.octop.main, so a change to packages.agent-context-kit.integrations.octop.main can break packages.agent-context-kit.integrations.octop, while a change to packages.agent-context-kit.integrations.octop can't break packages.agent-context-kit.integrations.octop.main.
- Position
- Below the diagonal: packages.agent-context-kit.integrations.octop uses a module listed above it, which is the healthy direction.
18→12 packages.agent-context-kit.src.adapters.cline uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.cline uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.adapters.cline.ClineAdapterOptions→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src.adapters.cline uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src.adapters.cline, while a change to packages.agent-context-kit.src.adapters.cline can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.cline uses a module listed above it, which is the healthy direction.
19→13 packages.agent-context-kit.src.adapters.gemini-cli uses packages.agent-context-kit.src.types✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters.gemini-cli uses a type in packages.agent-context-kit.src.types.
- The types involved
packages.agent-context-kit.src.adapters.gemini-cli.FileGeminiStateStore→packages.agent-context-kit.src.types.LifecycleSnapshotpackages.agent-context-kit.src.adapters.gemini-cli.GeminiStateStore→packages.agent-context-kit.src.types.LifecycleSnapshot
- Direction
- packages.agent-context-kit.src.adapters.gemini-cli uses packages.agent-context-kit.src.types, so a change to packages.agent-context-kit.src.types can break packages.agent-context-kit.src.adapters.gemini-cli, while a change to packages.agent-context-kit.src.adapters.gemini-cli can't break packages.agent-context-kit.src.types.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.gemini-cli uses a module listed above it, which is the healthy direction.
20→12 packages.agent-context-kit.src.adapters.mimocode uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.mimocode uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.adapters.mimocode.MiMoCodeAdapterOptions→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src.adapters.mimocode uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src.adapters.mimocode, while a change to packages.agent-context-kit.src.adapters.mimocode can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.mimocode uses a module listed above it, which is the healthy direction.
21→12 packages.agent-context-kit.src.adapters.opencode uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.opencode uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.adapters.opencode.OpenCodeAdapterOptions→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src.adapters.opencode uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src.adapters.opencode, while a change to packages.agent-context-kit.src.adapters.opencode can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.opencode uses a module listed above it, which is the healthy direction.
22→10 packages.agent-context-kit.src.adapters.opencode-context uses packages.agent-context-kit.src.controlled-tasks✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.opencode-context uses a type in packages.agent-context-kit.src.controlled-tasks.
- The types involved
packages.agent-context-kit.src.adapters.opencode-context.OpenCodeContextPolicyOptions→packages.agent-context-kit.src.controlled-tasks.ControlledTaskCommands
- Direction
- packages.agent-context-kit.src.adapters.opencode-context uses packages.agent-context-kit.src.controlled-tasks, so a change to packages.agent-context-kit.src.controlled-tasks can break packages.agent-context-kit.src.adapters.opencode-context, while a change to packages.agent-context-kit.src.adapters.opencode-context can't break packages.agent-context-kit.src.controlled-tasks.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.opencode-context uses a module listed above it, which is the healthy direction.
23→10 packages.agent-context-kit.src.adapters.pi-context uses packages.agent-context-kit.src.controlled-tasks✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.pi-context uses a type in packages.agent-context-kit.src.controlled-tasks.
- The types involved
packages.agent-context-kit.src.adapters.pi-context.ContextPolicyPiOptions→packages.agent-context-kit.src.controlled-tasks.ControlledTaskCommands
- Direction
- packages.agent-context-kit.src.adapters.pi-context uses packages.agent-context-kit.src.controlled-tasks, so a change to packages.agent-context-kit.src.controlled-tasks can break packages.agent-context-kit.src.adapters.pi-context, while a change to packages.agent-context-kit.src.adapters.pi-context can't break packages.agent-context-kit.src.controlled-tasks.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.pi-context uses a module listed above it, which is the healthy direction.
24→8 packages.agent-context-kit.src.context-files uses packages.agent-context-kit.src.context-access✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.context-files uses a type in packages.agent-context-kit.src.context-access.
- The types involved
packages.agent-context-kit.src.context-files.ContextFiles→packages.agent-context-kit.src.context-access.ContextAccessDecision
- Direction
- packages.agent-context-kit.src.context-files uses packages.agent-context-kit.src.context-access, so a change to packages.agent-context-kit.src.context-access can break packages.agent-context-kit.src.context-files, while a change to packages.agent-context-kit.src.context-files can't break packages.agent-context-kit.src.context-access.
- Position
- Below the diagonal: packages.agent-context-kit.src.context-files uses a module listed above it, which is the healthy direction.
25→10 packages.agent-context-kit.src.context-markers uses packages.agent-context-kit.src.controlled-tasks✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.context-markers uses a type in packages.agent-context-kit.src.controlled-tasks.
- The types involved
packages.agent-context-kit.src.context-markers.MarkerPlan→packages.agent-context-kit.src.controlled-tasks.ControlledTaskCommand
- Direction
- packages.agent-context-kit.src.context-markers uses packages.agent-context-kit.src.controlled-tasks, so a change to packages.agent-context-kit.src.controlled-tasks can break packages.agent-context-kit.src.context-markers, while a change to packages.agent-context-kit.src.context-markers can't break packages.agent-context-kit.src.controlled-tasks.
- Position
- Below the diagonal: packages.agent-context-kit.src.context-markers uses a module listed above it, which is the healthy direction.
26→8 packages.agent-context-kit.src.file-policy uses packages.agent-context-kit.src.context-access✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.file-policy uses a type in packages.agent-context-kit.src.context-access.
- The types involved
packages.agent-context-kit.src.file-policy.FileAccessPolicy→packages.agent-context-kit.src.context-access.ContextAccessDecision
- Direction
- packages.agent-context-kit.src.file-policy uses packages.agent-context-kit.src.context-access, so a change to packages.agent-context-kit.src.context-access can break packages.agent-context-kit.src.file-policy, while a change to packages.agent-context-kit.src.file-policy can't break packages.agent-context-kit.src.context-access.
- Position
- Below the diagonal: packages.agent-context-kit.src.file-policy uses a module listed above it, which is the healthy direction.
27→13 packages.agent-context-kit.src.session uses packages.agent-context-kit.src.types✕
- Connections
- 5 pairs of types, where a type in packages.agent-context-kit.src.session uses a type in packages.agent-context-kit.src.types.
- The types involved
packages.agent-context-kit.src.session.LifecycleSession→packages.agent-context-kit.src.types.AuditEventpackages.agent-context-kit.src.session.LifecycleSession→packages.agent-context-kit.src.types.ContextBlockDefinitionpackages.agent-context-kit.src.session.LifecycleSession→packages.agent-context-kit.src.types.ControlSourcepackages.agent-context-kit.src.session.LifecycleSession→packages.agent-context-kit.src.types.LifecycleSnapshotpackages.agent-context-kit.src.session.LifecycleSession→packages.agent-context-kit.src.types.ParsedMarkdown
- Direction
- packages.agent-context-kit.src.session uses packages.agent-context-kit.src.types, so a change to packages.agent-context-kit.src.types can break packages.agent-context-kit.src.session, while a change to packages.agent-context-kit.src.session can't break packages.agent-context-kit.src.types.
- Position
- Below the diagonal: packages.agent-context-kit.src.session uses a module listed above it, which is the healthy direction.
28→8 packages.agent-context-kit.src uses packages.agent-context-kit.src.context-access✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.context-access.
- The types involved
packages.agent-context-kit.src.context-access→packages.agent-context-kit.src.context-access.ContextAccessDecisionpackages.agent-context-kit.src.context-access→packages.agent-context-kit.src.context-access.ContextGuidance
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.context-access, so a change to packages.agent-context-kit.src.context-access can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.context-access.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
28→10 packages.agent-context-kit.src uses packages.agent-context-kit.src.controlled-tasks✕
- Connections
- 4 pairs of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.controlled-tasks.
- The types involved
packages.agent-context-kit.src.controlled-tasks→packages.agent-context-kit.src.controlled-tasks.ControlledTaskCommandpackages.agent-context-kit.src.controlled-tasks→packages.agent-context-kit.src.controlled-tasks.ControlledTaskNamepackages.agent-context-kit.src.controlled-tasks→packages.agent-context-kit.src.controlled-tasks.ControlledTaskResultpackages.agent-context-kit.src.controlled-tasks→packages.agent-context-kit.src.controlled-tasks.TaskProtocol
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.controlled-tasks, so a change to packages.agent-context-kit.src.controlled-tasks can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.controlled-tasks.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
28→11 packages.agent-context-kit.src uses packages.agent-context-kit.src.parser✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.parser.
- The types involved
packages.agent-context-kit.src.parser→packages.agent-context-kit.src.parser.SourceLine
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.parser, so a change to packages.agent-context-kit.src.parser can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.parser.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
28→12 packages.agent-context-kit.src uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.read-guard→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
28→13 packages.agent-context-kit.src uses packages.agent-context-kit.src.types✕
- Connections
- 3 pairs of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.types.
- The types involved
packages.agent-context-kit.src.parser→packages.agent-context-kit.src.types.ParsedMarkdownpackages.agent-context-kit.src.session→packages.agent-context-kit.src.types.LifecycleBlockpackages.agent-context-kit.src.session→packages.agent-context-kit.src.types.LifecycleMessage
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.types, so a change to packages.agent-context-kit.src.types can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.types.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
28→24 packages.agent-context-kit.src uses packages.agent-context-kit.src.context-files✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.context-files.
- The types involved
packages.agent-context-kit.src.context-read→packages.agent-context-kit.src.context-files.ContextFiles
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.context-files, so a change to packages.agent-context-kit.src.context-files can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.context-files.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
28→25 packages.agent-context-kit.src uses packages.agent-context-kit.src.context-markers✕
- Connections
- 3 pairs of types, where a type in packages.agent-context-kit.src uses a type in packages.agent-context-kit.src.context-markers.
- The types involved
packages.agent-context-kit.src.context-markers→packages.agent-context-kit.src.context-markers.ContextMarkerGenerationReportpackages.agent-context-kit.src.context-markers→packages.agent-context-kit.src.context-markers.ContextMarkerReportpackages.agent-context-kit.src.context-markers→packages.agent-context-kit.src.context-markers.MarkerPlan
- Direction
- packages.agent-context-kit.src uses packages.agent-context-kit.src.context-markers, so a change to packages.agent-context-kit.src.context-markers can break packages.agent-context-kit.src, while a change to packages.agent-context-kit.src can't break packages.agent-context-kit.src.context-markers.
- Position
- Below the diagonal: packages.agent-context-kit.src uses a module listed above it, which is the healthy direction.
29→27 packages.agent-context-kit.src.adapters.deepseek-harness uses packages.agent-context-kit.src.session✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.deepseek-harness uses a type in packages.agent-context-kit.src.session.
- The types involved
packages.agent-context-kit.src.adapters.deepseek-harness.AgentState→packages.agent-context-kit.src.session.LifecycleSession
- Direction
- packages.agent-context-kit.src.adapters.deepseek-harness uses packages.agent-context-kit.src.session, so a change to packages.agent-context-kit.src.session can break packages.agent-context-kit.src.adapters.deepseek-harness, while a change to packages.agent-context-kit.src.adapters.deepseek-harness can't break packages.agent-context-kit.src.session.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.deepseek-harness uses a module listed above it, which is the healthy direction.
30→12 packages.agent-context-kit.src.adapters.pi uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.pi uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.adapters.pi.PiAdapterOptions→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src.adapters.pi uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src.adapters.pi, while a change to packages.agent-context-kit.src.adapters.pi can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.pi uses a module listed above it, which is the healthy direction.
30→27 packages.agent-context-kit.src.adapters.pi uses packages.agent-context-kit.src.session✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.pi uses a type in packages.agent-context-kit.src.session.
- The types involved
packages.agent-context-kit.src.adapters.pi.PiLifecycleAdapter→packages.agent-context-kit.src.session.LifecycleSession
- Direction
- packages.agent-context-kit.src.adapters.pi uses packages.agent-context-kit.src.session, so a change to packages.agent-context-kit.src.session can break packages.agent-context-kit.src.adapters.pi, while a change to packages.agent-context-kit.src.adapters.pi can't break packages.agent-context-kit.src.session.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.pi uses a module listed above it, which is the healthy direction.
31→12 packages.agent-context-kit.src.adapters.workspace-runtime uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters.workspace-runtime uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.adapters.workspace-runtime.WorkspaceRuntimeOptions→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src.adapters.workspace-runtime uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src.adapters.workspace-runtime, while a change to packages.agent-context-kit.src.adapters.workspace-runtime can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.workspace-runtime uses a module listed above it, which is the healthy direction.
31→27 packages.agent-context-kit.src.adapters.workspace-runtime uses packages.agent-context-kit.src.session✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters.workspace-runtime uses a type in packages.agent-context-kit.src.session.
- The types involved
packages.agent-context-kit.src.adapters.workspace-runtime.SessionState→packages.agent-context-kit.src.session.LifecycleSessionpackages.agent-context-kit.src.adapters.workspace-runtime.WorkspaceLifecycleRuntime→packages.agent-context-kit.src.session.LifecycleSession
- Direction
- packages.agent-context-kit.src.adapters.workspace-runtime uses packages.agent-context-kit.src.session, so a change to packages.agent-context-kit.src.session can break packages.agent-context-kit.src.adapters.workspace-runtime, while a change to packages.agent-context-kit.src.adapters.workspace-runtime can't break packages.agent-context-kit.src.session.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters.workspace-runtime uses a module listed above it, which is the healthy direction.
32→24 packages.agent-context-kit.src.workspace-files uses packages.agent-context-kit.src.context-files✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.workspace-files uses a type in packages.agent-context-kit.src.context-files.
- The types involved
packages.agent-context-kit.src.workspace-files.WorkspaceFiles→packages.agent-context-kit.src.context-files.ContextFiles
- Direction
- packages.agent-context-kit.src.workspace-files uses packages.agent-context-kit.src.context-files, so a change to packages.agent-context-kit.src.context-files can break packages.agent-context-kit.src.workspace-files, while a change to packages.agent-context-kit.src.workspace-files can't break packages.agent-context-kit.src.context-files.
- Position
- Below the diagonal: packages.agent-context-kit.src.workspace-files uses a module listed above it, which is the healthy direction.
32→26 packages.agent-context-kit.src.workspace-files uses packages.agent-context-kit.src.file-policy✕
- Connections
- 3 pairs of types, where a type in packages.agent-context-kit.src.workspace-files uses a type in packages.agent-context-kit.src.file-policy.
- The types involved
packages.agent-context-kit.src.workspace-files.WorkspaceFiles→packages.agent-context-kit.src.file-policy.FileAccessPolicypackages.agent-context-kit.src.workspace-files.WorkspaceFiles→packages.agent-context-kit.src.file-policy.FileOperationpackages.agent-context-kit.src.workspace-files.WorkspaceFiles→packages.agent-context-kit.src.file-policy.FilePolicyOptions
- Direction
- packages.agent-context-kit.src.workspace-files uses packages.agent-context-kit.src.file-policy, so a change to packages.agent-context-kit.src.file-policy can break packages.agent-context-kit.src.workspace-files, while a change to packages.agent-context-kit.src.workspace-files can't break packages.agent-context-kit.src.file-policy.
- Position
- Below the diagonal: packages.agent-context-kit.src.workspace-files uses a module listed above it, which is the healthy direction.
33→4 packages.agent-context-kit.scripts uses packages.agent-context-kit.scripts.pi-runtime-trace✕
- Connections
- 3 pairs of types, where a type in packages.agent-context-kit.scripts uses a type in packages.agent-context-kit.scripts.pi-runtime-trace.
- The types involved
packages.agent-context-kit.scripts.pi-runtime-trace→packages.agent-context-kit.scripts.pi-runtime-trace.PiRuntimeTraceResultpackages.agent-context-kit.scripts.pi-runtime-trace→packages.agent-context-kit.scripts.pi-runtime-trace.ProviderRequestTracepackages.agent-context-kit.scripts.pi-runtime-trace→packages.agent-context-kit.scripts.pi-runtime-trace.TraceMessage
- Direction
- packages.agent-context-kit.scripts uses packages.agent-context-kit.scripts.pi-runtime-trace, so a change to packages.agent-context-kit.scripts.pi-runtime-trace can break packages.agent-context-kit.scripts, while a change to packages.agent-context-kit.scripts can't break packages.agent-context-kit.scripts.pi-runtime-trace.
- Position
- Below the diagonal: packages.agent-context-kit.scripts uses a module listed above it, which is the healthy direction.
33→7 packages.agent-context-kit.scripts uses packages.agent-context-kit.src.adapters.pi-progress✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.scripts uses a type in packages.agent-context-kit.src.adapters.pi-progress.
- The types involved
packages.agent-context-kit.scripts.pi-runtime-trace→packages.agent-context-kit.src.adapters.pi-progress.Message
- Direction
- packages.agent-context-kit.scripts uses packages.agent-context-kit.src.adapters.pi-progress, so a change to packages.agent-context-kit.src.adapters.pi-progress can break packages.agent-context-kit.scripts, while a change to packages.agent-context-kit.scripts can't break packages.agent-context-kit.src.adapters.pi-progress.
- Position
- Below the diagonal: packages.agent-context-kit.scripts uses a module listed above it, which is the healthy direction.
33→30 packages.agent-context-kit.scripts uses packages.agent-context-kit.src.adapters.pi✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.scripts uses a type in packages.agent-context-kit.src.adapters.pi.
- The types involved
packages.agent-context-kit.scripts.pi-runtime-trace→packages.agent-context-kit.src.adapters.pi.PiLifecycleAdapter
- Direction
- packages.agent-context-kit.scripts uses packages.agent-context-kit.src.adapters.pi, so a change to packages.agent-context-kit.src.adapters.pi can break packages.agent-context-kit.scripts, while a change to packages.agent-context-kit.scripts can't break packages.agent-context-kit.src.adapters.pi.
- Position
- Below the diagonal: packages.agent-context-kit.scripts uses a module listed above it, which is the healthy direction.
34→5 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.command-hook✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.command-hook.
- The types involved
packages.agent-context-kit.src.adapters.command-hook→packages.agent-context-kit.src.adapters.command-hook.CommandHookHostpackages.agent-context-kit.src.adapters.command-hook→packages.agent-context-kit.src.adapters.command-hook.CommandHookResult
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.command-hook, so a change to packages.agent-context-kit.src.adapters.command-hook can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.command-hook.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→6 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi-cli✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.pi-cli.
- The types involved
packages.agent-context-kit.src.adapters.pi-cli→packages.agent-context-kit.src.adapters.pi-cli.ParsedCliArgs
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi-cli, so a change to packages.agent-context-kit.src.adapters.pi-cli can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.pi-cli.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→7 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi-progress✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.pi-progress.
- The types involved
packages.agent-context-kit.src.adapters.pi-progress→packages.agent-context-kit.src.adapters.pi-progress.Message
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi-progress, so a change to packages.agent-context-kit.src.adapters.pi-progress can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.pi-progress.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→10 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.controlled-tasks✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.controlled-tasks.
- The types involved
packages.agent-context-kit.src.adapters.pi-context→packages.agent-context-kit.src.controlled-tasks.ControlledTaskCommands
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.controlled-tasks, so a change to packages.agent-context-kit.src.controlled-tasks can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.controlled-tasks.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→12 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.read-guard✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.read-guard.
- The types involved
packages.agent-context-kit.src.adapters.workspace-runtime→packages.agent-context-kit.src.read-guard.ReadGuardConfig
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.read-guard, so a change to packages.agent-context-kit.src.read-guard can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.read-guard.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→13 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.types✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.types.
- The types involved
packages.agent-context-kit.src.adapters.cline→packages.agent-context-kit.src.types.LifecycleMessagepackages.agent-context-kit.src.adapters.pi→packages.agent-context-kit.src.types.LifecycleMessage
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.types, so a change to packages.agent-context-kit.src.types can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.types.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→18 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.cline✕
- Connections
- 3 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.cline.
- The types involved
packages.agent-context-kit.src.adapters.cline→packages.agent-context-kit.src.adapters.cline.ClineAdapterOptionspackages.agent-context-kit.src.adapters.cline→packages.agent-context-kit.src.adapters.cline.ClinePluginApipackages.agent-context-kit.src.adapters.cline→packages.agent-context-kit.src.adapters.cline.ClinePluginContext
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.cline, so a change to packages.agent-context-kit.src.adapters.cline can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.cline.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→19 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.gemini-cli✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.gemini-cli.
- The types involved
packages.agent-context-kit.src.adapters.gemini-cli→packages.agent-context-kit.src.adapters.gemini-cli.GeminiCliMessage
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.gemini-cli, so a change to packages.agent-context-kit.src.adapters.gemini-cli can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.gemini-cli.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→20 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.mimocode✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.mimocode.
- The types involved
packages.agent-context-kit.src.adapters.mimocode→packages.agent-context-kit.src.adapters.mimocode.MiMoCodeAdapterOptionspackages.agent-context-kit.src.adapters.mimocode→packages.agent-context-kit.src.adapters.mimocode.MiMoPluginInput
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.mimocode, so a change to packages.agent-context-kit.src.adapters.mimocode can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.mimocode.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→21 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.opencode✕
- Connections
- 4 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.opencode.
- The types involved
packages.agent-context-kit.src.adapters.kilo→packages.agent-context-kit.src.adapters.opencode.OpenCodeAdapterOptionspackages.agent-context-kit.src.adapters.opencode→packages.agent-context-kit.src.adapters.opencode.OpenCodeAdapterOptionspackages.agent-context-kit.src.adapters.opencode→packages.agent-context-kit.src.adapters.opencode.OpenCodeV1Inputpackages.agent-context-kit.src.adapters.opencode→packages.agent-context-kit.src.adapters.opencode.OpenCodeV2Context
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.opencode, so a change to packages.agent-context-kit.src.adapters.opencode can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.opencode.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→22 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.opencode-context✕
- Connections
- 3 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.opencode-context.
- The types involved
packages.agent-context-kit.src.adapters.opencode-context→packages.agent-context-kit.src.adapters.opencode-context.OpenCodeContextPolicyOptionspackages.agent-context-kit.src.adapters.opencode-context→packages.agent-context-kit.src.adapters.opencode-context.OpenCodePolicyContextpackages.agent-context-kit.src.adapters.pi-completion→packages.agent-context-kit.src.adapters.opencode-context.ToolDefinition
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.opencode-context, so a change to packages.agent-context-kit.src.adapters.opencode-context can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.opencode-context.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→23 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi-context✕
- Connections
- 1 pair of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.pi-context.
- The types involved
packages.agent-context-kit.src.adapters.pi-context→packages.agent-context-kit.src.adapters.pi-context.ContextPolicyPiOptions
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi-context, so a change to packages.agent-context-kit.src.adapters.pi-context can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.pi-context.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→29 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.deepseek-harness✕
- Connections
- 4 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.deepseek-harness.
- The types involved
packages.agent-context-kit.src.adapters.deepseek-harness→packages.agent-context-kit.src.adapters.deepseek-harness.AgentStatepackages.agent-context-kit.src.adapters.deepseek-harness→packages.agent-context-kit.src.adapters.deepseek-harness.DeepSeekAgentpackages.agent-context-kit.src.adapters.deepseek-harness→packages.agent-context-kit.src.adapters.deepseek-harness.DeepSeekContextpackages.agent-context-kit.src.adapters.deepseek-harness→packages.agent-context-kit.src.adapters.deepseek-harness.DeepSeekMessage
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.deepseek-harness, so a change to packages.agent-context-kit.src.adapters.deepseek-harness can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.deepseek-harness.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→30 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.pi.
- The types involved
packages.agent-context-kit.src.adapters.pi→packages.agent-context-kit.src.adapters.pi.PiAdapterOptionspackages.agent-context-kit.src.adapters.pi→packages.agent-context-kit.src.adapters.pi.PiExtensionApi
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.pi, so a change to packages.agent-context-kit.src.adapters.pi can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.pi.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters uses a module listed above it, which is the healthy direction.
34→31 packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.workspace-runtime✕
- Connections
- 2 pairs of types, where a type in packages.agent-context-kit.src.adapters uses a type in packages.agent-context-kit.src.adapters.workspace-runtime.
- The types involved
packages.agent-context-kit.src.adapters.command-hook→packages.agent-context-kit.src.adapters.workspace-runtime.WorkspaceLifecycleRuntimepackages.agent-context-kit.src.adapters.opencode→packages.agent-context-kit.src.adapters.workspace-runtime.WorkspaceLifecycleRuntime
- Direction
- packages.agent-context-kit.src.adapters uses packages.agent-context-kit.src.adapters.workspace-runtime, so a change to packages.agent-context-kit.src.adapters.workspace-runtime can break packages.agent-context-kit.src.adapters, while a change to packages.agent-context-kit.src.adapters can't break packages.agent-context-kit.src.adapters.workspace-runtime.
- Position
- Below the diagonal: packages.agent-context-kit.src.adapters 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 10 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
| A05:2025 — Injection | 2 | Medium |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.4 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +5.4 pts | Medium | Security & performance tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +3.6 pts | Medium | Dependency Hygiene |
| Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. | +1.5 pts | Low | Secrets (history) |
| Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Secrets (history) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +0.9 pts | Low | Dependency Vulnerabilities |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.6 pts | Medium | Release Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +0.7 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| packages/agent-context-kit/src/controlled-tasks.ts | 7.0 | Mixed | Cyclomatic Complexity: controlled-tasks.renderDiagnostics.diagnostics (cyclomatic 27) |
| packages/agent-context-kit/integrations/hermes/agent_context_kit.py | 7.1 | Mixed | Cyclomatic Complexity: agent_context_kit._pre_tool_call (cyclomatic 18) |
| packages/agent-context-kit/src/context-markers.ts | 7.2 | Mixed | Cyclomatic Complexity: context-markers.loadPlan (cyclomatic 35) |
| packages/agent-context-kit/src/adapters/opencode-context.ts | 7.2 | Mixed | Cyclomatic Complexity: opencode-context.createOpenCodeContextPolicyTools (cyclomatic 17) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| packages/agent-context-kit/src/parser.ts | 7.4 | Mixed | Cyclomatic Complexity: parser.parseMarkdown (cyclomatic 17) |
| packages/agent-context-kit/src/adapters/pi-policy-feedback.ts | 7.8 | Mixed | Cyclomatic Complexity: pi-policy-feedback.registerPiPolicyFeedback (cyclomatic 35) |
| packages/agent-context-kit/src/file-policy.ts | 7.8 | Mixed | Cyclomatic Complexity: FileAccessPolicy.checkMutation (cyclomatic 32) |
| packages/agent-context-kit/src/adapters/pi-progress.ts | 7.8 | Mixed | Cyclomatic Complexity: pi-progress.registerPiProgressRecovery (cyclomatic 25) |
| packages/agent-context-kit/src/adapters/pi-completion.ts | 7.8 | Mixed | Cyclomatic Complexity: pi-completion.createPiCompletionGuard (cyclomatic 25) |
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 73 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 — 73 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, 140 of 151 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 1 package.json manifest(s) and its 1 committed lockfile(s) WERE read; what went unanswered is the currency half, because it grades the production `dependencies` a lockfile resolves and these manifests declare none — only 5 devDependencies, which D12 does not grade. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: the lockfile was resolved, and no reader we could write would find a production dependency in it.
- D14 License Compliance — 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. Not scored — this repository's committed lockfile was read and it resolves no production dependency: everything it installs is declared under `devDependencies`, or is a workspace-internal package with no registry release behind it. Licences are resolved from registry.npmjs.org, because an npm checkout does not contain its dependencies' licences. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 232 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 3 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 532 sampled here came from .mjs/.ts files. This repository's .py source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- 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/agent-context-kit/src/adapters/pi-context.ts`, `packages/agent-context-kit/src/index.ts`, `packages/agent-context-kit/src/parser.ts` 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.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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
24 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was context-markers.loadPlan at 35. A further 1 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 read-guard.normalizedToolName at 22 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/agent-context-kit/src/read-guard.ts (read-guard.normalizedToolName at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 24 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with context-markers.loadPlan (cyclomatic 35), pi-policy-feedback.registerPiPolicyFeedback (cyclomatic 35), FileAccessPolicy.checkMutation (cyclomatic 32). — 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 24 together lifts Cyclomatic Complexity from 5.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
33 method(s) exceeded the cognitive complexity threshold of 15; the worst was FileAccessPolicy.checkMutation at 48.
What to do
- Bring the 33 bodies over 15 down to 15 or less in Cognitive Complexity — start with FileAccessPolicy.checkMutation (cognitive 48), pi-policy-feedback.registerPiPolicyFeedback (cognitive 40), model_provenance.codex_actor (cognitive 34). — 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 33 together lifts Cognitive Complexity from 3.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with parser.ts, pi-runtime-trace.ts. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 93.5%. Measured from the JavaScript/TypeScript suite (node:test via `npm ci --ignore-scripts` in the repository root; node:test via `npm ci --ignore-scripts` in packages/agent-context-kit/).
D9 · Test Distribution
182 test methods: 160 unit, 22 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 148 `it`/`test` case(s) across 35 test file(s) declaring at least one; its tier split is read from package names and paths only. The Python suite contributes 34 test function(s) across 5 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.
D10 · Test Quality
4 skipped (4 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 148 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in the repository root (144 tests); node:test via `npm ci --ignore-scripts` in packages/agent-context-kit/ (136 tests)): measured (0 flaky).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 5195 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 34 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 46 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 2 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
32 % of calls cross a namespace and 6 % 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. Measured over the .mjs/.ts source only — this repository's .py was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep hit a parse error in 3 file(s) — `packages/agent-context-kit/src/adapters/pi-context.ts` (line 118), `packages/agent-context-kit/src/index.ts` (line 18), `packages/agent-context-kit/src/parser.ts` (line 50) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 1 high, 3 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 32 of the 43 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.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/agent-context-kit`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `packages/agent-context-kit/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`. — packages/agent-context-kit/package.json:107
What to do
- Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `readFileSync` in `createTools` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — integrations/pi-teaql/tools.mjs:140
- `lstatSync` in `execute` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/agent-context-kit/src/adapters/pi-cli.ts:47
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- packages/agent-context-kit/src/adapters/mimocode.ts:5 · packages/agent-context-kit/src/adapters/opencode.ts:32 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/agent-context-kit/src/adapters/mimocode.ts:5
- packages/agent-context-kit/src/adapters/mimocode.ts:71 · packages/agent-context-kit/src/adapters/opencode.ts:94 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/agent-context-kit/src/adapters/mimocode.ts:71
- REDACTED:151 · REDACTED:204 — the two spans are one implementation copied and then locally edited — 86 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:151
- packages/agent-context-kit/scripts/build-command-hook.ts:6 · packages/agent-context-kit/scripts/build-marker-cli.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/agent-context-kit/scripts/build-command-hook.ts:6
- packages/agent-context-kit/src/adapters/pi.ts:88 · packages/agent-context-kit/src/adapters/workspace-runtime.ts:42 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/agent-context-kit/src/adapters/pi.ts:88
- packages/agent-context-kit/src/adapters/workspace-runtime.ts:25 · packages/agent-context-kit/src/session.ts:44 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/agent-context-kit/src/adapters/workspace-runtime.ts:25
- REDACTED:85 · packages/agent-context-kit/src/context-markers.ts:68 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:85
- packages/agent-context-kit/src/session.ts:166 · packages/agent-context-kit/src/session.ts:191 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/agent-context-kit/src/session.ts:166
- packages/agent-context-kit/src/adapters/deepseek-harness.ts:77 · packages/agent-context-kit/src/adapters/workspace-runtime.ts:25 · packages/agent-context-kit/src/session.ts:44 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/agent-context-kit/src/adapters/deepseek-harness.ts:77
- packages/agent-context-kit/src/adapters/deepseek-harness.ts:120 · packages/agent-context-kit/src/session.ts:36 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/agent-context-kit/src/adapters/deepseek-harness.ts:120
- packages/agent-context-kit/src/adapters/mimocode.ts:53 · packages/agent-context-kit/src/adapters/opencode.ts:141 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/agent-context-kit/src/adapters/mimocode.ts:53
- packages/agent-context-kit/src/adapters/pi-cli.ts:21 · packages/agent-context-kit/src/adapters/pi-context.ts:30 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/agent-context-kit/src/adapters/pi-cli.ts:21
- packages/agent-context-kit/src/adapters/cline.ts:36 · packages/agent-context-kit/src/adapters/cline.ts:49 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/agent-context-kit/src/adapters/cline.ts:36
- packages/agent-context-kit/src/adapters/pi-completion.ts:24 · packages/agent-context-kit/src/adapters/pi-progress.ts:59 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/agent-context-kit/src/adapters/pi-completion.ts:24
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- tests/context-runtime/skill-contract.test.mjs:4 reaches past another workspace package's public entry into its internals with a relative path (../../packages/agent-context-kit/src/parser.ts) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/context-runtime/skill-contract.test.mjs:4
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- checkMutation has cyclomatic complexity 32 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/file-policy.ts:58
- loadPlan has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/context-markers.ts:101
- loadPiHostTools has cyclomatic complexity 25 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/adapters/pi-host-tools.ts:7
- (anonymous) has cyclomatic complexity 24 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:17
- (anonymous) has cyclomatic complexity 24 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/controlled-tasks.ts:161
- parse has cyclomatic complexity 23 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/controlled-tasks.ts:132
- grep has cyclomatic complexity 21 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:167
- execute has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — integrations/pi-teaql/tools.mjs:81
- snapshotTaskCommand has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/controlled-tasks.ts:71
- parseMarkdown has cyclomatic complexity 18 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/parser.ts:67
- loadContextPolicyFiles has cyclomatic complexity 17 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/context-loading.ts:8
- inspectContextRead has cyclomatic complexity 17 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/context-read.ts:23
- checkContextAccess has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/context-access.ts:109
- parseReadGuardConfig has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/read-guard.ts:157
- applyPlan has cyclomatic complexity 13 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/context-markers.ts:162
- execute has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/adapters/opencode-context.ts:65
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/adapters/pi-completion.ts:29
- evaluate has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/read-guard.ts:224
- handleCommandHook has cyclomatic complexity 13 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/agent-context-kit/src/adapters/command-hook.ts:39
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — packages/agent-context-kit/scripts/build-command-hook.ts:1, packages/agent-context-kit/src/adapters/gemini-cli-hook.ts:1, packages/agent-context-kit/scripts/pi-context-cli.mjs:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 25 application, 2 tooling and 34 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
- no import path from any entry point (25 application, 2 tooling, 34 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — packages/agent-context-kit/src/adapters/gemini-cli-hook.ts, packages/agent-context-kit/integrations/mimocode/agent-context-kit.ts
- Nothing imports this binding — it is safe to review for removal. — integrations/pi-teaql/tools.mjs:138
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×4) — tests/context-runtime/installation-entrypoints.test.mjs:85, integrations/pi-teaql/tools.mjs:6, packages/agent-context-kit/test/integration/opencode-context.test.ts:6, …
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 3/4 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `runControlledTask` holds an AbortSignal but calls `spawn(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `spawn(…, { signal })`. — packages/agent-context-kit/src/controlled-tasks.ts:213
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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
- `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/agent-context-kit/src/controlled-tasks.ts:138
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — packages/agent-context-kit/src/controlled-tasks.ts:177, packages/agent-context-kit/src/controlled-tasks.ts:238, packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:55, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — integrations/pi-teaql/tools.mjs:120
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- ~5.5 `!` null assertions per 1k TypeScript source lines — 25 assertion(s) across the 4572 source line(s) of the 35 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/agent-context-kit/src/workspace-files.ts (9), REDACTED (5), packages/agent-context-kit/src/controlled-tasks.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 86% | Strong | Strongest area. |
| Maturity | 77% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31% | Weak — gated by R8, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D28 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 3 observation(s) recorded · Dependency currency not established — this repository declares no production dependency to grade
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D14 License Compliance — npm licences not graded — this repository's lockfile resolves no production dependency
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript 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"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 68 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@earendil-works/pi-coding-agent' tests/context-runtime/installation-entrypoints.test.mjs:85
- Unlisted import 'typebox' integrations/pi-teaql/tools.mjs:6
- Unlisted import '@opencode/ai' packages/agent-context-kit/test/integration/opencode-context.test.ts:6
- Unlisted import 'effect' packages/agent-context-kit/test/integration/opencode-sdk.test.ts:6
Serious — 112 finding(s)
- Swallowed exception (empty catch) packages/agent-context-kit/src/controlled-tasks.ts:177
- Swallowed exception (empty catch) packages/agent-context-kit/src/controlled-tasks.ts:238
- Swallowed exception (empty catch) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:55
- Swallowed exception (empty catch) integrations/pi-teaql/tools.mjs:15
- Swallowed exception (empty catch) integrations/pi-teaql/tools.mjs:120
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2 locations) packages/agent-context-kit/src/adapters/deepseek-harness.ts:120
- Duplicated block (7 lines × 2 locations) packages/agent-context-kit/src/adapters/mimocode.ts:53
- Duplicated block (7 lines × 2 locations) packages/agent-context-kit/src/adapters/pi-cli.ts:21
- No test reaches this file packages/agent-context-kit/scripts/build-command-hook.ts:1
- No test reaches this file packages/agent-context-kit/src/adapters/gemini-cli-hook.ts:1
- No test reaches this file packages/agent-context-kit/scripts/pi-context-cli.mjs:1
- FunctionTooLong: parser.parseMarkdown packages/agent-context-kit/src/parser.ts:67
- FunctionTooLong: pi-runtime-trace.runPiRuntimeTrace packages/agent-context-kit/scripts/pi-runtime-trace.ts:124
- Sync-over-async blocking integrations/pi-teaql/tools.mjs:140
- Sync-over-async blocking packages/agent-context-kit/src/adapters/pi-cli.ts:47
- Duplicated block (8 lines × 2 locations) packages/agent-context-kit/src/adapters/workspace-runtime.ts:25
- Duplicated block (8 lines × 2 locations) REDACTED:85
- context-markers.loadPlan (cyclomatic 35) packages/agent-context-kit/src/context-markers.ts:101
- pi-policy-feedback.registerPiPolicyFeedback (cyclomatic 35) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:12
- FileAccessPolicy.checkMutation (cyclomatic 32) packages/agent-context-kit/src/file-policy.ts:58
- controlled-tasks.renderDiagnostics.diagnostics (cyclomatic 27) packages/agent-context-kit/src/controlled-tasks.ts:161
- pi-progress.registerPiProgressRecovery (cyclomatic 25) packages/agent-context-kit/src/adapters/pi-progress.ts:45
- pi-completion.createPiCompletionGuard (cyclomatic 25) packages/agent-context-kit/src/adapters/pi-completion.ts:10
- pi-host-tools.loadPiHostTools (cyclomatic 25) packages/agent-context-kit/src/adapters/pi-host-tools.ts:7
- model_provenance.codex_actor (cyclomatic 24) skills/build-teaql-app/scripts/model_provenance.py:38
- TaskProtocol.parse (cyclomatic 23) packages/agent-context-kit/src/controlled-tasks.ts:132
- ContextFiles.grep (cyclomatic 21) REDACTED:167
- controlled-tasks.runControlledTask (cyclomatic 21) packages/agent-context-kit/src/controlled-tasks.ts:213
- pi-cli.createPiContextMutationTools (cyclomatic 21) packages/agent-context-kit/src/adapters/pi-cli.ts:31
- createTeaqlTools::execute (cyclomatic 21) integrations/pi-teaql/tools.mjs:81
- controlled-tasks.snapshotTaskCommand (cyclomatic 20) packages/agent-context-kit/src/controlled-tasks.ts:71
- agent_context_kit._pre_tool_call (cyclomatic 18) packages/agent-context-kit/integrations/hermes/agent_context_kit.py:283
- context-access.checkContextAccess (cyclomatic 17) packages/agent-context-kit/src/context-access.ts:109
- context-loading.loadContextPolicyFiles (cyclomatic 17) packages/agent-context-kit/src/context-loading.ts:8
- context-read.inspectContextRead (cyclomatic 17) packages/agent-context-kit/src/context-read.ts:23
- parser.parseMarkdown (cyclomatic 17) packages/agent-context-kit/src/parser.ts:67
- opencode-context.createOpenCodeContextPolicyTools (cyclomatic 17) packages/agent-context-kit/src/adapters/opencode-context.ts:60
- opencode-context.createOpenCodeContextPolicyPlugin.setup (cyclomatic 17) packages/agent-context-kit/src/adapters/opencode-context.ts:135
- main._policy_map (cyclomatic 17) REDACTED:79
- agent_context_kit._load_guard (cyclomatic 16) packages/agent-context-kit/integrations/hermes/agent_context_kit.py:216
- FileAccessPolicy.checkMutation (cognitive 48) packages/agent-context-kit/src/file-policy.ts:58
- pi-policy-feedback.registerPiPolicyFeedback (cognitive 40) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:12
- model_provenance.codex_actor (cognitive 34) skills/build-teaql-app/scripts/model_provenance.py:38
- ContextFiles.grep (cognitive 33) REDACTED:167
- controlled-tasks.runControlledTask (cognitive 33) packages/agent-context-kit/src/controlled-tasks.ts:213
- parser.parseMarkdown (cognitive 33) packages/agent-context-kit/src/parser.ts:67
- context-loading.loadContextPolicyFiles (cognitive 31) packages/agent-context-kit/src/context-loading.ts:8
- pi-completion.createPiCompletionGuard (cognitive 31) packages/agent-context-kit/src/adapters/pi-completion.ts:10
- createTeaqlTools::execute (cognitive 31) integrations/pi-teaql/tools.mjs:81
- agent_context_kit._pre_tool_call (cognitive 30) packages/agent-context-kit/integrations/hermes/agent_context_kit.py:283
- context-markers.loadPlan (cognitive 29) packages/agent-context-kit/src/context-markers.ts:101
- OctopContextMiddleware._project (cognitive 29) REDACTED:201
- pi-host-tools.loadPiHostTools (cognitive 25) packages/agent-context-kit/src/adapters/pi-host-tools.ts:7
- controlled-tasks.renderDiagnostics.diagnostics (cognitive 24) packages/agent-context-kit/src/controlled-tasks.ts:161
- context-read.inspectContextRead (cognitive 24) packages/agent-context-kit/src/context-read.ts:23
- agent_context_kit._parse_source (cognitive 24) packages/agent-context-kit/integrations/hermes/agent_context_kit.py:70
- main._policy_map (cognitive 24) REDACTED:79
- context-markers.validateTargets (cognitive 23) packages/agent-context-kit/src/context-markers.ts:83
- OctopContextMiddleware.before_model (cognitive 22) REDACTED:155
- opencode-context.createOpenCodeContextPolicyTools (cognitive 21) packages/agent-context-kit/src/adapters/opencode-context.ts:60
- parseRustMakeOutput (cognitive 21) integrations/pi-teaql/rust-make.mjs:25
- context-markers.applyPlan (cognitive 20) packages/agent-context-kit/src/context-markers.ts:162
- pi-cli.createPiContextMutationTools (cognitive 20) packages/agent-context-kit/src/adapters/pi-cli.ts:31
- pi-progress.registerPiProgressRecovery (cognitive 19) packages/agent-context-kit/src/adapters/pi-progress.ts:45
- TaskProtocol.parse (cognitive 18) packages/agent-context-kit/src/controlled-tasks.ts:132
- controlled-tasks.snapshotTaskCommand (cognitive 18) packages/agent-context-kit/src/controlled-tasks.ts:71
- opencode-context.createOpenCodeContextPolicyPlugin.setup (cognitive 18) packages/agent-context-kit/src/adapters/opencode-context.ts:135
- context-access.checkContextAccess (cognitive 17) packages/agent-context-kit/src/context-access.ts:109
- read-guard.pathInputs (cognitive 17) packages/agent-context-kit/src/read-guard.ts:86
- LifecycleSession.buildContextView (cognitive 17) packages/agent-context-kit/src/session.ts:158
- agent_context_kit._load_guard (cognitive 16) packages/agent-context-kit/integrations/hermes/agent_context_kit.py:216
- policy.read_denial (cognitive 16) packages/agent-context-kit/integrations/octop/policy.py:51
- REDACTED
- REDACTED
- No CI pipeline
- Duplicated block (41 lines × 2 locations) packages/agent-context-kit/src/adapters/mimocode.ts:5
- Duplicated block (16 lines × 2 locations) packages/agent-context-kit/src/adapters/mimocode.ts:71
- Duplicated block with local edits (15 matched lines × 2 locations) REDACTED:151
- Duplicated block (13 lines × 2 locations) packages/agent-context-kit/scripts/build-command-hook.ts:6
- Duplicated block (12 lines × 2 locations) packages/agent-context-kit/src/adapters/pi.ts:88
- Duplicated block with local edits (8 matched lines × 2 locations) packages/agent-context-kit/src/session.ts:166
- Duplicated block (7 lines × 3 locations) packages/agent-context-kit/src/adapters/deepseek-harness.ts:77
- Duplicated block with local edits (6 matched lines × 2 locations) packages/agent-context-kit/src/adapters/cline.ts:36
- Duplicated block with local edits (5 matched lines × 2 locations) packages/agent-context-kit/src/adapters/pi-completion.ts:24
- Boundary violation [package:test-cross-package-internals] tests/context-runtime/skill-contract.test.mjs:4
- Complex function checkMutation (cyclomatic 32, cognitive 50) packages/agent-context-kit/src/file-policy.ts:58
- Complex function loadPlan (cyclomatic 28, cognitive 31) packages/agent-context-kit/src/context-markers.ts:101
- Complex function loadPiHostTools (cyclomatic 25, cognitive 27) packages/agent-context-kit/src/adapters/pi-host-tools.ts:7
- Complex function (anonymous) (cyclomatic 24, cognitive 30) packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:17
- Complex function (anonymous) (cyclomatic 24, cognitive 25) packages/agent-context-kit/src/controlled-tasks.ts:161
- Complex function parse (cyclomatic 23, cognitive 19) packages/agent-context-kit/src/controlled-tasks.ts:132
- Complex function grep (cyclomatic 21, cognitive 35) REDACTED:167
- Complex function execute (cyclomatic 21, cognitive 31) integrations/pi-teaql/tools.mjs:81
- Complex function snapshotTaskCommand (cyclomatic 21, cognitive 22) packages/agent-context-kit/src/controlled-tasks.ts:71
- Complex function parseMarkdown (cyclomatic 18, cognitive 34) packages/agent-context-kit/src/parser.ts:67
- Complex function loadContextPolicyFiles (cyclomatic 17, cognitive 31) packages/agent-context-kit/src/context-loading.ts:8
- Complex function inspectContextRead (cyclomatic 17, cognitive 24) packages/agent-context-kit/src/context-read.ts:23
- Complex function checkContextAccess (cyclomatic 16, cognitive 17) packages/agent-context-kit/src/context-access.ts:109
- Complex function parseReadGuardConfig (cyclomatic 14, cognitive 11) packages/agent-context-kit/src/read-guard.ts:157
- Complex function applyPlan (cyclomatic 13, cognitive 21) packages/agent-context-kit/src/context-markers.ts:162
- Complex function execute (cyclomatic 13, cognitive 14) packages/agent-context-kit/src/adapters/opencode-context.ts:65
- Complex function (anonymous) (cyclomatic 13, cognitive 14) packages/agent-context-kit/src/adapters/pi-completion.ts:29
- Complex function evaluate (cyclomatic 13, cognitive 12) packages/agent-context-kit/src/read-guard.ts:224
- Complex function handleCommandHook (cyclomatic 13, cognitive 10) packages/agent-context-kit/src/adapters/command-hook.ts:39
- No lint script
- Dead file (~17 LoC) packages/agent-context-kit/src/adapters/gemini-cli-hook.ts
- Dead file (~1 LoC) packages/agent-context-kit/integrations/mimocode/agent-context-kit.ts
- Async function without AbortSignal: runControlledTask packages/agent-context-kit/src/controlled-tasks.ts:213
- Swallowed exception (caught, then discarded) packages/agent-context-kit/src/controlled-tasks.ts:138
Minor — 20 finding(s)
- Duplicated predicate packages/agent-context-kit/src/adapters/mimocode.ts:46
- Duplicated predicate packages/agent-context-kit/src/adapters/pi-cli.ts:63
- Duplicated predicate packages/agent-context-kit/src/adapters/mimocode.ts:34
- Duplicated predicate packages/agent-context-kit/src/adapters/pi.ts:96
- Duplicated predicate packages/agent-context-kit/src/adapters/pi.ts:125
- Duplicated predicate packages/agent-context-kit/src/adapters/command-hook.ts:14
- Deprecated: @opentelemetry/sdk-trace-base REDACTED:1636
- Deprecated: @opentelemetry/sdk-trace-node REDACTED:1655
- Deprecated: node-domexception REDACTED:3275
- No ADRs found
- REDACTED
- No ADRs
- Logging is not universal
- No SAST
- No dependency-update automation packages/agent-context-kit/package.json:107
- No changelog
- Unused export 'createTools' integrations/pi-teaql/tools.mjs:138
- Not all async functions that make a request accept an AbortSignal
- Null assertions (`!`) override strict null checking
- Silent fallback default in catch packages/agent-context-kit/src/adapters/pi-policy-feedback.ts:14
Minor — 5 finding(s)
- Skipped (documented): filesystem permission errors fail closed packages/agent-context-kit/test/context-access.test.ts:157
- Skipped (documented): unreadable marker body still excludes with default guidance packages/agent-context-kit/test/context-access.test.ts:181
- Skipped (documented): CLI SIGTERM cancels its generator and restores the deleted output marker packages/agent-context-kit/test/context-markers.test.ts:272
- Skipped (documented): POSIX timeout kills descendants that ignore SIGTERM packages/agent-context-kit/test/controlled-tasks.test.ts:219
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile resolved no direct production dependency)
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-acf17752207441b2ba591a3e5d56410b/history.json --exit-code 0 --source . | 6 | 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-acf17752207441b2ba591a3e5d56410b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 2 | 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/** . | 4 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `packages/agent-context-kit/src/adapters/pi-context.ts`, `packages/agent-context-kit/src/index.ts`, `packages/agent-context-kit/src/parser.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |