Public report of openai/build-hours, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 21:08 UTC · Survey ID cd_e41ab6136fc448afbaee54b51df27eba
openai/build-hours
Measured 16 November 2026, 21:08 UTC, at code version 4e04a13
First survey, so nothing to compare with yet
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 73,988 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 14.5
Findings by how serious they are
435 critical768 serious544 minor
9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 21:08 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
81of 81 dimensions measured by tools.
1597of 1747 findings point to an exact file and line, so you can open each one in the code. The other 150 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 73,988 lines of product code in 22 projects.
openai/build-hours is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back 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 31.9 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 14.5, is the weakest lens and counts most in the score. The best first step for the work it takes is adding tests for untested code, worth about 1.3 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 2.4 points. Raising Production Readiness to 70 would lift the score to about 45.9.
382 known security holes in the packages the code depends on can be used by attackers. Two weaknesses in the code could be used by an attacker, and eighteen form fields can't be read by a screen reader. Updating the vulnerable packages, fixing the weaknesses the scanner points to and labelling the form fields would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the place where the code runs text as code or as a command needs a direct call instead. The 12 controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 73,988 lines, about €67,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 14.5 to 70, the lowest score rated Strong, the score would rise from 31.9 to about 45.9.
Code composition: what the lines of code are
Product code 94%Tests 6%
Rebuild cost: about €67,000 · Estimate
Cost to rebuild
€22,000 to €110,000, for 371 to 1,176 hours of work, about 0.5 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 32. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 73,988 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.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Low coverage finding(s) in Code Coverage — start with ValuemaxxingLab.tsx, REDACTED.
Raises the score by about 1.3 points · Low effort · Code Coverage
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 2.4 points · Medium effort · CI/CD gates
3
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.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €67,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 14.5 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Low coverage finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 1.3 points for low effort, because it clears the 2 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 206 lines over the last 90 days, which is about 835 lines a year. At that pace, the extra work comes to an estimated 0 to 0.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
325 modules, with 176 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 285 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
1 pair of types, where a type in 06-structured_outputs.structured-outputs-assistant-final.components.cart uses a type in 06-structured_outputs.structured-outputs-assistant-final.lib.assistant.
06-structured_outputs.structured-outputs-assistant-final.components.cart uses 06-structured_outputs.structured-outputs-assistant-final.lib.assistant, so a change to 06-structured_outputs.structured-outputs-assistant-final.lib.assistant can break 06-structured_outputs.structured-outputs-assistant-final.components.cart, while a change to 06-structured_outputs.structured-outputs-assistant-final.components.cart can't break 06-structured_outputs.structured-outputs-assistant-final.lib.assistant.
Position
Below the diagonal: 06-structured_outputs.structured-outputs-assistant-final.components.cart uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar uses a type in 14-voice-agents.realtime-workspace-agents.src.app.types.
14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar uses 14-voice-agents.realtime-workspace-agents.src.app.types, so a change to 14-voice-agents.realtime-workspace-agents.src.app.types can break 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar, while a change to 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar can't break 14-voice-agents.realtime-workspace-agents.src.app.types.
Position
Below the diagonal: 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-final.components.tool-call uses a type in 16-built-in-tools.dashboard-demo-final.lib.assistant.
16-built-in-tools.dashboard-demo-final.components.tool-call uses 16-built-in-tools.dashboard-demo-final.lib.assistant, so a change to 16-built-in-tools.dashboard-demo-final.lib.assistant can break 16-built-in-tools.dashboard-demo-final.components.tool-call, while a change to 16-built-in-tools.dashboard-demo-final.components.tool-call can't break 16-built-in-tools.dashboard-demo-final.lib.assistant.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-final.components.tool-call uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in 18-responses-api.openai-simulator.src.dialogue.BaseDialogueAgent uses a type in 18-responses-api.openai-simulator.src.dialogue.types.
18-responses-api.openai-simulator.src.dialogue.BaseDialogueAgent uses 18-responses-api.openai-simulator.src.dialogue.types, so a change to 18-responses-api.openai-simulator.src.dialogue.types can break 18-responses-api.openai-simulator.src.dialogue.BaseDialogueAgent, while a change to 18-responses-api.openai-simulator.src.dialogue.BaseDialogueAgent can't break 18-responses-api.openai-simulator.src.dialogue.types.
Position
Below the diagonal: 18-responses-api.openai-simulator.src.dialogue.BaseDialogueAgent uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 25-realtime-2.src.agent.contracts uses a type in 06-structured_outputs.structured-outputs-assistant-final.lib.assistant.
25-realtime-2.src.agent.contracts uses 06-structured_outputs.structured-outputs-assistant-final.lib.assistant, so a change to 06-structured_outputs.structured-outputs-assistant-final.lib.assistant can break 25-realtime-2.src.agent.contracts, while a change to 25-realtime-2.src.agent.contracts can't break 06-structured_outputs.structured-outputs-assistant-final.lib.assistant.
Position
Below the diagonal: 25-realtime-2.src.agent.contracts uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop.metricLoopContracts uses 25-realtime-2.src.metricloop.metricLoopEngine, so a change to 25-realtime-2.src.metricloop.metricLoopEngine can break 25-realtime-2.src.metricloop.metricLoopContracts, while a change to 25-realtime-2.src.metricloop.metricLoopContracts can't break 25-realtime-2.src.metricloop.metricLoopEngine.
Position
Below the diagonal: 25-realtime-2.src.metricloop.metricLoopContracts uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.services.task_service uses 26-agents-sdk.app.models, so a change to 26-agents-sdk.app.models can break 26-agents-sdk.app.services.task_service, while a change to 26-agents-sdk.app.services.task_service can't break 26-agents-sdk.app.models.
Position
Below the diagonal: 26-agents-sdk.app.services.task_service uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.services.task_service uses 26-agents-sdk.app.schemas, so a change to 26-agents-sdk.app.schemas can break 26-agents-sdk.app.services.task_service, while a change to 26-agents-sdk.app.services.task_service can't break 26-agents-sdk.app.schemas.
Position
Below the diagonal: 26-agents-sdk.app.services.task_service uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.services.workspace_service uses 26-agents-sdk.app.models, so a change to 26-agents-sdk.app.models can break 26-agents-sdk.app.services.workspace_service, while a change to 26-agents-sdk.app.services.workspace_service can't break 26-agents-sdk.app.models.
Position
Below the diagonal: 26-agents-sdk.app.services.workspace_service uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.services.workspace_service uses 26-agents-sdk.app.storage.base, so a change to 26-agents-sdk.app.storage.base can break 26-agents-sdk.app.services.workspace_service, while a change to 26-agents-sdk.app.services.workspace_service can't break 26-agents-sdk.app.storage.base.
Position
Below the diagonal: 26-agents-sdk.app.services.workspace_service uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.storage uses 26-agents-sdk.app.config, so a change to 26-agents-sdk.app.config can break 26-agents-sdk.app.storage, while a change to 26-agents-sdk.app.storage can't break 26-agents-sdk.app.config.
Position
Below the diagonal: 26-agents-sdk.app.storage uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.storage uses 26-agents-sdk.app.models, so a change to 26-agents-sdk.app.models can break 26-agents-sdk.app.storage, while a change to 26-agents-sdk.app.storage can't break 26-agents-sdk.app.models.
Position
Below the diagonal: 26-agents-sdk.app.storage uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.storage uses 26-agents-sdk.app.storage.base, so a change to 26-agents-sdk.app.storage.base can break 26-agents-sdk.app.storage, while a change to 26-agents-sdk.app.storage can't break 26-agents-sdk.app.storage.base.
Position
Below the diagonal: 26-agents-sdk.app.storage uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 06-structured_outputs.structured-outputs-assistant-final.components uses a type in 06-structured_outputs.structured-outputs-assistant-final.components.cart.
06-structured_outputs.structured-outputs-assistant-final.components uses 06-structured_outputs.structured-outputs-assistant-final.components.cart, so a change to 06-structured_outputs.structured-outputs-assistant-final.components.cart can break 06-structured_outputs.structured-outputs-assistant-final.components, while a change to 06-structured_outputs.structured-outputs-assistant-final.components can't break 06-structured_outputs.structured-outputs-assistant-final.components.cart.
Position
Below the diagonal: 06-structured_outputs.structured-outputs-assistant-final.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 06-structured_outputs.structured-outputs-assistant-starting-point.components uses a type in 06-structured_outputs.structured-outputs-assistant-final.components.cart.
06-structured_outputs.structured-outputs-assistant-starting-point.components uses 06-structured_outputs.structured-outputs-assistant-final.components.cart, so a change to 06-structured_outputs.structured-outputs-assistant-final.components.cart can break 06-structured_outputs.structured-outputs-assistant-starting-point.components, while a change to 06-structured_outputs.structured-outputs-assistant-starting-point.components can't break 06-structured_outputs.structured-outputs-assistant-final.components.cart.
Position
Below the diagonal: 06-structured_outputs.structured-outputs-assistant-starting-point.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-final.components uses a type in 16-built-in-tools.dashboard-demo-final.stores.useDataStore.
16-built-in-tools.dashboard-demo-final.components uses 16-built-in-tools.dashboard-demo-final.stores.useDataStore, so a change to 16-built-in-tools.dashboard-demo-final.stores.useDataStore can break 16-built-in-tools.dashboard-demo-final.components, while a change to 16-built-in-tools.dashboard-demo-final.components can't break 16-built-in-tools.dashboard-demo-final.stores.useDataStore.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-final.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-final.components uses a type in 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar.
16-built-in-tools.dashboard-demo-final.components uses 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar, so a change to 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar can break 16-built-in-tools.dashboard-demo-final.components, while a change to 16-built-in-tools.dashboard-demo-final.components can't break 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-final.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-final.components uses a type in 16-built-in-tools.dashboard-demo-final.components.tool-call.
16-built-in-tools.dashboard-demo-final.components uses 16-built-in-tools.dashboard-demo-final.components.tool-call, so a change to 16-built-in-tools.dashboard-demo-final.components.tool-call can break 16-built-in-tools.dashboard-demo-final.components, while a change to 16-built-in-tools.dashboard-demo-final.components can't break 16-built-in-tools.dashboard-demo-final.components.tool-call.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-final.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-starting-point.components uses a type in 16-built-in-tools.dashboard-demo-final.stores.useDataStore.
16-built-in-tools.dashboard-demo-starting-point.components uses 16-built-in-tools.dashboard-demo-final.stores.useDataStore, so a change to 16-built-in-tools.dashboard-demo-final.stores.useDataStore can break 16-built-in-tools.dashboard-demo-starting-point.components, while a change to 16-built-in-tools.dashboard-demo-starting-point.components can't break 16-built-in-tools.dashboard-demo-final.stores.useDataStore.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-starting-point.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-starting-point.components uses a type in 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar.
16-built-in-tools.dashboard-demo-starting-point.components uses 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar, so a change to 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar can break 16-built-in-tools.dashboard-demo-starting-point.components, while a change to 16-built-in-tools.dashboard-demo-starting-point.components can't break 14-voice-agents.realtime-workspace-agents.src.app.components.workspace.Sidebar.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-starting-point.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in 16-built-in-tools.dashboard-demo-starting-point.components uses a type in 16-built-in-tools.dashboard-demo-final.components.tool-call.
16-built-in-tools.dashboard-demo-starting-point.components uses 16-built-in-tools.dashboard-demo-final.components.tool-call, so a change to 16-built-in-tools.dashboard-demo-final.components.tool-call can break 16-built-in-tools.dashboard-demo-starting-point.components, while a change to 16-built-in-tools.dashboard-demo-starting-point.components can't break 16-built-in-tools.dashboard-demo-final.components.tool-call.
Position
Below the diagonal: 16-built-in-tools.dashboard-demo-starting-point.components uses a module listed above it, which is the healthy direction.
25-realtime-2.src uses 06-structured_outputs.structured-outputs-assistant-final.lib.assistant, so a change to 06-structured_outputs.structured-outputs-assistant-final.lib.assistant can break 25-realtime-2.src, while a change to 25-realtime-2.src can't break 06-structured_outputs.structured-outputs-assistant-final.lib.assistant.
Position
Below the diagonal: 25-realtime-2.src uses a module listed above it, which is the healthy direction.
25-realtime-2.src uses 25-realtime-2.src.agent.contracts, so a change to 25-realtime-2.src.agent.contracts can break 25-realtime-2.src, while a change to 25-realtime-2.src can't break 25-realtime-2.src.agent.contracts.
Position
Below the diagonal: 25-realtime-2.src uses a module listed above it, which is the healthy direction.
25-realtime-2.src.agent uses 14-voice-agents.realtime-workspace-agents.src.app.types, so a change to 14-voice-agents.realtime-workspace-agents.src.app.types can break 25-realtime-2.src.agent, while a change to 25-realtime-2.src.agent can't break 14-voice-agents.realtime-workspace-agents.src.app.types.
Position
Below the diagonal: 25-realtime-2.src.agent uses a module listed above it, which is the healthy direction.
25-realtime-2.src.agent uses 25-realtime-2.src.realtime.realtimeResponseController, so a change to 25-realtime-2.src.realtime.realtimeResponseController can break 25-realtime-2.src.agent, while a change to 25-realtime-2.src.agent can't break 25-realtime-2.src.realtime.realtimeResponseController.
Position
Below the diagonal: 25-realtime-2.src.agent uses a module listed above it, which is the healthy direction.
25-realtime-2.src.agent uses 25-realtime-2.src.agent.contracts, so a change to 25-realtime-2.src.agent.contracts can break 25-realtime-2.src.agent, while a change to 25-realtime-2.src.agent can't break 25-realtime-2.src.agent.contracts.
Position
Below the diagonal: 25-realtime-2.src.agent uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop.useMetricLoopRealtime uses 25-realtime-2.src.metricloop.metricLoopContracts, so a change to 25-realtime-2.src.metricloop.metricLoopContracts can break 25-realtime-2.src.metricloop.useMetricLoopRealtime, while a change to 25-realtime-2.src.metricloop.useMetricLoopRealtime can't break 25-realtime-2.src.metricloop.metricLoopContracts.
Position
Below the diagonal: 25-realtime-2.src.metricloop.useMetricLoopRealtime uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server.metricloopForensicsRuntime uses 25-realtime-2.src.metricloop.metricLoopContracts, so a change to 25-realtime-2.src.metricloop.metricLoopContracts can break 25-realtime-2.src.server.metricloopForensicsRuntime, while a change to 25-realtime-2.src.server.metricloopForensicsRuntime can't break 25-realtime-2.src.metricloop.metricLoopContracts.
Position
Below the diagonal: 25-realtime-2.src.server.metricloopForensicsRuntime uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server.metricloopSessionStore uses 25-realtime-2.src.metricloop.metricLoopEngine, so a change to 25-realtime-2.src.metricloop.metricLoopEngine can break 25-realtime-2.src.server.metricloopSessionStore, while a change to 25-realtime-2.src.server.metricloopSessionStore can't break 25-realtime-2.src.metricloop.metricLoopEngine.
Position
Below the diagonal: 25-realtime-2.src.server.metricloopSessionStore uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server.metricloopSessionStore uses 25-realtime-2.src.metricloop.metricLoopContracts, so a change to 25-realtime-2.src.metricloop.metricLoopContracts can break 25-realtime-2.src.server.metricloopSessionStore, while a change to 25-realtime-2.src.server.metricloopSessionStore can't break 25-realtime-2.src.metricloop.metricLoopContracts.
Position
Below the diagonal: 25-realtime-2.src.server.metricloopSessionStore uses a module listed above it, which is the healthy direction.
26-agents-sdk.app uses 26-agents-sdk.app.config, so a change to 26-agents-sdk.app.config can break 26-agents-sdk.app, while a change to 26-agents-sdk.app can't break 26-agents-sdk.app.config.
Position
Below the diagonal: 26-agents-sdk.app uses a module listed above it, which is the healthy direction.
26-agents-sdk.app uses 26-agents-sdk.app.storage.base, so a change to 26-agents-sdk.app.storage.base can break 26-agents-sdk.app, while a change to 26-agents-sdk.app can't break 26-agents-sdk.app.storage.base.
Position
Below the diagonal: 26-agents-sdk.app uses a module listed above it, which is the healthy direction.
26-agents-sdk.app uses 26-agents-sdk.app.services.task_service, so a change to 26-agents-sdk.app.services.task_service can break 26-agents-sdk.app, while a change to 26-agents-sdk.app can't break 26-agents-sdk.app.services.task_service.
Position
Below the diagonal: 26-agents-sdk.app uses a module listed above it, which is the healthy direction.
26-agents-sdk.app uses 26-agents-sdk.app.services.workspace_service, so a change to 26-agents-sdk.app.services.workspace_service can break 26-agents-sdk.app, while a change to 26-agents-sdk.app can't break 26-agents-sdk.app.services.workspace_service.
Position
Below the diagonal: 26-agents-sdk.app uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.agents uses 26-agents-sdk.app.config, so a change to 26-agents-sdk.app.config can break 26-agents-sdk.app.agents, while a change to 26-agents-sdk.app.agents can't break 26-agents-sdk.app.config.
Position
Below the diagonal: 26-agents-sdk.app.agents uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.agents uses 26-agents-sdk.app.models, so a change to 26-agents-sdk.app.models can break 26-agents-sdk.app.agents, while a change to 26-agents-sdk.app.agents can't break 26-agents-sdk.app.models.
Position
Below the diagonal: 26-agents-sdk.app.agents uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.agents uses 26-agents-sdk.app.storage.base, so a change to 26-agents-sdk.app.storage.base can break 26-agents-sdk.app.agents, while a change to 26-agents-sdk.app.agents can't break 26-agents-sdk.app.storage.base.
Position
Below the diagonal: 26-agents-sdk.app.agents uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.agents uses 26-agents-sdk.app.services.task_service, so a change to 26-agents-sdk.app.services.task_service can break 26-agents-sdk.app.agents, while a change to 26-agents-sdk.app.agents can't break 26-agents-sdk.app.services.task_service.
Position
Below the diagonal: 26-agents-sdk.app.agents uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.agents uses 26-agents-sdk.app.services.workspace_service, so a change to 26-agents-sdk.app.services.workspace_service can break 26-agents-sdk.app.agents, while a change to 26-agents-sdk.app.agents can't break 26-agents-sdk.app.services.workspace_service.
Position
Below the diagonal: 26-agents-sdk.app.agents uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.api uses 26-agents-sdk.app.schemas, so a change to 26-agents-sdk.app.schemas can break 26-agents-sdk.app.api, while a change to 26-agents-sdk.app.api can't break 26-agents-sdk.app.schemas.
Position
Below the diagonal: 26-agents-sdk.app.api uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.api uses 26-agents-sdk.app.storage.base, so a change to 26-agents-sdk.app.storage.base can break 26-agents-sdk.app.api, while a change to 26-agents-sdk.app.api can't break 26-agents-sdk.app.storage.base.
Position
Below the diagonal: 26-agents-sdk.app.api uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.api uses 26-agents-sdk.app.services.task_service, so a change to 26-agents-sdk.app.services.task_service can break 26-agents-sdk.app.api, while a change to 26-agents-sdk.app.api can't break 26-agents-sdk.app.services.task_service.
Position
Below the diagonal: 26-agents-sdk.app.api uses a module listed above it, which is the healthy direction.
26-agents-sdk.app.api uses 26-agents-sdk.app.services.workspace_service, so a change to 26-agents-sdk.app.services.workspace_service can break 26-agents-sdk.app.api, while a change to 26-agents-sdk.app.api can't break 26-agents-sdk.app.services.workspace_service.
Position
Below the diagonal: 26-agents-sdk.app.api uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop uses 14-voice-agents.realtime-workspace-agents.src.app.types, so a change to 14-voice-agents.realtime-workspace-agents.src.app.types can break 25-realtime-2.src.metricloop, while a change to 25-realtime-2.src.metricloop can't break 14-voice-agents.realtime-workspace-agents.src.app.types.
Position
Below the diagonal: 25-realtime-2.src.metricloop uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop uses 25-realtime-2.src.metricloop.metricLoopEngine, so a change to 25-realtime-2.src.metricloop.metricLoopEngine can break 25-realtime-2.src.metricloop, while a change to 25-realtime-2.src.metricloop can't break 25-realtime-2.src.metricloop.metricLoopEngine.
Position
Below the diagonal: 25-realtime-2.src.metricloop uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop uses 25-realtime-2.src.realtime.realtimeResponseController, so a change to 25-realtime-2.src.realtime.realtimeResponseController can break 25-realtime-2.src.metricloop, while a change to 25-realtime-2.src.metricloop can't break 25-realtime-2.src.realtime.realtimeResponseController.
Position
Below the diagonal: 25-realtime-2.src.metricloop uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop uses 25-realtime-2.src.metricloop.metricLoopContracts, so a change to 25-realtime-2.src.metricloop.metricLoopContracts can break 25-realtime-2.src.metricloop, while a change to 25-realtime-2.src.metricloop can't break 25-realtime-2.src.metricloop.metricLoopContracts.
Position
Below the diagonal: 25-realtime-2.src.metricloop uses a module listed above it, which is the healthy direction.
25-realtime-2.src.metricloop uses 25-realtime-2.src.metricloop.useMetricLoopRealtime, so a change to 25-realtime-2.src.metricloop.useMetricLoopRealtime can break 25-realtime-2.src.metricloop, while a change to 25-realtime-2.src.metricloop can't break 25-realtime-2.src.metricloop.useMetricLoopRealtime.
Position
Below the diagonal: 25-realtime-2.src.metricloop uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server uses 25-realtime-2.src.metricloop.metricLoopEngine, so a change to 25-realtime-2.src.metricloop.metricLoopEngine can break 25-realtime-2.src.server, while a change to 25-realtime-2.src.server can't break 25-realtime-2.src.metricloop.metricLoopEngine.
Position
Below the diagonal: 25-realtime-2.src.server uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server uses 25-realtime-2.src.metricloop.metricLoopContracts, so a change to 25-realtime-2.src.metricloop.metricLoopContracts can break 25-realtime-2.src.server, while a change to 25-realtime-2.src.server can't break 25-realtime-2.src.metricloop.metricLoopContracts.
Position
Below the diagonal: 25-realtime-2.src.server uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server uses 25-realtime-2.src.metricloop.useMetricLoopRealtime, so a change to 25-realtime-2.src.metricloop.useMetricLoopRealtime can break 25-realtime-2.src.server, while a change to 25-realtime-2.src.server can't break 25-realtime-2.src.metricloop.useMetricLoopRealtime.
Position
Below the diagonal: 25-realtime-2.src.server uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server uses 25-realtime-2.src.server.metricloopForensicsRuntime, so a change to 25-realtime-2.src.server.metricloopForensicsRuntime can break 25-realtime-2.src.server, while a change to 25-realtime-2.src.server can't break 25-realtime-2.src.server.metricloopForensicsRuntime.
Position
Below the diagonal: 25-realtime-2.src.server uses a module listed above it, which is the healthy direction.
25-realtime-2.src.server uses 25-realtime-2.src.server.metricloopSessionStore, so a change to 25-realtime-2.src.server.metricloopSessionStore can break 25-realtime-2.src.server, while a change to 25-realtime-2.src.server can't break 25-realtime-2.src.server.metricloopSessionStore.
Position
Below the diagonal: 25-realtime-2.src.server uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 36.5 · Weak · gated by R10, R7, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
537
High / Critical
A05:2025 — Injection
43
High / Critical
A07:2025 — Authentication Failures
2
Medium
A02:2025 — Security Misconfiguration
2
Medium
A08:2025 — Software or Data Integrity Failures
2
Medium
Roadmap
Top priorities: Resolve the 242 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (12), REDACTED (5), select.tsx (5); 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Low coverage finding(s) in Code Coverage — start with ValuemaxxingLab.tsx, REDACTED.
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.
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.
Reconcile the README with reality: 11-recommendation/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10; 20-agent-rft/README.md names Python 3.9 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.9; 21-agentic-memory/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10; 25-realtime-2/README.md names React 19, but the manifest declares `react` ^18; 25-realtime-2/README.md names Vite 7, but the manifest declares `vite` ^5.3.1.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 435
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.
Serious — 768
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.
Minor — 544
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
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 81 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.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 81 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 1597 of 1747 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
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.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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 617 sampled here came from .js/.ts/.tsx 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. `09-realtime/realtime-from-scratch/tailwind.config.ts`, `REDACTED`, `14-voice-agents/realtime-workspace-agents/tailwind.config.ts`, `15-reinforcement-fine-tuning/projects/toy/pipelines/pipeline.py`, `15-reinforcement-fine-tuning/projects/toy/pipelines/rft_pipeline.py`, … (+8 more) 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.
AC6 Visual & motion safety — 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. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in 25-realtime-2/src/server/realtimeSidebandSession.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — 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. `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
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.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
R10 Code Duplication — 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. 167 further occurrence(s) are not listed individually; the score already reflects all 207.
R2 Cyclomatic Complexity — 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. 60 further occurrence(s) are not listed individually; the score already reflects all 100.
R4 Test Coverage — 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. 323 further occurrence(s) are not listed individually; the score already reflects all 363.
R7 Dead Code — 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. 83 further occurrence(s) are not listed individually; the score already reflects all 123.
R8 Dependency Hygiene — 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. 93 further occurrence(s) are not listed individually; the score already reflects all 133.
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.
X10 Duplicated predicate — 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. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
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
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
71 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ValuemaxxingLab.ValuemaxxingLab at 102. 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 useMetricLoopRealtime.useMetricLoopRealtime.connect at 16 — they are counted neither in the figure above nor in this dimension's score.
+ 62 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with ValuemaxxingLab.ValuemaxxingLab (cyclomatic 102), MetricLoopDashboard.MetricLoopDashboard (cyclomatic 70), ParetoFrontier.ParetoFrontier (cyclomatic 65). — 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 4 together lifts Cyclomatic Complexity from 5.1 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 82 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with tracing_storing.process_single_item (cognitive 104), ValuemaxxingLab.ValuemaxxingLab (cognitive 88), ParetoFrontier.ParetoFrontier (cognitive 83). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 4.2 to about 5.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 41 FunctionTooLong finding(s) in God Classes — start with App.tsx (5), useSupplyRealtime.ts (3), ValuemaxxingLab.tsx (2). — One of this dimension's main actionable groups (41 warning-level).
Resolve the 16 FileTooLong finding(s) in God Classes — start with ValuemaxxingLab.tsx, agent_service.py, App.tsx. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes — start with ValuemaxxingLab.tsx, useMetricLoopRealtime.ts, MetricLoopDashboard.tsx. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
27 duplicated block group(s) detected. 1.1 % of the production lines (824 of 73,988) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx, .ts (80% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (21 corresponding lines) · ×221-agentic-memory/scripts/agent_service.py:1084
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with agent_service.py, mmrag_bh.py. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (24 lines × 2) finding(s) in Code Duplication — start with 2_tools.py, upload_utils.py. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with 01_create_stanbot_draft_datasett.py, 4_queue_server.py. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
13 production modules (npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 10 of the 13 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 58.0% — 2 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in 24-api-codex/agentic-legibility-scorecard/, the 3 run(s) test reliability made; node:test via `npm ci --ignore-scripts` in 27-valuemaxxing/, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
Resolve the 2 Low coverage finding(s) in Code Coverage — start with ValuemaxxingLab.tsx, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 174 tests.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in 24-api-codex/agentic-legibility-scorecard/ (17 tests); vitest via `npm ci --ignore-scripts` in 25-realtime-2/ (127 tests); node:test via `npm ci --ignore-scripts` in 27-valuemaxxing/ (27 tests)): measured (0 flaky).
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
137 outdated, 0 yanked pinned Python distributions. 161 of 171 shipped distributions were graded against pypi.org (0 not published there, 10 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (poetry.lock, REDACTED, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
Outdated: aiohappyeyeballs · ×137
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 257 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 171 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (86 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 46 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is 25-realtime-2/src/agent/useSupplyRealtime.ts. Counted over 250 of the 557 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
2 deducted task-comment markers across 69208 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.
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with materials.ts, 02_stanbot_eval.py. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names09-realtime/openai-realtime-console-example/src/utils/wav_renderer.ts:68
What to do
Resolve the 11 redundant comment finding(s) in Comment Value — start with useAudioDownload.ts (3), REDACTED (2), constants.ts (2). — One of this dimension's main actionable groups (11 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 22 build units (Python, checkout, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×225-realtime-2/package.json:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
6 % of calls cross a namespace and 2 % go through an interface, but 78 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .js/.ts/.tsx source only — this repository's .py was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
43 finding(s): 0 critical, 4 high, 39 medium, 0 low. semgrep hit a parse error in 13 file(s) — `09-realtime/realtime-from-scratch/tailwind.config.ts` (line 18), `REDACTED` (line 42), `14-voice-agents/realtime-workspace-agents/tailwind.config.ts` (line 18), `15-reinforcement-fine-tuning/projects/toy/pipelines/pipeline.py` (lines 2–3), `15-reinforcement-fine-tuning/projects/toy/pipelines/rft_pipeline.py` (lines 2–3), … (+8 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 321 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (202), REDACTED (94), REDACTED (15). — One of this dimension's main actionable groups (321 issue-level).
Resolve the 44 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17), REDACTED (10), REDACTED (9). — One of this dimension's main actionable groups (44 issue-level).
Resolve the 12 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
245 of 250 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is 21-agentic-memory/scripts/agent_service.py. Counted over 250 of the 557 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×321-agentic-memory/scripts/agent_service.py:1
Concentrated knowledge decay
What to do
Resolve the 242 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (12), REDACTED (5), select.tsx (5). — One of this dimension's main actionable groups (242 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with agent_service.py, App.tsx, ValuemaxxingLab.tsx. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d43_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 171 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.4 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:551, 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:52
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:571, 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:574
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.5 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×11) — 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:75, 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:75, 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:63, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×6) — 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:93, 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:93, 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:133, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×6) — 14-voice-agents/realtime-workspace-agents/src/app/components/BottomToolbar.tsx:158, 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:109, 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/TabContent.tsx:50, …
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — 21-agentic-memory/components/configuration-panel.tsx:513, 21-agentic-memory/components/configuration-panel.tsx:536, 21-agentic-memory/components/configuration-panel.tsx:559
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — 22-chatgptapp-pingpong/public/pingpong.html:469
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×6) — 25-realtime-2/src/metricloop/MetricLoopVisualizations.tsx:108, 25-realtime-2/src/metricloop/MetricLoopVisualizations.tsx:113, 26-agents-sdk/web/src/components/task-card.tsx:36, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×5) — 09-realtime/realtime-from-scratch/app/layout.tsx:27, 14-voice-agents/realtime-workspace-agents/src/app/layout.tsx:16, 17-gpt-5/minecraft/index.html:2, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — 17-gpt-5/outputs/saas_landing_page_persistence.html:341
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×2) — 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:1205, 25-realtime-2/src/metricloop/MetricLoopVisualizations.tsx:170
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — 26-agents-sdk/fake data/asset-task/event-page-template.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×10) — 09-realtime/openai-realtime-console-example/src/components/toggle/Toggle.tsx:48, 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:594, 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:655, …
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) — 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:178, 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:104
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×4) — 25-realtime-2/src/App.tsx:1483, 26-agents-sdk/web/src/components/app-shell.tsx:18, 26-agents-sdk/web/src/components/app-shell.tsx:19, …
This <section role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — 25-realtime-2/src/App.tsx:1853
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — 27-valuemaxxing/app/ValuemaxxingLab.tsx:1241
This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — 27-valuemaxxing/app/ValuemaxxingLab.tsx:302
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×7) — 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:75, 06-structured_outputs/structured-outputs-assistant-final/components/ui/textarea.tsx:13, 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:75, …
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×11) — 06-structured_outputs/structured-outputs-math-tutor-final/components/ui/warning.tsx:15, 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/ui/warning.tsx:15, 09-realtime/realtime-from-scratch/app/page.tsx:77, …
<select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — 14-voice-agents/realtime-workspace-agents/src/app/components/BottomToolbar.tsx:158
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:221, 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:109, 21-agentic-memory/components/ui/input.tsx:7
`#play` sets color: #fff on background-color: #4caf50 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — 17-gpt-5/minecraft/index.html:38
`.chevron` moves (`transition: transform .25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 17-gpt-5/outputs/saas_landing_page_persistence.html:231
`.fade-in` moves (`animation: fadeUp .3s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 17-gpt-5/outputs/saas_landing_page_persistence.html:250
The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. (×2) — 17-gpt-5/outputs/saas_landing_page_persistence.html:390, 17-gpt-5/outputs/saas_landing_page_persistence.html:401
`.hud` moves (`animation: floatIn 500ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 22-chatgptapp-pingpong/public/pingpong.html:64
`.analysis` moves (`animation: floatIn 500ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 22-chatgptapp-pingpong/public/pingpong.html:127
`button` moves (`transition: transform 150ms ease, box-shadow 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 22-chatgptapp-pingpong/public/pingpong.html:179
`.arena` moves (`animation: glowIn 700ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 22-chatgptapp-pingpong/public/pingpong.html:203
`.arena::after` moves (`animation: pulse 4s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — 22-chatgptapp-pingpong/public/pingpong.html:225
`.result-identity > span:last-child` sets color: #777970 on background-color: #efede7 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — 27-valuemaxxing/app/globals.css:949
`.experiment-number` sets color: #fffefa on background-color: #f05d35 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — 27-valuemaxxing/app/globals.css:1330
`.tool-chips span` sets color: #777970 on background-color: #fffefa — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — 27-valuemaxxing/app/globals.css:1854
`.frontier-chart-footer` sets color: #777970 on background-color: #f8f7f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — 27-valuemaxxing/app/globals.css:2456
`.experiment-action select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — 27-valuemaxxing/app/globals.css:1403
`.comment-form textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — 26-agents-sdk/web/src/styles/app.css:703
`.composer-title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — 26-agents-sdk/web/src/styles/app.css:1024
`.composer-session input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — 26-agents-sdk/web/src/styles/app.css:1091
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`SupplyAgentContextValue` declares 17 required operations: `getHikingNeeds`, `getSavedProfile`, `getScreenState`, `searchProducts`, `applyFilters`, `highlightProducts`, `openProduct`, `selectQuantity`, `selectShoeSize`, `openSizeGuide`, `closeSizeGuide`, `addToCart`, `summarizeProductReviews`, `searchWeatherWeb`, `goToCart`, `goHome`, `clearFilters`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — 25-realtime-2/src/agent/contracts.ts:206
`MetricLoopAgentContextValue` declares 16 required operations: `getDashboardState`, `openActivationFunnel`, `applySegmentFilter`, `applyFilter`, `openInsight`, `setBreakdown`, `switchVisualization`, `comparePeriods`, `checkReleaseNotes`, `clusterSupportTickets`, `openSessionReplays`, `openSessionReplay`, `generateInvestigationBoard`, `startRootCauseInvestigation`, `updateInvestigationNotebook`, `noOp`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — 25-realtime-2/src/metricloop/metricLoopContracts.ts:326
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`handleTool` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — 06-structured_outputs/structured-outputs-assistant-starting-point/lib/assistant.ts:29
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — 25-realtime-2/src/App.tsx:1701
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/__tests__/workspaceManagerAgent.integration.test.ts:14
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 68 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
11-recommendation/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 11-recommendation/README.md:19
20-agent-rft/README.md names Python 3.9 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.9. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 20-agent-rft/README.md:6
21-agentic-memory/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 21-agentic-memory/README.md:27
25-realtime-2/README.md names React 19, but the manifest declares `react` ^18. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 25-realtime-2/README.md:91
25-realtime-2/README.md names Vite 7, but the manifest declares `vite` ^5.3.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — 25-realtime-2/README.md:92
What to do
Reconcile the README with reality: 11-recommendation/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10; 20-agent-rft/README.md names Python 3.9 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.9; 21-agentic-memory/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10; 25-realtime-2/README.md names React 19, but the manifest declares `react` ^18; 25-realtime-2/README.md names Vite 7, but the manifest declares `vite` ^5.3.1.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.6 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 4/19 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `06-structured_outputs/structured-outputs-assistant-final`, `06-structured_outputs/structured-outputs-assistant-starting-point`, `06-structured_outputs/structured-outputs-math-tutor-final`, `06-structured_outputs/structured-outputs-math-tutor-starting-point`, `07-reasoning/shipmentPlanning/backend` and 10 more.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
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.
`06-structured_outputs/node-example/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`. — 06-structured_outputs/node-example/package.json:13
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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
This repository versions its schema (Alembic), but SQLAlchemy create_all() here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Alembic own the schema. (×2) — 26-agents-sdk/app/db.py:29, 05-4o_fine_tuning/example_cot.py:132
What to do
Turn off SQLAlchemy create_all() in production and let the versioned migrations own the schema.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety9.3 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
06-structured_outputs/structured-outputs-assistant-final/ and 06-structured_outputs/structured-outputs-assistant-starting-point/ are near-verbatim copies of each other: 45 files are byte-identical under the same relative paths (~27598 lines; the trees hold 51 and 51 files). That is one structural fact, not 45 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
16-built-in-tools/dashboard-demo-final/ and 16-built-in-tools/dashboard-demo-starting-point/ are near-verbatim copies of each other: 49 files are byte-identical under the same relative paths (~15629 lines; the trees hold 53 and 53 files). That is one structural fact, not 49 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
06-structured_outputs/structured-outputs-math-tutor-final/ and 06-structured_outputs/structured-outputs-math-tutor-starting-point/ are near-verbatim copies of each other: 31 files are byte-identical under the same relative paths (~7760 lines; the trees hold 31 and 31 files). That is one structural fact, not 31 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — REDACTED:1
51 duplicated blocks under 06-structured_outputs/ have copies in at least two of the sibling directories structured-outputs-assistant-final, structured-outputs-assistant-starting-point, structured-outputs-math-tutor-final, structured-outputs-math-tutor-starting-point — 45 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 51 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 51 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 51 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — 06-structured_outputs/structured-outputs-assistant-final/lib/database.ts:1
29 duplicated blocks under 16-built-in-tools/ have copies in at least two of the sibling directories dashboard-demo-final, dashboard-demo-starting-point — 28 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 29 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1
19 duplicated blocks under the repository root have copies in at least two of the sibling directories 06-structured_outputs, 07-reasoning, 09-realtime, 13-image-gen, 14-voice-agents, 16-built-in-tools (+5 more sibling(s) not listed) — 14 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:3
15 duplicated blocks under 25-realtime-2/src/ have copies in at least two of the sibling directories agent, metricloop, server — 10 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — 25-realtime-2/src/agent/useSupplyRealtime.ts:66
16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1 · 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:1 — these 2 files are line-for-line copies of one another — 344 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1
25-realtime-2/src/agent/useSupplyRealtime.ts:66 · 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:68 — the two spans are one implementation copied and then locally edited — 2050 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. — 25-realtime-2/src/agent/useSupplyRealtime.ts:66
16-built-in-tools/dashboard-demo-final/components/data-table.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/data-table.tsx:3 — these 2 files are line-for-line copies of one another — 226 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 16-built-in-tools/dashboard-demo-final/components/data-table.tsx:3
16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:1 · 16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:1 — these 2 files are line-for-line copies of one another — 190 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:1
REDACTED:3 · REDACTED:3 · REDACTED:3 · REDACTED:3 — these 4 files are line-for-line copies of one another — 183 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:3
06-structured_outputs/structured-outputs-assistant-final/lib/database.ts:1 · 06-structured_outputs/structured-outputs-assistant-starting-point/lib/database.ts:1 — these 2 files are line-for-line copies of one another — 136 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/lib/database.ts:1
06-structured_outputs/structured-outputs-assistant-final/components/ui/dropdown-menu.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/dropdown-menu.tsx:3 — these 2 files are line-for-line copies of one another — 117 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/dropdown-menu.tsx:3
21-agentic-memory/components/ui/context-menu.tsx:110 · 21-agentic-memory/components/ui/menubar.tsx:87 — 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. — 21-agentic-memory/components/ui/context-menu.tsx:110
21-agentic-memory/components/ui/item.tsx:8 · 21-agentic-memory/components/ui/sidebar.tsx:346 — the two spans are one implementation copied and then locally edited — 394 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. — 21-agentic-memory/components/ui/item.tsx:8
06-structured_outputs/structured-outputs-assistant-final/lib/components-mapping.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/lib/components-mapping.tsx:3 — these 2 files are line-for-line copies of one another — 107 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/lib/components-mapping.tsx:3
21-agentic-memory/components/ui/use-toast.ts:4 · 21-agentic-memory/hooks/use-toast.ts:4 — these 2 files are line-for-line copies of one another — 103 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 21-agentic-memory/components/ui/use-toast.ts:4
06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:1 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/useSolution.ts:1 — these 2 files are line-for-line copies of one another — 100 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:1
16-built-in-tools/dashboard-demo-final/components/chat.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/chat.tsx:3 — these 2 files are line-for-line copies of one another — 100 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 16-built-in-tools/dashboard-demo-final/components/chat.tsx:3
21-agentic-memory/components/ui/dropdown-menu.tsx:131 · 21-agentic-memory/components/ui/menubar.tsx:149 — 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. — 21-agentic-memory/components/ui/dropdown-menu.tsx:131
06-structured_outputs/structured-outputs-assistant-final/components/ui/select.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/select.tsx:3 · 16-built-in-tools/dashboard-demo-final/components/ui/select.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/ui/select.tsx:3 — these 4 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/select.tsx:3
06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:3 — these 2 files are line-for-line copies of one another — 92 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:3
16-built-in-tools/dashboard-demo-final/components/chart-area-interactive.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/chart-area-interactive.tsx:3 — these 2 files are line-for-line copies of one another — 88 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 16-built-in-tools/dashboard-demo-final/components/chart-area-interactive.tsx:3
21-agentic-memory/components/chat-interface.tsx:282 · 21-agentic-memory/components/chat-interface.tsx:367 — all 2 copies are in the same file, 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. — 21-agentic-memory/components/chat-interface.tsx:282
06-structured_outputs/structured-outputs-assistant-final/components/assistant.tsx:12 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/assistant.tsx:12 — the two spans are one implementation copied and then locally edited — 420 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. — 06-structured_outputs/structured-outputs-assistant-final/components/assistant.tsx:12
16-built-in-tools/dashboard-demo-final/components/annotations.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/annotations.tsx:3 — 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. — 16-built-in-tools/dashboard-demo-final/components/annotations.tsx:3
06-structured_outputs/structured-outputs-assistant-final/components/ui/sheet.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/sheet.tsx:3 — these 2 files are line-for-line copies of one another — 72 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/sheet.tsx:3
25-realtime-2/src/agent/useSupplyRealtime.ts:929 · 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:1047 — 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. — 25-realtime-2/src/agent/useSupplyRealtime.ts:929
14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/chatSupervisor/supervisorAgent.ts:186 · 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/workspaceManager.ts:186 — 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. — 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/chatSupervisor/supervisorAgent.ts:186
06-structured_outputs/structured-outputs-math-tutor-final/components/solution.tsx:2 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/solution.tsx:2 — these 2 files are line-for-line copies of one another — 66 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-math-tutor-final/components/solution.tsx:2
06-structured_outputs/structured-outputs-assistant-final/components/ui/card.tsx:5 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/card.tsx:5 · 16-built-in-tools/dashboard-demo-final/components/ui/card.tsx:5 · 16-built-in-tools/dashboard-demo-starting-point/components/ui/card.tsx:5 — the 4 copies are spread across 4 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/card.tsx:5
06-structured_outputs/structured-outputs-assistant-final/components/ui/drawer.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/drawer.tsx:3 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/drawer.tsx:3
06-structured_outputs/structured-outputs-math-tutor-final/components/ui/icons.tsx:3 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/ui/icons.tsx:3 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-math-tutor-final/components/ui/icons.tsx:3
06-structured_outputs/structured-outputs-math-tutor-final/tailwind.config.ts:2 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/tailwind.config.ts:2 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-math-tutor-final/tailwind.config.ts:2
06-structured_outputs/structured-outputs-assistant-final/components/ui/breadcrumb.tsx:1 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/breadcrumb.tsx:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/breadcrumb.tsx:1
REDACTED:5 · REDACTED:5 — 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. — REDACTED:5
06-structured_outputs/structured-outputs-assistant-final/components/ui/table.tsx:1 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/table.tsx:1 · 16-built-in-tools/dashboard-demo-final/components/ui/table.tsx:1 · 16-built-in-tools/dashboard-demo-starting-point/components/ui/table.tsx:1 — these 4 files are line-for-line copies of one another — 58 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-assistant-final/components/ui/table.tsx:1
06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:1 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/prompt-form.tsx:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:1
16-built-in-tools/dashboard-demo-final/tailwind.config.ts:1 · 16-built-in-tools/dashboard-demo-starting-point/tailwind.config.ts:1 — these 2 files are line-for-line copies of one another — 55 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — 16-built-in-tools/dashboard-demo-final/tailwind.config.ts:1
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.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1 imports openai/lib/jsonschema, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1
06-structured_outputs/structured-outputs-assistant-starting-point/lib/tools.ts:1 imports openai/lib/jsonschema, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — 06-structured_outputs/structured-outputs-assistant-starting-point/lib/tools.ts:1
09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:17 imports @openai/realtime-api-beta/dist/lib/client.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:17
16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:7 imports react-syntax-highlighter/dist/esm/styles/prism, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:7
16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:7 imports react-syntax-highlighter/dist/esm/styles/prism, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — 16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:7
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 81 and cognitive complexity 95; 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. (×2) — 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:165, 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:165
(anonymous) has cyclomatic complexity 53 and cognitive complexity 59; 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. — 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:846
(anonymous) has cyclomatic complexity 52 and cognitive complexity 60; 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. — 25-realtime-2/src/agent/useSupplyRealtime.ts:718
ValuemaxxingLab has cyclomatic complexity 44 and cognitive complexity 42; 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. — 27-valuemaxxing/app/ValuemaxxingLab.tsx:777
runTool has cyclomatic complexity 34 and cognitive complexity 44; 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. — 25-realtime-2/src/server/metricloopToolRuntime.ts:72
buildGameInsights has cyclomatic complexity 27 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. — REDACTED:155
(anonymous) has cyclomatic complexity 27 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. — 25-realtime-2/src/agent/useSupplyRealtime.ts:573
update has cyclomatic complexity 27 and cognitive complexity 28; 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. — 18-responses-api/openai-simulator/src/scenes/MainScene.ts:287
ChatInterface has cyclomatic complexity 27 and cognitive complexity 20; 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. — 21-agentic-memory/components/chat-interface.tsx:237
runTool has cyclomatic complexity 26 and cognitive complexity 39; 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. — 25-realtime-2/src/server/metricloopForensicsRuntime.ts:271
(anonymous) has cyclomatic complexity 25 and cognitive complexity 32; 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:451
ParetoFrontier has cyclomatic complexity 25 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 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. — 27-valuemaxxing/app/ParetoFrontier.tsx:356
(anonymous) has cyclomatic complexity 24 and cognitive complexity 44; 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. — 18-responses-api/openai-simulator/src/scenes/MainScene.ts:781
provideResponseStream has cyclomatic complexity 23 and cognitive complexity 32; 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. — 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:30
formatToolChip has cyclomatic complexity 23 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 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. — 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:151
analysisViewReducer 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. — 24-api-codex/agentic-legibility-scorecard/lib/analysis/state.ts:51
runNpcConversation has cyclomatic complexity 22 and cognitive complexity 39; 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. — 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1200
runPythonAgent has cyclomatic complexity 22 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. — 21-agentic-memory/lib/python-agent-bridge.ts:286
runToolExperiment has cyclomatic complexity 21 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. — REDACTED:256
buildEngineeringBrief has cyclomatic complexity 21 and cognitive complexity 18; 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. — 25-realtime-2/src/metricloop/metricLoopEngine.ts:1174
SupplyAssistant has cyclomatic complexity 21 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 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. — 25-realtime-2/src/agent/SupplyAssistant.tsx:198
normalizeImportedResult has cyclomatic complexity 21 and cognitive complexity 16; 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. — 27-valuemaxxing/lib/runs.ts:113
Home has cyclomatic complexity 20 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. — 24-api-codex/agentic-legibility-scorecard/app/page.tsx:25
(anonymous) has cyclomatic complexity 20 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. — 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:324
ForensicsTraceCard has cyclomatic complexity 20 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 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. — 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx:114
currentPhaseLabel has cyclomatic complexity 19 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. — 24-api-codex/agentic-legibility-scorecard/app/page.tsx:450
(anonymous) has cyclomatic complexity 19 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 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. — REDACTED:367
CacheResults has cyclomatic complexity 19 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 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. — 27-valuemaxxing/app/ValuemaxxingLab.tsx:498
ConsolePage has cyclomatic complexity 19 and cognitive complexity 16; 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. — 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:57
formatToolChip has cyclomatic complexity 18 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 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. — 25-realtime-2/src/agent/useSupplyRealtime.ts:157
createDashboardFiltersForRow has cyclomatic complexity 18 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 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. — 25-realtime-2/src/server/metricloopForensicsRuntime.ts:667
(anonymous) 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. — 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:110
addBorderToImage has cyclomatic complexity 17 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. — 13-image-gen/imagegen-demo/src/lib/imageProcessing.ts:22
(anonymous) has cyclomatic complexity 17 and cognitive complexity 16; 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. — 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:703
buildShoeInsights has cyclomatic complexity 17 and cognitive complexity 16; 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. — 25-realtime-2/src/reviewInsights.ts:130
outputText has cyclomatic complexity 17 and cognitive complexity 16; 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. — 26-agents-sdk/web/src/components/task-drawer.tsx:52
TaskDrawer has cyclomatic complexity 17 and cognitive complexity 16; 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. — 26-agents-sdk/web/src/components/task-drawer.tsx:65
(anonymous) has cyclomatic complexity 17 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. (×2) — REDACTED:193, REDACTED:193
Do you agree with this assessment?
R3 · Large Files7.8 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
27-valuemaxxing/app/ValuemaxxingLab.tsx has 1862 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 27-valuemaxxing/app/ValuemaxxingLab.tsx:1
25-realtime-2/src/App.tsx has 1763 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/App.tsx:1
25-realtime-2/src/metricloop/metricLoopEngine.ts has 1390 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/metricloop/metricLoopEngine.ts:1
18-responses-api/openai-simulator/src/scenes/MainScene.ts has 1249 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1
25-realtime-2/src/metricloop/MetricLoopDashboard.tsx has 1165 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:1
25-realtime-2/src/metricloop/useMetricLoopRealtime.ts has 1153 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:1
25-realtime-2/src/data.ts has 998 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/data.ts:1
25-realtime-2/src/agent/useSupplyRealtime.ts has 995 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/agent/useSupplyRealtime.ts:1
21-agentic-memory/components/configuration-panel.tsx has 840 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 21-agentic-memory/components/configuration-panel.tsx:1
27-valuemaxxing/app/ParetoFrontier.tsx has 777 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 27-valuemaxxing/app/ParetoFrontier.tsx:1
09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx has 732 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:1
25-realtime-2/src/metricloop/metricLoopForensicsData.ts has 726 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/metricloop/metricLoopForensicsData.ts:1
25-realtime-2/src/server/metricloopForensicsRuntime.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/server/metricloopForensicsRuntime.ts:1
21-agentic-memory/components/ui/sidebar.tsx has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 21-agentic-memory/components/ui/sidebar.tsx:1
25-realtime-2/src/metricloop/MetricLoopNotebook.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx:1
REDACTED has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js:1
24-api-codex/agentic-legibility-scorecard/app/page.tsx has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 24-api-codex/agentic-legibility-scorecard/app/page.tsx:1
16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:1
16-built-in-tools/dashboard-demo-final/lib/assistant.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1
24-api-codex/agentic-legibility-scorecard/lib/analysis/openai.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 24-api-codex/agentic-legibility-scorecard/lib/analysis/openai.ts:1
21-agentic-memory/components/chat-interface.tsx has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 21-agentic-memory/components/chat-interface.tsx:1
06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1
25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx:1
14-voice-agents/realtime-workspace-agents/src/app/App.tsx has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage1.6 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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. (×40) — 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1, 21-agentic-memory/components/configuration-panel.tsx:1, 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
54 outdated package(s); JS/npm CVEs scored in D30
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
`21-agentic-memory` is TypeScript, but a type error in it cannot fail anything this repository runs: its Next.js config sets `typescript.ignoreBuildErrors: true`, so `next build` — the one step that would run the type checker — passes over type errors, and no script, config or CI step of the package runs `tsc` instead. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — 21-agentic-memory/next.config.mjs:7
Do you agree with this assessment?
R7 · Dead Code3.0 / 10Weak✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 93 application, 63 tooling and 40 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (93 application, 63 tooling, 40 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 (×33) — 21-agentic-memory/components/ui/sidebar.tsx, REDACTED, 21-agentic-memory/components/ui/menubar.tsx, …
no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/authentication.ts, 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/returns.ts
no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (14-voice-agents/realtime-workspace-agents/src/app/components/Workspace.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/TabContent.tsx, 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx
no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (21-agentic-memory/components/ui/command.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — 21-agentic-memory/components/ui/dialog.tsx
no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (21-agentic-memory/components/ui/sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — 21-agentic-memory/components/ui/sheet.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×4) — 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/__tests__/workspaceManagerAgent.integration.test.ts:2, 14-voice-agents/realtime-workspace-agents/src/app/contexts/WorkspaceContext.tsx:15, 16-built-in-tools/dashboard-demo-final/eslint.config.mjs:3, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6) — REDACTED:21, REDACTED:29, REDACTED:30, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6) — REDACTED:21, REDACTED:29, REDACTED:30, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×23) — REDACTED:16, REDACTED:17, REDACTED:18, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — while 14-voice-agents/realtime-workspace-agents/src/app/contexts/WorkspaceContext.tsx DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — REDACTED:40
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception. (×2) — 12-agentic-tool-calling/4_queue_server.py:59, 12-agentic-tool-calling/5_todos.py:107
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`getComponent` is exported and takes `component: Component` from its caller, and it calls itself at line 89 (`getComponent`) with a piece of `component` — and nowhere in `getComponent` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getComponent` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. (×2) — 06-structured_outputs/structured-outputs-assistant-starting-point/lib/components-mapping.tsx:89, 06-structured_outputs/structured-outputs-assistant-final/lib/components-mapping.tsx:89
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 15/29 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.
`searchWeatherWeb` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — 25-realtime-2/src/weatherSearch.ts:187
`loadConfigs` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — 21-agentic-memory/components/dual-agent-demo.tsx:104
`openProxyStream` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:146
`fetchEphemeralKey` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:196
`runGuardrailClassifier` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/guardrails.ts:8, 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/guardrails.ts:8
`execute` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/returns.ts:229
`getSolution` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/actions.ts:12, 06-structured_outputs/structured-outputs-math-tutor-final/lib/actions.ts:12
`handleTurn` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — 06-structured_outputs/structured-outputs-assistant-starting-point/lib/assistant.ts:33, 06-structured_outputs/structured-outputs-assistant-final/lib/assistant.ts:75
`resetDb` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — 06-structured_outputs/structured-outputs-assistant-starting-point/components/main-view.tsx:9, 06-structured_outputs/structured-outputs-assistant-final/components/main-view.tsx:9
`addToCart` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — 06-structured_outputs/structured-outputs-assistant-final/lib/assistant.ts:42
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.8 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — REDACTED:87, REDACTED:87, REDACTED:84
`result` is text this program did not author, and it is written into a URL attribute through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:52
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. (×18) — 27-valuemaxxing/app/ValuemaxxingLab.tsx:107, 27-valuemaxxing/app/ValuemaxxingLab.tsx:113, 27-valuemaxxing/app/ValuemaxxingLab.tsx:123, …
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×10) — 21-agentic-memory/scripts/agent_service.py:194, 21-agentic-memory/scripts/agent_service.py:384, 21-agentic-memory/scripts/agent_service.py:1758, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info` at line 192 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. (×2) — 11-recommendation/helper_functions.py:192, 05-4o_fine_tuning/data_validator.py:192
`error` at line 320 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/helper_functions.py:320
`error` at line 333 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/helper_functions.py:333
`info` at line 347 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/helper_functions.py:347
`info` at line 373 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/helper_functions.py:373
`error` at line 386 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/helper_functions.py:386
`info` at line 458 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/helper_functions.py:458
`error` at line 34 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:34
`error` at line 37 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:37
`info` at line 43 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:43
`error` at line 45 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:45
`info` at line 60 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:60
`warning` at line 77 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:77
`error` at line 79 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:79
`warning` at line 81 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:81
`info` at line 105 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:105
`error` at line 108 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:108
`info` at line 117 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:117
`error` at line 119 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/upload-to-qdrant.py:119
`info` at line 45 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 11-recommendation/pages/page_2_explainable_recommendations.py:45
`info` at line 42 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:42
`info` at line 61 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:61
`info` at line 94 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:94
`info` at line 99 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:99
`error` at line 141 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:141
`error` at line 143 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:143
`info` at line 145 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:145
`info` at line 164 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:164
`info` at line 173 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:173
`info` at line 174 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:174
`info` at line 175 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:175
`info` at line 177 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:177
`info` at line 190 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 05-4o_fine_tuning/data_validator.py:190
`info` at line 79 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 04-mmrag_tooluse/mmrag_bh.py:79
`error` at line 83 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 04-mmrag_tooluse/mmrag_bh.py:83
`warning` at line 122 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — 04-mmrag_tooluse/mmrag_bh.py:122
`warning` at line 192 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — 04-mmrag_tooluse/mmrag_bh.py:192
`info` at line 241 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — 04-mmrag_tooluse/mmrag_bh.py:241
`error` at line 245 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — 04-mmrag_tooluse/mmrag_bh.py:245
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
17/18 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.4 `!` null assertions per 1k TypeScript source lines — 22 assertion(s) across the 51715 source line(s) of the 323 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: 18-responses-api/openai-simulator/src/scenes/MainScene.ts (9), 26-agents-sdk/web/src/pages/board-page.tsx (5), 18-responses-api/openai-simulator/src/scenes/StartScene.ts (2). 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 `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 44 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — C2 reached only 20% of this repository's production lines — typescript (54,656 lines), javascript (4,780 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Python surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 13 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 9 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 32 value object(s); 1 domain event(s); its 9 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD; its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
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
P9 Domain vs controller coverage — coverage data present for 25 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 REDACTED, 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.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 20% of this repository's production lines — typescript (54,656 lines), javascript (4,780 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×11
Click handler on a non-interactive <div> 09-realtime/openai-realtime-console-example/src/components/toggle/Toggle.tsx:48— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:594— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:655— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 13-image-gen/imagegen-demo/src/components/result-gallery.tsx:14— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 13-image-gen/imagegen-demo/src/components/result-gallery.tsx:28— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:448— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 14-voice-agents/realtime-workspace-agents/src/app/components/Events.tsx:59— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 14-voice-agents/realtime-workspace-agents/src/app/components/GuardrailChip.tsx:64— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:178— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:185— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> 16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:185— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· <textarea> without a programmatic label · ×8
<textarea> without a programmatic label 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:75— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:75— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label 13-image-gen/imagegen-demo/src/components/image-remix-tool.tsx:331— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/TabContent.tsx:50— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label 16-built-in-tools/dashboard-demo-final/components/chat.tsx:86— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label 16-built-in-tools/dashboard-demo-starting-point/components/chat.tsx:86— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label 26-agents-sdk/web/src/components/create-task-modal.tsx:131— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label 26-agents-sdk/web/src/components/task-drawer.tsx:197— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC2 · Forms & labels· <input> without a programmatic label · ×8
<input> without a programmatic label 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:63— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/prompt-form.tsx:63— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:221— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:109— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/TabContent.tsx:59— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label 22-chatgptapp-pingpong/public/pingpong.html:469— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label 26-agents-sdk/web/src/components/create-task-modal.tsx:123— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label 27-valuemaxxing/app/ValuemaxxingLab.tsx:1524— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×6
<button> with no accessible text 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:93— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:93— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:133— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:142— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text 16-built-in-tools/dashboard-demo-final/components/chat.tsx:100— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text 16-built-in-tools/dashboard-demo-starting-point/components/chat.tsx:100— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <label> that labels no control · ×6
<label> that labels no control 25-realtime-2/src/metricloop/MetricLoopVisualizations.tsx:108— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control 25-realtime-2/src/metricloop/MetricLoopVisualizations.tsx:113— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control 26-agents-sdk/web/src/components/task-card.tsx:36— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control 26-agents-sdk/web/src/components/task-drawer.tsx:142— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control 26-agents-sdk/web/src/components/task-drawer.tsx:150— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control 26-agents-sdk/web/src/components/task-drawer.tsx:156— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
D30 · Dependency Vulnerabilities· High vulnerability · ×5
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC1 · Text alternatives· <img> without a text alternative · ×2
<img> without a text alternative 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:551— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:52— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <select> without a programmatic label · ×2
<select> without a programmatic label 14-voice-agents/realtime-workspace-agents/src/app/components/BottomToolbar.tsx:158— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label 26-agents-sdk/web/src/components/task-drawer.tsx:143— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
Unlisted import '@eslint/eslintrc' 16-built-in-tools/dashboard-demo-final/eslint.config.mjs:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@eslint/eslintrc' 16-built-in-tools/dashboard-demo-starting-point/eslint.config.mjs:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
<html> without a lang 26-agents-sdk/fake data/asset-task/event-page-template.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×1
Click handler on a non-interactive <li> 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:104— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Unlisted import '@openai/agents-realtime' 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/__tests__/workspaceManagerAgent.integration.test.ts:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'nanoid' 14-voice-agents/realtime-workspace-agents/src/app/contexts/WorkspaceContext.tsx:15— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Serious — 768 finding(s)
D30 · Dependency Vulnerabilities· Medium CVE · ×112
FunctionTooLong: ValuemaxxingLab.ValuemaxxingLab 27-valuemaxxing/app/ValuemaxxingLab.tsx:777— FunctionTooLong — ValuemaxxingLab runs 1004 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 904 over it, 10.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useMetricLoopRealtime.useMetricLoopRealtime 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:325— FunctionTooLong — useMetricLoopRealtime runs 684 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 584 over it, 6.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MetricLoopDashboard.MetricLoopDashboard 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:150— FunctionTooLong — MetricLoopDashboard runs 630 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 530 over it, 6.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useSupplyRealtime.useSupplyRealtime 25-realtime-2/src/agent/useSupplyRealtime.ts:270— FunctionTooLong — useSupplyRealtime runs 612 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 512 over it, 6.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: App.StorefrontApp 25-realtime-2/src/App.tsx:167— FunctionTooLong — StorefrontApp runs 544 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 444 over it, 5.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: configuration-panel.AgentConfigCard 21-agentic-memory/components/configuration-panel.tsx:388— FunctionTooLong — AgentConfigCard runs 421 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 321 over it, 4.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ParetoFrontier.ParetoFrontier 27-valuemaxxing/app/ParetoFrontier.tsx:356— FunctionTooLong — ParetoFrontier runs 400 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 300 over it, 4.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: page.Home 24-api-codex/agentic-legibility-scorecard/app/page.tsx:25— FunctionTooLong — Home runs 332 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 232 over it, 3.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: App.App 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:43— FunctionTooLong — App runs 305 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dual-agent-demo.DualAgentDemo 21-agentic-memory/components/dual-agent-demo.tsx:90— FunctionTooLong — DualAgentDemo runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MetricLoopNotebook.NotebookSummary 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx:127— FunctionTooLong — NotebookSummary runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: configuration-panel.ConfigurationPanel 21-agentic-memory/components/configuration-panel.tsx:24— FunctionTooLong — ConfigurationPanel runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: App.ProductPage 25-realtime-2/src/App.tsx:1416— FunctionTooLong — ProductPage runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: App.ResultsPage 25-realtime-2/src/App.tsx:1079— FunctionTooLong — ResultsPage runs 235 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 135 over it, 2.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: chat-interface.ChatInterface 21-agentic-memory/components/chat-interface.tsx:237— FunctionTooLong — ChatInterface runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: task-drawer.TaskDrawer 26-agents-sdk/web/src/components/task-drawer.tsx:65— FunctionTooLong — TaskDrawer runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PlanDisplay.PlanDisplay 07-reasoning/shipmentPlanning/frontend/src/PlanDisplay.js:6— FunctionTooLong — PlanDisplay runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: App.App 07-reasoning/shipmentPlanning/frontend/src/App.js:36— FunctionTooLong — App runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MetricLoopDashboard.MetricLoopShell 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:951— FunctionTooLong — MetricLoopShell runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Transcript.Transcript 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:20— FunctionTooLong — Transcript runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SupplyAssistant.SupplyAssistant 25-realtime-2/src/agent/SupplyAssistant.tsx:198— FunctionTooLong — SupplyAssistant runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: metricLoopEngine.buildScopedReport 25-realtime-2/src/metricloop/metricLoopEngine.ts:743— FunctionTooLong — buildScopedReport runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ExecutionStream.ExecutionStream 07-reasoning/shipmentPlanning/frontend/src/ExecutionStream.js:24— FunctionTooLong — ExecutionStream runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: board-page.BoardPage 26-agents-sdk/web/src/pages/board-page.tsx:22— FunctionTooLong — BoardPage runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MetricLoopActionConsole.MetricLoopActionConsole 25-realtime-2/src/metricloop/MetricLoopActionConsole.tsx:86— FunctionTooLong — MetricLoopActionConsole runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
+ 16 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1— 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.
No test reaches this file 21-agentic-memory/components/configuration-panel.tsx:1— 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.
No test reaches this file 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:1— 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.
No test reaches this file 21-agentic-memory/components/ui/sidebar.tsx:1— 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.
No test reaches this file REDACTED:1— 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.
No test reaches this file 24-api-codex/agentic-legibility-scorecard/app/page.tsx:1— 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.
No test reaches this file 09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js:1— 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.
No test reaches this file 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:1— 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.
No test reaches this file 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1— 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.
No test reaches this file 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:1— 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.
No test reaches this file 21-agentic-memory/components/chat-interface.tsx:1— 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.
No test reaches this file 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1— 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.
No test reaches this file 21-agentic-memory/components/dual-agent-demo.tsx:1— 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.
No test reaches this file 21-agentic-memory/lib/python-agent-bridge.ts:1— 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.
No test reaches this file REDACTED:1— 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.
No test reaches this file REDACTED:1— 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.
No test reaches this file REDACTED:1— 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.
No test reaches this file REDACTED:1— 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.
No test reaches this file 16-built-in-tools/dashboard-demo-final/components/data-table.tsx:1— 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.
No test reaches this file 16-built-in-tools/dashboard-demo-starting-point/components/data-table.tsx:1— 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.
No test reaches this file 13-image-gen/imagegen-demo/src/components/image-remix-tool.tsx:1— 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.
No test reaches this file REDACTED:1— 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.
No test reaches this file 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/authentication.ts:1— 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.
No test reaches this file 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/returns.ts:1— 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.
No test reaches this file 26-agents-sdk/web/src/components/task-drawer.tsx:1— 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.
Swallowed exception (empty catch) 27-valuemaxxing/app/ValuemaxxingLab.tsx:107— 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.
Swallowed exception (empty catch) 27-valuemaxxing/app/ValuemaxxingLab.tsx:113— 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.
Swallowed exception (empty catch) 27-valuemaxxing/app/ValuemaxxingLab.tsx:123— 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.
Swallowed exception (empty catch) 27-valuemaxxing/app/ValuemaxxingLab.tsx:884— 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.
Swallowed exception (empty catch) 27-valuemaxxing/app/ValuemaxxingLab.tsx:968— 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.
Swallowed exception (empty catch) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:408— 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.
Swallowed exception (empty catch) 25-realtime-2/src/realtime/realtimeCostTrace.ts:259— 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.
Swallowed exception (empty catch) 25-realtime-2/src/metricloop/MetricLoopActionConsole.tsx:155— 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.
Swallowed exception (empty catch) 25-realtime-2/src/agent/supplyRealtimeDebugLog.ts:121— 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.
Swallowed exception (empty catch) 25-realtime-2/src/agent/SupplyAssistant.tsx:232— 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.
Swallowed exception (empty catch) 25-realtime-2/src/agent/SupplyAssistant.tsx:241— 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.
Swallowed exception (empty catch) 21-agentic-memory/scripts/agent_service.py:1725— 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.
Swallowed exception (empty catch) 21-agentic-memory/scripts/agent_service.py:1731— 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.
Swallowed exception (empty catch) 21-agentic-memory/scripts/agent_service.py:1736— 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.
Swallowed exception (empty catch) 21-agentic-memory/scripts/agent_service.py:1741— 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.
Swallowed exception (empty catch) 21-agentic-memory/scripts/agent_service.py:1891— 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.
Swallowed exception (empty catch) 20-agent-rft/utils_shared/tracing_storing.py:140— 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.
Swallowed exception (empty catch) 14-voice-agents/realtime-workspace-agents/src/app/contexts/WorkspaceContext.tsx:58— 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.
FileTooLong: app/ValuemaxxingLab.tsx 27-valuemaxxing/app/ValuemaxxingLab.tsx— FileTooLong — 1633 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: ValuemaxxingLab (777-1956). The bar is 500 significant lines; this is 1133 over it, 3.27× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: scripts/agent_service.py 21-agentic-memory/scripts/agent_service.py— FileTooLong — 1603 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1103 over it, 3.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/App.tsx 25-realtime-2/src/App.tsx— FileTooLong — 1583 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1083 over it, 3.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: metricloop/metricLoopEngine.ts 25-realtime-2/src/metricloop/metricLoopEngine.ts— FileTooLong — 1157 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 657 over it, 2.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: public/pingpong.html 22-chatgptapp-pingpong/public/pingpong.html— FileTooLong — 1118 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 618 over it, 2.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scenes/MainScene.ts 18-responses-api/openai-simulator/src/scenes/MainScene.ts— FileTooLong — 1005 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: MainScene (58-1540). The bar is 500 significant lines; this is 505 over it, 2.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: metricloop/MetricLoopDashboard.tsx 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx— FileTooLong — 993 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: MetricLoopDashboard (150-949). The bar is 500 significant lines; this is 493 over it, 1.99× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: metricloop/useMetricLoopRealtime.ts 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: useMetricLoopRealtime (325-1269). The bar is 500 significant lines; this is 435 over it, 1.87× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/data.ts 25-realtime-2/src/data.ts— FileTooLong — 903 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 403 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: agent/useSupplyRealtime.ts 25-realtime-2/src/agent/useSupplyRealtime.ts— FileTooLong — 816 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: useSupplyRealtime (270-1097). The bar is 500 significant lines; this is 316 over it, 1.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: components/configuration-panel.tsx 21-agentic-memory/components/configuration-panel.tsx— FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: AgentConfigCard (388-926). The bar is 500 significant lines; this is 195 over it, 1.39× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: scripts/score_repo.py 24-api-codex/skills/agentic-legibility/scripts/score_repo.py— FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 185 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: app/ParetoFrontier.tsx 27-valuemaxxing/app/ParetoFrontier.tsx— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 180 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: metricloop/metricLoopForensicsData.ts 25-realtime-2/src/metricloop/metricLoopForensicsData.ts— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 110 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: server/metricloopForensicsRuntime.ts 25-realtime-2/src/server/metricloopForensicsRuntime.ts— FileTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: createMetricLoopForensicsRuntime (87-549). The bar is 500 significant lines; this is 84 over it, 1.17× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ui/sidebar.tsx 21-agentic-memory/components/ui/sidebar.tsx— FileTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 61 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
X2 · Cancellation propagation· Async function without AbortSignal · ×14
Async function without AbortSignal: searchWeatherWeb 25-realtime-2/src/weatherSearch.ts:187— `searchWeatherWeb` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: loadConfigs 21-agentic-memory/components/dual-agent-demo.tsx:104— `loadConfigs` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: openProxyStream 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:146— `openProxyStream` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchEphemeralKey 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:196— `fetchEphemeralKey` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: runGuardrailClassifier 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/guardrails.ts:8— `runGuardrailClassifier` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: runGuardrailClassifier 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/guardrails.ts:8— `runGuardrailClassifier` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: execute 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/returns.ts:229— `execute` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getSolution 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/actions.ts:12— `getSolution` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getSolution 06-structured_outputs/structured-outputs-math-tutor-final/lib/actions.ts:12— `getSolution` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handleTurn 06-structured_outputs/structured-outputs-assistant-starting-point/lib/assistant.ts:33— `handleTurn` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: resetDb 06-structured_outputs/structured-outputs-assistant-starting-point/components/main-view.tsx:9— `resetDb` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: addToCart 06-structured_outputs/structured-outputs-assistant-final/lib/assistant.ts:42— `addToCart` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handleTurn 06-structured_outputs/structured-outputs-assistant-final/lib/assistant.ts:75— `handleTurn` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: resetDb 06-structured_outputs/structured-outputs-assistant-final/components/main-view.tsx:9— `resetDb` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Focus outline removed inline 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:75— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 06-structured_outputs/structured-outputs-assistant-final/components/ui/textarea.tsx:13— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:75— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/textarea.tsx:13— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 14-voice-agents/realtime-workspace-agents/src/app/components/BottomToolbar.tsx:158— <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:221— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:109— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 16-built-in-tools/dashboard-demo-final/components/chat.tsx:86— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 16-built-in-tools/dashboard-demo-starting-point/components/chat.tsx:86— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 21-agentic-memory/components/ui/input.tsx:7— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline 21-agentic-memory/components/ui/textarea.tsx:7— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Swallowed exception (caught, then discarded) 21-agentic-memory/scripts/agent_service.py:194— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 21-agentic-memory/scripts/agent_service.py:384— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 21-agentic-memory/scripts/agent_service.py:1758— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 21-agentic-memory/scripts/agent_service.py:1924— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 21-agentic-memory/scripts/agent_service.py:1949— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 20-agent-rft/tool_server_modal.py:204— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 20-agent-rft/utils_shared/tools_helper.py:151— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 20-agent-rft/utils_shared/tracing_storing.py:267— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) 15-reinforcement-fine-tuning/utils/grader_utils.py:36— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:19— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×8
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×7
Animation without a prefers-reduced-motion guard 17-gpt-5/outputs/saas_landing_page_persistence.html:231— `.chevron` moves (`transition: transform .25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard 17-gpt-5/outputs/saas_landing_page_persistence.html:250— `.fade-in` moves (`animation: fadeUp .3s ease both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard 22-chatgptapp-pingpong/public/pingpong.html:64— `.hud` moves (`animation: floatIn 500ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard 22-chatgptapp-pingpong/public/pingpong.html:127— `.analysis` moves (`animation: floatIn 500ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard 22-chatgptapp-pingpong/public/pingpong.html:179— `button` moves (`transition: transform 150ms ease, box-shadow 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard 22-chatgptapp-pingpong/public/pingpong.html:203— `.arena` moves (`animation: glowIn 700ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard 22-chatgptapp-pingpong/public/pingpong.html:225— `.arena::after` moves (`animation: pulse 4s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AC3 · Page structure· Page without a main landmark · ×5
Page without a main landmark 09-realtime/realtime-from-scratch/app/layout.tsx:27— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark 14-voice-agents/realtime-workspace-agents/src/app/layout.tsx:16— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark 17-gpt-5/minecraft/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark 22-chatgptapp-pingpong/public/pingpong.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark 27-valuemaxxing/app/layout.tsx:34— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Boundary violation [package:third-party-deep-import] 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1— 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1 imports openai/lib/jsonschema, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] 06-structured_outputs/structured-outputs-assistant-starting-point/lib/tools.ts:1— 06-structured_outputs/structured-outputs-assistant-starting-point/lib/tools.ts:1 imports openai/lib/jsonschema, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:17— 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:17 imports @openai/realtime-api-beta/dist/lib/client.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:7— 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:7 imports react-syntax-highlighter/dist/esm/styles/prism, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] 16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:7— 16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:7 imports react-syntax-highlighter/dist/esm/styles/prism, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
AC4 · Keyboard semantics· Anchor without href · ×4
Anchor without href 25-realtime-2/src/App.tsx:1483— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href 26-agents-sdk/web/src/components/app-shell.tsx:18— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href 26-agents-sdk/web/src/components/app-shell.tsx:19— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href 26-agents-sdk/web/src/components/app-shell.tsx:22— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×4
Focus outline removed in CSS without a :focus replacement 27-valuemaxxing/app/globals.css:1403— `.experiment-action select` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement 26-agents-sdk/web/src/styles/app.css:703— `.comment-form textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement 26-agents-sdk/web/src/styles/app.css:1024— `.composer-title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement 26-agents-sdk/web/src/styles/app.css:1091— `.composer-session input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
ClassTooLong: ValuemaxxingLab 27-valuemaxxing/app/ValuemaxxingLab.tsx:1— ClassTooLong — 1004 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 604 over it, 2.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: useMetricLoopRealtime 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:1— ClassTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 284 over it, 1.71× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MetricLoopDashboard 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:1— ClassTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 230 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: useSupplyRealtime 25-realtime-2/src/agent/useSupplyRealtime.ts:1— ClassTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 212 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped REDACTED:87— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:87— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:52— `result` is text this program did not author, and it is written into a URL attribute through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:84— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC2 · Forms & labels· <Select> field component without a label · ×3
<Select> field component without a label 21-agentic-memory/components/configuration-panel.tsx:513— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label 21-agentic-memory/components/configuration-panel.tsx:536— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label 21-agentic-memory/components/configuration-panel.tsx:559— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
Low contrast Tailwind colour pair (2.9:1) 21-agentic-memory/components/chat-interface.tsx:289— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.9:1) 21-agentic-memory/components/chat-interface.tsx:375— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.9:1) 21-agentic-memory/components/configuration-panel.tsx:495— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
chart.ChartTooltipContent (cyclomatic 31) REDACTED:121— chart.ChartTooltipContent has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 193, 141). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cyclomatic 31) REDACTED:121— chart.ChartTooltipContent has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 193, 141). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cyclomatic 31) REDACTED:107— chart.ChartTooltipContent has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 182, 131). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cognitive 27) REDACTED:121— chart.ChartTooltipContent has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 193, 141). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cognitive 27) REDACTED:121— chart.ChartTooltipContent has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 193, 141). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chart.ChartTooltipContent (cognitive 27) REDACTED:107— chart.ChartTooltipContent has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 182, 131). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Dead file (~120 LoC) 06-structured_outputs/structured-outputs-assistant-final/components/ui/table.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~120 LoC) 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/table.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~120 LoC) 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/chatSupervisor/index.ts— no import path from any entry point (93 application, 63 tooling, 40 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
AC1 · Text alternatives· <canvas> without a text alternative · ×2
<canvas> without a text alternative 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:571— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:574— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC3 · Page structure· Data table has no header cells · ×2
Data table has no header cells 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:1205— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells 25-realtime-2/src/metricloop/MetricLoopVisualizations.tsx:170— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×2
Modal dialog does not manage focus 25-realtime-2/src/App.tsx:1853— This <section role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus 27-valuemaxxing/app/ValuemaxxingLab.tsx:302— This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Low contrast Tailwind colour pair (3.3:1) 06-structured_outputs/structured-outputs-math-tutor-final/components/ui/warning.tsx:15— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.3:1) 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/ui/warning.tsx:15— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) 13-image-gen/imagegen-demo/src/components/image-remix-tool.tsx:325— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.4:1) 13-image-gen/imagegen-demo/src/components/result-gallery.tsx:24— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
TodoComment 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/materials.ts:7— // TODO: This could use an MCP connection to search a materials database — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment 08-evals/02_stanbot_eval.py:56— # TODO benchmark — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) 21-agentic-memory/scripts/agent_service.py:1084— 21-agentic-memory/scripts/agent_service.py:1084-1104 | 21-agentic-memory/scripts/agent_service.py:1107-1129 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) 04-mmrag_tooluse/mmrag_bh.py:340— 04-mmrag_tooluse/mmrag_bh.py:340-360 | 04-mmrag_tooluse/mmrag_bh.py:537-562 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (24 lines × 2) 02-assistants/2_tools.py:54— 02-assistants/2_tools.py:54-77 | 02-assistants/3_tools.py:48-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (24 lines × 2) 15-reinforcement-fine-tuning/utils/upload_utils.py:37— 15-reinforcement-fine-tuning/utils/upload_utils.py:37-60 | 20-agent-rft/utils_shared/file_upload.py:111-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) 08-evals/01_create_stanbot_draft_datasett.py:63— 08-evals/01_create_stanbot_draft_datasett.py:63-78 | 08-evals/03_create_summary_grader_dataset.py:50-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) 12-agentic-tool-calling/4_queue_server.py:30— 12-agentic-tool-calling/4_queue_server.py:30-45 | 12-agentic-tool-calling/5_todos.py:78-93 — before extracting anything, compare `12-agentic-tool-calling/4_queue_server.py` and `12-agentic-tool-calling/5_todos.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) 26-agents-sdk/app/agents/runtime.py:251— 26-agents-sdk/app/agents/runtime.py:251-262 | 26-agents-sdk/app/agents/runtime.py:377-388 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) 04-mmrag_tooluse/mmrag_bh.py:290— 04-mmrag_tooluse/mmrag_bh.py:290-301 | 11-recommendation/upload-to-qdrant.py:50-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) 21-agentic-memory/scripts/agent_service.py:1096— 21-agentic-memory/scripts/agent_service.py:1096-1104 | 21-agentic-memory/scripts/agent_service.py:1121-1129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) 21-agentic-memory/scripts/agent_service.py:2110— 21-agentic-memory/scripts/agent_service.py:2110-2118 | 21-agentic-memory/scripts/agent_service.py:2120-2128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Low coverage: 27-valuemaxxing/app/ValuemaxxingLab.tsx 27-valuemaxxing/app/ValuemaxxingLab.tsx:1— 12.8% line coverage (251/1956).
Low coverage: REDACTED REDACTED:1— 49.5% line coverage (213/430).
P8 · Schema migrations· Schema created by SQLAlchemy create_all() outside the migrations · ×2
Schema created by SQLAlchemy create_all() outside the migrations 26-agents-sdk/app/db.py:29— This repository versions its schema (Alembic), but SQLAlchemy create_all() here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Alembic own the schema.
Schema created by SQLAlchemy create_all() outside the migrations 05-4o_fine_tuning/example_cot.py:132— This repository versions its schema (Alembic), but SQLAlchemy create_all() here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Alembic own the schema.
Wholesale file copy (100 identical lines × 2 files) 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:1— 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:1 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/useSolution.ts:1 — these 2 files are line-for-line copies of one another — 100 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (100 identical lines × 2 files) 16-built-in-tools/dashboard-demo-final/components/chat.tsx:3— 16-built-in-tools/dashboard-demo-final/components/chat.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/chat.tsx:3 — these 2 files are line-for-line copies of one another — 100 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (65 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/components/ui/drawer.tsx:3— 06-structured_outputs/structured-outputs-assistant-final/components/ui/drawer.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/drawer.tsx:3 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (65 identical lines × 2 files) 06-structured_outputs/structured-outputs-math-tutor-final/components/ui/icons.tsx:3— 06-structured_outputs/structured-outputs-math-tutor-final/components/ui/icons.tsx:3 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/ui/icons.tsx:3 — these 2 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Complex function (anonymous) (cyclomatic 81, cognitive 95) 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:165— (anonymous) has cyclomatic complexity 81 and cognitive complexity 95; 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.
Complex function (anonymous) (cyclomatic 81, cognitive 95) 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:165— (anonymous) has cyclomatic complexity 81 and cognitive complexity 95; 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.
Complex function (anonymous) (cyclomatic 17, cognitive 12) REDACTED:193— (anonymous) has cyclomatic complexity 17 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.
Complex function (anonymous) (cyclomatic 17, cognitive 12) REDACTED:193— (anonymous) has cyclomatic complexity 17 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.
Dead file (~164 LoC) 06-structured_outputs/structured-outputs-assistant-final/components/ui/select.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~164 LoC) 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/select.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~140 LoC) 06-structured_outputs/structured-outputs-assistant-final/components/ui/sheet.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~140 LoC) 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/sheet.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~118 LoC) 06-structured_outputs/structured-outputs-assistant-final/components/ui/drawer.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~118 LoC) 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/drawer.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~115 LoC) 06-structured_outputs/structured-outputs-assistant-final/components/ui/breadcrumb.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~115 LoC) 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/breadcrumb.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Unused dependency '@xyflow/react' REDACTED:21— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@xyflow/react' REDACTED:21— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'pdf2json' REDACTED:29— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'pdf2json' REDACTED:29— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'pdfjs-dist' REDACTED:30— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'pdfjs-dist' REDACTED:30— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-dropzone' REDACTED:33— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-dropzone' REDACTED:33— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-flow-renderer' REDACTED:34— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-flow-renderer' REDACTED:34— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-pdf' REDACTED:36— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-pdf' REDACTED:36— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X1 · Async correctness· Task from `asyncio.create_task` is not kept · ×2
Task from `asyncio.create_task` is not kept 12-agentic-tool-calling/4_queue_server.py:59— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
Task from `asyncio.create_task` is not kept 12-agentic-tool-calling/5_todos.py:107— The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap 06-structured_outputs/structured-outputs-assistant-starting-point/lib/components-mapping.tsx:89— `getComponent` is exported and takes `component: Component` from its caller, and it calls itself at line 89 (`getComponent`) with a piece of `component` — and nowhere in `getComponent` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getComponent` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap 06-structured_outputs/structured-outputs-assistant-final/lib/components-mapping.tsx:89— `getComponent` is exported and takes `component: Component` from its caller, and it calls itself at line 89 (`getComponent`) with a piece of `component` — and nowhere in `getComponent` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getComponent` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 17-gpt-5/outputs/saas_landing_page_persistence.html:341— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×1
Link used as a button (placeholder href) 27-valuemaxxing/app/ValuemaxxingLab.tsx:1241— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Low contrast Tailwind colour pair (3.8:1) 09-realtime/realtime-from-scratch/app/page.tsx:77— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.3:1) 09-realtime/realtime-from-scratch/app/page.tsx:83— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.4:1) 14-voice-agents/realtime-workspace-agents/src/app/components/BottomToolbar.tsx:90— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (2.6:1) 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx:58— This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast colour pair in CSS (2.8:1) 17-gpt-5/minecraft/index.html:38— `#play` sets color: #fff on background-color: #4caf50 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair (3.6:1) 17-gpt-5/outputs/saas_landing_page_persistence.html:390— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (3.1:1) 17-gpt-5/outputs/saas_landing_page_persistence.html:401— The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair in CSS (3.8:1) 27-valuemaxxing/app/globals.css:949— `.result-identity > span:last-child` sets color: #777970 on background-color: #efede7 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.3:1) 27-valuemaxxing/app/globals.css:1330— `.experiment-number` sets color: #fffefa on background-color: #f05d35 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) 27-valuemaxxing/app/globals.css:1854— `.tool-chips span` sets color: #777970 on background-color: #fffefa — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) 27-valuemaxxing/app/globals.css:2456— `.frontier-chart-footer` sets color: #777970 on background-color: #f8f7f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
ValuemaxxingLab.ValuemaxxingLab (cyclomatic 102) 27-valuemaxxing/app/ValuemaxxingLab.tsx:777— ValuemaxxingLab.ValuemaxxingLab has cyclomatic complexity 102 (threshold 15). Of this number, 42 points are the body's own statements and 60 belong to 19 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetricLoopDashboard.MetricLoopDashboard (cyclomatic 70) 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:150— MetricLoopDashboard.MetricLoopDashboard has cyclomatic complexity 70 (threshold 15). Most of this is not in the body itself: 1 of the 70 points is its own statement and the rest belongs to 17 function literals inside it that branch (lines 324, 404, 532, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ParetoFrontier.ParetoFrontier (cyclomatic 65) 27-valuemaxxing/app/ParetoFrontier.tsx:356— ParetoFrontier.ParetoFrontier has cyclomatic complexity 65 (threshold 15). Of this number, 21 points are the body's own statements and 44 belong to 19 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
configuration-panel.AgentConfigCard (cyclomatic 63) 21-agentic-memory/components/configuration-panel.tsx:388— configuration-panel.AgentConfigCard has cyclomatic complexity 63 (threshold 15). Of this number, 20 points are the body's own statements and 43 belong to 30 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
App.StorefrontApp (cyclomatic 60) 25-realtime-2/src/App.tsx:167— App.StorefrontApp has cyclomatic complexity 60 (threshold 15). Most of this is not in the body itself: 7 of the 60 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 254, a function literal at line 467, a function literal at line 657, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
agent_service.run_agent (cyclomatic 51) 21-agentic-memory/scripts/agent_service.py:1708— agent_service.run_agent has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
chat-interface.ChatInterface (cyclomatic 50) 21-agentic-memory/components/chat-interface.tsx:237— chat-interface.ChatInterface has cyclomatic complexity 50 (threshold 15). Of this number, 27 points are the body's own statements and 23 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
configuration-panel.ConfigurationPanel (cyclomatic 49) 21-agentic-memory/components/configuration-panel.tsx:24— configuration-panel.ConfigurationPanel has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 2 of the 49 points are its own statements and the rest belongs to 10 function items inside it that branch (handleAgentMemoryTrimmingChange, handleAgentMemoryCompactingChange, handleAgentMemorySummarizationChange, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
App.App (cyclomatic 47) 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:43— App.App has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 2 of the 47 points are its own statements and the rest belongs to 21 function items inside it that branch (connectToRealtime, a function literal at line 47, a function literal at line 174, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tracing_storing.process_single_item (cyclomatic 47) 20-agent-rft/utils_shared/tracing_storing.py:49— tracing_storing.process_single_item has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useSupplyRealtime.useSupplyRealtime.handleServerEvent (cyclomatic 45) 25-realtime-2/src/agent/useSupplyRealtime.ts:718— useSupplyRealtime.useSupplyRealtime.handleServerEvent has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useMetricLoopRealtime.useMetricLoopRealtime.handleServerEvent (cyclomatic 45) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:846— useMetricLoopRealtime.useMetricLoopRealtime.handleServerEvent has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
metricloopToolRuntime.createMetricLoopToolRuntime.runTool (cyclomatic 36) 25-realtime-2/src/server/metricloopToolRuntime.ts:72— metricloopToolRuntime.createMetricLoopToolRuntime.runTool has cyclomatic complexity 36 (threshold 15). Of this number, 32 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useHandleSessionHistory.useHandleSessionHistory (cyclomatic 34) 14-voice-agents/realtime-workspace-agents/src/app/hooks/useHandleSessionHistory.ts:7— useHandleSessionHistory.useHandleSessionHistory has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 13 function items inside it that branch (handleHistoryAdded, a function literal at line 24, extractModeration, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
page.Home (cyclomatic 34) 24-api-codex/agentic-legibility-scorecard/app/page.tsx:25— page.Home has cyclomatic complexity 34 (threshold 15). Of this number, 17 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SupplyAssistant.SupplyAssistant (cyclomatic 34) 25-realtime-2/src/agent/SupplyAssistant.tsx:198— SupplyAssistant.SupplyAssistant has cyclomatic complexity 34 (threshold 15). Of this number, 23 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MainScene.update (cyclomatic 33) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:287— MainScene.update has cyclomatic complexity 33 (threshold 15). Of this number, 26 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Transcript.Transcript (cyclomatic 32) 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:20— Transcript.Transcript has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 4 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 110, a function literal at line 42, a function literal at line 40, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
createPingPongServer (cyclomatic 31) REDACTED:242— createPingPongServer has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 367, 277, 327, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MetricLoopActionConsole.MetricLoopActionConsole (cyclomatic 30) 25-realtime-2/src/metricloop/MetricLoopActionConsole.tsx:86— MetricLoopActionConsole.MetricLoopActionConsole has cyclomatic complexity 30 (threshold 15). Of this number, 17 points are the body's own statements and 13 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
buildGameInsights (cyclomatic 27) REDACTED:155— buildGameInsights has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useSupplyRealtime.useSupplyRealtime.runFunctionCall (cyclomatic 26) 25-realtime-2/src/agent/useSupplyRealtime.ts:573— useSupplyRealtime.useSupplyRealtime.runFunctionCall has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
task-drawer.TaskDrawer (cyclomatic 26) 26-agents-sdk/web/src/components/task-drawer.tsx:65— task-drawer.TaskDrawer has cyclomatic complexity 26 (threshold 15). Of this number, 17 points are the body's own statements and 9 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pingpong.html.connectToRoom (cyclomatic 25) 22-chatgptapp-pingpong/public/pingpong.html:1132— pingpong.html.connectToRoom has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 12 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1216, 1246, 1266). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
(anonymous) (cyclomatic 25) REDACTED:451— (anonymous) has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainScene.updateNpcMovement (cyclomatic 24) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:778— MainScene.updateNpcMovement has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to one function literal inside it that branches (line 781). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
pingpong.html.applyRemoteState (cyclomatic 24) 22-chatgptapp-pingpong/public/pingpong.html:950— pingpong.html.applyRemoteState has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
server.httpServer (cyclomatic 23) REDACTED:451— server.httpServer has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useMetricLoopRealtime.formatToolChip (cyclomatic 23) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:151— useMetricLoopRealtime.formatToolChip has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
plot_eval_runs.plot_score_stats_plotly (cyclomatic 23) 15-reinforcement-fine-tuning/utils/plot_eval_runs.py:197— plot_eval_runs.plot_score_stats_plotly has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dual-agent-demo.DualAgentDemo (cyclomatic 22) 21-agentic-memory/components/dual-agent-demo.tsx:90— dual-agent-demo.DualAgentDemo has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 104, handleSaveConfigs, handleSendMessage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
App.ProductPage (cyclomatic 22) 25-realtime-2/src/App.tsx:1416— App.ProductPage has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SummarizingSession.add_items (cyclomatic 22) 21-agentic-memory/scripts/agent_service.py:1187— SummarizingSession.add_items has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
compacting_session._stringify_content_field (cyclomatic 22) 21-agentic-memory/scripts/compacting_session.py:129— compacting_session._stringify_content_field has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenAIDialogueAgent.provideResponseStream (cyclomatic 21) 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:30— OpenAIDialogueAgent.provideResponseStream has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
runs.normalizeImportedResult (cyclomatic 21) 27-valuemaxxing/lib/runs.ts:113— runs.normalizeImportedResult has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
score_repo.score_lint_format (cyclomatic 21) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:467— score_repo.score_lint_format has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainScene.computePath (cyclomatic 20) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:619— MainScene.computePath has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainScene.runNpcConversation (cyclomatic 20) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1200— MainScene.runNpcConversation has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataValidator.check_data_format_errors (cyclomatic 20) 05-4o_fine_tuning/data_validator.py:66— DataValidator.check_data_format_errors has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
agent_service._extract_usage (cyclomatic 20) 21-agentic-memory/scripts/agent_service.py:1990— agent_service._extract_usage has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
page.currentPhaseLabel (cyclomatic 19) 24-api-codex/agentic-legibility-scorecard/app/page.tsx:450— page.currentPhaseLabel has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useSupplyRealtime.collectToolDetails (cyclomatic 19) 25-realtime-2/src/agent/useSupplyRealtime.ts:182— useSupplyRealtime.collectToolDetails has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
metricLoopEngine.buildEngineeringBrief (cyclomatic 19) 25-realtime-2/src/metricloop/metricLoopEngine.ts:1174— metricLoopEngine.buildEngineeringBrief has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MetricLoopForensicsWorkbench.ForensicsTraceCard (cyclomatic 19) 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx:114— MetricLoopForensicsWorkbench.ForensicsTraceCard has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
route.runToolExperiment (cyclomatic 19) REDACTED:256— route.runToolExperiment has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
score_repo.score_agent_repo_map (cyclomatic 19) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:535— score_repo.score_agent_repo_map has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useSupplyRealtime.formatToolChip (cyclomatic 18) 25-realtime-2/src/agent/useSupplyRealtime.ts:157— useSupplyRealtime.formatToolChip has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
App.ResultsPage (cyclomatic 18) 25-realtime-2/src/App.tsx:1079— App.ResultsPage has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
metricloopForensicsRuntime.createDashboardFiltersForRow (cyclomatic 18) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:667— metricloopForensicsRuntime.createDashboardFiltersForRow has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
assignee-combobox.AssigneeCombobox (cyclomatic 18) 26-agents-sdk/web/src/components/assignee-combobox.tsx:12— assignee-combobox.AssigneeCombobox has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (handleKeyDown, a function literal at line 29, a function literal at line 37, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ValuemaxxingLab.CacheResults (cyclomatic 18) 27-valuemaxxing/app/ValuemaxxingLab.tsx:498— ValuemaxxingLab.CacheResults has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LLMSummarizer.summarize (cyclomatic 18) 21-agentic-memory/scripts/agent_service.py:822— LLMSummarizer.summarize has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
agent_service._extract_role_and_text (cyclomatic 18) 21-agentic-memory/scripts/agent_service.py:392— agent_service._extract_role_and_text has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CompactingSession._maybe_compact (cyclomatic 18) 21-agentic-memory/scripts/compacting_session.py:331— CompactingSession._maybe_compact has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
pingpong.html.update (cyclomatic 17) 22-chatgptapp-pingpong/public/pingpong.html:1576— pingpong.html.update has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
reviewInsights.buildShoeInsights (cyclomatic 17) 25-realtime-2/src/reviewInsights.ts:130— reviewInsights.buildShoeInsights has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useMetricLoopRealtime.useMetricLoopRealtime.applyMetricLoopUiTool (cyclomatic 17) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:703— useMetricLoopRealtime.useMetricLoopRealtime.applyMetricLoopUiTool has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetricLoopDashboard.MetricLoopShell (cyclomatic 17) 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:951— MetricLoopDashboard.MetricLoopShell has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
metricloopForensicsRuntime.createMetricLoopForensicsRuntime::runTool (cyclomatic 17) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:271— metricloopForensicsRuntime.createMetricLoopForensicsRuntime::runTool has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
create-task-modal.CreateTaskModal (cyclomatic 17) 26-agents-sdk/web/src/components/create-task-modal.tsx:23— create-task-modal.CreateTaskModal has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 8 function items inside it that branch (submitWithShortcut, a function literal at line 72, a function literal at line 34, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
score_repo.score_structured_docs (cyclomatic 17) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:601— score_repo.score_structured_docs has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
metricLoopEngine.buildScopedReport (cyclomatic 16) 25-realtime-2/src/metricloop/metricLoopEngine.ts:743— metricLoopEngine.buildScopedReport has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
runs.isExperimentRun (cyclomatic 16) 27-valuemaxxing/lib/runs.ts:262— runs.isExperimentRun has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
tool_server_modal.list_endpoint (cyclomatic 16) 20-agent-rft/tool_server_modal.py:161— tool_server_modal.list_endpoint has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
agent_service._extract_text_from_final_output (cyclomatic 16) 21-agentic-memory/scripts/agent_service.py:297— agent_service._extract_text_from_final_output has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tracing_storing.process_single_item (cognitive 104) 20-agent-rft/utils_shared/tracing_storing.py:49— tracing_storing.process_single_item has cognitive complexity 104 (threshold 15). Drivers by points: if/else 23 (57 pts), ternaries 7 (22 pts), loops 5 (12 pts), boolean chains 7, error handling 4 (6 pts) (nesting depth added 58). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ValuemaxxingLab.ValuemaxxingLab (cognitive 88) 27-valuemaxxing/app/ValuemaxxingLab.tsx:777— ValuemaxxingLab.ValuemaxxingLab has cognitive complexity 88 (threshold 15). Drivers by points: ternaries 49 (118 pts), if/else 27 (34 pts), boolean chains 16, error handling 8 (10 pts), loops 1 (nesting depth added 78). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ValuemaxxingLab.ValuemaxxingLab::runMatrix::worker) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ParetoFrontier.ParetoFrontier (cognitive 83) 27-valuemaxxing/app/ParetoFrontier.tsx:356— ParetoFrontier.ParetoFrontier has cognitive complexity 83 (threshold 15). Drivers by points: ternaries 29 (49 pts), if/else 18 (21 pts), boolean chains 11, error handling 1, loops 1 (nesting depth added 23). Of this number, 33 points are the body's own statements and 50 belong to 19 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetricLoopDashboard.MetricLoopDashboard (cognitive 79) 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:150— MetricLoopDashboard.MetricLoopDashboard has cognitive complexity 79 (threshold 15). Drivers by points: ternaries 61 (73 pts), boolean chains 3, if/else 3 (nesting depth added 12). None of this is in the body itself: all 79 points belong to 17 function literals inside it that branch (lines 324, 404, 532, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
agent_service.run_agent (cognitive 70) 21-agentic-memory/scripts/agent_service.py:1708— agent_service.run_agent has cognitive complexity 70 (threshold 15). Drivers by points: if/else 22 (29 pts), error handling 11 (20 pts), boolean chains 16, ternaries 2 (4 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App.StorefrontApp (cognitive 55) 25-realtime-2/src/App.tsx:167— App.StorefrontApp has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 20 (22 pts), if/else 16 (18 pts), boolean chains 15 (nesting depth added 4). Most of this is not in the body itself: 6 of the 55 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 254, a function literal at line 467, a function literal at line 236, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
App.App (cognitive 54) 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:43— App.App has cognitive complexity 54 (threshold 15). Drivers by points: if/else 31 (35 pts), boolean chains 10, error handling 5 (7 pts), ternaries 2 (nesting depth added 6). Most of this is not in the body itself: 1 of the 54 points is its own statement and the rest belongs to 21 function items inside it that branch (connectToRealtime, a function literal at line 380, a function literal at line 47, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useSupplyRealtime.useSupplyRealtime.handleServerEvent (cognitive 53) 25-realtime-2/src/agent/useSupplyRealtime.ts:718— useSupplyRealtime.useSupplyRealtime.handleServerEvent has cognitive complexity 53 (threshold 15). Drivers by points: if/else 26 (39 pts), boolean chains 9, ternaries 2 (5 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
configuration-panel.ConfigurationPanel (cognitive 52) 21-agentic-memory/components/configuration-panel.tsx:24— configuration-panel.ConfigurationPanel has cognitive complexity 52 (threshold 15). Drivers by points: if/else 22 (26 pts), ternaries 14, boolean chains 7, error handling 5 (nesting depth added 4). Most of this is not in the body itself: 1 of the 52 points is its own statement and the rest belongs to 10 function items inside it that branch (handleAgentMemoryTrimmingChange, handleAgentMemorySummarizationChange, handleAgentMemoryCompactingChange, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useMetricLoopRealtime.useMetricLoopRealtime.handleServerEvent (cognitive 51) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:846— useMetricLoopRealtime.useMetricLoopRealtime.handleServerEvent has cognitive complexity 51 (threshold 15). Drivers by points: if/else 23 (33 pts), boolean chains 9, ternaries 4 (9 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataValidator.check_data_format_errors (cognitive 47) 05-4o_fine_tuning/data_validator.py:66— DataValidator.check_data_format_errors has cognitive complexity 47 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 5 (11 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
page.Home (cognitive 42) 24-api-codex/agentic-legibility-scorecard/app/page.tsx:25— page.Home has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 23 (32 pts), if/else 5 (6 pts), boolean chains 3, error handling 1 (nesting depth added 10). Of this number, 19 points are the body's own statements and 23 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent_service._extract_usage (cognitive 41) 21-agentic-memory/scripts/agent_service.py:1990— agent_service._extract_usage has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 3 (5 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
configuration-panel.AgentConfigCard (cognitive 39) 21-agentic-memory/components/configuration-panel.tsx:388— configuration-panel.AgentConfigCard has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 17, boolean chains 16, if/else 6. Of this number, 17 points are the body's own statements and 22 belong to 30 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CompactingSession._maybe_compact (cognitive 39) 21-agentic-memory/scripts/compacting_session.py:331— CompactingSession._maybe_compact has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useHandleSessionHistory.useHandleSessionHistory (cognitive 38) 14-voice-agents/realtime-workspace-agents/src/app/hooks/useHandleSessionHistory.ts:7— useHandleSessionHistory.useHandleSessionHistory has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 10, error handling 1 (2 pts), ternaries 1 (nesting depth added 4). None of this is in the body itself: all 38 points belong to 13 function items inside it that branch (handleHistoryAdded, handleTranscriptionCompleted, a function literal at line 24, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
chat-interface.ChatInterface (cognitive 38) 21-agentic-memory/components/chat-interface.tsx:237— chat-interface.ChatInterface has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 26, ternaries 7 (11 pts), if/else 1 (nesting depth added 4). Of this number, 20 points are the body's own statements and 18 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MainScene.updateNpcMovement (cognitive 37) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:778— MainScene.updateNpcMovement has cognitive complexity 37 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 12). None of this is in the body itself: all 37 points belong to one function literal inside it that branches (line 781). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
MainScene.runNpcConversation (cognitive 37) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1200— MainScene.runNpcConversation has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (26 pts), ternaries 3 (6 pts), boolean chains 4, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Transcript.Transcript (cognitive 36) 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:20— Transcript.Transcript has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 11, if/else 9, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 110, a function literal at line 42, a function literal at line 40, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
pingpong.html.connectToRoom (cognitive 36) 22-chatgptapp-pingpong/public/pingpong.html:1132— pingpong.html.connectToRoom has cognitive complexity 36 (threshold 15). Drivers by points: if/else 23 (32 pts), ternaries 2, boolean chains 1, error handling 1 (nesting depth added 9). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1216, 1266, 1246). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
page_1_semantic_search.main (cognitive 34) 11-recommendation/pages/page_1_semantic_search.py:14— page_1_semantic_search.main has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 2 (6 pts), error handling 1 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainScene.update (cognitive 33) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:287— MainScene.update has cognitive complexity 33 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 10, ternaries 2 (nesting depth added 2). Of this number, 26 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
route.runToolExperiment (cognitive 33) REDACTED:256— route.runToolExperiment has cognitive complexity 33 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 5 (10 pts), boolean chains 5, loops 3 (5 pts) (nesting depth added 15). Of this number, 30 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
metricloopForensicsRuntime.createMetricLoopForensicsRuntime::runTool (cognitive 32) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:271— metricloopForensicsRuntime.createMetricLoopForensicsRuntime::runTool has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 3 (8 pts), ternaries 3 (8 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 32) REDACTED:451— (anonymous) has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 6, error handling 2 (4 pts), other 2, ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
buildGameInsights (cognitive 31) REDACTED:155— buildGameInsights has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (15 pts), other 9, boolean chains 4, ternaries 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OpenAIDialogueAgent.provideResponseStream (cognitive 30) 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:30— OpenAIDialogueAgent.provideResponseStream has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 2 (3 pts), match/switch 1 (3 pts), error handling 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainScene.computePath (cognitive 30) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:619— MainScene.computePath has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (23 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 12). Of this number, 18 points are the body's own statements and 12 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.httpServer (cognitive 30) REDACTED:451— server.httpServer has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 6, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useSupplyRealtime.useSupplyRealtime.runFunctionCall (cognitive 29) 25-realtime-2/src/agent/useSupplyRealtime.ts:573— useSupplyRealtime.useSupplyRealtime.runFunctionCall has cognitive complexity 29 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 2, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
metricLoopEngine.buildAlternativeCauses (cognitive 29) 25-realtime-2/src/metricloop/metricLoopEngine.ts:1016— metricLoopEngine.buildAlternativeCauses has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 10 (25 pts), if/else 3, boolean chains 1 (nesting depth added 15). None of this is in the body itself: all 29 points belong to one function literal inside it that branches (line 1027). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
createPingPongServer (cognitive 29) REDACTED:242— createPingPongServer has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (10 pts), ternaries 5, other 3 (nesting depth added 1). None of this is in the body itself: all 29 points belong to 4 function literals inside it that branch (lines 367, 277, 327, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
metricloopForensicsRuntime.createDashboardFiltersForRow (cognitive 27) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:667— metricloopForensicsRuntime.createDashboardFiltersForRow has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 17 (27 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SummarizingSession.add_items (cognitive 27) 21-agentic-memory/scripts/agent_service.py:1187— SummarizingSession.add_items has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (19 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
metricLoopEngine.buildEngineeringBrief (cognitive 26) 25-realtime-2/src/metricloop/metricLoopEngine.ts:1174— metricLoopEngine.buildEngineeringBrief has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 14 (24 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetricLoopActionConsole.MetricLoopActionConsole (cognitive 26) 25-realtime-2/src/metricloop/MetricLoopActionConsole.tsx:86— MetricLoopActionConsole.MetricLoopActionConsole has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 6, ternaries 5 (6 pts), error handling 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 13 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
page.currentPhaseLabel (cognitive 25) 24-api-codex/agentic-legibility-scorecard/app/page.tsx:450— page.currentPhaseLabel has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
reviewInsights.buildShoeInsights (cognitive 25) 25-realtime-2/src/reviewInsights.ts:130— reviewInsights.buildShoeInsights has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 16 (25 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tools_helper.load_tools_completions_from_project_data (cognitive 25) 20-agent-rft/utils_shared/tools_helper.py:158— tools_helper.load_tools_completions_from_project_data has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLMSummarizer.summarize (cognitive 25) 21-agentic-memory/scripts/agent_service.py:822— LLMSummarizer.summarize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (6 pts), boolean chains 4, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent_service._extract_text_from_message (cognitive 25) 21-agentic-memory/scripts/agent_service.py:257— agent_service._extract_text_from_message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 5, error handling 1 (4 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compacting_session._stringify_content_field (cognitive 25) 21-agentic-memory/scripts/compacting_session.py:129— compacting_session._stringify_content_field has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
score_repo.discover_scopes (cognitive 25) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:191— score_repo.discover_scopes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dual-agent-demo.DualAgentDemo (cognitive 24) 21-agentic-memory/components/dual-agent-demo.tsx:90— dual-agent-demo.DualAgentDemo has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4, error handling 4, ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 104, handleSaveConfigs, handleSendMessage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tool_server_modal.list_endpoint (cognitive 24) 20-agent-rft/tool_server_modal.py:161— tool_server_modal.list_endpoint has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 3 (6 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pingpong.html.update (cognitive 23) 22-chatgptapp-pingpong/public/pingpong.html:1576— pingpong.html.update has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SupplyAssistant.SupplyAssistant (cognitive 23) 25-realtime-2/src/agent/SupplyAssistant.tsx:198— SupplyAssistant.SupplyAssistant has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, if/else 4, error handling 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 2). Of this number, 15 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
metricLoopForensicsData.addSessionsForPeriod (cognitive 23) 25-realtime-2/src/metricloop/metricLoopForensicsData.ts:532— metricLoopForensicsData.addSessionsForPeriod has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 3 (7 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
upload-to-qdrant.insert_data_into_qdrant (cognitive 23) 11-recommendation/upload-to-qdrant.py:65— upload-to-qdrant.insert_data_into_qdrant has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 3 (9 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plot_eval_runs.plot_score_stats_plotly (cognitive 23) 15-reinforcement-fine-tuning/utils/plot_eval_runs.py:197— plot_eval_runs.plot_score_stats_plotly has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11, if/else 6 (7 pts), boolean chains 4, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
agent_service._extract_text_from_final_output (cognitive 23) 21-agentic-memory/scripts/agent_service.py:297— agent_service._extract_text_from_final_output has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
score_repo.score_lint_format (cognitive 23) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:467— score_repo.score_lint_format has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
metricLoopEngine.buildScopedReport (cognitive 22) 25-realtime-2/src/metricloop/metricLoopEngine.ts:743— metricLoopEngine.buildScopedReport has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11 (18 pts), if/else 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useMetricLoopRealtime.formatToolChip (cognitive 22) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:151— useMetricLoopRealtime.formatToolChip has cognitive complexity 22 (threshold 15). Drivers by points: if/else 18, boolean chains 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
metricloopToolRuntime.createMetricLoopToolRuntime.runTool (cognitive 22) 25-realtime-2/src/server/metricloopToolRuntime.ts:72— metricloopToolRuntime.createMetricLoopToolRuntime.runTool has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 5, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ValuemaxxingLab.CacheResults (cognitive 22) 27-valuemaxxing/app/ValuemaxxingLab.tsx:498— ValuemaxxingLab.CacheResults has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11 (19 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app.call_gpt4o (cognitive 22) REDACTED:334— app.call_gpt4o has cognitive complexity 22 (threshold 15). Drivers by points: error handling 3 (10 pts), if/else 4 (8 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent_service._extract_role_and_text (cognitive 22) 21-agentic-memory/scripts/agent_service.py:392— agent_service._extract_role_and_text has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
route.POST (cognitive 21) REDACTED:21— route.POST has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 4 (6 pts), error handling 4, loops 2 (3 pts), boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 75). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
useSupplyRealtime.collectToolDetails (cognitive 21) 25-realtime-2/src/agent/useSupplyRealtime.ts:182— useSupplyRealtime.collectToolDetails has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 3 (6 pts) (nesting depth added 3). Of this number, 12 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ValuemaxxingLab.ValuemaxxingLab::runMatrix::worker (cognitive 21) 27-valuemaxxing/app/ValuemaxxingLab.tsx:996— ValuemaxxingLab.ValuemaxxingLab::runMatrix::worker has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 2 (9 pts), if/else 3 (7 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ValuemaxxingLab.ValuemaxxingLab) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
eval.process_file (cognitive 21) 05-4o_fine_tuning/eval.py:137— eval.process_file has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 1, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CompactingSession._normalize_item (cognitive 21) 21-agentic-memory/scripts/compacting_session.py:442— CompactingSession._normalize_item has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 2 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
score_repo.score_agent_repo_map (cognitive 21) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:535— score_repo.score_agent_repo_map has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ExecutionStream.ExecutionStream (cognitive 20) 07-reasoning/shipmentPlanning/frontend/src/ExecutionStream.js:24— ExecutionStream.ExecutionStream has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (7 pts), error handling 2 (6 pts), if/else 2 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 69, 27). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
agent_service._serialize_tool_value (cognitive 20) 21-agentic-memory/scripts/agent_service.py:204— agent_service._serialize_tool_value has cognitive complexity 20 (threshold 15). Drivers by points: error handling 6 (13 pts), if/else 5 (6 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainScene.updateNpcConversations (cognitive 19) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1128— MainScene.updateNpcConversations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ingest.ingest_json_files (cognitive 19) 04-mmrag_tooluse/ingest.py:49— ingest.ingest_json_files has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (13 pts), if/else 3 (6 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CompactingSession._strip_compacted_labels (cognitive 19) 21-agentic-memory/scripts/compacting_session.py:495— CompactingSession._strip_compacted_labels has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainScene.consumeNpcStream (cognitive 18) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1469— MainScene.consumeNpcStream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
data_explorer.main (cognitive 18) 05-4o_fine_tuning/data_explorer.py:43— data_explorer.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent_service._ensure_session (cognitive 18) 21-agentic-memory/scripts/agent_service.py:1539— agent_service._ensure_session has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WorkspaceContext.WorkspaceProvider (cognitive 17) 14-voice-agents/realtime-workspace-agents/src/app/contexts/WorkspaceContext.tsx:37— WorkspaceContext.WorkspaceProvider has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 1 (2 pts), ternaries 2 (nesting depth added 5). None of this is in the body itself: all 17 points belong to 6 function literals inside it that branch (lines 48, 65, 76, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
python-agent-bridge.runPythonAgent (cognitive 17) 21-agentic-memory/lib/python-agent-bridge.ts:286— python-agent-bridge.runPythonAgent has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (6 pts), if/else 2 (3 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useSupplyRealtime.formatToolChip (cognitive 17) 25-realtime-2/src/agent/useSupplyRealtime.ts:157— useSupplyRealtime.formatToolChip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useMetricLoopRealtime.collectToolDetails (cognitive 17) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:208— useMetricLoopRealtime.collectToolDetails has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App.ResultsPage (cognitive 17) 25-realtime-2/src/App.tsx:1079— App.ResultsPage has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 7 (nesting depth added 2). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
task-drawer.TaskDrawer (cognitive 17) 26-agents-sdk/web/src/components/task-drawer.tsx:65— task-drawer.TaskDrawer has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 3, ternaries 3. Of this number, 10 points are the body's own statements and 7 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
score_repo.score_structured_docs (cognitive 17) 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:601— score_repo.score_structured_docs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
main.resolveCollisions (cognitive 16) 17-gpt-5/minecraft/src/main.js:116— main.resolveCollisions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainScene.findClosestWalkableTile (cognitive 16) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:592— MainScene.findClosestWalkableTile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useMetricLoopRealtime.useMetricLoopRealtime.applyMetricLoopUiTool (cognitive 16) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:703— useMetricLoopRealtime.useMetricLoopRealtime.applyMetricLoopUiTool has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetricLoopDashboard.MetricLoopShell (cognitive 16) 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:951— MetricLoopDashboard.MetricLoopShell has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 12, boolean chains 3, if/else 1. Of this number, 12 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
agent_service._is_rag_tool_item (cognitive 16) 21-agentic-memory/scripts/agent_service.py:480— agent_service._is_rag_tool_item has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent_service.handle_command (cognitive 16) 21-agentic-memory/scripts/agent_service.py:2092— agent_service.handle_command has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: MainScene 18-responses-api/openai-simulator/src/scenes/MainScene.ts:58— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
MethodTooLong: MainScene.create 18-responses-api/openai-simulator/src/scenes/MainScene.ts:110— MethodTooLong — create runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) 21-agentic-memory/scripts/compacting_session.py:516— 21-agentic-memory/scripts/compacting_session.py:516-549 | 21-agentic-memory/scripts/compacting_session.py:552-579 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) 15-reinforcement-fine-tuning/utils/upload_utils.py:35— 15-reinforcement-fine-tuning/utils/upload_utils.py:35-66 | 20-agent-rft/utils_shared/file_upload.py:96-140 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) 02-assistants/4_tools.py:46— 02-assistants/4_tools.py:46-83 | 02-assistants/5_escalation.py:55-92 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) 26-agents-sdk/app/services/task_service.py:48— 26-agents-sdk/app/services/task_service.py:48-72 | 26-agents-sdk/app/services/task_service.py:75-91 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) 21-agentic-memory/scripts/agent_service.py:1610— 21-agentic-memory/scripts/agent_service.py:1610-1627 | 21-agentic-memory/scripts/agent_service.py:1637-1659 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) 15-reinforcement-fine-tuning/utils/upload_utils.py:15— 15-reinforcement-fine-tuning/utils/upload_utils.py:15-27 | 20-agent-rft/utils_shared/file_upload.py:48-64 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) 21-agentic-memory/scripts/agent_service.py:596— 21-agentic-memory/scripts/agent_service.py:596-611 | 21-agentic-memory/scripts/agent_service.py:616-630 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (27 lines × 2) 02-assistants/4_tools.py:46— 02-assistants/4_tools.py:46-72 | 02-assistants/5_escalation.py:55-81 — before extracting anything, compare `02-assistants/4_tools.py` and `02-assistants/5_escalation.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24 lines × 3) 02-assistants/4_tools.py:60— 02-assistants/4_tools.py:60-83 | 02-assistants/5_escalation.py:69-92 | 02-assistants/6_agents.py:39-62 — before extracting anything, compare `02-assistants/4_tools.py` and `02-assistants/5_escalation.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `02-assistants/4_tools.py:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–22 lines × 2) 21-agentic-memory/scripts/compacting_session.py:528— 21-agentic-memory/scripts/compacting_session.py:528-549 | 21-agentic-memory/scripts/compacting_session.py:561-579 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) 04-mmrag_tooluse/ingest.py:89— 04-mmrag_tooluse/ingest.py:89-111 | 04-mmrag_tooluse/ingest.py:113-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `04-mmrag_tooluse/ingest.py:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `04-mmrag_tooluse/ingest.py:88` calls `get` and `04-mmrag_tooluse/ingest.py:112` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) 16-built-in-tools/script/final.py:20— 16-built-in-tools/script/final.py:20-37 | 16-built-in-tools/script/main.py:14-31 — before extracting anything, compare `16-built-in-tools/script/final.py` and `16-built-in-tools/script/main.py` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13–14 lines × 2) 02-assistants/6_agents.py:25— 02-assistants/6_agents.py:25-37 | 02-assistants/7_orchestration.py:28-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `02-assistants/6_agents.py:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) 04-mmrag_tooluse/mmrag_bh.py:347— 04-mmrag_tooluse/mmrag_bh.py:347-360 | 04-mmrag_tooluse/mmrag_bh.py:545-558 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `04-mmrag_tooluse/mmrag_bh.py:347` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11–12 lines × 3) 26-agents-sdk/migrations/versions/0001_initial.py:82— 26-agents-sdk/migrations/versions/0001_initial.py:82-92 | 26-agents-sdk/migrations/versions/0001_initial.py:95-105 | 26-agents-sdk/migrations/versions/0001_initial.py:109-120 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `26-agents-sdk/migrations/versions/0001_initial.py:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) 12-agentic-tool-calling/4_queue_server.py:50— 12-agentic-tool-calling/4_queue_server.py:50-60 | 12-agentic-tool-calling/5_todos.py:98-108 — before extracting anything, compare `12-agentic-tool-calling/4_queue_server.py` and `12-agentic-tool-calling/5_todos.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 4) 26-agents-sdk/migrations/versions/0001_initial.py:65— 26-agents-sdk/migrations/versions/0001_initial.py:65-75 | 26-agents-sdk/migrations/versions/0001_initial.py:83-92 | 26-agents-sdk/migrations/versions/0001_initial.py:96-105 | 26-agents-sdk/migrations/versions/0001_initial.py:110-120 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `26-agents-sdk/migrations/versions/0001_initial.py:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `26-agents-sdk/migrations/versions/0001_initial.py:120` calls `Column`, `String`, `ForeignKey` and `26-agents-sdk/migrations/versions/0001_initial.py:75` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) 21-agentic-memory/scripts/compacting_session.py:151— 21-agentic-memory/scripts/compacting_session.py:151-159 | 21-agentic-memory/scripts/compacting_session.py:164-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6–9 lines × 3) 26-agents-sdk/migrations/versions/0001_initial.py:20— 26-agents-sdk/migrations/versions/0001_initial.py:20-25 | 26-agents-sdk/migrations/versions/0001_initial.py:94-102 | 26-agents-sdk/migrations/versions/0001_initial.py:108-116 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `26-agents-sdk/migrations/versions/0001_initial.py:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) 15-reinforcement-fine-tuning/utils/plot_eval_runs.py:112— 15-reinforcement-fine-tuning/utils/plot_eval_runs.py:112-126 | 15-reinforcement-fine-tuning/utils/plot_eval_runs.py:252-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) 15-reinforcement-fine-tuning/utils/upload_utils.py:21— 15-reinforcement-fine-tuning/utils/upload_utils.py:21-27 | 20-agent-rft/utils_shared/file_upload.py:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) 21-agentic-memory/scripts/agent_service.py:1610— 21-agentic-memory/scripts/agent_service.py:1610-1615 | 21-agentic-memory/scripts/agent_service.py:1637-1642 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 5) 02-assistants/3_tools.py:33— 02-assistants/3_tools.py:33-38 | 02-assistants/4_tools.py:33-38 | 02-assistants/5_escalation.py:33-38 | 02-assistants/6_agents.py:87-92 | 02-assistants/7_orchestration.py:166-171 — before extracting anything, compare `02-assistants/4_tools.py` and `02-assistants/5_escalation.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (7 lines × 3) 02-assistants/4_tools.py:87— 02-assistants/4_tools.py:87-93 | 02-assistants/5_escalation.py:96-102 | 02-assistants/6_agents.py:66-72 — before extracting anything, compare `02-assistants/4_tools.py` and `02-assistants/5_escalation.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) 02-assistants/5_escalation.py:42— 02-assistants/5_escalation.py:42-47 | 02-assistants/6_agents.py:96-101 | 02-assistants/7_orchestration.py:88-93 — before extracting anything, compare `02-assistants/5_escalation.py` and `02-assistants/6_agents.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) 12-agentic-tool-calling/4_queue_server.py:65— 12-agentic-tool-calling/4_queue_server.py:65-72 | 12-agentic-tool-calling/5_todos.py:113-120 — before extracting anything, compare `12-agentic-tool-calling/4_queue_server.py` and `12-agentic-tool-calling/5_todos.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Fake-async — async method never awaits 06-structured_outputs/structured-outputs-assistant-starting-point/lib/assistant.ts:29— `handleTool` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing 25-realtime-2/src/App.tsx:1701— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Forked directory tree (45 identical files, ~27598 lines × 2 trees) REDACTED:1— 06-structured_outputs/structured-outputs-assistant-final/ and 06-structured_outputs/structured-outputs-assistant-starting-point/ are near-verbatim copies of each other: 45 files are byte-identical under the same relative paths (~27598 lines; the trees hold 51 and 51 files). That is one structural fact, not 45 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Forked directory tree (49 identical files, ~15629 lines × 2 trees) REDACTED:1— 16-built-in-tools/dashboard-demo-final/ and 16-built-in-tools/dashboard-demo-starting-point/ are near-verbatim copies of each other: 49 files are byte-identical under the same relative paths (~15629 lines; the trees hold 53 and 53 files). That is one structural fact, not 49 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Forked directory tree (31 identical files, ~7760 lines × 2 trees) REDACTED:1— 06-structured_outputs/structured-outputs-math-tutor-final/ and 06-structured_outputs/structured-outputs-math-tutor-starting-point/ are near-verbatim copies of each other: 31 files are byte-identical under the same relative paths (~7760 lines; the trees hold 31 and 31 files). That is one structural fact, not 31 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplication concentrated across 4 sibling directories (51 clone groups) 06-structured_outputs/structured-outputs-assistant-final/lib/database.ts:1— 51 duplicated blocks under 06-structured_outputs/ have copies in at least two of the sibling directories structured-outputs-assistant-final, structured-outputs-assistant-starting-point, structured-outputs-math-tutor-final, structured-outputs-math-tutor-starting-point — 45 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 51 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 51 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 51 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (29 clone groups) 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1— 29 duplicated blocks under 16-built-in-tools/ have copies in at least two of the sibling directories dashboard-demo-final, dashboard-demo-starting-point — 28 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 29 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 11 sibling directories (19 clone groups) REDACTED:3— 19 duplicated blocks under the repository root have copies in at least two of the sibling directories 06-structured_outputs, 07-reasoning, 09-realtime, 13-image-gen, 14-voice-agents, 16-built-in-tools (+5 more sibling(s) not listed) — 14 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (15 clone groups) 25-realtime-2/src/agent/useSupplyRealtime.ts:66— 15 duplicated blocks under 25-realtime-2/src/ have copies in at least two of the sibling directories agent, metricloop, server — 10 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (344 identical lines × 2 files) 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1— 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1 · 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:1 — these 2 files are line-for-line copies of one another — 344 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (320 matched lines × 2 locations) · ×1
Duplicated block with local edits (320 matched lines × 2 locations) 25-realtime-2/src/agent/useSupplyRealtime.ts:66— 25-realtime-2/src/agent/useSupplyRealtime.ts:66 · 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:68 — the two spans are one implementation copied and then locally edited — 2050 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.
Wholesale file copy (226 identical lines × 2 files) 16-built-in-tools/dashboard-demo-final/components/data-table.tsx:3— 16-built-in-tools/dashboard-demo-final/components/data-table.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/data-table.tsx:3 — these 2 files are line-for-line copies of one another — 226 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (190 identical lines × 2 files) 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:1— 16-built-in-tools/dashboard-demo-final/components/tool-call.tsx:1 · 16-built-in-tools/dashboard-demo-starting-point/components/tool-call.tsx:1 — these 2 files are line-for-line copies of one another — 190 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (183 identical lines × 4 files) REDACTED:3— REDACTED:3 · REDACTED:3 · REDACTED:3 · REDACTED:3 — these 4 files are line-for-line copies of one another — 183 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (136 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/lib/database.ts:1— 06-structured_outputs/structured-outputs-assistant-final/lib/database.ts:1 · 06-structured_outputs/structured-outputs-assistant-starting-point/lib/database.ts:1 — these 2 files are line-for-line copies of one another — 136 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (117 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/components/ui/dropdown-menu.tsx:3— 06-structured_outputs/structured-outputs-assistant-final/components/ui/dropdown-menu.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/dropdown-menu.tsx:3 — these 2 files are line-for-line copies of one another — 117 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (116 lines × 2 locations) 21-agentic-memory/components/ui/context-menu.tsx:110— 21-agentic-memory/components/ui/context-menu.tsx:110 · 21-agentic-memory/components/ui/menubar.tsx:87 — 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.
R10 · Code Duplication· Duplicated block with local edits (108 matched lines × 2 locations) · ×1
Duplicated block with local edits (108 matched lines × 2 locations) 21-agentic-memory/components/ui/item.tsx:8— 21-agentic-memory/components/ui/item.tsx:8 · 21-agentic-memory/components/ui/sidebar.tsx:346 — the two spans are one implementation copied and then locally edited — 394 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.
Wholesale file copy (107 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/lib/components-mapping.tsx:3— 06-structured_outputs/structured-outputs-assistant-final/lib/components-mapping.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/lib/components-mapping.tsx:3 — these 2 files are line-for-line copies of one another — 107 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (103 identical lines × 2 files) 21-agentic-memory/components/ui/use-toast.ts:4— 21-agentic-memory/components/ui/use-toast.ts:4 · 21-agentic-memory/hooks/use-toast.ts:4 — these 2 files are line-for-line copies of one another — 103 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (96 lines × 2 locations) 21-agentic-memory/components/ui/dropdown-menu.tsx:131— 21-agentic-memory/components/ui/dropdown-menu.tsx:131 · 21-agentic-memory/components/ui/menubar.tsx:149 — 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.
Wholesale file copy (94 identical lines × 4 files) 06-structured_outputs/structured-outputs-assistant-final/components/ui/select.tsx:3— 06-structured_outputs/structured-outputs-assistant-final/components/ui/select.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/select.tsx:3 · 16-built-in-tools/dashboard-demo-final/components/ui/select.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/ui/select.tsx:3 — these 4 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (92 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:3— 06-structured_outputs/structured-outputs-assistant-final/components/chat.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/chat.tsx:3 — these 2 files are line-for-line copies of one another — 92 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (88 identical lines × 2 files) 16-built-in-tools/dashboard-demo-final/components/chart-area-interactive.tsx:3— 16-built-in-tools/dashboard-demo-final/components/chart-area-interactive.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/chart-area-interactive.tsx:3 — these 2 files are line-for-line copies of one another — 88 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (80 lines × 2 locations) 21-agentic-memory/components/chat-interface.tsx:282— 21-agentic-memory/components/chat-interface.tsx:282 · 21-agentic-memory/components/chat-interface.tsx:367 — all 2 copies are in the same file, 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.
R10 · Code Duplication· Duplicated block with local edits (75 matched lines × 2 locations) · ×1
Duplicated block with local edits (75 matched lines × 2 locations) 06-structured_outputs/structured-outputs-assistant-final/components/assistant.tsx:12— 06-structured_outputs/structured-outputs-assistant-final/components/assistant.tsx:12 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/assistant.tsx:12 — the two spans are one implementation copied and then locally edited — 420 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.
Duplicated block (73 lines × 2 locations) 16-built-in-tools/dashboard-demo-final/components/annotations.tsx:3— 16-built-in-tools/dashboard-demo-final/components/annotations.tsx:3 · 16-built-in-tools/dashboard-demo-starting-point/components/annotations.tsx:3 — 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.
Wholesale file copy (72 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/components/ui/sheet.tsx:3— 06-structured_outputs/structured-outputs-assistant-final/components/ui/sheet.tsx:3 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/sheet.tsx:3 — these 2 files are line-for-line copies of one another — 72 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (70 lines × 2 locations) 25-realtime-2/src/agent/useSupplyRealtime.ts:929— 25-realtime-2/src/agent/useSupplyRealtime.ts:929 · 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:1047 — 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.
Duplicated block (69 lines × 2 locations) 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/chatSupervisor/supervisorAgent.ts:186— 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/chatSupervisor/supervisorAgent.ts:186 · 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/workspaceManager.ts:186 — 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.
Wholesale file copy (66 identical lines × 2 files) 06-structured_outputs/structured-outputs-math-tutor-final/components/solution.tsx:2— 06-structured_outputs/structured-outputs-math-tutor-final/components/solution.tsx:2 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/solution.tsx:2 — these 2 files are line-for-line copies of one another — 66 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (65 lines × 4 locations) 06-structured_outputs/structured-outputs-assistant-final/components/ui/card.tsx:5— 06-structured_outputs/structured-outputs-assistant-final/components/ui/card.tsx:5 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/card.tsx:5 · 16-built-in-tools/dashboard-demo-final/components/ui/card.tsx:5 · 16-built-in-tools/dashboard-demo-starting-point/components/ui/card.tsx:5 — the 4 copies are spread across 4 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Wholesale file copy (63 identical lines × 2 files) 06-structured_outputs/structured-outputs-math-tutor-final/tailwind.config.ts:2— 06-structured_outputs/structured-outputs-math-tutor-final/tailwind.config.ts:2 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/tailwind.config.ts:2 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (61 identical lines × 2 files) 06-structured_outputs/structured-outputs-assistant-final/components/ui/breadcrumb.tsx:1— 06-structured_outputs/structured-outputs-assistant-final/components/ui/breadcrumb.tsx:1 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/breadcrumb.tsx:1 — these 2 files are line-for-line copies of one another — 61 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (61 lines × 2 locations) REDACTED:5— REDACTED:5 · REDACTED:5 — 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.
Wholesale file copy (58 identical lines × 4 files) 06-structured_outputs/structured-outputs-assistant-final/components/ui/table.tsx:1— 06-structured_outputs/structured-outputs-assistant-final/components/ui/table.tsx:1 · 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/table.tsx:1 · 16-built-in-tools/dashboard-demo-final/components/ui/table.tsx:1 · 16-built-in-tools/dashboard-demo-starting-point/components/ui/table.tsx:1 — these 4 files are line-for-line copies of one another — 58 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (56 identical lines × 2 files) 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:1— 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:1 · 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/prompt-form.tsx:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (55 identical lines × 2 files) 16-built-in-tools/dashboard-demo-final/tailwind.config.ts:1— 16-built-in-tools/dashboard-demo-final/tailwind.config.ts:1 · 16-built-in-tools/dashboard-demo-starting-point/tailwind.config.ts:1 — these 2 files are line-for-line copies of one another — 55 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Complex function (anonymous) (cyclomatic 53, cognitive 59) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:846— (anonymous) has cyclomatic complexity 53 and cognitive complexity 59; 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.
Complex function (anonymous) (cyclomatic 52, cognitive 60) 25-realtime-2/src/agent/useSupplyRealtime.ts:718— (anonymous) has cyclomatic complexity 52 and cognitive complexity 60; 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.
Complex function ValuemaxxingLab (cyclomatic 44, cognitive 42) 27-valuemaxxing/app/ValuemaxxingLab.tsx:777— ValuemaxxingLab has cyclomatic complexity 44 and cognitive complexity 42; 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.
Complex function runTool (cyclomatic 34, cognitive 44) 25-realtime-2/src/server/metricloopToolRuntime.ts:72— runTool has cyclomatic complexity 34 and cognitive complexity 44; 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.
Complex function buildGameInsights (cyclomatic 27, cognitive 31) REDACTED:155— buildGameInsights has cyclomatic complexity 27 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.
Complex function (anonymous) (cyclomatic 27, cognitive 30) 25-realtime-2/src/agent/useSupplyRealtime.ts:573— (anonymous) has cyclomatic complexity 27 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.
Complex function update (cyclomatic 27, cognitive 28) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:287— update has cyclomatic complexity 27 and cognitive complexity 28; 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.
Complex function ChatInterface (cyclomatic 27, cognitive 20) 21-agentic-memory/components/chat-interface.tsx:237— ChatInterface has cyclomatic complexity 27 and cognitive complexity 20; 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.
Complex function runTool (cyclomatic 26, cognitive 39) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:271— runTool has cyclomatic complexity 26 and cognitive complexity 39; 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.
Complex function (anonymous) (cyclomatic 25, cognitive 32) REDACTED:451— (anonymous) has cyclomatic complexity 25 and cognitive complexity 32; 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.
Complex function ParetoFrontier (cyclomatic 25, cognitive 21) 27-valuemaxxing/app/ParetoFrontier.tsx:356— ParetoFrontier has cyclomatic complexity 25 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 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.
Complex function (anonymous) (cyclomatic 24, cognitive 44) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:781— (anonymous) has cyclomatic complexity 24 and cognitive complexity 44; 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.
Complex function provideResponseStream (cyclomatic 23, cognitive 32) 18-responses-api/openai-simulator/src/dialogue/OpenAIAgent.ts:30— provideResponseStream has cyclomatic complexity 23 and cognitive complexity 32; 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.
Complex function formatToolChip (cyclomatic 23, cognitive 22) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:151— formatToolChip has cyclomatic complexity 23 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 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.
Complex function analysisViewReducer (cyclomatic 23, cognitive 19) 24-api-codex/agentic-legibility-scorecard/lib/analysis/state.ts:51— analysisViewReducer 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.
Complex function runNpcConversation (cyclomatic 22, cognitive 39) 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1200— runNpcConversation has cyclomatic complexity 22 and cognitive complexity 39; 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.
Complex function runPythonAgent (cyclomatic 22, cognitive 24) 21-agentic-memory/lib/python-agent-bridge.ts:286— runPythonAgent has cyclomatic complexity 22 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.
Complex function runToolExperiment (cyclomatic 21, cognitive 34) REDACTED:256— runToolExperiment has cyclomatic complexity 21 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.
Complex function buildEngineeringBrief (cyclomatic 21, cognitive 18) 25-realtime-2/src/metricloop/metricLoopEngine.ts:1174— buildEngineeringBrief has cyclomatic complexity 21 and cognitive complexity 18; 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.
Complex function SupplyAssistant (cyclomatic 21, cognitive 17) 25-realtime-2/src/agent/SupplyAssistant.tsx:198— SupplyAssistant has cyclomatic complexity 21 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 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.
Complex function normalizeImportedResult (cyclomatic 21, cognitive 16) 27-valuemaxxing/lib/runs.ts:113— normalizeImportedResult has cyclomatic complexity 21 and cognitive complexity 16; 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.
R2 · Cyclomatic Complexity· Complex function Home (cyclomatic 20, cognitive 19) · ×1
Complex function Home (cyclomatic 20, cognitive 19) 24-api-codex/agentic-legibility-scorecard/app/page.tsx:25— Home has cyclomatic complexity 20 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.
Complex function (anonymous) (cyclomatic 20, cognitive 19) 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:324— (anonymous) has cyclomatic complexity 20 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.
Complex function ForensicsTraceCard (cyclomatic 20, cognitive 17) 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx:114— ForensicsTraceCard has cyclomatic complexity 20 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 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.
Complex function currentPhaseLabel (cyclomatic 19, cognitive 25) 24-api-codex/agentic-legibility-scorecard/app/page.tsx:450— currentPhaseLabel has cyclomatic complexity 19 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.
Complex function (anonymous) (cyclomatic 19, cognitive 17) REDACTED:367— (anonymous) has cyclomatic complexity 19 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 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.
Complex function CacheResults (cyclomatic 19, cognitive 17) 27-valuemaxxing/app/ValuemaxxingLab.tsx:498— CacheResults has cyclomatic complexity 19 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 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.
Complex function ConsolePage (cyclomatic 19, cognitive 16) 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:57— ConsolePage has cyclomatic complexity 19 and cognitive complexity 16; 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.
Complex function formatToolChip (cyclomatic 18, cognitive 17) 25-realtime-2/src/agent/useSupplyRealtime.ts:157— formatToolChip has cyclomatic complexity 18 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 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.
Complex function createDashboardFiltersForRow (cyclomatic 18, cognitive 17) 25-realtime-2/src/server/metricloopForensicsRuntime.ts:667— createDashboardFiltersForRow has cyclomatic complexity 18 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 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.
Complex function (anonymous) (cyclomatic 17, cognitive 24) 14-voice-agents/realtime-workspace-agents/src/app/components/Transcript.tsx:110— (anonymous) 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.
Complex function addBorderToImage (cyclomatic 17, cognitive 22) 13-image-gen/imagegen-demo/src/lib/imageProcessing.ts:22— addBorderToImage has cyclomatic complexity 17 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.
Complex function (anonymous) (cyclomatic 17, cognitive 16) 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:703— (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; 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.
Complex function buildShoeInsights (cyclomatic 17, cognitive 16) 25-realtime-2/src/reviewInsights.ts:130— buildShoeInsights has cyclomatic complexity 17 and cognitive complexity 16; 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.
Complex function outputText (cyclomatic 17, cognitive 16) 26-agents-sdk/web/src/components/task-drawer.tsx:52— outputText has cyclomatic complexity 17 and cognitive complexity 16; 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.
Complex function TaskDrawer (cyclomatic 17, cognitive 16) 26-agents-sdk/web/src/components/task-drawer.tsx:65— TaskDrawer has cyclomatic complexity 17 and cognitive complexity 16; 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.
R3 · Large Files· 27-valuemaxxing/app/ValuemaxxingLab.tsx · ×1
27-valuemaxxing/app/ValuemaxxingLab.tsx: 1862 lines of code 27-valuemaxxing/app/ValuemaxxingLab.tsx:1— 27-valuemaxxing/app/ValuemaxxingLab.tsx has 1862 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
25-realtime-2/src/App.tsx: 1763 lines of code 25-realtime-2/src/App.tsx:1— 25-realtime-2/src/App.tsx has 1763 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/metricloop/metricLoopEngine.ts · ×1
25-realtime-2/src/metricloop/metricLoopEngine.ts: 1390 lines of code 25-realtime-2/src/metricloop/metricLoopEngine.ts:1— 25-realtime-2/src/metricloop/metricLoopEngine.ts has 1390 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 18-responses-api/openai-simulator/src/scenes/MainScene.ts · ×1
18-responses-api/openai-simulator/src/scenes/MainScene.ts: 1249 lines of code 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1— 18-responses-api/openai-simulator/src/scenes/MainScene.ts has 1249 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx · ×1
25-realtime-2/src/metricloop/MetricLoopDashboard.tsx: 1165 lines of code 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:1— 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx has 1165 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts · ×1
25-realtime-2/src/metricloop/useMetricLoopRealtime.ts: 1153 lines of code 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:1— 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts has 1153 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
25-realtime-2/src/data.ts: 998 lines of code 25-realtime-2/src/data.ts:1— 25-realtime-2/src/data.ts has 998 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/agent/useSupplyRealtime.ts · ×1
25-realtime-2/src/agent/useSupplyRealtime.ts: 995 lines of code 25-realtime-2/src/agent/useSupplyRealtime.ts:1— 25-realtime-2/src/agent/useSupplyRealtime.ts has 995 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 21-agentic-memory/components/configuration-panel.tsx · ×1
21-agentic-memory/components/configuration-panel.tsx: 840 lines of code 21-agentic-memory/components/configuration-panel.tsx:1— 21-agentic-memory/components/configuration-panel.tsx has 840 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 27-valuemaxxing/app/ParetoFrontier.tsx · ×1
27-valuemaxxing/app/ParetoFrontier.tsx: 777 lines of code 27-valuemaxxing/app/ParetoFrontier.tsx:1— 27-valuemaxxing/app/ParetoFrontier.tsx has 777 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx · ×1
09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx: 732 lines of code 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:1— 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx has 732 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/metricloop/metricLoopForensicsData.ts · ×1
25-realtime-2/src/metricloop/metricLoopForensicsData.ts: 726 lines of code 25-realtime-2/src/metricloop/metricLoopForensicsData.ts:1— 25-realtime-2/src/metricloop/metricLoopForensicsData.ts has 726 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/server/metricloopForensicsRuntime.ts · ×1
25-realtime-2/src/server/metricloopForensicsRuntime.ts: 704 lines of code 25-realtime-2/src/server/metricloopForensicsRuntime.ts:1— 25-realtime-2/src/server/metricloopForensicsRuntime.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 21-agentic-memory/components/ui/sidebar.tsx · ×1
21-agentic-memory/components/ui/sidebar.tsx: 672 lines of code 21-agentic-memory/components/ui/sidebar.tsx:1— 21-agentic-memory/components/ui/sidebar.tsx has 672 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx · ×1
25-realtime-2/src/metricloop/MetricLoopNotebook.tsx: 544 lines of code 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx:1— 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx has 544 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 541 lines of code REDACTED:1— REDACTED has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js · ×1
09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js: 519 lines of code 09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js:1— 09-realtime/openai-realtime-console-example/src/lib/wavtools/lib/wav_recorder.js has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 24-api-codex/agentic-legibility-scorecard/app/page.tsx · ×1
24-api-codex/agentic-legibility-scorecard/app/page.tsx: 508 lines of code 24-api-codex/agentic-legibility-scorecard/app/page.tsx:1— 24-api-codex/agentic-legibility-scorecard/app/page.tsx has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts · ×1
16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts: 504 lines of code 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:1— 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 16-built-in-tools/dashboard-demo-final/lib/assistant.ts · ×1
16-built-in-tools/dashboard-demo-final/lib/assistant.ts: 499 lines of code 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:1— 16-built-in-tools/dashboard-demo-final/lib/assistant.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 24-api-codex/agentic-legibility-scorecard/lib/analysis/openai.ts · ×1
24-api-codex/agentic-legibility-scorecard/lib/analysis/openai.ts: 497 lines of code 24-api-codex/agentic-legibility-scorecard/lib/analysis/openai.ts:1— 24-api-codex/agentic-legibility-scorecard/lib/analysis/openai.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 21-agentic-memory/components/chat-interface.tsx · ×1
21-agentic-memory/components/chat-interface.tsx: 462 lines of code 21-agentic-memory/components/chat-interface.tsx:1— 21-agentic-memory/components/chat-interface.tsx has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts · ×1
06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts: 460 lines of code 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts:1— 06-structured_outputs/structured-outputs-assistant-final/lib/tools.ts has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx · ×1
25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx: 438 lines of code 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx:1— 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· 14-voice-agents/realtime-workspace-agents/src/app/App.tsx · ×1
14-voice-agents/realtime-workspace-agents/src/app/App.tsx: 433 lines of code 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:1— 14-voice-agents/realtime-workspace-agents/src/app/App.tsx has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step 21-agentic-memory/next.config.mjs:7— `21-agentic-memory` is TypeScript, but a type error in it cannot fail anything this repository runs: its Next.js config sets `typescript.ignoreBuildErrors: true`, so `next build` — the one step that would run the type checker — passes over type errors, and no script, config or CI step of the package runs `tsc` instead. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
Dead file (~726 LoC) 21-agentic-memory/components/ui/sidebar.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~353 LoC) REDACTED— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~329 LoC) 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/authentication.ts— no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~305 LoC) 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/returns.ts— no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/customerServiceRetail/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~276 LoC) 21-agentic-memory/components/ui/menubar.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~257 LoC) 21-agentic-memory/components/ui/dropdown-menu.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~252 LoC) 21-agentic-memory/components/ui/context-menu.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~244 LoC) 21-agentic-memory/components/ui/field.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~241 LoC) 21-agentic-memory/components/ui/carousel.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~213 LoC) 21-agentic-memory/components/ui/calendar.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~205 LoC) 06-structured_outputs/structured-outputs-assistant-starting-point/components/ui/dropdown-menu.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~198 LoC) 21-agentic-memory/components/context-visualization.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~193 LoC) 21-agentic-memory/components/ui/item.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~191 LoC) 21-agentic-memory/components/ui/use-toast.ts— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~184 LoC) 21-agentic-memory/components/ui/command.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~171 LoC) 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/TabContent.tsx— no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (14-voice-agents/realtime-workspace-agents/src/app/components/Workspace.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~169 LoC) 21-agentic-memory/components/ui/input-group.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~167 LoC) 21-agentic-memory/components/ui/form.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~166 LoC) 21-agentic-memory/components/ui/navigation-menu.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~157 LoC) 21-agentic-memory/components/ui/alert-dialog.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~155 LoC) 14-voice-agents/realtime-workspace-agents/src/app/components/workspace/Sidebar.tsx— no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (14-voice-agents/realtime-workspace-agents/src/app/components/Workspace.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~143 LoC) 21-agentic-memory/components/ui/dialog.tsx— no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (21-agentic-memory/components/ui/command.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~139 LoC) 21-agentic-memory/components/ui/sheet.tsx— no import path from any entry point (93 application, 63 tooling, 40 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (21-agentic-memory/components/ui/sidebar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~135 LoC) 21-agentic-memory/components/ui/drawer.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~127 LoC) 21-agentic-memory/components/ui/pagination.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~116 LoC) 21-agentic-memory/components/ui/table.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~109 LoC) 21-agentic-memory/components/ui/breadcrumb.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Dead file (~104 LoC) 21-agentic-memory/components/ui/empty.tsx— no import path from any entry point (93 application, 63 tooling, 40 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
Unused dependency '@ai-sdk/openai' REDACTED:16— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-alert-dialog' REDACTED:17— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-dialog' REDACTED:18— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-dropdown-menu' REDACTED:19— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-icons' REDACTED:20— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-label' REDACTED:21— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-select' REDACTED:22— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-separator' REDACTED:23— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-slot' REDACTED:24— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-switch' REDACTED:25— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@radix-ui/react-tooltip' REDACTED:26— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@vercel/kv' REDACTED:28— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@vercel/og' REDACTED:29— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'ai' REDACTED:30— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'class-variance-authority' REDACTED:32— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'd3-scale' REDACTED:34— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'date-fns' REDACTED:35— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'focus-trap-react' REDACTED:36— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'framer-motion' REDACTED:37— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'nanoid' REDACTED:40— Declared in REDACTED but never imported anywhere in that package or its workspace members — while 14-voice-agents/realtime-workspace-agents/src/app/contexts/WorkspaceContext.tsx DOES import it and no REDACTED above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the REDACTED that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
Unused dependency 'next-auth' REDACTED:42— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'next-themes' REDACTED:43— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'node-fetch' REDACTED:44— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-confetti' REDACTED:47— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked 07-reasoning/shipmentPlanning/frontend/package.json:5— 07-reasoning/shipmentPlanning/frontend/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Orphaned file 18-responses-api/openai-simulator/src/scenes/MainScene.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/metricloop/metricLoopEngine.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/metricloop/MetricLoopDashboard.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 21-agentic-memory/components/configuration-panel.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/data.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 27-valuemaxxing/app/ParetoFrontier.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 06-structured_outputs/python-example/data/input.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/server/metricloopForensicsRuntime.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 09-realtime/openai-realtime-console-example/src/pages/ConsolePage.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/metricloop/metricLoopForensicsData.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 04-mmrag_tooluse/mmrag_bh.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 07-reasoning/flightCancellationPolicy/functionDefinitions.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 21-agentic-memory/scripts/compacting_session.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 21-agentic-memory/components/ui/sidebar.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/metricloop/metricLoopPrompt.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 21-agentic-memory/components/chat-interface.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 11-recommendation/helper_functions.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 24-api-codex/agentic-legibility-scorecard/app/page.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 25-realtime-2/src/agent/supplyPrompt.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 20-agent-rft/utils_shared/tracing_storing.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 26-agents-sdk/app/agents/runtime.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:54— `!(path === 'fn' && isFunctionNode(parent)) && !['pi', 'e'].includes(node.name)` appears character-identically in 2 files — 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts, 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/useSolution.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:355— `!activeMessageId || !hasActivityTrace(trace)` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:794— `!audioTurnPreparedRef.current && !pendingAudioUserMessageIdRef.current` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:64— `!body || typeof body.enable !== "boolean"` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:314— `!dataChannel || dataChannel.readyState !== 'open'` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:51— `!isSymbolNode(node.fn) || !answerFunctions.has(node.fn.name)` appears character-identically in 2 files — 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts, 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/useSolution.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:180— `!lastItem || lastItem.type !== "message" || lastItem.role !== "assistant" || (lastItem.id && lastItem.id !== item_id)` appears character-identically in 2 files — 16-built-in-tools/dashboard-demo-final/lib/assistant.ts, 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts:102— `!responseMessageContent || (!responseMessageContent.steps && !responseMessageContent.refusal)` appears character-identically in 2 files — 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts, 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/useSolution.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx:345— `!value || typeof value !== 'object' || Array.isArray(value)` appears character-identically in 2 files — 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:771— `(event.type === 'response.output_audio_transcript.delta' || event.type === 'response.output_text.delta') && event.delta && event.item_id` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/supplyRealtimeDebugLog.ts:35— `Boolean(value) && typeof value === 'object' && !Array.isArray(value)` appears character-identically in 3 files — 25-realtime-2/src/agent/supplyRealtimeDebugLog.ts, 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 16-built-in-tools/dashboard-demo-final/components/message.tsx:38— `a.type === "container_file_citation" && a.filename && /\.(png|jpg|jpeg|gif|webp|svg)$/i.test(a.filename)` appears character-identically in 2 files — 16-built-in-tools/dashboard-demo-final/components/message.tsx, 16-built-in-tools/dashboard-demo-starting-point/components/message.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 16-built-in-tools/dashboard-demo-final/components/annotations.tsx:57— `a.type === annotation.type && ((annotation.type === "file_citation" && a.fileId === annotation.fileId) || (annotation.type === "url_citation…` appears character-identically in 2 files — 16-built-in-tools/dashboard-demo-final/components/annotations.tsx, 16-built-in-tools/dashboard-demo-starting-point/components/annotations.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/metricloop/MetricLoopActionConsole.tsx:68— `activity.status === 'done' || activity.status === 'repaired' || activity.status === 'fallback_used' || activity.status === 'needs_rewrite'` appears character-identically in 3 files — 25-realtime-2/src/metricloop/MetricLoopActionConsole.tsx, 25-realtime-2/src/metricloop/MetricLoopForensicsWorkbench.tsx, 25-realtime-2/src/metricloop/MetricLoopNotebook.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 16-built-in-tools/dashboard-demo-final/components/annotations.tsx:44— `annotation.filename || annotation.fileId` appears character-identically in 2 files — 16-built-in-tools/dashboard-demo-final/components/annotations.tsx, 16-built-in-tools/dashboard-demo-starting-point/components/annotations.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:119— `body.model !== undefined && (typeof body.model !== "string" || !isModelId(body.model))` appears character-identically in 3 files — REDACTED, 27-valuemaxxing/app/api/experiments/compaction/route.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 06-structured_outputs/structured-outputs-math-tutor-final/app/api/math_responses/route.ts:43— `completion.choices && completion.choices.length > 0` appears character-identically in 2 files — 06-structured_outputs/structured-outputs-math-tutor-final/app/api/math_responses/route.ts, 06-structured_outputs/structured-outputs-math-tutor-starting-point/app/api/math_responses/route.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 16-built-in-tools/dashboard-demo-final/lib/assistant.ts:198— `contentItem && contentItem.type === "output_text"` appears character-identically in 2 files — 16-built-in-tools/dashboard-demo-final/lib/assistant.ts, 16-built-in-tools/dashboard-demo-starting-point/lib/assistant.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 06-structured_outputs/structured-outputs-math-tutor-final/lib/actions.ts:26— `errorMessage || 'Failed to fetch solution'` appears character-identically in 2 files — 06-structured_outputs/structured-outputs-math-tutor-final/lib/actions.ts, 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/actions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:750— `event.item.type === 'function_call' && event.item.call_id && event.item.name` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 16-built-in-tools/dashboard-demo-final/components/chat.tsx:35— `event.key === "Enter" && !event.shiftKey && !isComposing` appears character-identically in 2 files — 16-built-in-tools/dashboard-demo-final/components/chat.tsx, 16-built-in-tools/dashboard-demo-starting-point/components/chat.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx:14— `event.key === 'Enter' && !event.shiftKey && !event.nativeEvent.isComposing` appears character-identically in 2 files — 06-structured_outputs/structured-outputs-math-tutor-final/components/prompt-form.tsx, 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/prompt-form.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:760— `event.type === 'response.function_call_arguments.delta' && event.item_id && event.delta` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:747— `event.type === 'response.output_item.added' && event.item?.id` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate 25-realtime-2/src/agent/useSupplyRealtime.ts:807— `event.type === 'response.output_item.done' && event.item?.type === 'function_call' && event.item.id && event.item.call_id && event.item.name` appears character-identically in 2 files — 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/metricloop/useMetricLoopRealtime.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:192— `info` at line 192 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:320— `error` at line 320 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:333— `error` at line 333 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:347— `info` at line 347 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:373— `info` at line 373 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:386— `error` at line 386 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/helper_functions.py:458— `info` at line 458 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:34— `error` at line 34 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:37— `error` at line 37 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:43— `info` at line 43 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:45— `error` at line 45 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:60— `info` at line 60 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:77— `warning` at line 77 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:79— `error` at line 79 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:81— `warning` at line 81 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:105— `info` at line 105 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:108— `error` at line 108 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:117— `info` at line 117 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/upload-to-qdrant.py:119— `error` at line 119 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 11-recommendation/pages/page_2_explainable_recommendations.py:45— `info` at line 45 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 05-4o_fine_tuning/data_validator.py:42— `info` at line 42 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 05-4o_fine_tuning/data_validator.py:61— `info` at line 61 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 05-4o_fine_tuning/data_validator.py:94— `info` at line 94 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 05-4o_fine_tuning/data_validator.py:99— `info` at line 99 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging 05-4o_fine_tuning/data_validator.py:141— `error` at line 141 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
redundant comment 09-realtime/realtime-from-scratch/app/hooks/useAudioPlayer.ts:121— "Create a Blob from the module code" repeats the code it sits on: 4 of its 4 words (create, blob, module, code) are already in `const blob = new Blob([moduleCode], { type: "application/javascript" });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 14-voice-agents/realtime-workspace-agents/src/app/App.tsx:417— "The remote audio stream from the audio element." repeats the code it sits on: 4 of its 4 words (remote, audio, stream, element) are already in `const remoteStream = audioElementRef.current.srcObject as MediaStream;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 14-voice-agents/realtime-workspace-agents/src/app/hooks/useAudioDownload.ts:7— "Ref to collect all recorded Blob chunks." repeats the code it sits on: 4 of its 5 words (ref, recorded, blob, chunks) are already in `const recordedChunksRef = useRef<Blob[]>([]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 14-voice-agents/realtime-workspace-agents/src/app/hooks/useAudioDownload.ts:80— "Request the current data." repeats the code it sits on: 3 of its 3 words (request, current, data) are already in `mediaRecorderRef.current.requestData();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 14-voice-agents/realtime-workspace-agents/src/app/hooks/useAudioDownload.ts:95— "Convert the WebM blob into a WAV blob." repeats the code it sits on: 4 of its 4 words (convert, web, blob, wav) are already in `const wavBlob = await convertWebMBlobToWav(webmBlob);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 14-voice-agents/realtime-workspace-agents/src/app/hooks/useHandleSessionHistory.ts:168— "find the last assistant message in details.context.history" repeats the code it sits on: 6 of its 7 words (last, assistant, message, details, context, history) are already in `const lastAssistant = extractLastAssistantMessage(details?.context?.history);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 16-built-in-tools/dashboard-demo-final/app/api/functions/get_joke/route.ts:3— "Fetch a programming joke" repeats the code it sits on: 3 of its 3 words (fetch, programming, joke) are already in `const jokeRes = await fetch("https://v2.jokeapi.dev/joke/Programming");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 16-built-in-tools/dashboard-demo-final/config/constants.ts:3— "Developer prompt for the assistant" repeats the code it sits on: 3 of its 3 words (developer, prompt, assistant) are already in `export const DEVELOPER_PROMPT = ``. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 16-built-in-tools/dashboard-demo-starting-point/app/api/functions/get_joke/route.ts:3— "Fetch a programming joke" repeats the code it sits on: 3 of its 3 words (fetch, programming, joke) are already in `const jokeRes = await fetch("https://v2.jokeapi.dev/joke/Programming");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 16-built-in-tools/dashboard-demo-starting-point/config/constants.ts:3— "Developer prompt for the assistant" repeats the code it sits on: 3 of its 3 words (developer, prompt, assistant) are already in `export const DEVELOPER_PROMPT = ``. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment 21-agentic-memory/components/ui/sidebar.tsx:85— "This sets the cookie to keep the sidebar state." repeats the code it sits on: 4 of its 5 words (sets, cookie, sidebar, state) are already in `document.cookie = `${SIDEBAR_COOKIE_NAME}=${openState}; path=/; max-age=${SIDEBAR_COOKIE_MAX_AGE}``. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
README/code drift 11-recommendation/README.md:19— 11-recommendation/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift 20-agent-rft/README.md:6— 20-agent-rft/README.md names Python 3.9 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.9. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift 21-agentic-memory/README.md:27— 21-agentic-memory/README.md names Python 3.10 or later, but 18-responses-api/openai-simulator/pyproject.toml:4 requires `requires-python = ">=3.11"` (the lowest of 2 declarations): the package does not install on Python 3.10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift 25-realtime-2/README.md:91— 25-realtime-2/README.md names React 19, but the manifest declares `react` ^18. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift 25-realtime-2/README.md:92— 25-realtime-2/README.md names Vite 7, but the manifest declares `vite` ^5.3.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Silent fallback default in catch REDACTED:19— `_load_cache` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch 21-agentic-memory/scripts/agent_service.py:384— `_estimate_tokens_from_text` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:446— `readJsonBody` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch 25-realtime-2/src/agent/supplyRealtimeDebugLog.ts:112— `readSupplyRealtimeDebugLog` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch 27-valuemaxxing/lib/frontier.ts:74— `validSourceUrl` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file 21-agentic-memory/scripts/agent_service.py:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file 25-realtime-2/src/App.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file 27-valuemaxxing/app/ValuemaxxingLab.tsx:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
X7 · Silent fallback defaults· Pending state with no failure state · ×3
Pending state with no failure state 26-agents-sdk/web/src/pages/board-page.tsx:161— The view draws `Loading board...` under `tasks . isLoading`, but `tasks` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state 06-structured_outputs/structured-outputs-math-tutor-starting-point/components/solution.tsx:52— The view draws `<div class="flex justify-center items-center h-full">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state 06-structured_outputs/structured-outputs-math-tutor-final/components/solution.tsx:52— The view draws `<div class="flex justify-center items-center h-full">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Silent fallback default on parse failure 15-reinforcement-fine-tuning/utils/upload_utils.py:24— `_load_cache` returns `{}` when `json.JSONDecodeError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure 20-agent-rft/utils_shared/file_upload.py:61— `_load_cache` returns `{}` when `json.JSONDecodeError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure 24-api-codex/skills/agentic-legibility/scripts/score_repo.py:120— `parse_package_scripts` returns `set()` when `json.JSONDecodeError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Fat interface: SupplyAgentContextValue (17 required operations) 25-realtime-2/src/agent/contracts.ts:206— `SupplyAgentContextValue` declares 17 required operations: `getHikingNeeds`, `getSavedProfile`, `getScreenState`, `searchProducts`, `applyFilters`, `highlightProducts`, `openProduct`, `selectQuantity`, `selectShoeSize`, `openSizeGuide`, `closeSizeGuide`, `addToCart`, `summarizeProductReviews`, `searchWeatherWeb`, `goToCart`, `goHome`, `clearFilters`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: MetricLoopAgentContextValue (16 required operations) 25-realtime-2/src/metricloop/metricLoopContracts.ts:326— `MetricLoopAgentContextValue` declares 16 required operations: `getDashboardState`, `openActivationFunnel`, `applySegmentFilter`, `applyFilter`, `openInsight`, `setBreakdown`, `switchVisualization`, `comparePeriods`, `checkReleaseNotes`, `clusterSupportTickets`, `openSessionReplays`, `openSessionReplay`, `generateInvestigationBoard`, `startRootCauseInvestigation`, `updateInvestigationNotebook`, `noOp`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion 25-realtime-2/package.json:1— `25-realtime-2` (14977 LoC, 156 module-visible types across 5 directories) overshoots its size bounds. 2 of 22 build unit(s) (Python, checkout, npm) overshoot their size bounds, lowering Project Cohesion to 8.2/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion REDACTED:1— `21-agentic-memory` (11321 LoC, 87 module-visible types across 12 directories) overshoots its size bounds. 2 of 22 build unit(s) (Python, checkout, npm) overshoot their size bounds, lowering Project Cohesion to 8.2/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: 25-realtime-2/src/agent/useSupplyRealtime.ts, 25-realtime-2/src/realtime/realtimeResponseController.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (5 single-owned of 250 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 250 of the 557 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: 06-structured_outputs/structured-outputs-math-tutor-starting-point/lib/useSolution.ts, 06-structured_outputs/structured-outputs-math-tutor-final/lib/useSolution.ts, 18-responses-api/openai-simulator/backend/server.py.
Concentrated knowledge decay — 245 of 250 significant files have no living knowledge, while the repository is still being changed at a low rate (1 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 245 separate risks. Counted over 250 of the 557 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
Disabled test 14-voice-agents/realtime-workspace-agents/src/app/agentConfigs/workspaceBuilder/__tests__/workspaceManagerAgent.integration.test.ts:14— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Thin README README.md:1— The root README is 68 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — 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.
Logging is not universal — Only 4/19 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `06-structured_outputs/structured-outputs-assistant-final`, `06-structured_outputs/structured-outputs-assistant-starting-point`, `06-structured_outputs/structured-outputs-math-tutor-final`, `06-structured_outputs/structured-outputs-math-tutor-starting-point`, `07-reasoning/shipmentPlanning/backend` and 10 more.
No SAST — 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.
No dependency-update automation 06-structured_outputs/node-example/package.json:13— `06-structured_outputs/node-example/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`.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 15/29 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.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 17/18 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~0.4 `!` null assertions per 1k TypeScript source lines — 22 assertion(s) across the 51715 source line(s) of the 323 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: 18-responses-api/openai-simulator/src/scenes/MainScene.ts (9), 26-agents-sdk/web/src/pages/board-page.tsx (5), 18-responses-api/openai-simulator/src/scenes/StartScene.ts (2). 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.
Outdated: aiohappyeyeballs — `aiohappyeyeballs` is pinned to 2.6.1, but 2.7.1 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 2.6.1 until the declaration is edited.
Outdated: aiohttp — `aiohttp` is pinned to 3.12.13, but 3.14.5 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 3.12.13 until the declaration is edited.
Outdated: aiosignal — `aiosignal` is pinned to 1.3.2, but 1.4.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.3.2 until the declaration is edited.
Outdated: altair — `altair` is pinned to 5.5.0, but 6.3.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 5.5.0 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: annotated-types — `annotated-types` is pinned to 0.7.0, but 0.8.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 0.7.0 until the declaration is edited.
Outdated: anyio — `anyio` is pinned to 4.6.0, but 4.16.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 4.6.0 until the declaration is edited.
Outdated: appnope — `appnope` is pinned to 0.1.4, but 1.0.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 0.1.4 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: argon2-cffi-bindings — `argon2-cffi-bindings` is pinned to 21.2.0, but 26.2.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 21.2.0 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: arrow — `arrow` is pinned to 1.3.0, but 1.4.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.3.0 until the declaration is edited.
Outdated: asttokens — `asttokens` is pinned to 3.0.0, but 3.0.2 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 3.0.0 until the declaration is edited.
Outdated: async-lru — `async-lru` is pinned to 2.0.5, but 2.4.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 2.0.5 until the declaration is edited.
Outdated: attrs — `attrs` is pinned to 24.2.0, but 26.1.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 24.2.0 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: babel — `babel` is pinned to 2.17.0, but 2.18.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 2.17.0 until the declaration is edited.
Outdated: beautifulsoup4 — `beautifulsoup4` is pinned to 4.13.4, but 4.15.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 4.13.4 until the declaration is edited.
Outdated: bleach — `bleach` is pinned to 6.2.0, but 6.4.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 6.2.0 until the declaration is edited.
Outdated: cachetools — `cachetools` is pinned to 5.5.0, but 8.0.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 5.5.0 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: certifi — `certifi` is pinned to 2024.8.30, but 2026.10.23 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 2024.8.30 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: cffi — `cffi` is pinned to 1.17.1, but 2.1.1 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.17.1 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: charset-normalizer — `charset-normalizer` is pinned to 3.4.0, but 3.5.2 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 3.4.0 until the declaration is edited.
Outdated: choreographer — `choreographer` is pinned to 1.0.9, but 1.4.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.0.9 until the declaration is edited.
Outdated: click — `click` is pinned to 8.1.7, but 8.5.1 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 8.1.7 until the declaration is edited.
Outdated: comm — `comm` is pinned to 0.2.2, but 0.2.3 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 0.2.2 until the declaration is edited.
Outdated: contourpy — `contourpy` is pinned to 1.3.2, but 1.4.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.3.2 until the declaration is edited.
Outdated: datasets — `datasets` is pinned to 3.6.0, but 5.2.0 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 3.6.0 until the declaration is edited. This crosses a major version, so it is a migration rather than a bump.
Outdated: debugpy — `debugpy` is pinned to 1.8.14, but 1.8.22 is the current stable release on PyPI. An exact pin never moves on its own, so this repository installs 1.8.14 until the declaration is edited.
doc comments repeat the names 09-realtime/openai-realtime-console-example/src/utils/wav_renderer.ts:68— 0 of 22 documented parameters and 0 of 55 summaries in `openai-realtime-console` only repeat the member or parameter name (e.g. "" for `canvas`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 13 file(s) — `09-realtime/realtime-from-scratch/tailwind.config.ts`, `REDACTED`, `14-voice-agents/realtime-workspace-agents/tailwind.config.ts`, `15-reinforcement-fine-tuning/projects/toy/pipelines/pipeline.py`, `15-reinforcement-fine-tuning/projects/toy/pipelines/rft_pipeline.py`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
Run 01a1e630-323a-75f6-9d57-cc2e35b7b909 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 435 · Warnings: 768 · Recommendations: 406 · Info: 138 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 21:08 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.