Public report of davila7/claude-code-templates, 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 report Measured 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, 05:52 UTC · Survey ID cd_e210a0a3e3414251ab96c9a3d419a6f9

davila7/claude-code-templates

Measured 16 November 2026, 05:50 UTC, at code version 1530598

CAI score 42out of 100 At risk No change since the last survey

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 large codebase: 176,310 lines of product code in 19 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Code Health, 28

Findings by how serious they are

198 critical 1660 serious 257 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 05:50 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 ▸

83of 83 dimensions measured by tools.
2098of 2115 findings point to an exact file and line, so you can open each one in the code. The other 17 concern the repository as a whole, such as missing documentation.
83dimensions across 7 lenses, read from 176,310 lines of product code in 19 projects.
Chapters

Executive summary

davila7/claude-code-templates is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 42 out of 100, which the At risk rating leaves unchanged.

Code Health, at 28, is the weakest lens and counts most in the score. The best first step is removing the unused code, worth about 5 points. Removing the copied code comes next, worth about 4 points. Raising Code Health to 70 would lift the score to about 53.

Sixty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-three known security holes in the packages the code depends on can be used by attackers, and twenty-six form fields can't be read by a screen reader. Pinning each tool to an exact version, updating the vulnerable packages and labelling the form fields would close these risks. Fixing the weaknesses the scanner points to would fix the six security weaknesses in the code, and the seven places where the code runs text as code or as a command need a direct call instead. The 25 controls that only work with a mouse need to work with the keyboard, or to become a real button.

The product code is 176,310 lines, about €160,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 for The 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.
Code Health 28 · counts for 46%Production Readiness 47 · counts for 25%Accessibility 47 · counts for 14%Performance 60 · counts for 8%Security and Compliance 74 · counts for 4%Architecture 94 · counts for 2%Maturity 94 · counts for 1%

If Code Health rose from 28 to 70, the lowest score rated Strong, the score would rise from 42 to about 53.

Code composition: what the lines of code are
Product code 93%Tests 7%
New since the last survey: 290 findings

These 290 critical or serious findings weren't in the previous survey, on 4 November 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · page-audit.auditDom (cyclomatic 49) cli-tool/components/skills/development/senior-frontend/scripts/page-audit.mjs
  • Cyclomatic Complexity · SkillReviewFlow.SkillReviewFlow (cyclomatic 48) dashboard/src/components/SkillReviewFlow.tsx
  • Cyclomatic Complexity · detect.reasonFor (cyclomatic 41) REDACTED
  • Cyclomatic Complexity · certifications.validateItem (cyclomatic 33) dashboard/src/lib/certifications.ts
  • Cyclomatic Complexity · rex-tty.register::pane (cyclomatic 31) cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts
  • Cyclomatic Complexity · check_docs.main (cyclomatic 27) docs-site/scripts/check_docs.py
  • Cyclomatic Complexity · index.installIndividualPlugin (cyclomatic 23) cli-tool/src/index.js
  • Cyclomatic Complexity · sign-in.showInAppDialog (cyclomatic 23) dashboard/src/lib/sign-in.ts
  • Cyclomatic Complexity · CertificationsView.CertificationsView (cyclomatic 20) dashboard/src/components/CertificationsView.tsx
  • Cyclomatic Complexity · pending-action.parsePendingAction (cyclomatic 18) dashboard/src/lib/pending-action.ts
  • Cyclomatic Complexity · component-content.filesFromContent (cyclomatic 17) cli-tool/src/component-content.js
  • Cyclomatic Complexity · detect.segments (cyclomatic 17) REDACTED
  • Cyclomatic Complexity · CertificationsView.FacetDropdown (cyclomatic 17) dashboard/src/components/CertificationsView.tsx
  • Cyclomatic Complexity · external-skill.downloadExternalSkill (cyclomatic 16) cli-tool/src/external-skill.js
  • Cyclomatic Complexity · index.downloadModFromGitHub::downloadDirectory (cyclomatic 16) cli-tool/src/index.js
  • Cyclomatic Complexity · stack-link.decodeStack (cyclomatic 16) dashboard/src/lib/stack-link.ts
  • Cognitive Complexity · page-audit.auditDom (cognitive 63) cli-tool/components/skills/development/senior-frontend/scripts/page-audit.mjs
  • Cognitive Complexity · SkillReviewFlow.SkillReviewFlow (cognitive 57) dashboard/src/components/SkillReviewFlow.tsx
  • Cognitive Complexity · check_docs.main (cognitive 52) docs-site/scripts/check_docs.py
  • Cognitive Complexity · detect.reasonFor (cognitive 39) REDACTED
  • Cognitive Complexity · certifications.validateItem (cognitive 32) dashboard/src/lib/certifications.ts
  • Cognitive Complexity · index.installIndividualPlugin (cognitive 31) cli-tool/src/index.js
  • Cognitive Complexity · rex-tty.register::pane (cognitive 31) cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts
  • Cognitive Complexity · stack-link.decodeStack (cognitive 25) dashboard/src/lib/stack-link.ts
  • Cognitive Complexity · external-skill.downloadExternalSkill (cognitive 23) cli-tool/src/external-skill.js
  • Cognitive Complexity · index.downloadModFromGitHub::downloadDirectory (cognitive 22) cli-tool/src/index.js
  • Cognitive Complexity · sign-in.showInAppDialog (cognitive 21) dashboard/src/lib/sign-in.ts
  • Cognitive Complexity · pending-action.parsePendingAction (cognitive 20) dashboard/src/lib/pending-action.ts
  • Cognitive Complexity · filesFromContent (cognitive 20) cli-tool/src/component-content.js
  • Cognitive Complexity · external-skill.findLegalFiles (cognitive 19) cli-tool/src/external-skill.js
  • Cognitive Complexity · catalog-lookup.resolveItems (cognitive 19) cli-tool/src/catalog-lookup.js
  • Cognitive Complexity · CertificationsView.CertificationsView (cognitive 19) dashboard/src/components/CertificationsView.tsx
  • Cognitive Complexity · security-headers.parseCspReports (cognitive 18) dashboard/src/lib/security-headers.ts
  • Cognitive Complexity · middleware.onRequest (cognitive 18) dashboard/src/middleware.ts
  • Cognitive Complexity · detect.segments (cognitive 16) REDACTED
  • Cognitive Complexity · detect.unwrap (cognitive 16) REDACTED
  • God Classes · FunctionTooLong: jev-auto-mode.register cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts
  • God Classes · FunctionTooLong: SkillReviewFlow.SkillReviewFlow dashboard/src/components/SkillReviewFlow.tsx
  • God Classes · FunctionTooLong: CertificationsView.CertificationsView dashboard/src/components/CertificationsView.tsx
  • God Classes · FileTooLong: pulse/index.js cloudflare-workers/pulse/index.js
  • Code Duplication · Edited copy of a member (31 corresponding lines) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py
  • Code Duplication · Edited copy of a member (35 corresponding lines) cli-tool/components/settings/statusline/context-monitor.py
  • Code Duplication · Members sharing a duplicated core (20 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py
  • Code Duplication · Members sharing a duplicated core (20 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py
  • Code Duplication · Members sharing a duplicated core (20 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py
  • Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py
  • Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) cli-tool/components/skills/scientific/string-database/scripts/string_api.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/convert_pdf_to_images.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/create_validation_image.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py
  • Code Duplication · Edited copy of a member (56 corresponding lines) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py
  • Code Duplication · Edited copy of a member (118 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py
  • Code Duplication · Edited copy of a member (109 corresponding lines) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py
  • Code Duplication · Edited copy of a member (52 corresponding lines) cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py
  • Code Duplication · Edited copy of a member (52 corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py
  • Code Duplication · Edited copy of a member (29 corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py
  • Code Duplication · Edited copy of a member (67 corresponding lines) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py
  • Code Duplication · Edited copy of a member (47 corresponding lines) cli-rust/src/commands/install.rs
  • Code Duplication · Edited copy of a member (52 corresponding lines) cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py
  • Code Duplication · Edited copy of a member (49 corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py
  • Code Duplication · Edited copy of a member (22 corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py
  • Code Duplication · Edited copy of a member (36 corresponding lines) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py
  • Code Duplication · Edited copy of a member (30 corresponding lines) cli-tool/components/skills/scientific/clinical-reports/scripts/check_deidentification.py
  • Code Duplication · Edited copy of a member (34 corresponding lines) cli-tool/components/skills/scientific/rdkit/scripts/molecular_properties.py
  • Code Duplication · Edited copy of a member (39 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py
  • Code Duplication · Edited copy of a member (25 corresponding lines) cli-tool/components/skills/scientific/clinical-reports/scripts/compliance_checker.py
  • Code Duplication · Edited copy of a member (15 corresponding lines) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py
  • Code Duplication · Edited copy of a member (19 corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py
  • Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py
  • Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py
  • Code Duplication · Edited copy of a member (17 corresponding lines) cli-tool/components/skills/media/speech/scripts/atlas_text_to_speech.py
  • Code Duplication · Edited copy of a member (19 corresponding lines) cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py
  • Code Duplication · Edited copy of a member (27 corresponding lines) cli-tool/components/skills/scientific/clinical-reports/scripts/extract_clinical_data.py
  • Code Duplication · Edited copy of a member (31 corresponding lines) cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py
  • Code Duplication · Edited copy of a member (20 corresponding lines) cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py
  • Code Duplication · Edited copy of a member (32 corresponding lines) cli-tool/components/skills/scientific/biorxiv-database/scripts/biorxiv_search.py
  • Code Duplication · Edited copy of a member (10 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py
  • Code Duplication · Edited copy of a member (20 corresponding lines) cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py
  • Code Duplication · Edited copy of a member (28 corresponding lines) cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py
  • Code Duplication · Edited copies of one member (3 members, 42+ corresponding lines) cli-tool/components/skills/scientific/pytorch-lightning/scripts/quick_trainer_setup.py
  • Code Duplication · Edited copy of a member (25 corresponding lines) REDACTED
  • Code Duplication · Edited copy of a member (20 corresponding lines) cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py
  • Code Duplication · Edited copy of a member (31 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py
  • Code Duplication · Edited copy of a member (11 corresponding lines) cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py
  • Code Duplication · Edited copy of a member (33 corresponding lines) cli-tool/components/skills/scientific/pytdc/scripts/benchmark_evaluation.py

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 1320 findings

These 1320 critical or serious findings were in the previous survey, on 4 November 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · generate_components_json.generate_components_json (cyclomatic 128) scripts/generate_components_json.py
  • Cyclomatic Complexity · generate_plugins_json.process_repo (cyclomatic 53) scripts/generate_plugins_json.py
  • Cyclomatic Complexity · generate_claude_jobs.parse_hn_comment (cyclomatic 36) scripts/generate_claude_jobs.py
  • Cyclomatic Complexity · validate_components.main (cyclomatic 35) scripts/validate_components.py
  • Cyclomatic Complexity · generate_plugins_json.extract_marketplace_plugins_detail (cyclomatic 31) scripts/generate_plugins_json.py
  • Cyclomatic Complexity · skillspector_scan.build_markdown (cyclomatic 31) scripts/skillspector_scan.py
  • Cyclomatic Complexity · generate_components_json.run_security_validation (cyclomatic 30) scripts/generate_components_json.py
  • Cyclomatic Complexity · generate_trending_data.process_downloads_data (cyclomatic 30) scripts/generate_trending_data.py
  • Cyclomatic Complexity · changelog-parser.classifyChange (cyclomatic 23) dashboard/src/lib/api/changelog-parser.ts
  • Cyclomatic Complexity · generate_claude_jobs.collect_anthropic_careers (cyclomatic 22) scripts/generate_claude_jobs.py
  • Cyclomatic Complexity · generate_plugins_json.extract_plugin_components (cyclomatic 21) scripts/generate_plugins_json.py
  • Cyclomatic Complexity · external_skills.validate_manifest (cyclomatic 20) scripts/external_skills.py
  • Cyclomatic Complexity · generate_plugins_json.scan_plugin_dir_components (cyclomatic 20) scripts/generate_plugins_json.py
  • Cyclomatic Complexity · generate_blog_images.main (cyclomatic 19) scripts/generate_blog_images.py
  • Cyclomatic Complexity · external_skills.local_dir (cyclomatic 18) scripts/external_skills.py
  • Cyclomatic Complexity · skillspector_catalog.attach_skillspector (cyclomatic 18) scripts/skillspector_catalog.py
  • Cyclomatic Complexity · skillspector_scan.main (cyclomatic 18) scripts/skillspector_scan.py
  • Cognitive Complexity · generate_components_json.generate_components_json (cognitive 448) scripts/generate_components_json.py
  • Cognitive Complexity · generate_components_json.run_security_validation (cognitive 153) scripts/generate_components_json.py
  • Cognitive Complexity · generate_plugins_json.process_repo (cognitive 76) scripts/generate_plugins_json.py
  • Cognitive Complexity · validate_components.main (cognitive 64) scripts/validate_components.py
  • Cognitive Complexity · generate_plugins_json.extract_marketplace_plugins_detail (cognitive 63) scripts/generate_plugins_json.py
  • Cognitive Complexity · generate_plugins_json.scan_plugin_dir_components (cognitive 56) scripts/generate_plugins_json.py
  • Cognitive Complexity · skillspector_scan.build_markdown (cognitive 52) scripts/skillspector_scan.py
  • Cognitive Complexity · generate_claude_jobs.parse_hn_comment (cognitive 45) scripts/generate_claude_jobs.py
  • Cognitive Complexity · generate_trending_data.process_downloads_data (cognitive 42) scripts/generate_trending_data.py
  • Cognitive Complexity · generate_claude_jobs.collect_anthropic_careers (cognitive 33) scripts/generate_claude_jobs.py
  • Cognitive Complexity · skillspector_catalog.attach_skillspector (cognitive 28) scripts/skillspector_catalog.py
  • Cognitive Complexity · generate_blog_images.main (cognitive 27) scripts/generate_blog_images.py
  • Cognitive Complexity · generate_plugins_json.extract_plugin_components (cognitive 27) scripts/generate_plugins_json.py
  • Cognitive Complexity · generate_blog_images.generate_blog_image (cognitive 25) scripts/generate_blog_images.py
  • Cognitive Complexity · skillspector_scan._aggregate_sarif (cognitive 25) scripts/skillspector_scan.py
  • Cognitive Complexity · external_skills.local_dir (cognitive 23) scripts/external_skills.py
  • Cognitive Complexity · generate_trending_data.fetch_with_retry (cognitive 23) scripts/generate_trending_data.py
  • Cognitive Complexity · generate_trending_data.main (cognitive 23) scripts/generate_trending_data.py
  • Cognitive Complexity · external_skills.check (cognitive 22) scripts/external_skills.py
  • Cognitive Complexity · generate_plugins_json.gh_api (cognitive 22) scripts/generate_plugins_json.py
  • Cognitive Complexity · skillspector_components_pr.to_components (cognitive 22) scripts/skillspector_components_pr.py
  • Cognitive Complexity · skillspector_scan.discover_changed_skills (cognitive 22) scripts/skillspector_scan.py
  • Cognitive Complexity · external_skills.validate_manifest (cognitive 21) scripts/external_skills.py
  • Cognitive Complexity · generate_claude_prs.fetch_prs (cognitive 20) scripts/generate_claude_prs.py
  • Cognitive Complexity · generate_components_json.fetch_download_stats (cognitive 20) scripts/generate_components_json.py
  • Cognitive Complexity · skillspector_scan.main (cognitive 20) scripts/skillspector_scan.py
  • Cognitive Complexity · index.installIndividualMod::downloadDirectory (cognitive 18) cli-tool/src/index.js
  • Cognitive Complexity · generate_claude_jobs.extract_salary (cognitive 17) scripts/generate_claude_jobs.py
  • Cognitive Complexity · generate_plugins_json.build_highlights (cognitive 16) scripts/generate_plugins_json.py
  • God Classes · FileTooLong: scripts/generate_components_json.py scripts/generate_components_json.py
  • God Classes · FunctionTooLong: claude-code-check.handleCheck dashboard/src/pages/api/claude-code-check.ts
  • God Classes · FileTooLong: scripts/generate_claude_jobs.py scripts/generate_claude_jobs.py
  • God Classes · FileTooLong: scripts/generate_trending_data.py scripts/generate_trending_data.py
  • God Classes · FileTooLong: scripts/generate_plugins_json.py scripts/generate_plugins_json.py
  • Code Duplication · Near-duplicate member family (5 members, 38 shared lines) cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py
  • Code Duplication · Near-duplicate member family (4 members, 16 shared lines) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py
  • Code Duplication · Near-duplicate member family (3 members, 174 shared lines) cli-tool/components/skills/development/skill-development/scripts/run_loop.py
  • Code Duplication · Near-duplicate member family (3 members, 41 shared lines) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py
  • Code Duplication · Edited copy of a member (31 corresponding lines) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py
  • Code Duplication · Edited copy of a member (35 corresponding lines) cli-tool/components/settings/statusline/context-monitor.py
  • Code Duplication · Members sharing a duplicated core (23 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py
  • Code Duplication · Members sharing a duplicated core (23 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py
  • Code Duplication · Members sharing a duplicated core (23 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py
  • Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py
  • Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) cli-tool/components/skills/scientific/string-database/scripts/string_api.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/convert_pdf_to_images.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/create_validation_image.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py
  • Code Duplication · Duplicated block (69 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_loop.py
  • Code Duplication · Duplicated block (57 lines × 2) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py
  • Code Duplication · Duplicated block (21–34 lines × 2) cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py
  • Code Duplication · Duplicated block (32 lines × 2) cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py
  • Code Duplication · Duplicated block (25 lines × 2) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py
  • Code Duplication · Duplicated block (25 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py
  • Code Duplication · Duplicated block (5–23 lines × 2) cli-tool/components/skills/scientific/clinical-decision-support/scripts/generate_survival_analysis.py
  • Code Duplication · Duplicated block (23 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py
  • Code Duplication · Duplicated block (23 lines × 2) cli-tool/components/skills/scientific/markitdown/scripts/batch_convert.py
  • Code Duplication · Duplicated block (20–22 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py
  • Code Duplication · Duplicated block (20–21 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py
  • Code Duplication · Duplicated block (19 lines × 3) cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py
  • Code Duplication · Duplicated block (19 lines × 3) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py
  • Code Duplication · Duplicated block (19 lines × 2) cli-tool/components/skills/scientific/market-research-reports/scripts/generate_market_visuals.py
  • Code Duplication · Duplicated block (17 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py
  • Code Duplication · Duplicated block (17 lines × 2) cli-tool/components/skills/scientific/opentrons-integration/scripts/pcr_setup_template.py
  • Code Duplication · Duplicated block (15–17 lines × 2) cli-tool/components/skills/scientific/pydicom/scripts/anonymize_dicom.py
  • Code Duplication · Duplicated block (15 lines × 2) cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py
  • Code Duplication · Duplicated block (15 lines × 2) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py
  • Code Duplication · Duplicated block (14 lines × 6) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py
  • Code Duplication · Duplicated block (13–14 lines × 2) cli-tool/components/skills/scientific/gget/scripts/gene_analysis.py
  • Code Duplication · Duplicated block (13 lines × 2) cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py
  • Code Duplication · Duplicated block (13 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/search_google_scholar.py
  • Code Duplication · Duplicated block (13 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€54,000 to €270,000, for 904 to 2,867 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problemStandard, 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 42. 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.
SizeLarge: 176,310 lines of product code
What it is notNot 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
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 5 points · Medium effort · Dead Code
2
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.
Raises the score by about 4 points · Medium effort · Code Duplication
3
Resolve the 1 Flaky test finding(s) in Test Reliability.
Raises the score by about 1 point · Low effort · Test Reliability

Diagnosis: what the measurements show together

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 €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Code Health, at 28 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. 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 5.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 16% on every change. The history of the code shows how much it changes: about 158,447 lines over the last 90 days, which is about 642,591 lines a year. At that pace, the extra work comes to an estimated 113.1 to 678.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.

776 modules, with 181 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; 736 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.
uses →1 claude_code_templates2 cli-tool.analytics-ui.src.components.SessionTimer3 cli-tool.components.mods.games.2048.hooks.boards.common4 cli-tool.components.mods.games.cc-arcade.hooks.boards.pet5 cli-tool.components.mods.games.cc-arcade.hooks.games.doom6 cli-tool.components.mods.games.cc-arcade.hooks.games.pet7 cli-tool.components.mods.games.chess.hooks.chess8 cli-tool.components.mods.games.chess.hooks.jev9 cli-tool.components.mods.productivity.jev-model-router.hooks.policy10 cli-tool.components.mods.productivity.ultra-config.hooks.profiles11 cli-tool.components.mods.security.jev-guardrails.hooks.policy12 cli-tool.components.mods.security.jev-vercel-sandbox.hooks.jev-vercel-sandbox13 cli-tool.src.validation.BaseValidator14 dashboard.src.components.SkillReviewFlow15 dashboard.src.lib.types16 cli-tool.analytics-ui.src.components17 cli-tool.components.mods.enterprise.policy-ceiling.hooks.ceiling18 cli-tool.components.mods.games.2048.hooks.boards19 cli-tool.components.mods.games.cc-arcade.hooks.boards20 cli-tool.components.mods.games.cc-arcade.hooks.games21 cli-tool.components.mods.games.chess.hooks22 cli-tool.components.mods.games.diff-invaders.hooks.boards23 cli-tool.components.mods.games.doom.hooks.boards24 cli-tool.components.mods.games.flappy.hooks.boards25 cli-tool.components.mods.games.invaders.hooks.boards26 cli-tool.components.mods.games.minesweeper.hooks.boards27 cli-tool.components.mods.games.pacman.hooks.boards28 cli-tool.components.mods.games.pet.hooks.boards29 cli-tool.components.mods.games.tool-defense.hooks.boards30 cli-tool.components.mods.productivity.jev-model-router.hooks31 cli-tool.components.mods.productivity.jev-skill-suggestion.hooks32 cli-tool.components.mods.productivity.jev-skill-typeahead.hooks33 cli-tool.components.mods.productivity.subagent-tuner.hooks34 cli-tool.components.mods.security.jev-auto-mode.hooks35 cli-tool.components.mods.security.jev-guardrails.hooks36 cli-tool.components.mods.security.jev-vercel-sandbox.hooks37 dashboard.src.components38 dashboard.src.lib.save-stack39 cli-tool.components.mods.enterprise.policy-ceiling.hooks40 dashboard.src.lib
1 claude_code_templates
2 cli-tool.analytics-ui.src.components.SessionTimer
3 cli-tool.components.mods.games.2048.hooks.boards.common
4 cli-tool.components.mods.games.cc-arcade.hooks.boards.pet
5 cli-tool.components.mods.games.cc-arcade.hooks.games.doom
6 cli-tool.components.mods.games.cc-arcade.hooks.games.pet
7 cli-tool.components.mods.games.chess.hooks.chess
8 cli-tool.components.mods.games.chess.hooks.jev
9 cli-tool.components.mods.productivity.jev-model-router.hooks.policy
10 cli-tool.components.mods.productivity.ultra-config.hooks.profiles
11 cli-tool.components.mods.security.jev-guardrails.hooks.policy
12 cli-tool.components.mods.security.jev-vercel-sandbox.hooks.jev-vercel-sandbox
13 cli-tool.src.validation.BaseValidator
14 dashboard.src.components.SkillReviewFlow
15 dashboard.src.lib.types
16 cli-tool.analytics-ui.src.components1
17 cli-tool.components.mods.enterprise.policy-ceiling.hooks.ceiling1
18 cli-tool.components.mods.games.2048.hooks.boards21
19 cli-tool.components.mods.games.cc-arcade.hooks.boards10110
20 cli-tool.components.mods.games.cc-arcade.hooks.games121
21 cli-tool.components.mods.games.chess.hooks323
22 cli-tool.components.mods.games.diff-invaders.hooks.boards11
23 cli-tool.components.mods.games.doom.hooks.boards21
24 cli-tool.components.mods.games.flappy.hooks.boards21
25 cli-tool.components.mods.games.invaders.hooks.boards21
26 cli-tool.components.mods.games.minesweeper.hooks.boards21
27 cli-tool.components.mods.games.pacman.hooks.boards21
28 cli-tool.components.mods.games.pet.hooks.boards11
29 cli-tool.components.mods.games.tool-defense.hooks.boards11
30 cli-tool.components.mods.productivity.jev-model-router.hooks131
31 cli-tool.components.mods.productivity.jev-skill-suggestion.hooks11
32 cli-tool.components.mods.productivity.jev-skill-typeahead.hooks11
33 cli-tool.components.mods.productivity.subagent-tuner.hooks13
34 cli-tool.components.mods.security.jev-auto-mode.hooks112
35 cli-tool.components.mods.security.jev-guardrails.hooks114
36 cli-tool.components.mods.security.jev-vercel-sandbox.hooks11
37 dashboard.src.components1011
38 dashboard.src.lib.save-stack3
39 cli-tool.components.mods.enterprise.policy-ceiling.hooks11
40 dashboard.src.lib22
Uses a module listed above itPart of a loopThe module itself
1 claude_code_templates2 cli-tool.analytics-ui.src.components.SessionTimer3 cli-tool.components.mods.games.2048.hooks.boards.common4 cli-tool.components.mods.games.cc-arcade.hooks.boards.pet5 cli-tool.components.mods.games.cc-arcade.hooks.games.doom6 cli-tool.components.mods.games.cc-arcade.hooks.games.pet7 cli-tool.components.mods.games.chess.hooks.chess8 cli-tool.components.mods.games.chess.hooks.jev9 cli-tool.components.mods.productivity.jev-model-router.hooks.policy10 cli-tool.components.mods.productivity.ultra-config.hooks.profiles11 cli-tool.components.mods.security.jev-guardrails.hooks.policy12 cli-tool.components.mods.security.jev-vercel-sandbox.hooks.jev-vercel-sandbox13 cli-tool.src.validation.BaseValidator14 dashboard.src.components.SkillReviewFlow15 dashboard.src.lib.types16 cli-tool.analytics-ui.src.components17 cli-tool.components.mods.enterprise.policy-ceiling.hooks.ceiling18 cli-tool.components.mods.games.2048.hooks.boards19 cli-tool.components.mods.games.cc-arcade.hooks.boards20 cli-tool.components.mods.games.cc-arcade.hooks.games21 cli-tool.components.mods.games.chess.hooks22 cli-tool.components.mods.games.diff-invaders.hooks.boards23 cli-tool.components.mods.games.doom.hooks.boards24 cli-tool.components.mods.games.flappy.hooks.boards25 cli-tool.components.mods.games.invaders.hooks.boards26 cli-tool.components.mods.games.minesweeper.hooks.boards27 cli-tool.components.mods.games.pacman.hooks.boards28 cli-tool.components.mods.games.pet.hooks.boards29 cli-tool.components.mods.games.tool-defense.hooks.boards30 cli-tool.components.mods.productivity.jev-model-router.hooks31 cli-tool.components.mods.productivity.jev-skill-suggestion.hooks32 cli-tool.components.mods.productivity.jev-skill-typeahead.hooks33 cli-tool.components.mods.productivity.subagent-tuner.hooks34 cli-tool.components.mods.security.jev-auto-mode.hooks35 cli-tool.components.mods.security.jev-guardrails.hooks36 cli-tool.components.mods.security.jev-vercel-sandbox.hooks37 dashboard.src.components38 dashboard.src.lib.save-stack39 cli-tool.components.mods.enterprise.policy-ceiling.hooks40 dashboard.src.libclaude_code_templates1cli-tool.analytics-ui.src.components.SessionTimer2cli-tool.components.mods.games.2048.hooks.boards.common3cli-tool.components.mods.games.cc-arcade.hooks.boards.pet4cli-tool.components.mods.games.cc-arcade.hooks.games.doom5cli-tool.components.mods.games.cc-arcade.hooks.games.pet6cli-tool.components.mods.games.chess.hooks.chess7cli-tool.components.mods.games.chess.hooks.jev8cli-tool.components.mods.productivity.jev-model-router.hooks.policy9cli-tool.components.mods.productivity.ultra-config.hooks.profiles10cli-tool.components.mods.security.jev-guardrails.hooks.policy11cli-tool.components.mods.security.jev-vercel-sandbox.hooks.jev-vercel-sandbox12cli-tool.src.validation.BaseValidator13dashboard.src.components.SkillReviewFlow14dashboard.src.lib.types15cli-tool.analytics-ui.src.components16cli-tool.components.mods.enterprise.policy-ceiling.hooks.ceiling17cli-tool.components.mods.games.2048.hooks.boards18cli-tool.components.mods.games.cc-arcade.hooks.boards19cli-tool.components.mods.games.cc-arcade.hooks.games20cli-tool.components.mods.games.chess.hooks21cli-tool.components.mods.games.diff-invaders.hooks.boards22cli-tool.components.mods.games.doom.hooks.boards23cli-tool.components.mods.games.flappy.hooks.boards24cli-tool.components.mods.games.invaders.hooks.boards25cli-tool.components.mods.games.minesweeper.hooks.boards26cli-tool.components.mods.games.pacman.hooks.boards27cli-tool.components.mods.games.pet.hooks.boards28cli-tool.components.mods.games.tool-defense.hooks.boards29cli-tool.components.mods.productivity.jev-model-router.hooks30cli-tool.components.mods.productivity.jev-skill-suggestion.hooks31cli-tool.components.mods.productivity.jev-skill-typeahead.hooks32cli-tool.components.mods.productivity.subagent-tuner.hooks33cli-tool.components.mods.security.jev-auto-mode.hooks34cli-tool.components.mods.security.jev-guardrails.hooks35cli-tool.components.mods.security.jev-vercel-sandbox.hooks36dashboard.src.components37dashboard.src.lib.save-stack38cli-tool.components.mods.enterprise.policy-ceiling.hooks39dashboard.src.lib40112110110121323112121212121111113111111311211411101131122+736 more modules (most-connected shown)

At a glance — Code Health · 28% · Weak · gated by D1, D2, R10, R7, X4 ·

At a glance — Architecture · 94% · Exemplary ·

At a glance — Maturity · 94% · Exemplary ·

At a glance — Readiness · 47% · Weak · gated by R4, P2, P7 ·

At a glance — Security · 74% · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 47% · Weak · gated by AC4, AC6 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection151High / Critical
A03:2025 — Software Supply Chain Failures64High / Critical
A02:2025 — Security Misconfiguration13High / Critical

Roadmap

Top priorities: Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; 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; Bring the 44 bodies over 60 down to 60 or less in Cognitive Complexity — start with MobileAuditor.audit_file (cognitive 208), build_ownership_map.build_ownership_map (cognitive 189), viewer.html.renderBenchmark (cognitive 181).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+4.7 ptsMediumDead Code
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.+3.9 ptsMediumCode Duplication
Resolve the 1 Flaky test finding(s) in Test Reliability.+1.5 ptsLowTest Reliability
Bring the 44 bodies over 60 down to 60 or less in Cognitive Complexity — start with MobileAuditor.audit_file (cognitive 208), build_ownership_map.build_ownership_map (cognitive 189), viewer.html.renderBenchmark (cognitive 181).+2.3 ptsHighCognitive Complexity
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.+2.0 ptsMediumAsync & latency hygiene
Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.+1.8 ptsMediumObservability
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+1.6 ptsMediumKeyboard semantics
Interpolated log message defeats structured logging+1.3 ptsMediumStructured logging

File quality

Per-file score 0–10 — a quality signature. Of 416 files carrying findings, judged against the Production bar: 4% slop · 65% mixed · 31% near-clean.

FileScoreBandWorst signal
REDACTED1.3SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.4SlopDependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED1.6SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopDependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.5SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED

How the grades work

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 — 198

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 — 1660

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 — 257

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 83 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 — 83 dimensions across the health lenses
D1D2D3D4D6D7D10D11D12D13D14D15D17D19D20D24D26D28D29D30D31D34D35D36D37D40D41D43D44AC1AC2AC3AC4AC5AC6AX10AX2AX3AX4AX6AX9M1M2M3M4P1P10P2P3P4P5P6P7P8PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X16X17X2X21X24X25X28X29X3X30X4X5

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
  1. 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, 2098 of 2115 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1e2e8-6762-78ea-8924-4041a312e25b.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

  • D5 Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .py, and our analyzer cannot run the .py test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 74.6% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test 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. The 1,238 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 18 test source file(s) (.py, .rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in cli-tool/.claude/sandbox/cloudflare/ was NOT MEASURED: the install for cli-tool/.claude/sandbox/cloudflare/ left no `vitest` binary under node_modules, so the suite could not be launched. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in cli-tool/components/sandbox/cloudflare/ was NOT MEASURED: the install for cli-tool/components/sandbox/cloudflare/ left no `vitest` binary under node_modules, so the suite could not be launched. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate 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.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (175 contributor(s) across 2134 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 174 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D28 Secrets (history) — 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. No commit of the history (2142 commits) was scanned. `gitleaks` TIMED OUT after 235.7s against a 235.7s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
  • 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. `cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx`, `cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx`, `cli-tool/components/mods/types/claude-code.d.ts`, `cli-tool/components/skills/creative-design/ui-design-system/scripts/design_token_generator.py`, `cli-tool/components/skills/development/typescript-expert/references/utility-types.ts`, … (+3 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.
  • AC2 Forms & labels — 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. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
  • 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. 210 further occurrence(s) are not listed individually; the score already reflects all 250.
  • 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.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala and Rust source only, and this repository's Java, Python, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Python, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P7 Outbound HTTP resilience — 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. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
  • 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. 288 further occurrence(s) are not listed individually; the score already reflects all 328.
  • 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. 291 further occurrence(s) are not listed individually; the score already reflects all 331.
  • R3 Large Files — 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
  • 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. 185 further occurrence(s) are not listed individually; the score already reflects all 225.
  • 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. 97 further occurrence(s) are not listed individually; the score already reflects all 137.
  • 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. 73 further occurrence(s) are not listed individually; the score already reflects all 113.
  • 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.
  • X2 Cancellation propagation — 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. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
  • 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.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 193 further occurrence(s) are not listed individually; the score already reflects all 233.
  • 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. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
  • X7 Silent fallback defaults — 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. 2 further occurrence(s) are not listed individually; the score already reflects all 42.

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.
  • 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.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
  • D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity3.1 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 3.1 / 10 · rule-coverage 100% · ceiling Prevented

330 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MobileAuditor.audit_file at 156.

MarkdownCopier.processElement (cyclomatic 18) · ×20dashboard/public/blog/function-hooks-claude-code/index.html:827
MarkdownCopier.processElement (cyclomatic 17) · ×14dashboard/public/blog/code-reviewer-agent/index.html:612
MarkdownCopier.processElement (cyclomatic 16) · ×6dashboard/public/blog/heygen-best-practices-skill/index.html:796
ChatsMobileApp.mergeMessages (cyclomatic 37) · ×2REDACTED:4739
ChatsMobileApp.handleNewMessage (cyclomatic 31) · ×2REDACTED:4454

+ 236 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with MobileAuditor.audit_file (cyclomatic 156), ChatsMobile.setupRoutes (cyclomatic 140). — 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 2 together lifts Cyclomatic Complexity from 3.1 to about 3.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Prevented

453 method(s) exceeded the cognitive complexity threshold of 15; the worst was MobileAuditor.audit_file at 208.

claude_code_templates::commands::install::install_multiple (cognitive 27) · ×5cli-rust/src/commands/install.rs:623
jev-vercel-sandbox.register::runJob (cognitive 22) · ×3cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:618
research_lookup.main (cognitive 55) · ×2cli-tool/components/skills/scientific/research-lookup/research_lookup.py:316
ChatsMobileApp.mergeMessages (cognitive 41) · ×2REDACTED:4739
ChatsMobileApp.handleNewMessage (cognitive 39) · ×2REDACTED:4454

+ 372 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 44 bodies over 60 down to 60 or less in Cognitive Complexity — start with MobileAuditor.audit_file (cognitive 208), build_ownership_map.build_ownership_map (cognitive 189), viewer.html.renderBenchmark (cognitive 181). — 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 44 together lifts Cognitive Complexity from 2.0 to about 4.0/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.

D3 · God Classes8.4 / 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.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Prevented

83 god class(es) detected.

FunctionTooLong: MyComponentsView.MyComponentsView · ×33dashboard/src/components/MyComponentsView.tsx:467
FileTooLong: REDACTED · ×26REDACTED
TooManyMethods: ChatsMobileApp · ×11REDACTED:2557
ClassTooLong: ClaudeAnalytics · ×9REDACTED:20
MethodTooLong: ChatsMobile.setupRoutes · ×4REDACTED:120

What to do

  1. Resolve the 33 FunctionTooLong finding(s) in God Classes — start with register.tsx (3), MyComponentsView.tsx (2), prompts.js (2). — One of this dimension's main actionable groups (33 warning-level).
  2. Resolve the 26 FileTooLong finding(s) in God Classes — start with REDACTED (2), index.js (2), script.js. — One of this dimension's main actionable groups (26 warning-level).
  3. Resolve the 11 TooManyMethods finding(s) in God Classes — start with REDACTED (2), WebSocketService.js (2), health-check.js. — One of this dimension's main actionable groups (11 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication6.8 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 100% · ceiling Verified

209 duplicated block group(s) detected. 8.1 % of the production lines (14,295 of 176,310) are in a reported copy. A further 87 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 6 of the 296 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .tsx, .ts (32% 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.

Duplicated block (11 lines × 2) · ×11cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:57
Duplicated block (6 lines × 2) · ×9cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py:221
Members sharing a duplicated core (5 members, 50+ identical tokens) · ×8cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py:16
Duplicated block (10 lines × 2) · ×7REDACTED:51
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:20

+ 182 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 11 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with image_gen.py (3), risk_calculator.py, generate_star_history.py. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with tree_operations.py (2), devops_utils.py, extract_metadata.py. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 8 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with fill_fillable_fields.py (3), extract_form_field_info.py (2), check_bounding_boxes.py. — One of this dimension's main actionable groups (8 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)8.9 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Verified

4 of 43 classes have LCOM4 above 3.

Low cohesion: ClaudeAnalytics (LCOM4 8) · ×4REDACTED:20

What to do

  1. Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED, trending.js, StateCalculator.js. — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Detailed fixes: d7_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

1 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1238 tests. Measured on the JavaScript/TypeScript suite only — at least 18 test source file(s) (.py, .rs) went unread, so its test quality is unmeasured and is not in these counts.

Skipped test: should validate real frontend-developer agent as safecli-tool/tests/validation/SemanticValidator.test.js:41
Mock-dominated test: should handle real-time data refresh · ×2cli-tool/tests/unit/DataService.test.js:221

What to do

  1. Resolve the 2 Mock-dominated test finding(s) in Test Quality — start with DataService.test.js (2). — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 Skipped test finding(s) in Test Quality — start with SemanticValidator.test.js. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D11 · Test Reliability8.0 / 10Adequategated by 1 critical finding✓ 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.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Verified

1 flaky across 2 measured tier(s). JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in the repository root (60 tests); jest via `npm ci --ignore-scripts` in cli-tool/ (264 tests); vitest via `npm ci --ignore-scripts` in cli-tool/.claude/sandbox/cloudflare/; vitest via `npm ci --ignore-scripts` in cli-tool/components/sandbox/cloudflare/; node:test via `npm ci --ignore-scripts` in dashboard/ (105 tests)): measured (1 flaky); Python (repository root, 16 test files): measured (0 flaky).

Flaky test: cli-tool/tests/integration/analytics-system.test.js::Analytics System Integration Backend Integration should cache data efficiently

What to do

  1. Resolve the 1 Flaky test finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d11_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene9.7 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

7 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.

Outdated: anyhow · ×7

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 203 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.8 / 10Stronggated by 33 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: scripts/generate_components_json.py (13×152=1976); cli-tool/src/index.js (14×93=1302); cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx (3×335=1005)

Hotspot: scripts/generate_components_json.py · ×33scripts/generate_components_json.py:568

What to do

  1. Resolve the 33 Hotspot finding(s) in Churn × Complexity Hotspots — start with register.tsx (5), generate_components_json.py, index.js. — One of this dimension's main actionable groups (33 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Stronggated by 18 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

29 deducted task-comment markers across 176310 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.

TodoComment · ×17cli-tool/components/skills/scientific/pytdc/scripts/benchmark_evaluation.py:70
TodoComment repeated across 12 filescli-tool/components/skills/enterprise-communication/risk-management-specialist/scripts/example.py:15

What to do

  1. Resolve the 17 TodoComment finding(s) in Explicit Debt — start with hierarchical_model_template.py (5), linear_regression_template.py (5), REDACTED (3). — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 1 TodoComment repeated across 12 files finding(s) in Explicit Debt — start with example.py. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 249 document(s) read across 14 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 3 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D24 · Comment Value5.1 5.1 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.1 / 10 · rule-coverage 99% · ceiling Documented

201 of 4132 judged comments only repeat the code they sit on (4.9 %). 56 comment(s) in another language or script were not judged.

redundant comment · ×84cli-tool/analytics-ui/public/services/DataService.js:278
doc comments repeat the names · ×5cli-tool/analytics-ui/public/services/DataService.js:29

What to do

  1. Resolve the 84 redundant comment finding(s) in Comment Value — start with blog-loader.js (8), DataService.js (4), index.js (4). — One of this dimension's main actionable groups (84 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion6.8 / 10Adequate✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 100% · ceiling Documented

3 of 19 build units (Cargo, Python, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×3cli-tool/package.json:1

What to do

  1. Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json (3). — One of this dimension's main actionable groups (3 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the current working tree and the part of the history named below, and found no secrets. History coverage: No commit of the history (2142 commits) was scanned. `gitleaks` TIMED OUT after 235.7s against a 235.7s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

151 finding(s): 0 critical, 90 high, 58 medium, 3 low. 64 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 56 file(s) — `REDACTED` (line 2367), `cli-tool/components/hooks/quality-gates/tdd-gate.sh` (lines 43–55, line 122, line 135, …), `cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx` (line 63, line 68), `cli-tool/components/mods/productivity/subagent-tuner/hooks/stack-band.test.ts` (line 193), `cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx` (line 72, line 78), … (+51 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. Separately, one or more rules could not re-parse an embedded snippet in 12 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 22 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  3. No action in Static Analysis (SAST) — all 64 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (64 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

60 finding(s): 4 critical, 29 high, 20 medium, 7 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 4 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 29 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (28), REDACTED. — One of this dimension's main actionable groups (29 issue-level).
  2. Resolve the 2 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security8.5 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Documented

13 finding(s): 0 critical, 1 high, 11 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (4). — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.9 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

6 of 702 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py. Counted over 702 of the 1158 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×6cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D40 · Network Egress Confinement10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Kubernetes workloads are covered by a network policy that restricts egress.

✓ On the Gold path — maintain.

Detailed fixes: d40_recommendation.md.

D41 · Kernel & Syscall Confinement8.0 / 10Strong✓ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Documented

1/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.

Detailed fixes: d41_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 25 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.

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.

  • 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:419
  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×4) — cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:173, cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:181, cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:189, …

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.
AC2 · Forms & labels5.4 / 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 for>, a wrapping <label>, or aria-label. (×13) — REDACTED:2063, REDACTED:2114, REDACTED:2129, …
  • This <label> has no for 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 for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×14) — REDACTED:2110, REDACTED:2124, REDACTED:2161, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×13) — REDACTED:2168, REDACTED:2176, cli-tool/components/hooks/automation/plan-mode-game/index.html:472, …

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure7.4 / 10Strong✓ Tool-verified

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>. (×15) — REDACTED:2, cli-tool/analytics-ui/src/layouts/Base.astro:8, cli-tool/components/hooks/automation/plan-mode-game/index.html:2, …
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×4) — REDACTED:2099, cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:341, REDACTED:2099, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:2, dashboard/src/pages/github-callback.astro:5

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics2.8 / 10Weak✓ Tool-verified

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) — REDACTED:2262, REDACTED:2262, docs/js/component-page.js:352, …
  • A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — cli-tool/components/hooks/automation/plan-mode-game/index.html:415, cli-tool/components/hooks/automation/plan-mode-game/index.html:416, cli-tool/components/hooks/automation/plan-mode-game/index.html:417
  • This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, 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. (×2) — dashboard/src/components/CertificationModal.tsx:95, dashboard/src/components/StackHarness.astro:237
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×4) — dashboard/src/components/ComponentGrid.tsx:609, dashboard/src/components/ComponentGrid.tsx:705, dashboard/src/components/JsonViewer.tsx:143, …
  • This <span> carries its own click handler, but it sits inside a <a> that performs a different action. A keyboard user reaches the <a> and activating it runs the <a>'s handler, never this one, so this action has no keyboard path at all. Role and tabindex cannot supply one: HTML forbids a <a> from containing interactive content or any descendant with a tabindex, so the browser will not put this element in the tab order however it is marked up. Move it out of the <a> and make it a sibling <button>, so each action has its own control. — dashboard/src/components/JobsView.tsx:649
  • 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}. — dashboard/src/components/SearchModal.tsx:233
  • The repo's own CSS styles .template-card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — docs/js/index-events.js:593, docs/js/index-events.js:1048
  • The repo's own CSS styles .tree-node-header with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — docs/js/workflows-events.js:126, docs/js/workflows.js:147
  • The repo's own CSS styles .sub-item-drop-zone with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — docs/js/workflows-events.js:385
  • The repo's own CSS styles .tree-file with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — docs/js/workflows-events.js:145, docs/js/workflows.js:167

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety3.6 / 10Weak✓ Tool-verified

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.

  • `.search-panel` moves (`animation: slideDown 0.3s 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. — REDACTED:219
  • `.folder-browser-dropdown.active` moves (`animation: slideDown 0.2s 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. — REDACTED:502
  • `.chat-search-bar` moves (`animation: slideDown 0.2s 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. — REDACTED:602
  • `.project-toggle` moves (`transition: transform 0.2s 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. — REDACTED:936
  • `.toggle-icon` moves (`transition: transform 0.2s 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. — REDACTED:940
  • `.chat-view` moves (`transition: left 0.3s 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. — REDACTED:1469
  • `.loading-spinner` moves (`animation: spin 1s linear 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. — REDACTED:1626
  • `.status-dot.working` moves (`animation: pulse 2s 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. — REDACTED:1678
  • `.modal` moves (`animation: modalSlideIn 0.3s 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. — REDACTED:1776
  • `.analytics-wait-bar` moves (`transition: width 0.3s 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. — REDACTED:2007
  • `.analytics-user-bar` moves (`transition: width 0.3s 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. — REDACTED:2012
  • `.search-btn-primary` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:349
  • `.advanced-search-toggle:hover` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:393
  • `.folder-browser-toggle` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:464
  • `.folder-item.selected` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:551
  • `.message-highlight` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:690
  • `.message-current-highlight` sets color: white on background-color: #ffaa00 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:698
  • `.retry-messages` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:1442
  • <div> moves — its inline style sets `transition: width 0.4s ease` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — cli-tool/analytics-ui/src/components/BarList.tsx:99
  • `.activity-item` moves (`animation: slideIn 0.2s 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:142
  • `.announcement` moves (`animation: slideUp 0.6s cubic-bezier(0.16,1,0.3,1)`) 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:167
  • `.confetti` moves (`animation: confettiFall linear forwards`) 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:178
  • `.pause-modal` moves (`animation: pauseBounce 0.5s cubic-bezier(0.16,1,0.3,1)`) 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:191
  • `.share-btn` moves (`transition: background 0.2s, transform 0.1s`) 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:330
  • `.share-inner` moves (`animation: slideUp 0.4s cubic-bezier(0.16,1,0.3,1)`) 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. — cli-tool/components/hooks/automation/plan-mode-game/index.html:354
  • `.tab` sets color: #4b5563 on background-color: #12121f — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/hooks/automation/plan-mode-game/index.html:49
  • `.task-type` sets color: #718096 on background-color: #FFFFFF — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/ai-research/loki-mode/autonomy/.loki/dashboard/index.html:257
  • `.slider-container input[type="range"]` 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. — cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:163
  • `.button` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:235
  • `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — cli-tool/components/skills/development/skill-creator/assets/eval_review.html:17, cli-tool/components/skills/development/skill-development/assets/eval_review.html:17
  • `.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/assets/eval_review.html:19
  • `.grades-toggle .arrow` moves (`transition: transform 0.15s`) 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. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:275
  • `.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:83
  • `.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:136
  • `.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:197
  • `.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:221
  • `.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:302
  • `.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:303
  • `.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:467

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.
AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

M1 · Documentation (README)9.1 / 10Exemplary✓ Tool-verified

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.

M2 · Architecture documentation10.0 / 10Exemplary✓ Tool-verified

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.

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

M4 · Documentation accuracy9.0 / 10Exemplary✓ Tool-verified

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.

  • cli-tool/components/skills/creative-design/marp-slide/README.md links to `image.png`, but `cli-tool/components/skills/creative-design/marp-slide/image.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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. — cli-tool/components/skills/creative-design/marp-slide/README.md:58
  • cli-tool/components/skills/development/react-dev/README.md names React 18, but the manifest declares `react` ^19.2.4. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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. — cli-tool/components/skills/development/react-dev/README.md:48
  • cli-tool/components/skills/development/react-useeffect/README.md names React 18, but the manifest declares `react` ^19.2.4. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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. — cli-tool/components/skills/development/react-useeffect/README.md:299
  • cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/README.md links to `papers.md`, but `cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/papers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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. — cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/README.md:9
  • cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/README.md links to `papers.md`, but `cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/papers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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. — cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/README.md:9

What to do

  • Reconcile the README with reality: cli-tool/components/skills/creative-design/marp-slide/README.md links to `image.png`, but `cli-tool/components/skills/creative-design/marp-slide/image.png` does not exist; cli-tool/components/skills/development/react-dev/README.md names React 18, but the manifest declares `react` ^19.2.4; cli-tool/components/skills/development/react-useeffect/README.md names React 18, but the manifest declares `react` ^19.2.4; cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/README.md links to `papers.md`, but `cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/papers.md` does not exist; cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/README.md links to `papers.md`, but `cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/papers.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

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.

P2 · Observability1.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging call was found in the 257 JVM, Python, JavaScript/TypeScript, Rust production file(s) this check read across 18 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; Rust: the log and tracing crates (info!/warn!/error!, #[instrument]), slog, env_logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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.

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `cargo`, `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2

What to do

  • Dependabot is configured but does not watch `cargo`, `pip` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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.

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P5 · DR & Backup10.0 / 10Exemplary✓ 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.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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.

  • `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/vercel.ts:252
  • `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×12) — cli-tool/components/skills/scientific/clinicaltrials-database/scripts/query_clinicaltrials.py:87, cli-tool/components/skills/scientific/clinicaltrials-database/scripts/query_clinicaltrials.py:110, cli-tool/components/skills/scientific/clinpgx-database/scripts/query_clinpgx.py:36, …
  • `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×23) — cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:78, cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:131, cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:75, …
  • `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — cli-tool/components/skills/scientific/generate-image/scripts/generate_image.py:144, cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:172, cli-tool/components/skills/scientific/pubchem-database/scripts/bioactivity_query.py:46, …

What to do

  • Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
  • Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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.

  • `fs.statSync` in `handleFileActivity` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — cli-tool/src/analytics/core/FileWatcher.js:163
  • `fs.existsSync` in `getAvailableAgentsFromGitHub` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — cli-tool/src/index.js:1293
  • `fs.readFileSync` in `getAvailableAgentsFromGitHub` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — cli-tool/src/index.js:1294
  • `fs.existsSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:50
  • `execSync` in `extractGitMetadata` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — REDACTED:155, REDACTED:165, REDACTED:171, …
  • `fs.existsSync` in `generateProvenanceReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:304
  • `fs.readFileSync` in `fetchComponents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/src/lib/data.ts:24
  • `fs.readFileSync` in `fetchComponentsByType` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/src/lib/data.ts:111
  • `fs.readFileSync` in `fetchSearchIndex` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/src/lib/data.ts:153
  • `fs.readFileSync` in `fetchComponentContentData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/src/lib/data.ts:240

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety7.3 / 10Strong✓ 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.

R10 · Code Duplication0.7 / 10Critical✓ Tool-verified

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.

  • cli-tool/components/skills/creative-design/remotion-best-practices/rules/ and cli-tool/components/skills/video/remotion/references/ are near-verbatim copies of each other: 30 files are byte-identical under the same relative paths (~2909 lines; the trees hold 31 and 31 files). That is one structural fact, not 30 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. — cli-tool/components/skills/creative-design/remotion-best-practices/rules/extract-frames.md:1
  • 45 duplicated blocks under cli-tool/components/mods/ have copies in at least two of the sibling directories enterprise, games, integrations, observability, productivity, security (+1 more sibling(s) not listed) — 42 of them are reported below, and 3 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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. — cli-tool/components/mods/games/chess/hooks/jev.ts:18
  • 45 of the duplicated blocks reported below have copies in at least two of the sibling directories 2048, cc-arcade, diff-invaders, doom, flappy, invaders (+7 more sibling(s) not listed) under cli-tool/components/mods/games/. That concentration is one structural fact, not 45 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 45 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. — cli-tool/components/mods/games/cc-arcade/hooks/games/doom.ts:14
  • 12 duplicated blocks under cli-tool/components/mods/integrations/ have copies in at least two of the sibling directories bluesky-feed, linear-tickets, neon-branch-per-session, vercel-deploys — 10 of them are reported below, and 2 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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. — cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:65
  • 9 duplicated blocks under cli-tool/components/mods/ui/ have copies in at least two of the sibling directories agent-flow, git-sidebar, live-preview, stack-viewer, turn-inspector — 8 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:83
  • 8 of the duplicated blocks reported below have copies in at least two of the sibling directories block-destructive-commands, jev-auto-mode, jev-guardrails, jev-vercel-sandbox, large-edit-confirmation, protected-paths-guard (+1 more sibling(s) not listed) under cli-tool/components/mods/security/. That concentration is one structural fact, not 8 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 8 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. — cli-tool/components/mods/security/jev-auto-mode/hooks/judge.ts:20
  • 5 of the duplicated blocks reported below have copies in at least two of the sibling directories analytics-ui, src under cli-tool/. That concentration is one structural fact, not 5 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 5 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. — cli-tool/analytics-ui/public/services/WebSocketService.js:5
  • 5 of the duplicated blocks reported below have copies in at least two of the sibling directories aitmpl, jev-model-router, jev-skill-suggestion, jev-skill-typeahead, session-chats, ultra-config under cli-tool/components/mods/productivity/. That concentration is one structural fact, not 5 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 5 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. — cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts:66
  • 5 of the duplicated blocks reported below have copies in at least two of the sibling directories creative-design, development, document-processing, productivity, scientific, video under cli-tool/components/skills/. That concentration is one structural fact, not 5 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 5 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. — cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:28
  • cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:28 · cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js:28 — these 2 files are line-for-line copies of one another — 602 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. — cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:28
  • cli-tool/components/mods/games/cc-arcade/hooks/games/doom.ts:14 · cli-tool/components/mods/games/doom/hooks/games/doom.ts:14 — these 2 files are line-for-line copies of one another — 248 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. — cli-tool/components/mods/games/cc-arcade/hooks/games/doom.ts:14
  • cli-tool/analytics-ui/public/services/WebSocketService.js:5 · cli-tool/src/analytics-web/services/WebSocketService.js:5 — these 2 files are line-for-line copies of one another — 246 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. — cli-tool/analytics-ui/public/services/WebSocketService.js:5
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/doom.tsx:2 · cli-tool/components/mods/games/doom/hooks/boards/doom.tsx:2 — these 2 files are line-for-line copies of one another — 214 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/doom.tsx:2
  • cli-tool/analytics-ui/public/services/DataService.js:5 · cli-tool/src/analytics-web/services/DataService.js:5 — these 2 files are line-for-line copies of one another — 186 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. — cli-tool/analytics-ui/public/services/DataService.js:5
  • cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/charts-bar-chart.tsx:1 · cli-tool/components/skills/video/remotion/references/assets/charts/bar-chart.tsx:1 — these 2 files are line-for-line copies of one another — 116 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. — cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/charts-bar-chart.tsx:1
  • cli-tool/analytics-ui/public/services/StateService.js:5 · cli-tool/src/analytics-web/services/StateService.js:5 — these 2 files are line-for-line copies of one another — 101 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. — cli-tool/analytics-ui/public/services/StateService.js:5
  • cli-tool/src/index.js:576 · cli-tool/src/index.js:955 — the two spans are one implementation copied and then locally edited — 671 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cli-tool/src/index.js:576
  • cli-tool/components/skills/development/writing-skills/render-graphs.js:16 · cli-tool/components/skills/productivity/writing-skills/render-graphs.js:16 — these 2 files are line-for-line copies of one another — 96 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. — cli-tool/components/skills/development/writing-skills/render-graphs.js:16
  • cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:83 · cli-tool/components/mods/ui/git-sidebar/hooks/git-sidebar.tsx:99 — the two spans are one implementation copied and then locally edited — 682 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. — cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:83
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/minesweeper.tsx:2 · cli-tool/components/mods/games/minesweeper/hooks/boards/minesweeper.tsx:2 — these 2 files are line-for-line copies of one another — 74 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/minesweeper.tsx:2
  • REDACTED:333 · cli-tool/src/analytics/core/ConversationAnalyzer.js:626 — 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:333
  • REDACTED:447 · cli-tool/src/analytics/core/ConversationAnalyzer.js:779 — 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:447
  • REDACTED:627 · REDACTED:1036 — the two spans are one implementation copied and then locally edited — 402 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:627
  • cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-word-highlight.tsx:1 · cli-tool/components/skills/video/remotion/references/assets/text-animations-word-highlight.tsx:1 — 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. — cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-word-highlight.tsx:1
  • cloudflare-workers/crons/sentry.js:15 · cloudflare-workers/docs-monitor/sentry.js:15 · cloudflare-workers/newsletter/sentry.js:15 · cloudflare-workers/pulse/sentry.js:15 — these 4 files are line-for-line copies of one another — 64 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. — cloudflare-workers/crons/sentry.js:15
  • cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-typewriter.tsx:6 · cli-tool/components/skills/video/remotion/references/assets/text-animations-typewriter.tsx:6 — 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. — cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-typewriter.tsx:6
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/invaders.tsx:2 · cli-tool/components/mods/games/invaders/hooks/boards/invaders.tsx:2 — 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/invaders.tsx:2
  • cli-tool/components/mods/games/cc-arcade/hooks/games/tetris.ts:3 · cli-tool/components/mods/games/tetris/hooks/games/tetris.ts:3 — 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. — cli-tool/components/mods/games/cc-arcade/hooks/games/tetris.ts:3
  • cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:65 · cli-tool/components/mods/integrations/linear-tickets/hooks/linear-tickets.tsx:73 — the two spans are one implementation copied and then locally edited — 449 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. — cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:65
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/pong.tsx:2 · cli-tool/components/mods/games/pong/hooks/boards/pong.tsx:2 — these 2 files are line-for-line copies of one another — 59 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/pong.tsx:2
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/flappy.tsx:2 · cli-tool/components/mods/games/flappy/hooks/boards/flappy.tsx:2 — these 2 files are line-for-line copies of one another — 57 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/flappy.tsx:2
  • cli-tool/components/skills/creative-design/claude-d3js-skill/assets/chart-template.jsx:5 · cli-tool/components/skills/creative-design/claude-d3js-skill/assets/interactive-template.jsx:7 — the two spans are one implementation copied and then locally edited — 422 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. — cli-tool/components/skills/creative-design/claude-d3js-skill/assets/chart-template.jsx:5
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/tetris.tsx:2 · cli-tool/components/mods/games/tetris/hooks/boards/tetris.tsx:2 — 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/tetris.tsx:2
  • cli-tool/src/analytics/core/ConversationAnalyzer.js:267 · cli-tool/src/analytics/data/DataCache.js:134 — the two spans are one implementation copied and then locally edited — 426 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. — cli-tool/src/analytics/core/ConversationAnalyzer.js:267
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/snake.tsx:8 · cli-tool/components/mods/games/snake/hooks/boards/snake.tsx:8 — 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/snake.tsx:8
  • cli-tool/src/analytics/core/SessionAnalyzer.js:173 · cli-tool/src/analytics/core/SessionAnalyzer.js:305 — the two spans are one implementation copied and then locally edited — 401 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — cli-tool/src/analytics/core/SessionAnalyzer.js:173
  • cli-tool/components/mods/games/2048/hooks/register.tsx:12 · cli-tool/components/mods/games/flappy/hooks/register.tsx:12 · cli-tool/components/mods/games/invaders/hooks/register.tsx:12 · cli-tool/components/mods/games/pong/hooks/register.tsx:12 · +2 more site(s) not listed — the 6 copies are spread across 6 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. — cli-tool/components/mods/games/2048/hooks/register.tsx:12
  • cli-tool/components/mods/games/cc-arcade/hooks/boards/pet.tsx:2 · cli-tool/components/mods/games/pet/hooks/boards/pet.tsx:2 — these 2 files are line-for-line copies of one another — 52 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. — cli-tool/components/mods/games/cc-arcade/hooks/boards/pet.tsx:2
  • cli-tool/components/mods/games/2048/hooks/boards/twenty48.tsx:10 · cli-tool/components/mods/games/cc-arcade/hooks/boards/twenty48.tsx:10 — 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. — cli-tool/components/mods/games/2048/hooks/boards/twenty48.tsx:10
  • dashboard/src/components/JsonViewer.tsx:124 · dashboard/src/components/JsonViewer.tsx:197 — 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. — dashboard/src/components/JsonViewer.tsx:124

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries9.7 / 10Exemplary✓ Tool-verified

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.

  • dashboard/tests/download-client-signals.test.ts:11 reaches past another workspace package's public entry into its internals with a relative path (../../cli-tool/src/agent-detection.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — dashboard/tests/download-client-signals.test.ts:11

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity4.0 / 10Weak✓ Tool-verified

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.

  • createClaudeConfig has cyclomatic complexity 93 and cognitive complexity 76; 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. — cli-tool/src/index.js:86
  • Doom has cyclomatic complexity 76 and cognitive complexity 136; 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) — cli-tool/components/mods/games/cc-arcade/hooks/boards/doom.tsx:110, cli-tool/components/mods/games/doom/hooks/boards/doom.tsx:110
  • (anonymous) has cyclomatic complexity 76 and cognitive complexity 128; 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) — cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:534, cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js:534
  • getHookDescription has cyclomatic complexity 74 and cognitive complexity 71; 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. — cli-tool/src/hook-scanner.js:110
  • installIndividualSetting has cyclomatic complexity 59 and cognitive complexity 103; 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. — cli-tool/src/index.js:553
  • (anonymous) has cyclomatic complexity 59 and cognitive complexity 84; 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. — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:248
  • pseudoMoves has cyclomatic complexity 49 and cognitive complexity 97; 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. — cli-tool/components/mods/games/chess/hooks/chess.ts:147
  • (anonymous) has cyclomatic complexity 49 and cognitive complexity 68; 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. — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:1100
  • apply has cyclomatic complexity 48 and cognitive complexity 91; 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. — cli-tool/components/mods/enterprise/policy-ceiling/hooks/ceiling.ts:85
  • scanFiles has cyclomatic complexity 48 and cognitive complexity 88; 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. — cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:251
  • copyTemplateFiles has cyclomatic complexity 45 and cognitive complexity 98; 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. — cli-tool/src/file-operations.js:373
  • parseAndCorrelateToolMessages has cyclomatic complexity 45 and cognitive complexity 85; 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. — cli-tool/src/analytics/data/DataCache.js:142
  • (anonymous) has cyclomatic complexity 45 and cognitive complexity 43; 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:520
  • (anonymous) has cyclomatic complexity 43 and cognitive complexity 83; 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. — cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:187
  • (anonymous) has cyclomatic complexity 42 and cognitive complexity 51; 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. — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:992
  • getStepConfig has cyclomatic complexity 42 and cognitive complexity 49; 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. — cli-tool/src/prompts.js:79
  • reasonFor has cyclomatic complexity 42 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 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:177
  • installIndividualHook has cyclomatic complexity 41 and cognitive complexity 69; 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. — cli-tool/src/index.js:933
  • ruleMatches has cyclomatic complexity 39 and cognitive complexity 49; 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:635
  • validateRequest has cyclomatic complexity 38 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. — cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/ollama-adapter.mjs:58
  • gateFor has cyclomatic complexity 36 and cognitive complexity 97; 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:268
  • SkillExplorer has cyclomatic complexity 36 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 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:144
  • detectProject has cyclomatic complexity 35 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. — cli-tool/src/utils.js:4
  • pane has cyclomatic complexity 35 and cognitive complexity 41; 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. — cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts:134
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 67; 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. — cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts:278
  • pump has cyclomatic complexity 34 and cognitive complexity 56; 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. — cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts:440
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 56; 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) — cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:422, cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js:422
  • auditDom has cyclomatic complexity 34 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — cli-tool/components/skills/development/senior-frontend/scripts/page-audit.mjs:5
  • (anonymous) has cyclomatic complexity 34 and cognitive complexity 45; 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:24
  • (anonymous) has cyclomatic complexity 33 and cognitive complexity 51; 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. — cli-tool/components/mods/ui/git-sidebar/hooks/git-sidebar.tsx:186
  • bashParts has cyclomatic complexity 33 and cognitive complexity 49; 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:407
  • (anonymous) has cyclomatic complexity 33 and cognitive complexity 47; 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. — cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts:173
  • installMultipleComponents has cyclomatic complexity 33 and cognitive complexity 41; 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. — cli-tool/src/index.js:1979
  • (anonymous) has cyclomatic complexity 33 and cognitive complexity 36; 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. — dashboard/src/components/ComponentGrid.tsx:602
  • ComponentGrid has cyclomatic complexity 33 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 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. — dashboard/src/components/ComponentGrid.tsx:41
  • parseAndCorrelateToolMessages has cyclomatic complexity 32 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. — cli-tool/src/analytics/core/ConversationAnalyzer.js:275
  • main has cyclomatic complexity 32 and cognitive complexity 33; 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. — cli-tool/components/skills/design-to-code/scripts/coderio-skill.mjs:100
R3 · Large Files4.5 / 10Weak✓ 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.

  • cli-tool/src/index.js has 2425 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/index.js:1
  • REDACTED has 1742 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
  • cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx has 1285 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:1
  • cli-tool/src/health-check.js has 1244 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/health-check.js:1
  • dashboard/src/components/MyComponentsView.tsx has 1036 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/MyComponentsView.tsx:1
  • REDACTED has 1024 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
  • cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts has 886 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:1
  • cli-tool/src/analytics/core/ConversationAnalyzer.js has 875 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/analytics/core/ConversationAnalyzer.js:1
  • cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts has 866 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts:1
  • dashboard/src/components/ComponentGrid.tsx has 838 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/ComponentGrid.tsx:1
  • REDACTED has 741 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
  • cloudflare-workers/pulse/index.js has 679 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cloudflare-workers/pulse/index.js:1
  • dashboard/src/components/JobsView.tsx has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/JobsView.tsx:1
  • cli-tool/src/file-operations.js has 643 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/file-operations.js:1
  • REDACTED has 610 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
  • cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx has 608 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:1
  • cli-tool/src/analytics/data/DataCache.js has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/analytics/data/DataCache.js:1
  • cli-tool/src/analytics/core/SessionAnalyzer.js has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/analytics/core/SessionAnalyzer.js:1
  • cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx:1
  • cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts:1
  • cli-tool/analytics-ui/src/islands/Dashboard.tsx has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/analytics-ui/src/islands/Dashboard.tsx:1
  • cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts 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. — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:1
  • cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:1
  • cli-tool/components/mods/games/chess/hooks/register.tsx has 517 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/games/chess/hooks/register.tsx:1
  • cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx:1
  • dashboard/src/components/ComponentTerminal.tsx has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/ComponentTerminal.tsx:1
  • dashboard/src/components/SkillReviewFlow.tsx has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/SkillReviewFlow.tsx:1
  • cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:1
  • dashboard/public/blog/js/blog-loader.js has 491 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/public/blog/js/blog-loader.js:1
  • cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:1
  • cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts:1
  • REDACTED has 482 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
  • cli-tool/analytics-ui/public/services/WebSocketService.js has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/analytics-ui/public/services/WebSocketService.js:1
  • cli-tool/src/analytics-web/services/WebSocketService.js has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/analytics-web/services/WebSocketService.js:1
  • cli-tool/src/analytics/notifications/WebSocketServer.js has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/src/analytics/notifications/WebSocketServer.js:1
  • cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts:1
  • cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx:1
  • dashboard/src/components/TrendingView.tsx 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. — dashboard/src/components/TrendingView.tsx:1
  • cloudflare-workers/newsletter/index.js has 454 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cloudflare-workers/newsletter/index.js:1
  • REDACTED has 450 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

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage3.6 / 10Weak✓ 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) — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:1, dashboard/src/components/MyComponentsView.tsx:1, cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.6 / 10Strong✓ Tool-verified

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.

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json 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: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code0.0 / 10Critical✓ 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.

  • 1 file(s) (~300 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — cli-tool/components/skills/design-to-code/scripts
  • Unreachable from the 125 application, 31 tooling and 102 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 (125 application, 31 tooling, 102 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 (×34) — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx, dashboard/src/components/MyComponentsView.tsx, cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js, …
  • no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — 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 — REDACTED
  • no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/components/MyComponentsView.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 — dashboard/src/components/SendToRepoModal.tsx
  • no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/components/ComponentGrid.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 — dashboard/src/components/SaveToCollectionButton.tsx
  • no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (dashboard/src/components/CartSidebar.tsx, dashboard/src/components/ComponentGrid.tsx, dashboard/src/components/SearchModal.tsx and 3 more) — 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 — dashboard/src/lib/data.ts

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene6.5 / 10Adequate✓ Tool-verified

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 package.json — installs work only by hoisting accident. — cli-tool/components/skills/creative-design/claude-d3js-skill/assets/chart-template.jsx:1
  • Declared in cli-tool/analytics-ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — cli-tool/analytics-ui/package.json:12
  • Declared in dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — dashboard/package.json:36, dashboard/package.json:27

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.7.0/p5.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 23 such include(s) across the repository's markup. — cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:23

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X17 · Uncapped recursion over a caller-supplied document1.4 / 10Critical✓ 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.

  • `gateFor` is exported, takes a document from its caller (line 268) and hands it to `strings_in`, which calls itself at line 257 (`strings_in`) with a piece of `value` (and at line 258) — and nowhere in `strings_in` 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 `strings_in` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:257
  • `setPath` is exported and takes `obj: Json` from its caller, and it calls itself at line 209 (`setPath`) with a piece of `obj` — and nowhere in `setPath` 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 `setPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/productivity/ultra-config/hooks/profiles.ts:209
  • `widthOf` is exported and takes `node: Node` from its caller, and it calls itself at line 363 (`widthOf`) with a piece of `node` — and nowhere in `widthOf` 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 `widthOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/productivity/subagent-tuner/hooks/harness.ts:363
  • `isElement` is exported, takes a document from its caller (line 15) and hands it to `textOf`, which calls itself at line 31 (`textOf`) with a piece of `n` — and nowhere in `textOf` 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 `textOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/productivity/subagent-tuner/hooks/stack.ts:31
  • `rowsOf` is exported and takes `tree: unknown` from its caller, and it calls itself at line 46 (`rowsOf`) with a piece of `tree` — and nowhere in `rowsOf` 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 `rowsOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/productivity/subagent-tuner/hooks/stack.ts:46
  • `parseMode` is exported, takes a document from its caller (line 20) and hands it to `isOneOf`, which calls itself at line 34 (`isOneOf`) with a piece of `value` — and nowhere in `isOneOf` 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 `isOneOf` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/productivity/subagent-tuner/hooks/state.ts:34
  • `parseDeploy` is exported, takes a document from its caller (line 85) and hands it to `obj`, which calls itself at line 91 (`obj`) with a piece of `v` (and at line 110, line 117, line 135, line 138, line 154) — and nowhere in `obj` 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 `obj` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-api.ts:91
  • `parseDeploy` is exported, takes a document from its caller (line 85) and hands it to `str`, which calls itself at line 88 (`str`) with a piece of `v` (and at line 90, line 93, line 98, line 99, line 103, line 104, line 122, line 128, line 129, line 136, line 137, line 142, line 146) — and nowhere in `str` 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 `str` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-api.ts:88
  • `handleOf` is exported, takes a document from its caller (line 78) and hands it to `obj`, which calls itself at line 130 (`obj`) with a piece of `v` (and at line 137, line 138) — and nowhere in `obj` 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 `obj` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/integrations/bluesky-feed/hooks/bsky-api.ts:130
  • `serviceUrl` is exported, takes a document from its caller (line 68) and hands it to `str`, which calls itself at line 123 (`str`) with a piece of `v` (and at line 131, line 154, line 160, line 161, line 162, line 163, line 235, line 296, line 305) — and nowhere in `str` 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 `str` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/integrations/bluesky-feed/hooks/bsky-api.ts:123
  • `handleOf` is exported, takes a document from its caller (line 78) and hands it to `describeEmbed`, which calls itself at line 134 (`describeEmbed`) with a piece of `v` — and nowhere in `describeEmbed` 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 `describeEmbed` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — cli-tool/components/mods/integrations/bluesky-feed/hooks/bsky-api.ts:134

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.
X2 · Cancellation propagation5.7 / 10Adequate✓ Tool-verified

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 23/82 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.
  • `loadComponentsMarketplace` 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 })`. — docs/js/component-page.js:498
  • `loadMetadata` 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 })`. — docs/js/data-loader.js:388
  • `generateSearchData` 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 })`. — docs/js/generate-search-data.js:4
  • `fetchTemplatesConfig` 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) — docs/js/index-events.js:1140, docs/js/script.js:41
  • `loadComponentsData` 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 })`. — docs/js/plugin-page.js:83
  • `loadDownloadStatistics` 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 })`. (×4) — docs/js/script.js:335, docs/js/script.js:656, docs/js/script.js:1681, …
  • `loadAllComponentsData` 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 })`. — docs/js/script.js:1064
  • `loadComponentType` 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 })`. — docs/js/script.js:1231
  • `loadComponentsForSearch` 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 })`. — docs/js/search-functionality.js:133
  • `loadData` 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 })`. — docs/js/trending.js:30
  • `loadAllComponents` 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 })`. — docs/js/workflows.js:44
  • `loadArticles` 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) — docs/blog/js/blog-loader.js:202, dashboard/public/blog/js/blog-loader.js:202
  • `APIRoute` holds an AbortSignal but calls `fetch(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fetch(…, { signal })`. — dashboard/src/pages/api/github/token.ts:3
  • `fetchCertifications` 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 })`. — dashboard/src/lib/certifications.ts:176
  • `fetchJson` 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) — dashboard/src/lib/webmcp.ts:92, cloudflare-workers/newsletter/index.js:151
  • `captureApiError` 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 })`. — dashboard/src/lib/api/error-tracking.ts:51
  • `run` 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 })`. — dashboard/scripts/check-agent-endpoints.mjs:82
  • `collectGitHub` 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 })`. — cloudflare-workers/pulse/index.js:129
  • `collectDownloads` 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 })`. — cloudflare-workers/pulse/index.js:216
  • `sendToTelegram` 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) — cloudflare-workers/pulse/index.js:668, cloudflare-workers/daily-health-report/index.js:239
  • `reportError` 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 })`. (×3) — cloudflare-workers/pulse/sentry.js:36, cloudflare-workers/newsletter/sentry.js:36, cloudflare-workers/docs-monitor/sentry.js:36
  • `checkIn` 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 })`. (×3) — cloudflare-workers/pulse/sentry.js:104, cloudflare-workers/newsletter/sentry.js:108, cloudflare-workers/docs-monitor/sentry.js:104
  • `listBroadcastsByName` 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 })`. — cloudflare-workers/newsletter/index.js:385
  • `deleteBroadcast` 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 })`. — cloudflare-workers/newsletter/index.js:405
  • `sendBroadcast` 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 })`. — cloudflare-workers/newsletter/index.js:428
  • `sendTelegramNotification` 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 })`. — cloudflare-workers/docs-monitor/index.js:191
  • `resolveIssue` 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 })`. — cloudflare-workers/daily-health-report/index.js:128
  • `checkSentryErrors` 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 })`. — cloudflare-workers/daily-health-report/index.js:145

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X24 · Document value interpolated into markup unescaped6.8 / 10Adequate✓ 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.

  • `payload.s` is text this program did not author, and it is written into the text of an element through `res.end` (the page this server sends) with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:179
  • `payload.f` is text this program did not author, and it is written into the text of an element through `res.end` (the page this server sends) with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:180
  • `ts` is text this program did not author, and it is written into the text of an element through `res.end` (the page this server sends) with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:182
  • `escapeHtml(b.url)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — cloudflare-workers/newsletter/index.js:367
  • `this.escapeHtml(article.url)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — dashboard/public/blog/js/blog-loader.js:292, dashboard/public/blog/js/blog-loader.js:437
  • `this.escapeHtml(article.image)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×2) — dashboard/public/blog/js/blog-loader.js:294, dashboard/public/blog/js/blog-loader.js:439
  • `slide.html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:401
  • `sized` 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. — dashboard/src/components/TypeIcon.tsx:14

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob3.3 / 10Weak✓ Tool-verified

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.

  • `Cli.language` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:17
  • `Cli.framework` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:19
  • `Cli.template` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:21
  • `Cli.create_agent` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:49
  • `Cli.list_agents` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:51
  • `Cli.remove_agent` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:53
  • `Cli.update_agent` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:55
  • `Cli.command_stats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:59
  • `Cli.hook_stats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:61
  • `Cli.mcp_stats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:63
  • `Cli.health_check` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:70
  • `Cli.analytics` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:74
  • `Cli.chats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:76
  • `Cli.chats_mobile` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:80
  • `Cli.plugins` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:82
  • `Cli.skills_manager` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:84
  • `Cli.teams` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:86
  • `Cli.year_2025` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:88
  • `Cli.tunnel` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:90
  • `Cli.studio` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:92
  • `Cli.e2b_api_key` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:96
  • `Cli.anthropic_api_key` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:98
  • `Cli.clone_session` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:100
  • `Cli.verbose` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cli-rust/src/cli.rs:102

What to do

  • Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
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.

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.

X3 · Exception handling5.4 / 10Adequate✓ Tool-verified

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. (×30) — dashboard/src/pages/llms-full.txt.ts:15, dashboard/src/pages/llms.txt.ts:13, dashboard/src/pages/api/collections/share.ts:118, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×9) — dashboard/src/lib/save-component.ts:40, dashboard/src/lib/webmcp.ts:241, dashboard/src/components/CertificationsPreview.tsx:16, …
  • `catch (parseError)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — REDACTED:286

What to do

  • Swallowed exception (empty catch)
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.

X4 · Structured logging3.6 / 10Weak✓ Tool-verified

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 `package.json` 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.

  • `error` at line 152 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:152
  • `error` at line 156 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:156
  • `error` at line 160 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:160
  • `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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:177
  • `info` at line 186 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:186
  • `warning` at line 195 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:195
  • `error` at line 201 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:201
  • `info` at line 284 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:284
  • `error` at line 291 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:291
  • `error` at line 295 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:295
  • `error` at line 299 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. — cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:299
  • `warning` 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.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. (×2) — cli-tool/components/skills/document-processing/docx-official/scripts/accept_changes.py:117, cli-tool/components/skills/document-processing/docx/scripts/accept_changes.py:117
  • `info` at line 32 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. (×9) — cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:32, cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:32, cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:32, …
  • `error` 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.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. (×9) — cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:60, cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:60, cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:60, …
  • `error` at line 96 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. (×9) — cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:96, cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:96, cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:96, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types6.3 / 10Adequate✓ Tool-verified

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.

  • 6/9 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.
  • ~3.5 `!` null assertions per 1k TypeScript source lines — 176 assertion(s) across the 50721 source line(s) of the 262 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: cli-tool/components/mods/games/tool-defense/hooks/games/defense.ts (15), REDACTED (14), cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts (13). 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 `?`).

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).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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.

LensScoreRatingImpact
Code Health28%Weak — gated by D1, D2, R10, R7, X4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture94%ExemplarySolid.
Maturity94%ExemplaryStrongest area.
Readiness47%Weak — gated by R4, P2, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security74%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility47%Weak — gated by AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 5 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.

  • P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • SC1 Supply-chain hygiene — 9 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.
  • X6 Hand-rolled structured-format parsing — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 42 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 applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • 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
  • 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 start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. The cause is in the repository, not in our sandbox: package.json has no "start" script, so `npm run start` could not start the app. 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 44% of this repository's production lines — javascript (59,654 lines), typescript (38,600 lines), rust (1,941 lines), swift (160 lines), java (109 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.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency does not read html yet; not measured.
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript 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 — None of 1 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .java, .py, .rs, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
  • D5 Coupling — D5 reads a .NET project-reference graph only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (18 value object(s))
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala and Rust, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P9 Domain vs controller coverage — coverage data present for 59 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 a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 45% of this repository's production lines — javascript (59,654 lines), typescript (38,600 lines), swift (160 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.
  • 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.

Critical — 198 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 39 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×29
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 4 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×22
  • <input> without a programmatic label REDACTED:2063 — 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 REDACTED:2114 — 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 REDACTED:2129 — 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 REDACTED:2143 — 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 REDACTED:2168 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label REDACTED:2176 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label REDACTED:2191 — 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 REDACTED:2274 — 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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:342 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:358 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:367 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:376 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:385 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:399 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:408 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:417 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label REDACTED:2063 — 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 REDACTED:2114 — 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 REDACTED:2129 — 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 REDACTED:2143 — 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 REDACTED:2168 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label REDACTED:2176 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×16
  • Click handler on a non-interactive <div> cli-tool/components/hooks/automation/plan-mode-game/index.html:415 — A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> cli-tool/components/hooks/automation/plan-mode-game/index.html:416 — A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> cli-tool/components/hooks/automation/plan-mode-game/index.html:417 — A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> dashboard/src/components/ComponentGrid.tsx:609 — 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> dashboard/src/components/ComponentGrid.tsx:705 — 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> dashboard/src/components/JsonViewer.tsx:143 — 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> dashboard/src/components/JsonViewer.tsx:216 — 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> dashboard/src/components/SearchModal.tsx:233 — 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> docs/js/component-page.js:352 — 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> docs/js/index-events.js:1021 — 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> docs/js/index-events.js:1092 — 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> docs/js/script.js:151 — 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> docs/js/script.js:177 — 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> docs/js/script.js:1383 — 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> docs/js/script.js:1434 — 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> docs/js/workflows-events.js:403 — 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 · <label> that labels no control · ×14
  • <label> that labels no control REDACTED:2110 — This <label> has no for 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 for="<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 REDACTED:2124 — This <label> has no for 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 for="<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 REDACTED:2161 — This <label> has no for 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 for="<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 REDACTED:2187 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:356 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:365 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:374 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:383 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:397 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:406 — This <label> has no for 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 for="<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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:415 — This <label> has no for 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 for="<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 REDACTED:2110 — This <label> has no for 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 for="<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 REDACTED:2124 — This <label> has no for 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 for="<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 REDACTED:2161 — This <label> has no for 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 for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×7
  • Clickable element isn't keyboard-operable docs/js/index-events.js:593 — The repo's own CSS styles .template-card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable docs/js/index-events.js:1048 — The repo's own CSS styles .template-card with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable docs/js/workflows-events.js:126 — The repo's own CSS styles .tree-node-header with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable docs/js/workflows-events.js:385 — The repo's own CSS styles .sub-item-drop-zone with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable docs/js/workflows-events.js:145 — The repo's own CSS styles .tree-file with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable docs/js/workflows.js:147 — The repo's own CSS styles .tree-node-header with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable docs/js/workflows.js:167 — The repo's own CSS styles .tree-file with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×4
  • <img> without a text alternative cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:173 — 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 cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:181 — 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 cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:189 — 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 cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:207 — 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 · <textarea> without a programmatic label · ×4
  • <textarea> without a programmatic label cli-tool/components/hooks/automation/plan-mode-game/index.html:472 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:604 — 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.
  • <textarea> without a programmatic label cli-tool/components/skills/development/skill-development/eval-viewer/viewer.html:604 — 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.
  • <textarea> without a programmatic label cli-tool/components/skills/productivity/skill-creator/eval-viewer/viewer.html:604 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang dashboard/src/pages/github-callback.astro:5 — 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 <span> · ×2
  • Click handler on a non-interactive <span> REDACTED:2262 — 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 <span> REDACTED:2262 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a <span> nested inside <a> · ×1
  • Click handler on a <span> nested inside <a> dashboard/src/components/JobsView.tsx:649 — This <span> carries its own click handler, but it sits inside a <a> that performs a different action. A keyboard user reaches the <a> and activating it runs the <a>'s handler, never this one, so this action has no keyboard path at all. Role and tabindex cannot supply one: HTML forbids a <a> from containing interactive content or any descendant with a tabindex, so the browser will not put this element in the tab order however it is marked up. Move it out of the <a> and make it a sibling <button>, so each action has its own control.
D11 · Test Reliability · Flaky test · ×1
  • Flaky test: cli-tool/tests/integration/analytics-system.test.js::Analytics System Integration Backend Integration should cache data efficiently — Passed 2×, failed 1× across repeated runs.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'react' · ×1
  • Unlisted import 'react' cli-tool/components/skills/creative-design/claude-d3js-skill/assets/chart-template.jsx:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 1660 finding(s)
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×40
  • Outbound HTTP without resilience cli-tool/components/mods/security/jev-vercel-sandbox/hooks/vercel.ts:252 — `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/clinicaltrials-database/scripts/query_clinicaltrials.py:87 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/clinicaltrials-database/scripts/query_clinicaltrials.py:110 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/clinpgx-database/scripts/query_clinpgx.py:36 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:78 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:131 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:75 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:113 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:147 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:48 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:88 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:123 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/generate-image/scripts/generate_image.py:144 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:37 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:65 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:104 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:151 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:180 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:209 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:235 — `urllib.request.urlopen(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:172 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/pubchem-database/scripts/bioactivity_query.py:44 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/pubchem-database/scripts/bioactivity_query.py:46 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/reactome-database/scripts/reactome_query.py:36 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience cli-tool/components/skills/scientific/reactome-database/scripts/reactome_query.py:42 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.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 dashboard/src/components/MyComponentsView.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 cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.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 cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.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 dashboard/src/components/ComponentGrid.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 cloudflare-workers/pulse/index.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 cli-tool/components/skills/career/workorai/scripts/credential-store.mjs: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 dashboard/src/components/JobsView.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 cli-tool/components/mods/productivity/aitmpl/hooks/register.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 cli-tool/analytics-ui/src/islands/Dashboard.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 cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.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 cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.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 dashboard/public/blog/js/blog-loader.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 cli-tool/components/mods/productivity/ultra-config/hooks/register.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 cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.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 dashboard/src/components/ComponentTerminal.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 cli-tool/components/mods/games/chess/hooks/register.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 dashboard/src/components/SkillReviewFlow.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 cli-tool/analytics-ui/public/services/WebSocketService.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 cli-tool/src/analytics-web/services/WebSocketService.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 cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.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 cloudflare-workers/newsletter/index.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 cli-tool/components/mods/productivity/session-chats/hooks/session-chats.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.
  • + 15 more in this group — see findings.md.
X2 · Cancellation propagation · Async function without AbortSignal · ×39
  • Async function without AbortSignal: loadComponentsMarketplace docs/js/component-page.js:498 — `loadComponentsMarketplace` 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: loadMetadata docs/js/data-loader.js:388 — `loadMetadata` 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: generateSearchData docs/js/generate-search-data.js:4 — `generateSearchData` 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: fetchTemplatesConfig docs/js/index-events.js:1140 — `fetchTemplatesConfig` 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: loadComponentsData docs/js/plugin-page.js:83 — `loadComponentsData` 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: fetchTemplatesConfig docs/js/script.js:41 — `fetchTemplatesConfig` 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: loadDownloadStatistics docs/js/script.js:335 — `loadDownloadStatistics` 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: loadDownloadStatistics docs/js/script.js:656 — `loadDownloadStatistics` 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: loadAllComponentsData docs/js/script.js:1064 — `loadAllComponentsData` 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: loadComponentType docs/js/script.js:1231 — `loadComponentType` 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: loadDownloadStatistics docs/js/script.js:1681 — `loadDownloadStatistics` 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: loadDownloadStatistics docs/js/script.js:1926 — `loadDownloadStatistics` 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: loadComponentsForSearch docs/js/search-functionality.js:133 — `loadComponentsForSearch` 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: loadData docs/js/trending.js:30 — `loadData` 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: loadAllComponents docs/js/workflows.js:44 — `loadAllComponents` 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: loadArticles docs/blog/js/blog-loader.js:202 — `loadArticles` 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: APIRoute dashboard/src/pages/api/github/token.ts:3 — `APIRoute` holds an AbortSignal but calls `fetch(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fetch(…, { signal })`.
  • Async function without AbortSignal: fetchCertifications dashboard/src/lib/certifications.ts:176 — `fetchCertifications` 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: fetchJson dashboard/src/lib/webmcp.ts:92 — `fetchJson` 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: captureApiError dashboard/src/lib/api/error-tracking.ts:51 — `captureApiError` 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: run dashboard/scripts/check-agent-endpoints.mjs:82 — `run` 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: loadArticles dashboard/public/blog/js/blog-loader.js:202 — `loadArticles` 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: collectGitHub cloudflare-workers/pulse/index.js:129 — `collectGitHub` 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: collectDownloads cloudflare-workers/pulse/index.js:216 — `collectDownloads` 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: sendToTelegram cloudflare-workers/pulse/index.js:668 — `sendToTelegram` 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 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×39
  • Swallowed exception (empty catch) dashboard/src/pages/llms-full.txt.ts:15 — 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) dashboard/src/pages/llms.txt.ts:13 — 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) dashboard/src/pages/api/collections/share.ts:118 — 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) dashboard/src/lib/analytics.ts:118 — 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) dashboard/src/lib/data.ts:29 — 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) dashboard/src/lib/data.ts:115 — 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) dashboard/src/lib/data.ts:157 — 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) dashboard/src/lib/data.ts:243 — 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) dashboard/src/lib/pending-action.ts:64 — 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) dashboard/src/lib/pending-action.ts:72 — 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) dashboard/src/lib/pending-action.ts:104 — 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) dashboard/src/lib/pending-action.ts:106 — 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) dashboard/src/lib/save-component.ts:40 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) dashboard/src/lib/save-stack.ts:26 — 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) dashboard/src/lib/sign-in.ts:145 — 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) dashboard/src/lib/webmcp.ts:241 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) dashboard/src/lib/webmcp.ts:242 — 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) dashboard/src/components/AddToStackButton.tsx:51 — 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) dashboard/src/components/CartSidebar.tsx:65 — 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) dashboard/src/components/CertificationsPreview.tsx:16 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) dashboard/src/components/CertificationsView.tsx:212 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) dashboard/src/components/ComponentGrid.tsx:108 — 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) dashboard/src/components/ComponentGrid.tsx:117 — 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) dashboard/src/components/JobsPreview.tsx:74 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) dashboard/src/components/SearchModal.tsx:42 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • + 14 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×33
  • Hotspot: scripts/generate_components_json.py scripts/generate_components_json.py:568 — scripts/generate_components_json.py changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 152 in generate_components_json.generate_components_json at line 568. 3 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- scripts/generate_components_json.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/src/index.js cli-tool/src/index.js:86 — cli-tool/src/index.js changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 93 in index.createClaudeConfig at line 86. 4 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/src/index.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:301 — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 335 in jev-vercel-sandbox.register at line 301. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx:159 — cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 95 in register.register at line 159. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:171 — cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 94 in prompt-cache-control.register at line 171. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/ComponentGrid.tsx dashboard/src/components/ComponentGrid.tsx:41 — dashboard/src/components/ComponentGrid.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 96 in ComponentGrid.ComponentGrid at line 41. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/ComponentGrid.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/games/chess/hooks/register.tsx cli-tool/components/mods/games/chess/hooks/register.tsx:217 — cli-tool/components/mods/games/chess/hooks/register.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 93 in register.register at line 217. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/games/chess/hooks/register.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:121 — cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 108 in jev-auto-mode.register at line 121. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:144 — REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 104 in SkillExplorer.SkillExplorer at line 144. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/JobsView.tsx dashboard/src/components/JobsView.tsx:88 — dashboard/src/components/JobsView.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in JobsView.JobsView at line 88. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/JobsView.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx:81 — cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in register.register at line 81. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:130 — cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 83 in register.register at line 130. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx:58 — cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 80 in stack-viewer.register at line 58. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts:64 — cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in jev-model-router.register at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/MyComponentsView.tsx dashboard/src/components/MyComponentsView.tsx:467 — dashboard/src/components/MyComponentsView.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in MyComponentsView.MyComponentsView at line 467. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/MyComponentsView.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/SaveToCollectionButton.tsx dashboard/src/components/SaveToCollectionButton.tsx:60 — dashboard/src/components/SaveToCollectionButton.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in SaveToCollectionButton.SaveButton at line 60. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/SaveToCollectionButton.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/CartSidebar.tsx dashboard/src/components/CartSidebar.tsx:33 — dashboard/src/components/CartSidebar.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in CartSidebar.CartSidebar at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/CartSidebar.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:85 — cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in agent-flow.register at line 85. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/SearchModal.tsx dashboard/src/components/SearchModal.tsx:25 — dashboard/src/components/SearchModal.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in SearchModal.SearchModal at line 25. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/SearchModal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/JobsPreview.tsx dashboard/src/components/JobsPreview.tsx:66 — dashboard/src/components/JobsPreview.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in JobsPreview.JobsPreview at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/JobsPreview.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: scripts/generate_trending_data.py scripts/generate_trending_data.py:312 — scripts/generate_trending_data.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in generate_trending_data.process_downloads_data at line 312. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- scripts/generate_trending_data.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cli-tool/components/mods/integrations/neon-branch-per-session/hooks/neon-branch-per-session.ts cli-tool/components/mods/integrations/neon-branch-per-session/hooks/neon-branch-per-session.ts:60 — cli-tool/components/mods/integrations/neon-branch-per-session/hooks/neon-branch-per-session.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in neon-branch-per-session.register at line 60. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- cli-tool/components/mods/integrations/neon-branch-per-session/hooks/neon-branch-per-session.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/lib/certifications.ts dashboard/src/lib/certifications.ts:191 — dashboard/src/lib/certifications.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in certifications.validateItem at line 191. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/lib/certifications.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: scripts/external_skills.py scripts/external_skills.py:209 — scripts/external_skills.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in external_skills.local_dir at line 209. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- scripts/external_skills.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: dashboard/src/components/CertificationsView.tsx dashboard/src/components/CertificationsView.tsx:198 — dashboard/src/components/CertificationsView.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CertificationsView.CertificationsView at line 198. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 04:20:34 +00:00' --until='2026-11-16 04:20:34 +00:00' --full-history --no-merges -- dashboard/src/components/CertificationsView.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 8 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×33
  • FunctionTooLong: MyComponentsView.MyComponentsView dashboard/src/components/MyComponentsView.tsx:467 — FunctionTooLong — MyComponentsView runs 541 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 441 over it, 5.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: JobsView.JobsView dashboard/src/components/JobsView.tsx:88 — FunctionTooLong — JobsView runs 520 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 420 over it, 5.20× 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: TrendingView.TrendingView dashboard/src/components/TrendingView.tsx:54 — FunctionTooLong — TrendingView runs 370 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 270 over it, 3.70× 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: CartSidebar.CartSidebar dashboard/src/components/CartSidebar.tsx:33 — FunctionTooLong — CartSidebar runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.31× 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: stack-viewer.register cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx:58 — FunctionTooLong — register runs 308 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 208 over it, 3.08× 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: search-functionality.document.addEventListener("DOMContentLoaded") docs/js/search-functionality.js:724 — FunctionTooLong — document.addEventListener("DOMContentLoaded") runs 306 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 206 over it, 3.06× 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: register.register cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx:81 — FunctionTooLong — register runs 285 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: agent-flow.register cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:85 — FunctionTooLong — register runs 280 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× 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: index-events.showComponentContributeModal docs/js/index-events.js:1545 — FunctionTooLong — showComponentContributeModal runs 280 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× 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: turn-inspector.register cli-tool/components/mods/ui/turn-inspector/hooks/turn-inspector.tsx:71 — FunctionTooLong — register runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× 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: SendToRepoModal.SendToRepoModal dashboard/src/components/SendToRepoModal.tsx:96 — FunctionTooLong — SendToRepoModal runs 271 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 171 over it, 2.71× 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: MarketplacePluginsList.MarketplacePluginsList dashboard/src/components/MarketplacePluginsList.tsx:36 — FunctionTooLong — MarketplacePluginsList runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× 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: register.register cli-tool/components/mods/games/chess/hooks/register.tsx:217 — FunctionTooLong — register runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× 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: jev-auto-mode.register cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:121 — FunctionTooLong — register runs 257 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 157 over it, 2.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: SearchModal.SearchModal dashboard/src/components/SearchModal.tsx:25 — FunctionTooLong — SearchModal 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: SaveToCollectionButton.SaveButton dashboard/src/components/SaveToCollectionButton.tsx:60 — FunctionTooLong — SaveButton runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× 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: SkillReviewFlow.SkillReviewFlow dashboard/src/components/SkillReviewFlow.tsx:276 — FunctionTooLong — SkillReviewFlow runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× 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: Dashboard.DashboardView cli-tool/analytics-ui/src/islands/Dashboard.tsx:161 — FunctionTooLong — DashboardView runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.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: bluesky-feed.register cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:63 — FunctionTooLong — register runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× 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: PluginsGrid.PluginsGrid dashboard/src/components/PluginsGrid.tsx:34 — FunctionTooLong — PluginsGrid 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: CertificationsView.CertificationsView dashboard/src/components/CertificationsView.tsx:198 — FunctionTooLong — CertificationsView runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× 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: linear-tickets.register cli-tool/components/mods/integrations/linear-tickets/hooks/linear-tickets.tsx:70 — FunctionTooLong — register runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× 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: register.register cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:327 — FunctionTooLong — register 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: install-ui.createInstallUI cli-tool/src/install-ui.js:114 — FunctionTooLong — createInstallUI runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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: interactive-template.InteractiveChart cli-tool/components/skills/creative-design/claude-d3js-skill/assets/interactive-template.jsx:4 — FunctionTooLong — InteractiveChart runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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.
  • + 8 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×26
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1757 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1257 over it, 3.51× 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: REDACTED REDACTED — FileTooLong — 1757 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1257 over it, 3.51× 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/index.js cli-tool/src/index.js — FileTooLong — 1726 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 1226 over it, 3.45× 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: js/script.js docs/js/script.js — FileTooLong — 1345 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 845 over it, 2.69× 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: js/index-events.js docs/js/index-events.js — FileTooLong — 1337 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: IndexPageManager (11-1539). The bar is 500 significant lines; this is 837 over it, 2.67× 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: js/component-page.js docs/js/component-page.js — FileTooLong — 1265 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 765 over it, 2.53× 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: REDACTED REDACTED — FileTooLong — 1222 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ClaudeAnalytics (20-1977). The bar is 500 significant lines; this is 722 over it, 2.44× 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: monitoring/context-timeline.py cli-tool/components/hooks/monitoring/context-timeline.py — FileTooLong — 999 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 499 over it, 2.00× 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: components/MyComponentsView.tsx dashboard/src/components/MyComponentsView.tsx — FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: MyComponentsView (467-1101). The bar is 500 significant lines; this is 391 over it, 1.78× 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/health-check.js cli-tool/src/health-check.js — FileTooLong — 878 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: HealthChecker (13-1381). The bar is 500 significant lines; this is 378 over it, 1.76× 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/build_ownership_map.py cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py — FileTooLong — 782 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 282 over it, 1.56× 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: scripts/sora.py cli-tool/components/skills/video/sora/scripts/sora.py — FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 272 over it, 1.54× 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: js/workflows-events.js docs/js/workflows-events.js — FileTooLong — 734 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 234 over it, 1.47× 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: components/ComponentGrid.tsx dashboard/src/components/ComponentGrid.tsx — FileTooLong — 732 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 232 over it, 1.46× 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: js/search-functionality.js docs/js/search-functionality.js — FileTooLong — 728 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 228 over it, 1.46× 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: scripts/image_gen.py cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py — FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 193 over it, 1.39× 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: REDACTED REDACTED — FileTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ChatsMobile (16-1127). The bar is 500 significant lines; this is 187 over it, 1.37× 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: hooks/stack.ts cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts — FileTooLong — 682 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 182 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: scripts/enzyme_pathway_builder.py cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py — FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 166 over it, 1.33× 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: commands/install.rs cli-rust/src/commands/install.rs — FileTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 104 over it, 1.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: components/JobsView.tsx dashboard/src/components/JobsView.tsx — FileTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: JobsView (88-702). The bar is 500 significant lines; this is 85 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: js/trending.js docs/js/trending.js — FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: TrendingPage (6-616). The bar is 500 significant lines; this is 38 over it, 1.08× 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: REDACTED REDACTED — FileTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 29 over it, 1.06× 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: hooks/policy.ts cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts — FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 17 over it, 1.03× 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: pulse/index.js cloudflare-workers/pulse/index.js — FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 4 over it, 1.01× 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.
  • + 1 more in this group — see findings.md.
X25 · Inert configuration knob · Configuration option is read nowhere · ×24
  • Configuration option is read nowhere cli-rust/src/cli.rs:17 — `Cli.language` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:19 — `Cli.framework` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:21 — `Cli.template` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:49 — `Cli.create_agent` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:51 — `Cli.list_agents` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:53 — `Cli.remove_agent` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:55 — `Cli.update_agent` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:59 — `Cli.command_stats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:61 — `Cli.hook_stats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:63 — `Cli.mcp_stats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:70 — `Cli.health_check` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:74 — `Cli.analytics` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:76 — `Cli.chats` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:80 — `Cli.chats_mobile` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:82 — `Cli.plugins` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:84 — `Cli.skills_manager` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:86 — `Cli.teams` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:88 — `Cli.year_2025` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:90 — `Cli.tunnel` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:92 — `Cli.studio` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:96 — `Cli.e2b_api_key` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:98 — `Cli.anthropic_api_key` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:100 — `Cli.clone_session` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
  • Configuration option is read nowhere cli-rust/src/cli.rs:102 — `Cli.verbose` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
D29 · Static Analysis (SAST) · REDACTED · ×23
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D1 · Cyclomatic Complexity · MarkdownCopier.processElement (cyclomatic 18) · ×20
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/function-hooks-claude-code/index.html:827 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/hackathon-ai-strategist-agent/index.html:652 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/performance-budget-guard-hook/index.html:637 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/secure-git-workflow/index.html:642 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/security-hooks-secrets/index.html:722 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/simple-notifications-hook/index.html:673 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/skills-creator/index.html:630 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/supabase-claude-code-integration/index.html:747 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/technical-writer-agent/index.html:648 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) dashboard/public/blog/vercel-deployment-monitor-statusline/index.html:674 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/function-hooks-claude-code/index.html:827 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/hackathon-ai-strategist-agent/index.html:652 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/performance-budget-guard-hook/index.html:637 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/secure-git-workflow/index.html:642 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/security-hooks-secrets/index.html:722 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/simple-notifications-hook/index.html:673 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/skills-creator/index.html:630 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/supabase-claude-code-integration/index.html:747 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/technical-writer-agent/index.html:648 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 18) docs/blog/vercel-deployment-monitor-statusline/index.html:674 — MarkdownCopier.processElement has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×19
  • Animation without a prefers-reduced-motion guard REDACTED:219 — `.search-panel` moves (`animation: slideDown 0.3s 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 REDACTED:502 — `.folder-browser-dropdown.active` moves (`animation: slideDown 0.2s 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 REDACTED:602 — `.chat-search-bar` moves (`animation: slideDown 0.2s 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 REDACTED:936 — `.project-toggle` moves (`transition: transform 0.2s 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 REDACTED:940 — `.toggle-icon` moves (`transition: transform 0.2s 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 REDACTED:1469 — `.chat-view` moves (`transition: left 0.3s 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 REDACTED:1626 — `.loading-spinner` moves (`animation: spin 1s linear 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.
  • Animation without a prefers-reduced-motion guard REDACTED:1678 — `.status-dot.working` moves (`animation: pulse 2s 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.
  • Animation without a prefers-reduced-motion guard REDACTED:1776 — `.modal` moves (`animation: modalSlideIn 0.3s 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 REDACTED:2007 — `.analytics-wait-bar` moves (`transition: width 0.3s 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 REDACTED:2012 — `.analytics-user-bar` moves (`transition: width 0.3s 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 cli-tool/analytics-ui/src/components/BarList.tsx:99 — <div> moves — its inline style sets `transition: width 0.4s ease` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard cli-tool/components/hooks/automation/plan-mode-game/index.html:142 — `.activity-item` moves (`animation: slideIn 0.2s 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 cli-tool/components/hooks/automation/plan-mode-game/index.html:167 — `.announcement` moves (`animation: slideUp 0.6s cubic-bezier(0.16,1,0.3,1)`) 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 cli-tool/components/hooks/automation/plan-mode-game/index.html:178 — `.confetti` moves (`animation: confettiFall linear forwards`) 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 cli-tool/components/hooks/automation/plan-mode-game/index.html:191 — `.pause-modal` moves (`animation: pauseBounce 0.5s cubic-bezier(0.16,1,0.3,1)`) 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 cli-tool/components/hooks/automation/plan-mode-game/index.html:330 — `.share-btn` moves (`transition: background 0.2s, transform 0.1s`) 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 cli-tool/components/hooks/automation/plan-mode-game/index.html:354 — `.share-inner` moves (`animation: slideUp 0.4s cubic-bezier(0.16,1,0.3,1)`) 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 cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:275 — `.grades-toggle .arrow` moves (`transition: transform 0.15s`) 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.
D17 · Explicit Debt · TodoComment · ×17
  • TodoComment cli-tool/components/skills/scientific/pytdc/scripts/benchmark_evaluation.py:70 — # TODO: Replace with your model training — 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 cli-tool/components/skills/scientific/pytdc/scripts/benchmark_evaluation.py:129 — # TODO: Replace with your model — 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 cli-tool/components/skills/scientific/pymc/assets/hierarchical_model_template.py:7 — # TODO — 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 cli-tool/components/skills/scientific/pymc/assets/linear_regression_template.py:7 — # TODO — 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 cli-tool/components/skills/scientific/pymc/assets/hierarchical_model_template.py:20 — # TODO: Load your data with group structure — 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 cli-tool/components/skills/scientific/pymc/assets/hierarchical_model_template.py:48 — # TODO: Customize group names — 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 cli-tool/components/skills/scientific/pymc/assets/hierarchical_model_template.py:68 — # TODO: Adjust hyperpriors based on your domain knowledge — 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 cli-tool/components/skills/scientific/pymc/assets/hierarchical_model_template.py:268 — # TODO: Specify new data — 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 cli-tool/components/skills/scientific/pymc/assets/linear_regression_template.py:20 — # TODO: Load your data — 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 cli-tool/components/skills/scientific/pymc/assets/linear_regression_template.py:45 — # TODO: Customize predictor names — 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 cli-tool/components/skills/scientific/pymc/assets/linear_regression_template.py:55 — # TODO: Adjust prior parameters based on your domain knowledge — 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 cli-tool/components/skills/scientific/pymc/assets/linear_regression_template.py:197 — # TODO: Provide new data for predictions — 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 cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py:57 — ## [TODO: Replace with the first main section based on chosen structure] — 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 REDACTED:25 — # TODO: Configure this in production, e.g. ["api.example.com"] — 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 REDACTED:31 — # TODO: Update this with specific origins in production — 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 REDACTED:32 — # TODO: Set to True if you need cookies/auth headers, but restrict origins — 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 cli-tool/components/mods/productivity/webfetch-cache/hooks/webfetch-cache.ts:36 — // or a read past the first page would get the first page back. Not in the typings until they are regenerated (TODO: drop the cast then). — 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.
AC3 · Page structure · Page without a main landmark · ×15
  • Page without a main landmark REDACTED: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 cli-tool/analytics-ui/src/layouts/Base.astro:8 — 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 cli-tool/components/hooks/automation/plan-mode-game/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 cli-tool/components/skills/ai-research/loki-mode/autonomy/.loki/dashboard/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 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:18 — 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 cli-tool/components/skills/development/skill-creator/assets/eval_review.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 cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.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 cli-tool/components/skills/development/skill-development/assets/eval_review.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 cli-tool/components/skills/development/skill-development/eval-viewer/viewer.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 cli-tool/components/skills/productivity/skill-creator/assets/eval_review.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 cli-tool/components/skills/productivity/skill-creator/eval-viewer/viewer.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 cli-tool/components/skills/scientific/pptx-posters/assets/poster_html_template.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 REDACTED: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 dashboard/public/trending-dashboard.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 dashboard/src/pages/github-callback.astro:5 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D1 · Cyclomatic Complexity · MarkdownCopier.processElement (cyclomatic 17) · ×14
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/code-reviewer-agent/index.html:612 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/context7-mcp/index.html:576 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/e2b-claude-code-sandbox/index.html:752 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/edit-audit-log-hook/index.html:614 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/frontend-developer-agent/index.html:610 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/nextjs-vercel-claude-code-integration/index.html:953 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) dashboard/public/blog/task-move-command/index.html:651 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/code-reviewer-agent/index.html:612 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/context7-mcp/index.html:576 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/e2b-claude-code-sandbox/index.html:752 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/edit-audit-log-hook/index.html:614 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/frontend-developer-agent/index.html:610 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/nextjs-vercel-claude-code-integration/index.html:953 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 17) docs/blog/task-move-command/index.html:651 — MarkdownCopier.processElement has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×13
  • Sync-over-async blocking cli-tool/src/analytics/core/FileWatcher.js:163 — `fs.statSync` in `handleFileActivity` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking cli-tool/src/index.js:1293 — `fs.existsSync` in `getAvailableAgentsFromGitHub` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking cli-tool/src/index.js:1294 — `fs.readFileSync` in `getAvailableAgentsFromGitHub` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:50 — `fs.existsSync` in `validate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:155 — `execSync` in `extractGitMetadata` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:165 — `execSync` in `extractGitMetadata` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:171 — `execSync` in `extractGitMetadata` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:179 — `execSync` in `extractGitMetadata` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:304 — `fs.existsSync` in `generateProvenanceReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dashboard/src/lib/data.ts:24 — `fs.readFileSync` in `fetchComponents` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dashboard/src/lib/data.ts:111 — `fs.readFileSync` in `fetchComponentsByType` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dashboard/src/lib/data.ts:153 — `fs.readFileSync` in `fetchSearchIndex` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking dashboard/src/lib/data.ts:240 — `fs.readFileSync` in `fetchComponentContentData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
D29 · Static Analysis (SAST) · REDACTED · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · TooManyMethods · ×11
  • TooManyMethods: ChatsMobileApp REDACTED:2557 — TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× 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.
  • TooManyMethods: ChatsMobileApp REDACTED:2557 — TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× 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.
  • TooManyMethods: HealthChecker cli-tool/src/health-check.js:13 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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.
  • TooManyMethods: IndexPageManager docs/js/index-events.js:11 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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.
  • TooManyMethods: ClaudeAnalytics REDACTED:20 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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.
  • TooManyMethods: WorkflowManager docs/js/workflows-events.js:3 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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.
  • TooManyMethods: ConversationAnalyzer cli-tool/src/analytics/core/ConversationAnalyzer.js:9 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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.
  • TooManyMethods: ComponentPageManager docs/js/component-page.js:2 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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.
  • TooManyMethods: WebSocketService cli-tool/analytics-ui/public/services/WebSocketService.js:5 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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.
  • TooManyMethods: WebSocketService cli-tool/src/analytics-web/services/WebSocketService.js:5 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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.
  • TooManyMethods: DataLoader docs/js/data-loader.js:2 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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.
D31 · IaC & Container Security · Medium IaC · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×11
  • Duplicated block (11 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:57 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:57-67 | cli-tool/components/skills/video/sora/scripts/sora.py:61-71 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (11 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:336 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:336-346 | cli-tool/components/skills/video/sora/scripts/sora.py:229-239 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (11 lines × 2) cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:191 — cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:191-201 | cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:241-251 — 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 (11 lines × 2) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:98 — cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:98-108 | scripts/generate_star_history.py:72-82 — before extracting anything, compare `cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py` and `scripts/generate_star_history.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (11 lines × 2) cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:17 — cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:17-27 | cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py:16-26 — before extracting anything, compare `cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py` and `cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 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 (11 lines × 2) cli-tool/components/skills/scientific/pydicom/scripts/anonymize_dicom.py:108 — cli-tool/components/skills/scientific/pydicom/scripts/anonymize_dicom.py:108-118 | cli-tool/components/skills/scientific/pydicom/scripts/dicom_to_image.py:133-143 — 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 `cli-tool/components/skills/scientific/pydicom/scripts/anonymize_dicom.py:108` 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.
  • Duplicated block (11 lines × 2) cli-tool/components/skills/video/sora/scripts/sora.py:631 — cli-tool/components/skills/video/sora/scripts/sora.py:631-641 | cli-tool/components/skills/video/sora/scripts/sora.py:656-666 — 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 (11 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:315 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:315-325 | cli-tool/components/skills/video/sora/scripts/sora.py:188-198 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (11 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:303 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:303-313 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:303-313 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (11 lines × 2) cli-rust/src/commands/install.rs:240 — cli-rust/src/commands/install.rs:240-250 | cli-rust/src/commands/install.rs:407-417 — 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 `cli-rust/src/commands/install.rs:240` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) scripts/generate_components_json.py:982 — scripts/generate_components_json.py:982-992 | scripts/generate_components_json.py:1023-1033 — 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.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×11
  • Recursive walk over a caller-supplied document has no depth cap REDACTED:257 — `gateFor` is exported, takes a document from its caller (line 268) and hands it to `strings_in`, which calls itself at line 257 (`strings_in`) with a piece of `value` (and at line 258) — and nowhere in `strings_in` 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 `strings_in` 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 cli-tool/components/mods/productivity/ultra-config/hooks/profiles.ts:209 — `setPath` is exported and takes `obj: Json` from its caller, and it calls itself at line 209 (`setPath`) with a piece of `obj` — and nowhere in `setPath` 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 `setPath` 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 cli-tool/components/mods/productivity/subagent-tuner/hooks/harness.ts:363 — `widthOf` is exported and takes `node: Node` from its caller, and it calls itself at line 363 (`widthOf`) with a piece of `node` — and nowhere in `widthOf` 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 `widthOf` 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 cli-tool/components/mods/productivity/subagent-tuner/hooks/stack.ts:31 — `isElement` is exported, takes a document from its caller (line 15) and hands it to `textOf`, which calls itself at line 31 (`textOf`) with a piece of `n` — and nowhere in `textOf` 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 `textOf` 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 cli-tool/components/mods/productivity/subagent-tuner/hooks/stack.ts:46 — `rowsOf` is exported and takes `tree: unknown` from its caller, and it calls itself at line 46 (`rowsOf`) with a piece of `tree` — and nowhere in `rowsOf` 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 `rowsOf` 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 cli-tool/components/mods/productivity/subagent-tuner/hooks/state.ts:34 — `parseMode` is exported, takes a document from its caller (line 20) and hands it to `isOneOf`, which calls itself at line 34 (`isOneOf`) with a piece of `value` — and nowhere in `isOneOf` 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 `isOneOf` 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 cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-api.ts:91 — `parseDeploy` is exported, takes a document from its caller (line 85) and hands it to `obj`, which calls itself at line 91 (`obj`) with a piece of `v` (and at line 110, line 117, line 135, line 138, line 154) — and nowhere in `obj` 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 `obj` 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 cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-api.ts:88 — `parseDeploy` is exported, takes a document from its caller (line 85) and hands it to `str`, which calls itself at line 88 (`str`) with a piece of `v` (and at line 90, line 93, line 98, line 99, line 103, line 104, line 122, line 128, line 129, line 136, line 137, line 142, line 146) — and nowhere in `str` 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 `str` 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 cli-tool/components/mods/integrations/bluesky-feed/hooks/bsky-api.ts:130 — `handleOf` is exported, takes a document from its caller (line 78) and hands it to `obj`, which calls itself at line 130 (`obj`) with a piece of `v` (and at line 137, line 138) — and nowhere in `obj` 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 `obj` 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 cli-tool/components/mods/integrations/bluesky-feed/hooks/bsky-api.ts:123 — `serviceUrl` is exported, takes a document from its caller (line 68) and hands it to `str`, which calls itself at line 123 (`str`) with a piece of `v` (and at line 131, line 154, line 160, line 161, line 162, line 163, line 235, line 296, line 305) — and nowhere in `str` 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 `str` 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 cli-tool/components/mods/integrations/bluesky-feed/hooks/bsky-api.ts:134 — `handleOf` is exported, takes a document from its caller (line 78) and hands it to `describeEmbed`, which calls itself at line 134 (`describeEmbed`) with a piece of `v` — and nowhere in `describeEmbed` 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 `describeEmbed` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D29 · Static Analysis (SAST) · REDACTED · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×10
  • Untrusted text written into markup unescaped REDACTED:179 — `payload.s` is text this program did not author, and it is written into the text of an element through `res.end` (the page this server sends) 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:180 — `payload.f` is text this program did not author, and it is written into the text of an element through `res.end` (the page this server sends) 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:182 — `ts` is text this program did not author, and it is written into the text of an element through `res.end` (the page this server sends) 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 cloudflare-workers/newsletter/index.js:367 — `escapeHtml(b.url)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped dashboard/public/blog/js/blog-loader.js:292 — `this.escapeHtml(article.url)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped dashboard/public/blog/js/blog-loader.js:294 — `this.escapeHtml(article.image)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped dashboard/public/blog/js/blog-loader.js:437 — `this.escapeHtml(article.url)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped dashboard/public/blog/js/blog-loader.js:439 — `this.escapeHtml(article.image)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` 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. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped REDACTED:401 — `slide.html` 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 dashboard/src/components/TypeIcon.tsx:14 — `sized` 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.
D3 · God Classes · ClassTooLong · ×9
  • ClassTooLong: ClaudeAnalytics REDACTED:20 — ClassTooLong — 1179 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 779 over it, 2.95× 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: IndexPageManager docs/js/index-events.js:11 — ClassTooLong — 969 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 569 over it, 2.42× 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: HealthChecker cli-tool/src/health-check.js:13 — ClassTooLong — 850 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 450 over it, 2.13× 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: ChatsMobile REDACTED:16 — ClassTooLong — 641 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 241 over it, 1.60× 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: MyComponentsView dashboard/src/components/MyComponentsView.tsx:1 — ClassTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 141 over it, 1.35× 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: JobsView dashboard/src/components/JobsView.tsx:1 — ClassTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 120 over it, 1.30× 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: ConversationAnalyzer cli-tool/src/analytics/core/ConversationAnalyzer.js:9 — ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 95 over it, 1.24× 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: TrendingPage docs/js/trending.js:6 — ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 30 over it, 1.08× 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: register cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:1 — ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 9 over it, 1.02× 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×9
  • Duplicated block (6 lines × 2) cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py:221 — cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py:221-226 | cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py:260-278 — 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 `cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py:221` 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 (6 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:557 — cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:557-562 | cli-tool/components/skills/scientific/citation-management/scripts/search_google_scholar.py:270-275 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli-tool/components/skills/scientific/citation-management/scripts/search_google_scholar.py:266` calls `metadata_to_bibtex`, `join` and `cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:554` 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 (6 lines × 2) cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:169 — cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:169-174 | cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:177-182 — 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 lines × 2) cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:176 — cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:176-181 | cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:184-191 — 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 `cli-tool/components/skills/scientific/etetoolkit/scripts/tree_operations.py:184` 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.
  • Duplicated block (6 lines × 2) cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:140 — cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:140-145 | cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:162-167 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:147` calls `get` and `cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:170` does not — after which the two agree again for 3 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 (6 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:275 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:275-280 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:275-280 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:283` calls `_log` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:282` does not — after which the two agree again for 3 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 (6 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:99 — cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:99-104 | cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:111-116 — 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 lines × 2) cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:290 — cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:290-295 | cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:315-320 — 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 lines × 2) cli-rust/src/commands/install.rs:41 — cli-rust/src/commands/install.rs:41-46 | cli-rust/src/commands/install.rs:93-100 — 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 `cli-rust/src/commands/install.rs:41` 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.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×9
  • JavaScript dependencies are not locked cli-rust/npm/cct/package.json:33 — cli-rust/npm/cct/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cli-tool/.claude/sandbox/cloudflare/package.json:19 — cli-tool/.claude/sandbox/cloudflare/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cli-tool/components/sandbox/cloudflare/package.json:19 — cli-tool/components/sandbox/cloudflare/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cli-tool/components/sandbox/docker/package.json:11 — cli-tool/components/sandbox/docker/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cli-tool/components/skills/design-to-code/scripts/package.json:5 — cli-tool/components/skills/design-to-code/scripts/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cli-tool/components/skills/utilities/playwright-skill/package.json:19 — cli-tool/components/skills/utilities/playwright-skill/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cli-tool/components/skills/web-development/roier-seo/scripts/package.json:12 — cli-tool/components/skills/web-development/roier-seo/scripts/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cloudflare-workers/daily-health-report/package.json:27 — cloudflare-workers/daily-health-report/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
  • JavaScript dependencies are not locked cloudflare-workers/newsletter/package.json:25 — cloudflare-workers/newsletter/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×8
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py:16 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/document-processing/pdf-official/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/document-processing/pdf/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/check_bounding_boxes.py:19-60 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/convert_pdf_to_images.py:10 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/convert_pdf_to_images.py:10-24 | cli-tool/components/skills/document-processing/pdf-official/scripts/convert_pdf_to_images.py:10-24 | cli-tool/components/skills/document-processing/pdf-processing/scripts/convert_pdf_to_images.py:10-24 | cli-tool/components/skills/document-processing/pdf/scripts/convert_pdf_to_images.py:10-24 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/convert_pdf_to_images.py:11-26 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/create_validation_image.py:10 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/document-processing/pdf-official/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/document-processing/pdf-processing/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/document-processing/pdf/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/create_validation_image.py:13-30 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:20 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/extract_form_field_info.py:23-50 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:48 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/extract_form_field_info.py:63-137 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:12 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/document-processing/pdf/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_fillable_fields.py:13-56 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:56 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/document-processing/pdf/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_fillable_fields.py:60-75 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:75 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/document-processing/pdf/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_fillable_fields.py:91-103 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×7
  • Duplicated block (10 lines × 2) REDACTED:51 — REDACTED:51-60 | REDACTED:51-60 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:446 — cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:446-455 | cli-tool/components/skills/analytics/google-analytics/scripts/ga_client.py:301-310 — 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 (10 lines × 2) cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:348 — cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:348-357 | cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:407-416 — 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 (10 lines × 2) cli-tool/components/skills/scientific/fda-database/scripts/fda_examples.py:31 — cli-tool/components/skills/scientific/fda-database/scripts/fda_examples.py:31-40 | cli-tool/components/skills/scientific/fda-database/scripts/fda_examples.py:83-92 — 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 `cli-tool/components/skills/scientific/fda-database/scripts/fda_examples.py:31` 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.
  • Duplicated block (10 lines × 2) cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:58 — cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:58-67 | cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:84-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (10 lines × 2) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:112 — cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:112-121 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:122-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.
  • Duplicated block (10 lines × 2) cli-rust/src/merge.rs:29 — cli-rust/src/merge.rs:29-38 | cli-rust/src/merge.rs:54-63 — 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 `cli-rust/src/merge.rs:29` 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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×6
  • Low contrast colour pair in CSS (2.8:1) REDACTED:349 — `.search-btn-primary` sets color: white on background-color: #ff6b35 — 2.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 (2.8:1) REDACTED:393 — `.advanced-search-toggle:hover` sets color: white on background-color: #ff6b35 — 2.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 (2.8:1) REDACTED:464 — `.folder-browser-toggle` sets color: white on background-color: #ff6b35 — 2.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 (2.8:1) REDACTED:551 — `.folder-item.selected` sets color: white on background-color: #ff6b35 — 2.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 (2.8:1) REDACTED:690 — `.message-highlight` sets color: white on background-color: #ff6b35 — 2.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 (2.8:1) REDACTED:1442 — `.retry-messages` sets color: white on background-color: #ff6b35 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · MarkdownCopier.processElement (cyclomatic 16) · ×6
  • MarkdownCopier.processElement (cyclomatic 16) dashboard/public/blog/heygen-best-practices-skill/index.html:796 — MarkdownCopier.processElement has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 16) dashboard/public/blog/neon-open-source-program/index.html:807 — MarkdownCopier.processElement has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 16) dashboard/public/blog/react-best-practices-skill/index.html:732 — MarkdownCopier.processElement has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 16) docs/blog/heygen-best-practices-skill/index.html:796 — MarkdownCopier.processElement has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 16) docs/blog/neon-open-source-program/index.html:807 — MarkdownCopier.processElement has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • MarkdownCopier.processElement (cyclomatic 16) docs/blog/react-best-practices-skill/index.html:732 — MarkdownCopier.processElement has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:20 — cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:20-82 | cli-tool/components/skills/development/skill-creator/scripts/package_skill.py:43-108 | cli-tool/components/skills/development/skill-development/scripts/package_skill.py:43-108 | cli-tool/components/skills/productivity/skill-creator/scripts/package_skill.py:43-108 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:86 — cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:86-106 | cli-tool/components/skills/development/skill-creator/scripts/package_skill.py:112-132 | cli-tool/components/skills/development/skill-development/scripts/package_skill.py:112-132 | cli-tool/components/skills/productivity/skill-creator/scripts/package_skill.py:112-132 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:21 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_structure.py:21-88 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_structure.py:21-88 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:21-88 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_structure.py:21-88 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:92 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_structure.py:92-111 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_structure.py:92-111 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:92-111 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_structure.py:92-111 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:23 — cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:23-40 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:44-68 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:111-154 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:216-238 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:30 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:30-134 | cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:748-833 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py:33-136 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:683-759 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×6
  • Duplicated block (7 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:220 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:220-226 | cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:282-288 — 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 (7 lines × 2) cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:303 — cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:303-309 | cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:360-366 — 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) cli-tool/components/skills/scientific/torch_geometric/scripts/benchmark_model.py:32 — cli-tool/components/skills/scientific/torch_geometric/scripts/benchmark_model.py:32-38 | cli-tool/components/skills/scientific/torch_geometric/scripts/benchmark_model.py:67-73 — 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 `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 × 2) cli-tool/components/skills/scientific/drugbank-database/scripts/drugbank_helper.py:186 — cli-tool/components/skills/scientific/drugbank-database/scripts/drugbank_helper.py:186-192 | cli-tool/components/skills/scientific/drugbank-database/scripts/drugbank_helper.py:195-201 — 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) cli-tool/components/skills/media/screenshot/scripts/macos_display_info.swift:13 — cli-tool/components/skills/media/screenshot/scripts/macos_display_info.swift:13-19 | cli-tool/components/skills/media/screenshot/scripts/macos_window_info.swift:117-123 — 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 `cli-tool/components/skills/media/screenshot/scripts/macos_display_info.swift:13` 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.
  • Duplicated block (7 lines × 2) cli-tool/components/skills/media/screenshot/scripts/macos_display_info.swift:13 — cli-tool/components/skills/media/screenshot/scripts/macos_display_info.swift:13-19 | cli-tool/components/skills/media/screenshot/scripts/macos_permissions.swift:31-37 — 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 `cli-tool/components/skills/media/screenshot/scripts/macos_display_info.swift:13` 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.
D2 · Cognitive Complexity · claude_code_templates · ×5
  • claude_code_templates::commands::install::install_multiple (cognitive 27) cli-rust/src/commands/install.rs:623 — claude_code_templates::commands::install::install_multiple has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 6, boolean chains 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.
  • claude_code_templates::commands::install::has_setting_conflicts (cognitive 24) cli-rust/src/commands/install.rs:361 — claude_code_templates::commands::install::has_setting_conflicts has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (4 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.
  • claude_code_templates::commands::install::install_setting (cognitive 23) cli-rust/src/commands/install.rs:229 — claude_code_templates::commands::install::install_setting has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3 (5 pts), loops 2 (3 pts), boolean chains 2 (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.
  • claude_code_templates::github::walk (cognitive 20) cli-rust/src/github.rs:75 — claude_code_templates::github::walk has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 2 (7 pts), boolean chains 1, loops 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.
  • claude_code_templates::commands::install::install_hook (cognitive 16) cli-rust/src/commands/install.rs:396 — claude_code_templates::commands::install::install_hook has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 3 (5 pts), boolean chains 1, loops 1 (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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5
  • Duplicated block (8 lines × 2) cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:237 — cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:237-244 | cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:362-369 — 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 (8 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:407 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:407-414 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:394-401 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:417` calls `print_exc` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:402` 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 (8 lines × 2) cli-tool/components/skills/scientific/treatment-plans/scripts/timeline_generator.py:87 — cli-tool/components/skills/scientific/treatment-plans/scripts/timeline_generator.py:87-94 | cli-tool/components/skills/scientific/treatment-plans/scripts/timeline_generator.py:98-105 — 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. 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 (8 lines × 2) cli-rust/src/commands/install.rs:338 — cli-rust/src/commands/install.rs:338-345 | cli-rust/src/commands/install.rs:484-491 — 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 (8 lines × 2) cli-rust/src/merge.rs:43 — cli-rust/src/merge.rs:43-50 | cli-rust/src/merge.rs:100-107 — 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 `cli-rust/src/merge.rs:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×4
  • Heading level jumps from h1 to h3 REDACTED:2099 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:341 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 REDACTED:2099 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 dashboard/src/components/JobsView.tsx:575 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×4
  • MethodTooLong: ChatsMobile.setupRoutes REDACTED:120 — MethodTooLong — setupRoutes runs 418 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 318 over it, 4.18× 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.
  • MethodTooLong: ClaudeAnalytics.setupWebServer REDACTED:609 — MethodTooLong — setupWebServer runs 391 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 291 over it, 3.91× 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.
  • MethodTooLong: ClaudeAnalytics.getClaudeSessionInfo REDACTED:1636 — MethodTooLong — getClaudeSessionInfo runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.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.
  • MethodTooLong: TrendingPage.renderChart docs/js/trending.js:204 — MethodTooLong — renderChart runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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 (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py:447 — cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py:447-469 | cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py:476-495 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:48 — cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:48-67 | cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:71-93 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py:63 — cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py:63-88 | cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py:91-110 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) cli-tool/components/skills/scientific/ensembl-database/scripts/ensembl_query.py:142 — cli-tool/components/skills/scientific/ensembl-database/scripts/ensembl_query.py:142-162 | cli-tool/components/skills/scientific/ensembl-database/scripts/ensembl_query.py:170-189 — These two members are one piece of code written twice and then edited apart: 20 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 · Duplicated block (14 lines × 2) · ×4
  • Duplicated block (14 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:168 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:168-181 | cli-tool/components/skills/video/sora/scripts/sora.py:339-352 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (14 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:287 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:287-300 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:287-300 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (14 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:388 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:388-401 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:379-392 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:404` calls `get`, `_log` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:394` 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 (14 lines × 2) cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py:318 — cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py:318-331 | cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py:352-365 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×4
  • Duplicated block (9 lines × 2) cli-tool/components/agents/obsidian-ops-team/Scripts/metadata_adder.py:184 — cli-tool/components/agents/obsidian-ops-team/Scripts/metadata_adder.py:184-192 | cli-tool/components/agents/obsidian-ops-team/Scripts/tag_standardizer.py:371-379 — 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 (9 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:230 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:230-238 | cli-tool/components/skills/scientific/deepchem/scripts/predict_solubility.py:104-113 — 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 (9 lines × 2) cli-tool/components/skills/scientific/clinical-decision-support/scripts/create_cohort_tables.py:165 — cli-tool/components/skills/scientific/clinical-decision-support/scripts/create_cohort_tables.py:165-173 | cli-tool/components/skills/scientific/clinical-decision-support/scripts/create_cohort_tables.py:176-184 — 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) REDACTED:39 — REDACTED:39-47 | REDACTED:39-47 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:149 — cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:149-155 | cli-tool/components/skills/development/database-design/scripts/schema_validator.py:95-101 | cli-tool/components/skills/development/lint-and-validate/scripts/lint_runner.py:105-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
  • Duplicated block (7 lines × 3) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:395 — cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:395-401 | cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:379-385 | cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:88-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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 (7 lines × 3) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:155 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:155-161 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:91-97 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:150-156 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. 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) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:440 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:440-446 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:167-173 | cli-tool/components/skills/video/sora/scripts/sora.py:310-316 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×4
  • Duplicated block (5 lines × 3) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:375 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:375-379 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:272-276 | cli-tool/components/skills/video/sora/scripts/sora.py:268-272 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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 (5 lines × 3) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:432 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:432-436 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:159-163 | cli-tool/components/skills/video/sora/scripts/sora.py:302-306 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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 (5 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:53 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:53-57 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:53-57 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:53-57 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (5 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:61 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:61-65 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:61-65 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:61-65 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D6 · Cohesion (LCOM4) · Low cohesion · ×4
  • Low cohesion: ClaudeAnalytics (LCOM4 8) REDACTED:20 — ClaudeAnalytics's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TrendingPage (LCOM4 5) docs/js/trending.js:6 — TrendingPage's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: StateCalculator (LCOM4 4) cli-tool/src/analytics/core/StateCalculator.js:7 — StateCalculator's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WorkflowManager (LCOM4 4) docs/js/workflows-events.js:3 — WorkflowManager's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×3
  • Low contrast colour pair in CSS (3.1:1) cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:235 — `.button` sets color: white on background-color: #d97757 — 3.1: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.1:1) cli-tool/components/skills/development/skill-creator/assets/eval_review.html:19 — `.btn-export` sets color: white on background-color: #d97757 — 3.1: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.1:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:467 — `.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.1 · ×3
  • Low contrast colour pair in CSS (2.1:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:83 — `.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.1:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:136 — `.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.1:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:221 — `.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D2 · Cognitive Complexity · jev-vercel-sandbox.register · ×3
  • jev-vercel-sandbox.register::runJob (cognitive 22) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:618 — jev-vercel-sandbox.register::runJob has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 6 (7 pts), boolean chains 3, error handling 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. This shape REPEATS in the file: 2 other methods here (jev-vercel-sandbox.register::applyJob, jev-vercel-sandbox.register::detect) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
  • jev-vercel-sandbox.register::detect (cognitive 21) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:747 — jev-vercel-sandbox.register::detect has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 1 (3 pts), error handling 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. This shape REPEATS in the file: 2 other methods here (jev-vercel-sandbox.register::runJob, jev-vercel-sandbox.register::applyJob) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
  • jev-vercel-sandbox.register::applyJob (cognitive 16) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:703 — jev-vercel-sandbox.register::applyJob has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 4, error handling 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. This shape REPEATS in the file: 2 other methods here (jev-vercel-sandbox.register::runJob, jev-vercel-sandbox.register::detect) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×3
  • Edited copy of a member (31 corresponding lines) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:91 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:91-161 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:101-156 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:24 — cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:24-62 | cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:66-96 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:253 — cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:253-283 | cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:287-318 — These two members are one piece of code written twice and then edited apart: 31 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 · Members sharing a duplicated core (20 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (20 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:23 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:23-37 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:23-37 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:23-37 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:23-37 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:23-37 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:23-37 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:23-37 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:23-37 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:23-37 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:23-37 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:23-37 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:23-37 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:23-37 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:23-37 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:23-37 — These 20 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 20 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 20 times.
  • Members sharing a duplicated core (20 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:48 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:48-59 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:48-59 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:48-59 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:48-59 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:48-59 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:48-59 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:48-59 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:48-59 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:48-59 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:48-59 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:48-59 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:48-59 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:48-59 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:48-59 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:48-59 — These 20 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 20 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 20 times.
  • Members sharing a duplicated core (20 members, 50+ identical tokens) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:62 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:62-69 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:62-69 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:62-69 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:62-69 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:62-69 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:62-69 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:62-69 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:62-69 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:62-69 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:62-69 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:62-69 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:62-69 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:62-69 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:62-69 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:62-69 — These 20 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 20 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 20 times.
D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×3
  • Edited copy of a member (52 corresponding lines) cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:19 — cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:19-72 | cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:75-126 — These two members are one piece of code written twice and then edited apart: 52 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 (52 corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:284 — cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:284-346 | cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:215-266 — These two members are one piece of code written twice and then edited apart: 52 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 (52 corresponding lines) cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:182 — cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:182-233 | cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:237-293 — These two members are one piece of code written twice and then edited apart: 52 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 (19 corresponding lines) · ×3
  • Edited copy of a member (19 corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:456 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:456-474 | cli-tool/components/skills/video/sora/scripts/sora.py:527-545 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:140 — cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:140-159 | cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:162-180 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) cli-tool/components/skills/scientific/clinicaltrials-database/scripts/query_clinicaltrials.py:97 — cli-tool/components/skills/scientific/clinicaltrials-database/scripts/query_clinicaltrials.py:97-116 | cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py:71-89 — These two members are one piece of code written twice and then edited apart: 19 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 (10 corresponding lines) · ×3
  • Edited copy of a member (10 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:214 — cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:214-223 | cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:153-162 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:19 — cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:19-37 | cli-tool/components/skills/scientific/treatment-plans/scripts/check_completeness.py:43-52 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:434 — cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:434-443 | cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:446-455 — These two members are one piece of code written twice and then edited apart: 10 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 (28 corresponding lines) · ×3
  • Edited copy of a member (28 corresponding lines) cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py:304 — cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py:304-331 | cli-tool/components/skills/web-development/shopify-development/scripts/shopify_graphql.py:338-365 — 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.
  • Edited copy of a member (28 corresponding lines) cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:109 — cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:109-137 | cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:146-173 — 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.
  • Edited copy of a member (28 corresponding lines) cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py:38 — cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py:38-67 | cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py:112-139 — 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 · Duplicated block (26 lines × 2) · ×3
  • Duplicated block (26 lines × 2) cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py:274 — cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py:274-299 | cli-tool/components/skills/productivity/skill-creator/scripts/init_skill.py:274-299 — before extracting anything, compare `cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py` and `cli-tool/components/skills/productivity/skill-creator/scripts/init_skill.py` as WHOLE FILES: 100% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (26 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:28 — cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:28-53 | cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:44-69 — 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 (26 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:66 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:66-91 | cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py:13-38 — before extracting anything, compare `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py` and `cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 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 `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:66` 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×3
  • Duplicated block (23 lines × 2) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:72 — cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:72-94 | scripts/generate_star_history.py:46-68 — before extracting anything, compare `cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py` and `scripts/generate_star_history.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:72` 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 (23 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:131 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:131-153 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:126-148 — 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 `cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:126` 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.
  • Duplicated block (23 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:89 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:89-111 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:89-111 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×3
  • Duplicated block (22 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:186 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:186-207 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:226-247 — 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 (22 lines × 2) cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:46 — cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:46-67 | cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py:45-66 — before extracting anything, compare `cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py` and `cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 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 (22 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:109 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:109-130 | cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py:94-115 — before extracting anything, compare `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py` and `cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 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 `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:109` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3
  • Duplicated block (19 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:353 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:353-371 | cli-tool/components/skills/video/sora/scripts/sora.py:246-264 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (19 lines × 2) cli-tool/components/skills/scientific/uspto-database/scripts/trademark_client.py:43 — cli-tool/components/skills/scientific/uspto-database/scripts/trademark_client.py:43-61 | cli-tool/components/skills/scientific/uspto-database/scripts/trademark_client.py:64-82 — 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 (19 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:37 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:37-55 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:37-55 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×3
  • Duplicated block (12 lines × 3) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:417 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:417-428 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:144-155 | cli-tool/components/skills/video/sora/scripts/sora.py:287-298 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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 (12 lines × 3) cli-tool/components/skills/development/skill-development/scripts/package_skill.py:28 — cli-tool/components/skills/development/skill-creator/scripts/package_skill.py:28-39 | cli-tool/components/skills/development/skill-development/scripts/package_skill.py:28-39 | cli-tool/components/skills/productivity/skill-creator/scripts/package_skill.py:28-39 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/package_skill.py` and `cli-tool/components/skills/development/skill-development/scripts/package_skill.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (12 lines × 3) cli-tool/components/skills/scientific/deeptools/scripts/workflow_generator.py:33 — cli-tool/components/skills/scientific/deeptools/scripts/workflow_generator.py:33-44 | cli-tool/components/skills/scientific/deeptools/scripts/workflow_generator.py:108-119 | cli-tool/components/skills/scientific/deeptools/scripts/workflow_generator.py:276-287 — 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. 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, `cli-tool/components/skills/scientific/deeptools/scripts/workflow_generator.py:119` calls `get` and `cli-tool/components/skills/scientific/deeptools/scripts/workflow_generator.py:44` 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:319 — cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:319-330 | cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:244-255 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:331` calls `get` and `cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:257` 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 (12 lines × 2) cli-tool/components/skills/enterprise-communication/session-handoff/scripts/check_staleness.py:26 — cli-tool/components/skills/enterprise-communication/session-handoff/scripts/check_staleness.py:26-37 | cli-tool/components/skills/enterprise-communication/session-handoff/scripts/create_handoff.py:30-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. 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 (12 lines × 2) cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:31 — cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py:31-42 | cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py:30-41 — before extracting anything, compare `cli-tool/components/skills/scientific/labarchive-integration/scripts/entry_operations.py` and `cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 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.
AC4 · Keyboard semantics · Modal dialog does not manage focus · ×2
  • Modal dialog does not manage focus dashboard/src/components/CertificationModal.tsx:95 — This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, 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 dashboard/src/components/StackHarness.astro:237 — This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, 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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.0 · ×2
  • Low contrast colour pair in CSS (4.0:1) cli-tool/components/skills/ai-research/loki-mode/autonomy/.loki/dashboard/index.html:257 — `.task-type` sets color: #718096 on background-color: #FFFFFF — 4.0: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.0:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:303 — `.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.9 · ×2
  • Low contrast colour pair in CSS (2.9:1) cli-tool/components/skills/development/skill-creator/assets/eval_review.html:17 — `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.9:1) cli-tool/components/skills/development/skill-development/assets/eval_review.html:17 — `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · ChatsMobileApp.mergeMessages (cyclomatic 37) · ×2
  • ChatsMobileApp.mergeMessages (cyclomatic 37) REDACTED:4739 — ChatsMobileApp.mergeMessages has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 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.
  • ChatsMobileApp.mergeMessages (cyclomatic 37) REDACTED:4739 — ChatsMobileApp.mergeMessages has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · ChatsMobileApp.handleNewMessage (cyclomatic 31) · ×2
  • ChatsMobileApp.handleNewMessage (cyclomatic 31) REDACTED:4454 — ChatsMobileApp.handleNewMessage has cyclomatic complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
  • ChatsMobileApp.handleNewMessage (cyclomatic 31) REDACTED:4454 — ChatsMobileApp.handleNewMessage has cyclomatic complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · ChatsMobileApp.formatToolCall (cyclomatic 28) · ×2
  • ChatsMobileApp.formatToolCall (cyclomatic 28) REDACTED:3405 — ChatsMobileApp.formatToolCall has cyclomatic complexity 28 (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.
  • ChatsMobileApp.formatToolCall (cyclomatic 28) REDACTED:3405 — ChatsMobileApp.formatToolCall has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · REDACTED.populateAnalyticsModal (cyclomatic 28) · ×2
  • REDACTED.populateAnalyticsModal (cyclomatic 28) REDACTED:5176 — REDACTED.populateAnalyticsModal has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
  • REDACTED.populateAnalyticsModal (cyclomatic 28) REDACTED:5176 — REDACTED.populateAnalyticsModal has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · ChatsMobileApp.analyzeConversationStatus (cyclomatic 26) · ×2
  • ChatsMobileApp.analyzeConversationStatus (cyclomatic 26) REDACTED:4610 — ChatsMobileApp.analyzeConversationStatus has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 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.
  • ChatsMobileApp.analyzeConversationStatus (cyclomatic 26) REDACTED:4610 — ChatsMobileApp.analyzeConversationStatus has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · jev-vercel-sandbox.register · ×2
  • jev-vercel-sandbox.register::applyJob (cyclomatic 23) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:703 — jev-vercel-sandbox.register::applyJob 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. This shape REPEATS in the file: one other method here (jev-vercel-sandbox.register::runJob) 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.
  • jev-vercel-sandbox.register::runJob (cyclomatic 20) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:618 — jev-vercel-sandbox.register::runJob 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. This shape REPEATS in the file: one other method here (jev-vercel-sandbox.register::applyJob) 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.
D1 · Cyclomatic Complexity · research_lookup.main (cyclomatic 22) · ×2
  • research_lookup.main (cyclomatic 22) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:316 — research_lookup.main 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.
  • research_lookup.main (cyclomatic 22) cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:316 — research_lookup.main 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.
D1 · Cyclomatic Complexity · ChatsMobileApp.renderMessage (cyclomatic 20) · ×2
  • ChatsMobileApp.renderMessage (cyclomatic 20) REDACTED:3245 — ChatsMobileApp.renderMessage has cyclomatic complexity 20 (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.
  • ChatsMobileApp.renderMessage (cyclomatic 20) REDACTED:3245 — ChatsMobileApp.renderMessage has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · claude_code_templates · ×2
  • claude_code_templates::commands::install::install_multiple (cyclomatic 20) cli-rust/src/commands/install.rs:623 — claude_code_templates::commands::install::install_multiple 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.
  • claude_code_templates::commands::install::install_setting (cyclomatic 17) cli-rust/src/commands/install.rs:229 — claude_code_templates::commands::install::install_setting 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.
D1 · Cyclomatic Complexity · ChatsMobileApp.loadMoreMessages (cyclomatic 18) · ×2
  • ChatsMobileApp.loadMoreMessages (cyclomatic 18) REDACTED:3014 — ChatsMobileApp.loadMoreMessages 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.
  • ChatsMobileApp.loadMoreMessages (cyclomatic 18) REDACTED:3014 — ChatsMobileApp.loadMoreMessages 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.
D2 · Cognitive Complexity · research_lookup.main (cognitive 55) · ×2
  • research_lookup.main (cognitive 55) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:316 — research_lookup.main has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (36 pts), loops 4 (12 pts), ternaries 1 (5 pts), boolean chains 1, error handling 1 (nesting depth added 33). 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.
  • research_lookup.main (cognitive 55) cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:316 — research_lookup.main has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (36 pts), loops 4 (12 pts), ternaries 1 (5 pts), boolean chains 1, error handling 1 (nesting depth added 33). 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.
D2 · Cognitive Complexity · ChatsMobileApp.mergeMessages (cognitive 41) · ×2
  • ChatsMobileApp.mergeMessages (cognitive 41) REDACTED:4739 — ChatsMobileApp.mergeMessages has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 17, if/else 11 (15 pts), ternaries 5 (6 pts), loops 1 (3 pts) (nesting depth added 7). Of this number, 40 points are the body's own statements and 1 belongs 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, 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.
  • ChatsMobileApp.mergeMessages (cognitive 41) REDACTED:4739 — ChatsMobileApp.mergeMessages has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 17, if/else 11 (15 pts), ternaries 5 (6 pts), loops 1 (3 pts) (nesting depth added 7). Of this number, 40 points are the body's own statements and 1 belongs 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, 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.
D2 · Cognitive Complexity · ChatsMobileApp.handleNewMessage (cognitive 39) · ×2
  • ChatsMobileApp.handleNewMessage (cognitive 39) REDACTED:4454 — ChatsMobileApp.handleNewMessage has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 17, if/else 10 (12 pts), ternaries 5 (10 pts) (nesting depth added 7). Of this number, 38 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
  • ChatsMobileApp.handleNewMessage (cognitive 39) REDACTED:4454 — ChatsMobileApp.handleNewMessage has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 17, if/else 10 (12 pts), ternaries 5 (10 pts) (nesting depth added 7). Of this number, 38 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · ChatsMobileApp.analyzeConversationStatus (cognitive 39) · ×2
  • ChatsMobileApp.analyzeConversationStatus (cognitive 39) REDACTED:4610 — ChatsMobileApp.analyzeConversationStatus has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 8, ternaries 3 (7 pts) (nesting depth added 11). Of this number, 30 points are the body's own statements and 9 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.
  • ChatsMobileApp.analyzeConversationStatus (cognitive 39) REDACTED:4610 — ChatsMobileApp.analyzeConversationStatus has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 8, ternaries 3 (7 pts) (nesting depth added 11). Of this number, 30 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · REDACTED.populateAnalyticsModal (cognitive 36) · ×2
  • REDACTED.populateAnalyticsModal (cognitive 36) REDACTED:5176 — REDACTED.populateAnalyticsModal has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 15, ternaries 1 (nesting depth added 7). Of this number, 35 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
  • REDACTED.populateAnalyticsModal (cognitive 36) REDACTED:5176 — REDACTED.populateAnalyticsModal has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 15, ternaries 1 (nesting depth added 7). Of this number, 35 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D2 · Cognitive Complexity · ChatsMobileApp.formatToolCall (cognitive 27) · ×2
  • ChatsMobileApp.formatToolCall (cognitive 27) REDACTED:3405 — ChatsMobileApp.formatToolCall has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (11 pts), ternaries 3 (5 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.
  • ChatsMobileApp.formatToolCall (cognitive 27) REDACTED:3405 — ChatsMobileApp.formatToolCall has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (11 pts), ternaries 3 (5 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.
D2 · Cognitive Complexity · ChatsMobileApp.loadMoreMessages (cognitive 26) · ×2
  • ChatsMobileApp.loadMoreMessages (cognitive 26) REDACTED:3014 — ChatsMobileApp.loadMoreMessages has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 3, error handling 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.
  • ChatsMobileApp.loadMoreMessages (cognitive 26) REDACTED:3014 — ChatsMobileApp.loadMoreMessages has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 3, error handling 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.
D2 · Cognitive Complexity · ChatsMobileApp.isMessageRenderedInDOM (cognitive 22) · ×2
  • ChatsMobileApp.isMessageRenderedInDOM (cognitive 22) REDACTED:4852 — ChatsMobileApp.isMessageRenderedInDOM has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (5 pts), boolean chains 4, loops 1 (3 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.
  • ChatsMobileApp.isMessageRenderedInDOM (cognitive 22) REDACTED:4852 — ChatsMobileApp.isMessageRenderedInDOM has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (5 pts), boolean chains 4, loops 1 (3 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.
D2 · Cognitive Complexity · ChatsMobileApp.renderMessage (cognitive 21) · ×2
  • ChatsMobileApp.renderMessage (cognitive 21) REDACTED:3245 — ChatsMobileApp.renderMessage has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, ternaries 8 (10 pts), if/else 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.
  • ChatsMobileApp.renderMessage (cognitive 21) REDACTED:3245 — ChatsMobileApp.renderMessage has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, ternaries 8 (10 pts), if/else 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.
D2 · Cognitive Complexity · render-graphs.main (cognitive 16) · ×2
  • render-graphs.main (cognitive 16) cli-tool/components/skills/development/writing-skills/render-graphs.js:84 — render-graphs.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), error handling 1 (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.
  • render-graphs.main (cognitive 16) cli-tool/components/skills/productivity/writing-skills/render-graphs.js:84 — render-graphs.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), error handling 1 (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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (15 members, 50+ identical tokens) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:42 — cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:42-61 | cli-tool/components/skills/development/senior-computer-vision/scripts/inference_optimizer.py:42-61 | cli-tool/components/skills/development/senior-computer-vision/scripts/vision_model_trainer.py:42-61 | cli-tool/components/skills/development/senior-data-engineer/scripts/data_quality_validator.py:42-61 | cli-tool/components/skills/development/senior-data-engineer/scripts/etl_performance_optimizer.py:42-61 | cli-tool/components/skills/development/senior-data-engineer/scripts/pipeline_orchestrator.py:42-61 | cli-tool/components/skills/development/senior-data-scientist/scripts/experiment_designer.py:42-61 | cli-tool/components/skills/development/senior-data-scientist/scripts/feature_engineering_pipeline.py:42-61 | cli-tool/components/skills/development/senior-data-scientist/scripts/model_evaluation_suite.py:42-61 | cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:42-61 | cli-tool/components/skills/development/senior-ml-engineer/scripts/model_deployment_pipeline.py:42-61 | cli-tool/components/skills/development/senior-ml-engineer/scripts/rag_system_builder.py:42-61 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:42-61 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:42-61 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:42-61 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
  • Members sharing a duplicated core (15 members, 50+ identical tokens) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:69 — cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:69-97 | cli-tool/components/skills/development/senior-computer-vision/scripts/inference_optimizer.py:69-97 | cli-tool/components/skills/development/senior-computer-vision/scripts/vision_model_trainer.py:69-97 | cli-tool/components/skills/development/senior-data-engineer/scripts/data_quality_validator.py:69-97 | cli-tool/components/skills/development/senior-data-engineer/scripts/etl_performance_optimizer.py:69-97 | cli-tool/components/skills/development/senior-data-engineer/scripts/pipeline_orchestrator.py:69-97 | cli-tool/components/skills/development/senior-data-scientist/scripts/experiment_designer.py:69-97 | cli-tool/components/skills/development/senior-data-scientist/scripts/feature_engineering_pipeline.py:69-97 | cli-tool/components/skills/development/senior-data-scientist/scripts/model_evaluation_suite.py:69-97 | cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:69-97 | cli-tool/components/skills/development/senior-ml-engineer/scripts/model_deployment_pipeline.py:69-97 | cli-tool/components/skills/development/senior-ml-engineer/scripts/rag_system_builder.py:69-97 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:69-97 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:69-97 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:69-97 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×2
  • Edited copy of a member (25 corresponding lines) cli-tool/components/skills/scientific/clinical-reports/scripts/compliance_checker.py:47 — cli-tool/components/skills/scientific/clinical-reports/scripts/compliance_checker.py:47-72 | cli-tool/components/skills/scientific/clinical-reports/scripts/validate_trial_report.py:59-83 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) REDACTED:145 — REDACTED:145-169 | cli-tool/components/skills/ai-research/post-training-grpo-rl-training/templates/basic_grpo_training.py:97-122 — These two members are one piece of code written twice and then edited apart: 25 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) · ×2
  • Edited copy of a member (15 corresponding lines) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:211 — cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:211-228 | scripts/generate_star_history.py:185-199 — 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.
  • Edited copy of a member (15 corresponding lines) cli-tool/components/skills/scientific/rdkit/scripts/similarity_search.py:156 — cli-tool/components/skills/scientific/rdkit/scripts/similarity_search.py:156-171 | cli-tool/components/skills/scientific/rdkit/scripts/substructure_filter.py:214-228 — 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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:291 — cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:291-301 | cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:305-317 — These two members are one piece of code written twice and then edited apart: 11 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 (11 corresponding lines) cli-tool/components/skills/scientific/uspto-database/scripts/patent_search.py:30 — cli-tool/components/skills/scientific/uspto-database/scripts/patent_search.py:30-43 | cli-tool/components/skills/scientific/uspto-database/scripts/trademark_client.py:30-40 — These two members are one piece of code written twice and then edited apart: 11 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 copies of one member (3 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 15+ corresponding lines) cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:101 — cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:101-115 | cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:118-132 | cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:286-300 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:362 — cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:362-376 | cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:388-402 | cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:70-84 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:393 — cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:393-401 | cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:378-385 | cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:87-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) cli-tool/components/hooks/monitoring/context-timeline.py:144 — cli-tool/components/hooks/monitoring/context-timeline.py:144-151 | cli-tool/components/skills/development/webapp-testing/scripts/with_server.py:24-32 | cli-tool/components/skills/security/webapp-testing/scripts/with_server.py:24-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (76 lines × 2) · ×2
  • Duplicated block (76 lines × 2) cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py:195 — cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py:195-270 | cli-tool/components/skills/productivity/skill-creator/scripts/init_skill.py:195-270 — before extracting anything, compare `cli-tool/components/skills/development/skill-creation-guide/scripts/init_skill.py` and `cli-tool/components/skills/productivity/skill-creator/scripts/init_skill.py` as WHOLE FILES: 100% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (76 lines × 2) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:121 — cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:121-196 | scripts/generate_star_history.py:95-170 — before extracting anything, compare `cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py` and `scripts/generate_star_history.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:121` 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.
D4 · Code Duplication · Duplicated block (61 lines × 3) · ×2
  • Duplicated block (61 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:86 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:86-146 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:86-146 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:86-146 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (61 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:150 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:150-210 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:150-210 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:150-210 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×2
  • Duplicated block (36 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:249 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:249-284 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:249-284 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/scientific/research-lookup/research_lookup.py:249` 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 (36 lines × 2) cli-rust/src/commands/install.rs:295 — cli-rust/src/commands/install.rs:295-330 | cli-rust/src/commands/install.rs:446-481 — 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 `cli-rust/src/commands/install.rs:295` 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:58 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:58-86 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:58-86 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (29 lines × 2) scripts/generate_components_json.py:153 — scripts/generate_components_json.py:153-181 | scripts/generate_components_json.py:184-212 — 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.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×2
  • Duplicated block (27 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:333 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:333-359 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:333-359 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:333-359 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (27 lines × 3) cli-tool/components/skills/development/skill-development/scripts/improve_description.py:21 — cli-tool/components/skills/development/skill-creator/scripts/improve_description.py:21-47 | cli-tool/components/skills/development/skill-development/scripts/improve_description.py:21-47 | cli-tool/components/skills/productivity/skill-creator/scripts/improve_description.py:21-47 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/improve_description.py` and `cli-tool/components/skills/development/skill-development/scripts/improve_description.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×2
  • Duplicated block (24–25 lines × 2) cli-tool/components/agents/obsidian-ops-team/Scripts/enhance_tag_standardizer.py:226 — cli-tool/components/agents/obsidian-ops-team/Scripts/enhance_tag_standardizer.py:226-249 | cli-tool/components/agents/obsidian-ops-team/Scripts/tag_standardizer.py:137-161 — 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 (24–25 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:286 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:286-310 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:282-305 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×2
  • Duplicated block (20–21 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:622 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:622-641 | cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:680-700 — 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 (20–21 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:57 — cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:57-76 | cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:73-93 — 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 `cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:57` 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.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_loop.py:25 — cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:25-44 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:25-44 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:25-44 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_loop.py` and `cli-tool/components/skills/development/skill-development/scripts/run_loop.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 333 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (20 lines × 3) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:132 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:132-153 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:70-89 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:129-148 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×2
  • Duplicated block (19 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:362 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:362-380 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:362-380 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:362-380 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 3) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:46 — cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py:46-64 | cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:46-64 | cli-tool/components/skills/productivity/skill-creator/scripts/aggregate_benchmark.py:46-64 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py` and `cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 337 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×2
  • Duplicated block (18–19 lines × 2) cli-tool/components/skills/scientific/pubchem-database/scripts/bioactivity_query.py:164 — cli-tool/components/skills/scientific/pubchem-database/scripts/bioactivity_query.py:164-182 | cli-tool/components/skills/scientific/pubchem-database/scripts/bioactivity_query.py:186-203 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `max_results` to `int = 100` in one and `int = 1000` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (18–19 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:354 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:354-372 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:360-377 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×2
  • Duplicated block (18 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:289 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:289-306 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:289-306 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:289-306 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 3) cli-tool/components/skills/development/skill-development/scripts/generate_report.py:305 — cli-tool/components/skills/development/skill-creator/scripts/generate_report.py:305-322 | cli-tool/components/skills/development/skill-development/scripts/generate_report.py:305-322 | cli-tool/components/skills/productivity/skill-creator/scripts/generate_report.py:305-322 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/generate_report.py` and `cli-tool/components/skills/development/skill-development/scripts/generate_report.py` as WHOLE FILES: 100% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/search_google_scholar.py:259 — cli-tool/components/skills/scientific/citation-management/scripts/search_google_scholar.py:259-275 | cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:377-393 — 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 (17 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:118 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:118-134 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py:120-136 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:69 — cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:69-84 | cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:119-134 — 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 (16 lines × 2) cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py:91 — cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py:91-106 | cli-tool/components/skills/scientific/pytorch-lightning/scripts/template_lightning_module.py:113-128 — 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×2
  • Duplicated block (14–15 lines × 2) cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py:447 — cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py:447-461 | cli-tool/components/skills/business-marketing/app-store-optimization/launch_checklist.py:476-489 — 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 (14–15 lines × 2) cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:65 — cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:65-79 | cli-tool/components/skills/scientific/gene-database/scripts/batch_gene_lookup.py:119-132 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:79 — cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:79-93 | cli-tool/components/skills/utilities/geo-fundamentals/scripts/geo_checker.py:82-96 — 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 (15 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:460 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:460-474 | cli-tool/components/skills/video/sora/scripts/sora.py:531-545 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6–7 lines × 3) · ×2
  • Duplicated block (6–7 lines × 3) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:101 — cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:101-107 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:178-183 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:207-212 — 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. 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–7 lines × 3) cli-tool/components/skills/scientific/rdkit/scripts/molecular_properties.py:112 — cli-tool/components/skills/scientific/rdkit/scripts/molecular_properties.py:112-118 | cli-tool/components/skills/scientific/rdkit/scripts/similarity_search.py:68-73 | cli-tool/components/skills/scientific/rdkit/scripts/substructure_filter.py:77-82 — 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 all 3 call sites, so a change lands once. 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. 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×2
  • Duplicated block (6 lines × 4) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:35 — cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:35-40 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:62-68 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:148-154 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:233-238 — 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. 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 × 4) cli-rust/src/merge.rs:40 — cli-rust/src/merge.rs:40-45 | cli-rust/src/merge.rs:65-70 | cli-rust/src/merge.rs:85-90 | cli-rust/src/merge.rs:97-102 — 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 `cli-rust/src/merge.rs:40` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:47 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:47-53 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:56-62 | cli-tool/components/skills/media/transcribe/scripts/transcribe_diarize.py:34-40 | cli-tool/components/skills/video/sora/scripts/sora.py:51-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. 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 (7 lines × 4) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:24 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py:24-30 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py:24-30 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:24-30 | cli-tool/components/skills/document-processing/pdf/scripts/fill_pdf_form_with_annotations.py:24-30 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:325 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:325-330 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:325-330 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:325-330 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) cli-rust/src/commands/install.rs:147 — cli-rust/src/commands/install.rs:147-152 | cli-rust/src/commands/install.rs:232-237 | cli-rust/src/commands/install.rs:399-404 — 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 `cli-rust/src/commands/install.rs:147` 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.
P12 · CI test-gate honesty · Test failure does not fail the CI gate · ×2
  • Test failure does not fail the CI gate REDACTED:54 — `continue-on-error: true` lets the step or job that runs `cargo test --no-fail-fast 2>&1 | tee "$GITHUB_WORKSPACE/rust-test-output.txt"` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
  • Test failure does not fail the CI gate REDACTED:62 — `continue-on-error: true` lets the step or job that runs `cargo test --no-fail-fast -- --ignored 2>&1 | tee "$GITHUB_WORKSPACE/rust-test-net-output.txt"` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (5 clone groups) · ×2
  • Duplication concentrated across 6 sibling directories (5 clone groups) cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts:66 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories aitmpl, jev-model-router, jev-skill-suggestion, jev-skill-typeahead, session-chats, ultra-config under cli-tool/components/mods/productivity/. That concentration is one structural fact, not 5 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 5 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 6 sibling directories (5 clone groups) cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:28 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories creative-design, development, document-processing, productivity, scientific, video under cli-tool/components/skills/. That concentration is one structural fact, not 5 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 5 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.
R10 · Code Duplication · Wholesale file copy (61 identical lines × 2 files) · ×2
  • Wholesale file copy (61 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/invaders.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/invaders.tsx:2 · cli-tool/components/mods/games/invaders/hooks/boards/invaders.tsx:2 — 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.
  • Wholesale file copy (61 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/games/tetris.ts:3 — cli-tool/components/mods/games/cc-arcade/hooks/games/tetris.ts:3 · cli-tool/components/mods/games/tetris/hooks/games/tetris.ts:3 — 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.
R2 · Cyclomatic Complexity · Complex function Doom (cyclomatic 76, cognitive 136) · ×2
  • Complex function Doom (cyclomatic 76, cognitive 136) cli-tool/components/mods/games/cc-arcade/hooks/boards/doom.tsx:110 — Doom has cyclomatic complexity 76 and cognitive complexity 136; 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 Doom (cyclomatic 76, cognitive 136) cli-tool/components/mods/games/doom/hooks/boards/doom.tsx:110 — Doom has cyclomatic complexity 76 and cognitive complexity 136; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 76, cognitive 128) · ×2
  • Complex function (anonymous) (cyclomatic 76, cognitive 128) cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:534 — (anonymous) has cyclomatic complexity 76 and cognitive complexity 128; 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 76, cognitive 128) cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js:534 — (anonymous) has cyclomatic complexity 76 and cognitive complexity 128; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 34, cognitive 56) · ×2
  • Complex function (anonymous) (cyclomatic 34, cognitive 56) cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:422 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 56; 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 34, cognitive 56) cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js:422 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 56; 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.
R7 · Dead Code · Dead file (~979 LoC) · ×2
  • Dead file (~979 LoC) cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js — no import path from any entry point (125 application, 31 tooling, 102 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 (~979 LoC) cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~493 LoC) · ×2
  • Dead file (~493 LoC) REDACTED — no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — 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 (~493 LoC) dashboard/src/components/TrendingView.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~420 LoC) · ×2
  • Dead file (~420 LoC) cli-tool/components/mods/ui/turn-inspector/hooks/turn-inspector.tsx — no import path from any entry point (125 application, 31 tooling, 102 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 (~420 LoC) dashboard/src/components/SendToRepoModal.tsx — no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/components/MyComponentsView.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
R8 · Dependency Hygiene · Unused dependency 'geist' · ×2
  • Unused dependency 'geist' cli-tool/analytics-ui/package.json:12 — Declared in cli-tool/analytics-ui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Unused dependency 'geist' dashboard/package.json:36 — Declared in dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
AC1 · Text alternatives · <canvas> without a text alternative · ×1
  • <canvas> without a text alternative cli-tool/components/hooks/automation/plan-mode-game/index.html:419 — 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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.9 · ×1
  • Low contrast colour pair in CSS (1.9:1) REDACTED:698 — `.message-current-highlight` sets color: white on background-color: #ffaa00 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.5 · ×1
  • Low contrast colour pair in CSS (2.5:1) cli-tool/components/hooks/automation/plan-mode-game/index.html:49 — `.tab` sets color: #4b5563 on background-color: #12121f — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:163 — `.slider-container input[type="range"]` 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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.0 · ×1
  • Low contrast colour pair in CSS (3.0:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:197 — `.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.2 · ×1
  • Low contrast colour pair in CSS (3.2:1) cli-tool/components/skills/development/skill-creator/eval-viewer/viewer.html:302 — `.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · MobileAuditor.audit_file (cyclomatic 156) · ×1
  • MobileAuditor.audit_file (cyclomatic 156) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:81 — MobileAuditor.audit_file has cyclomatic complexity 156 (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.
D1 · Cyclomatic Complexity · ChatsMobile.setupRoutes (cyclomatic 140) · ×1
  • ChatsMobile.setupRoutes (cyclomatic 140) REDACTED:120 — ChatsMobile.setupRoutes has cyclomatic complexity 140 (threshold 15). Most of this is not in the body itself: 1 of the 140 points is its own statement and the rest belongs to 26 function literals inside it that branch (lines 520, 213, 607, …). 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.
D1 · Cyclomatic Complexity · jev-skill-suggestion.register (cyclomatic 113) · ×1
  • jev-skill-suggestion.register (cyclomatic 113) cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:130 — jev-skill-suggestion.register has cyclomatic complexity 113 (threshold 15). Most of this is not in the body itself: 9 of the 113 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 248, a function literal at line 489, a function literal at line 211, …). 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.
D1 · Cyclomatic Complexity · jev-auto-mode.register (cyclomatic 108) · ×1
  • jev-auto-mode.register (cyclomatic 108) cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:121 — jev-auto-mode.register has cyclomatic complexity 108 (threshold 15). Most of this is not in the body itself: 8 of the 108 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 187, a function literal at line 357, a function literal at line 330, …). 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.
D1 · Cyclomatic Complexity · SkillExplorer.SkillExplorer (cyclomatic 104) · ×1
  • SkillExplorer.SkillExplorer (cyclomatic 104) REDACTED:144 — SkillExplorer.SkillExplorer has cyclomatic complexity 104 (threshold 15). Of this number, 38 points are the body's own statements and 66 belong to 20 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.
D1 · Cyclomatic Complexity · ComponentGrid.ComponentGrid (cyclomatic 96) · ×1
  • ComponentGrid.ComponentGrid (cyclomatic 96) dashboard/src/components/ComponentGrid.tsx:41 — ComponentGrid.ComponentGrid has cyclomatic complexity 96 (threshold 15). Of this number, 33 points are the body's own statements and 63 belong to 20 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.
D1 · Cyclomatic Complexity · register.register (cyclomatic 95) · ×1
  • register.register (cyclomatic 95) cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx:159 — register.register has cyclomatic complexity 95 (threshold 15). Most of this is not in the body itself: 7 of the 95 points are its own statements and the rest belongs to 23 function items inside it that branch (a function literal at line 261, a function literal at line 322, a function literal at line 399, …). 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.
D1 · Cyclomatic Complexity · prompt-cache-control.register (cyclomatic 94) · ×1
  • prompt-cache-control.register (cyclomatic 94) cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:171 — prompt-cache-control.register has cyclomatic complexity 94 (threshold 15). Most of this is not in the body itself: 1 of the 94 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 360, 405, 229, …). 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.
D1 · Cyclomatic Complexity · index.createClaudeConfig (cyclomatic 93) · ×1
  • index.createClaudeConfig (cyclomatic 93) cli-tool/src/index.js:86 — index.createClaudeConfig has cyclomatic complexity 93 (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.
D1 · Cyclomatic Complexity · register.register (cyclomatic 93) · ×1
  • register.register (cyclomatic 93) cli-tool/components/mods/games/chess/hooks/register.tsx:217 — register.register has cyclomatic complexity 93 (threshold 15). Most of this is not in the body itself: 9 of the 93 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 405, a function literal at line 349, a function literal at line 253, …). 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.
D1 · Cyclomatic Complexity · setupWebServer (cyclomatic 87) · ×1
  • setupWebServer (cyclomatic 87) REDACTED:609 — setupWebServer has cyclomatic complexity 87 (threshold 15). Most of this is not in the body itself: 1 of the 87 points is its own statement and the rest belongs to 36 function literals inside it that branch (lines 904, 728, 979, …). 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.
D1 · Cyclomatic Complexity · build_ownership_map.build_ownership_map (cyclomatic 86) · ×1
  • build_ownership_map.build_ownership_map (cyclomatic 86) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:421 — build_ownership_map.build_ownership_map has cyclomatic complexity 86 (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.
D1 · Cyclomatic Complexity · jev-guardrails.register (cyclomatic 85) · ×1
  • jev-guardrails.register (cyclomatic 85) cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts:98 — jev-guardrails.register has cyclomatic complexity 85 (threshold 15). Most of this is not in the body itself: 12 of the 85 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 278, a function literal at line 173, setupLines, …). 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.
D1 · Cyclomatic Complexity · register.register (cyclomatic 83) · ×1
  • register.register (cyclomatic 83) cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:130 — register.register has cyclomatic complexity 83 (threshold 15). Most of this is not in the body itself: 8 of the 83 points are its own statements and the rest belongs to 20 function literals inside it that branch (lines 201, 488, 150, …). 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.
D1 · Cyclomatic Complexity · stack-viewer.register (cyclomatic 80) · ×1
  • stack-viewer.register (cyclomatic 80) cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx:58 — stack-viewer.register has cyclomatic complexity 80 (threshold 15). Most of this is not in the body itself: 1 of the 80 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 74, 315, 355, …). 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.
D1 · Cyclomatic Complexity · turn-inspector.register (cyclomatic 79) · ×1
  • turn-inspector.register (cyclomatic 79) cli-tool/components/mods/ui/turn-inspector/hooks/turn-inspector.tsx:71 — turn-inspector.register has cyclomatic complexity 79 (threshold 15). Most of this is not in the body itself: 1 of the 79 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 242, 157, 213, …). 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.
D1 · Cyclomatic Complexity · viewer.html.renderBenchmark (cyclomatic 79) · ×1
  • viewer.html.renderBenchmark (cyclomatic 79) cli-tool/components/skills/development/skill-development/eval-viewer/viewer.html:1114 — viewer.html.renderBenchmark has cyclomatic complexity 79 (threshold 15). Of this number, 66 points are the body's own statements and 13 belong to 7 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.
D1 · Cyclomatic Complexity · bluesky-feed.register (cyclomatic 78) · ×1
  • bluesky-feed.register (cyclomatic 78) cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:63 — bluesky-feed.register has cyclomatic complexity 78 (threshold 15). Most of this is not in the body itself: 2 of the 78 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 237, a function literal at line 200, a function literal at line 162, …). 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.
D1 · Cyclomatic Complexity · session-chats.register (cyclomatic 77) · ×1
  • session-chats.register (cyclomatic 77) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:87 — session-chats.register has cyclomatic complexity 77 (threshold 15). Most of this is not in the body itself: 5 of the 77 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 259, 173, 213, …). 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.
D1 · Cyclomatic Complexity · JobsView.JobsView (cyclomatic 76) · ×1
  • JobsView.JobsView (cyclomatic 76) dashboard/src/components/JobsView.tsx:88 — JobsView.JobsView has cyclomatic complexity 76 (threshold 15). Of this number, 28 points are the body's own statements and 48 belong to 14 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.
D1 · Cyclomatic Complexity · MarkdownViewer.MarkdownViewer (cyclomatic 75) · ×1
  • MarkdownViewer.MarkdownViewer (cyclomatic 75) REDACTED:80 — MarkdownViewer.MarkdownViewer has cyclomatic complexity 75 (threshold 15). Of this number, 21 points are the body's own statements and 54 belong to 13 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.
D1 · Cyclomatic Complexity · hook-scanner.getHookDescription (cyclomatic 74) · ×1
  • hook-scanner.getHookDescription (cyclomatic 74) cli-tool/src/hook-scanner.js:110 — hook-scanner.getHookDescription has cyclomatic complexity 74 (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.
D1 · Cyclomatic Complexity · index.installIndividualSetting (cyclomatic 73) · ×1
  • index.installIndividualSetting (cyclomatic 73) cli-tool/src/index.js:553 — index.installIndividualSetting has cyclomatic complexity 73 (threshold 15). Of this number, 59 points are the body's own statements and 14 belong to 4 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.
D1 · Cyclomatic Complexity · component-page.openValidationModal (cyclomatic 69) · ×1
  • component-page.openValidationModal (cyclomatic 69) docs/js/component-page.js:1371 — component-page.openValidationModal has cyclomatic complexity 69 (threshold 15). Of this number, 25 points are the body's own statements and 44 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.
D1 · Cyclomatic Complexity · agent-flow.register (cyclomatic 68) · ×1
  • agent-flow.register (cyclomatic 68) cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:85 — agent-flow.register has cyclomatic complexity 68 (threshold 15). Most of this is not in the body itself: 1 of the 68 points is its own statement and the rest belongs to 16 function literals inside it that branch (lines 256, 284, 294, …). 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.
D1 · Cyclomatic Complexity · MyComponentsView.MyComponentsView (cyclomatic 66) · ×1
  • MyComponentsView.MyComponentsView (cyclomatic 66) dashboard/src/components/MyComponentsView.tsx:467 — MyComponentsView.MyComponentsView has cyclomatic complexity 66 (threshold 15). Of this number, 23 points are the body's own statements and 43 belong to 17 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.
D1 · Cyclomatic Complexity · vercel-deploys.register (cyclomatic 62) · ×1
  • vercel-deploys.register (cyclomatic 62) cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-deploys.tsx:71 — vercel-deploys.register has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 1 of the 62 points is its own statement and the rest belongs to 14 function items inside it that branch (a function literal at line 198, a function literal at line 239, a function literal at line 253, …). 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.
D1 · Cyclomatic Complexity · jev-model-router.register (cyclomatic 62) · ×1
  • jev-model-router.register (cyclomatic 62) cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts:64 — jev-model-router.register has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 10 of the 62 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 212, a function literal at line 252, a function literal at line 128, …). 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.
D1 · Cyclomatic Complexity · take_screenshot.main (cyclomatic 60) · ×1
  • take_screenshot.main (cyclomatic 60) cli-tool/components/skills/media/screenshot/scripts/take_screenshot.py:420 — take_screenshot.main has cyclomatic complexity 60 (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.
D1 · Cyclomatic Complexity · git-sidebar.register (cyclomatic 58) · ×1
  • git-sidebar.register (cyclomatic 58) cli-tool/components/mods/ui/git-sidebar/hooks/git-sidebar.tsx:101 — git-sidebar.register has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 1 of the 58 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 186, 244, 278, …). 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.
D1 · Cyclomatic Complexity · chess.pseudoMoves (cyclomatic 53) · ×1
  • chess.pseudoMoves (cyclomatic 53) cli-tool/components/mods/games/chess/hooks/chess.ts:147 — chess.pseudoMoves has cyclomatic complexity 53 (threshold 15). Of this number, 49 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · linear-tickets.register (cyclomatic 51) · ×1
  • linear-tickets.register (cyclomatic 51) cli-tool/components/mods/integrations/linear-tickets/hooks/linear-tickets.tsx:70 — linear-tickets.register has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 2 of the 51 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 190, a function literal at line 163, a function literal at line 99, …). 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.
D1 · Cyclomatic Complexity · SearchModal.SearchModal (cyclomatic 51) · ×1
  • SearchModal.SearchModal (cyclomatic 51) dashboard/src/components/SearchModal.tsx:25 — SearchModal.SearchModal has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 11 of the 51 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 55, a function literal at line 145, a function literal at line 294, …). 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.
D1 · Cyclomatic Complexity · page-audit.auditDom (cyclomatic 49) · ×1
  • page-audit.auditDom (cyclomatic 49) cli-tool/components/skills/development/senior-frontend/scripts/page-audit.mjs:5 — page-audit.auditDom has cyclomatic complexity 49 (threshold 15). Of this number, 34 points are the body's own statements and 15 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.
D1 · Cyclomatic Complexity · SaveToCollectionButton.SaveButton (cyclomatic 49) · ×1
  • SaveToCollectionButton.SaveButton (cyclomatic 49) dashboard/src/components/SaveToCollectionButton.tsx:60 — SaveToCollectionButton.SaveButton has cyclomatic complexity 49 (threshold 15). Of this number, 19 points are the body's own statements and 30 belong to 13 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.
D1 · Cyclomatic Complexity · ComponentPageManager.renderComponentCode (cyclomatic 49) · ×1
  • ComponentPageManager.renderComponentCode (cyclomatic 49) docs/js/component-page.js:599 — ComponentPageManager.renderComponentCode has cyclomatic complexity 49 (threshold 15). Of this number, 20 points are the body's own statements and 29 belong to 10 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.
D1 · Cyclomatic Complexity · SkillReviewFlow.SkillReviewFlow (cyclomatic 48) · ×1
  • SkillReviewFlow.SkillReviewFlow (cyclomatic 48) dashboard/src/components/SkillReviewFlow.tsx:276 — SkillReviewFlow.SkillReviewFlow has cyclomatic complexity 48 (threshold 15). Most of this is not in the body itself: 4 of the 48 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 442, a function literal at line 462, a function literal at line 351, …). 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.
D1 · Cyclomatic Complexity · DataCache.parseAndCorrelateToolMessages (cyclomatic 46) · ×1
  • DataCache.parseAndCorrelateToolMessages (cyclomatic 46) cli-tool/src/analytics/data/DataCache.js:142 — DataCache.parseAndCorrelateToolMessages has cyclomatic complexity 46 (threshold 15). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · index.installIndividualHook (cyclomatic 46) · ×1
  • index.installIndividualHook (cyclomatic 46) cli-tool/src/index.js:933 — index.installIndividualHook has cyclomatic complexity 46 (threshold 15). Of this number, 41 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · file-operations.copyTemplateFiles (cyclomatic 45) · ×1
  • file-operations.copyTemplateFiles (cyclomatic 45) cli-tool/src/file-operations.js:373 — file-operations.copyTemplateFiles 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.
D1 · Cyclomatic Complexity · server.server (cyclomatic 45) · ×1
  • server.server (cyclomatic 45) REDACTED:24 — server.server has cyclomatic complexity 45 (threshold 15). Of this number, 34 points are the body's own statements and 11 belong to 7 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.
D1 · Cyclomatic Complexity · neon-branch-per-session.register (cyclomatic 45) · ×1
  • neon-branch-per-session.register (cyclomatic 45) cli-tool/components/mods/integrations/neon-branch-per-session/hooks/neon-branch-per-session.ts:60 — neon-branch-per-session.register has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 5 of the 45 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 80, a function literal at line 140, a function literal at line 181, …). 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.
D1 · Cyclomatic Complexity · pudu-task.main (cyclomatic 45) · ×1
  • pudu-task.main (cyclomatic 45) cli-tool/components/skills/development/pudu-task-telemetry/scripts/pudu-task.mjs:51 — pudu-task.main has cyclomatic complexity 45 (threshold 15). Of this number, 20 points are the body's own statements and 25 belong to 4 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.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 45) · ×1
  • (anonymous) (cyclomatic 45) REDACTED:24 — (anonymous) has cyclomatic complexity 45 (threshold 15). Of this number, 34 points are the body's own statements and 11 belong to 8 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.
D1 · Cyclomatic Complexity · ceiling.apply (cyclomatic 44) · ×1
  • ceiling.apply (cyclomatic 44) cli-tool/components/mods/enterprise/policy-ceiling/hooks/ceiling.ts:85 — ceiling.apply has cyclomatic complexity 44 (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.
D1 · Cyclomatic Complexity · ComponentPageManager.renderSecurityValidation (cyclomatic 44) · ×1
  • ComponentPageManager.renderSecurityValidation (cyclomatic 44) docs/js/component-page.js:209 — ComponentPageManager.renderSecurityValidation has cyclomatic complexity 44 (threshold 15). Of this number, 26 points are the body's own statements and 18 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.
D1 · Cyclomatic Complexity · rules.ruleMatches (cyclomatic 43) · ×1
  • rules.ruleMatches (cyclomatic 43) REDACTED:635 — rules.ruleMatches has cyclomatic complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · CartSidebar.CartSidebar (cyclomatic 43) · ×1
  • CartSidebar.CartSidebar (cyclomatic 43) dashboard/src/components/CartSidebar.tsx:33 — CartSidebar.CartSidebar has cyclomatic complexity 43 (threshold 15). Of this number, 16 points are the body's own statements and 27 belong to 12 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.
D1 · Cyclomatic Complexity · prompts.getStepConfig (cyclomatic 42) · ×1
  • prompts.getStepConfig (cyclomatic 42) cli-tool/src/prompts.js:79 — prompts.getStepConfig has cyclomatic complexity 42 (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.
D1 · Cyclomatic Complexity · register.register (cyclomatic 42) · ×1
  • register.register (cyclomatic 42) cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:327 — register.register has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 1 of the 42 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 372, 506, 420, …). 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.
D1 · Cyclomatic Complexity · detect.reasonFor (cyclomatic 41) · ×1
  • detect.reasonFor (cyclomatic 41) REDACTED:177 — detect.reasonFor has cyclomatic complexity 41 (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.
D1 · Cyclomatic Complexity · stack.scanFiles (cyclomatic 41) · ×1
  • stack.scanFiles (cyclomatic 41) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:251 — stack.scanFiles has cyclomatic complexity 41 (threshold 15). Of this number, 40 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · ComponentPageManager.renderMetadataSection (cyclomatic 41) · ×1
  • ComponentPageManager.renderMetadataSection (cyclomatic 41) docs/js/component-page.js:382 — ComponentPageManager.renderMetadataSection has cyclomatic complexity 41 (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.
D1 · Cyclomatic Complexity · ComponentTerminal.ComponentTerminal (cyclomatic 39) · ×1
  • ComponentTerminal.ComponentTerminal (cyclomatic 39) dashboard/src/components/ComponentTerminal.tsx:318 — ComponentTerminal.ComponentTerminal has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 422, 351, 331, …). 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.
D1 · Cyclomatic Complexity · community_maintainers.main (cyclomatic 38) · ×1
  • community_maintainers.main (cyclomatic 38) cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:378 — community_maintainers.main has cyclomatic complexity 38 (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.
D1 · Cyclomatic Complexity · coderio-skill.main (cyclomatic 37) · ×1
  • coderio-skill.main (cyclomatic 37) cli-tool/components/skills/design-to-code/scripts/coderio-skill.mjs:100 — coderio-skill.main has cyclomatic complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · rules.gateFor (cyclomatic 36) · ×1
  • rules.gateFor (cyclomatic 36) REDACTED:268 — rules.gateFor has cyclomatic complexity 36 (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.
D1 · Cyclomatic Complexity · ollama-adapter.validateRequest (cyclomatic 36) · ×1
  • ollama-adapter.validateRequest (cyclomatic 36) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/ollama-adapter.mjs:58 — ollama-adapter.validateRequest has cyclomatic complexity 36 (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.
D1 · Cyclomatic Complexity · SendToRepoModal.SendToRepoModal (cyclomatic 36) · ×1
  • SendToRepoModal.SendToRepoModal (cyclomatic 36) dashboard/src/components/SendToRepoModal.tsx:96 — SendToRepoModal.SendToRepoModal has cyclomatic complexity 36 (threshold 15). Of this number, 17 points are the body's own statements and 19 belong to 10 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.
D1 · Cyclomatic Complexity · utils.detectProject (cyclomatic 35) · ×1
  • utils.detectProject (cyclomatic 35) cli-tool/src/utils.js:4 — utils.detectProject has cyclomatic complexity 35 (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.
D1 · Cyclomatic Complexity · index.installMultipleComponents (cyclomatic 35) · ×1
  • index.installMultipleComponents (cyclomatic 35) cli-tool/src/index.js:1979 — index.installMultipleComponents has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · search-functionality.loadComponentsForSearch (cyclomatic 35) · ×1
  • search-functionality.loadComponentsForSearch (cyclomatic 35) docs/js/search-functionality.js:133 — search-functionality.loadComponentsForSearch has cyclomatic complexity 35 (threshold 15). Of this number, 29 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · prompts.createPrompts (cyclomatic 34) · ×1
  • prompts.createPrompts (cyclomatic 34) cli-tool/src/prompts.js:278 — prompts.createPrompts has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 5 of the 34 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 420, 323, 357, …). 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.
D1 · Cyclomatic Complexity · stack.mcpSection (cyclomatic 33) · ×1
  • stack.mcpSection (cyclomatic 33) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:646 — stack.mcpSection has cyclomatic complexity 33 (threshold 15). Of this number, 19 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · certifications.validateItem (cyclomatic 33) · ×1
  • certifications.validateItem (cyclomatic 33) dashboard/src/lib/certifications.ts:191 — certifications.validateItem has cyclomatic complexity 33 (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.
D1 · Cyclomatic Complexity · subagent-read-only-guard.check_git (cyclomatic 33) · ×1
  • subagent-read-only-guard.check_git (cyclomatic 33) cli-tool/components/hooks/security/subagent-read-only-guard.py:207 — subagent-read-only-guard.check_git has cyclomatic complexity 33 (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.
D1 · Cyclomatic Complexity · ConversationAnalyzer.parseAndCorrelateToolMessages (cyclomatic 32) · ×1
  • ConversationAnalyzer.parseAndCorrelateToolMessages (cyclomatic 32) cli-tool/src/analytics/core/ConversationAnalyzer.js:275 — ConversationAnalyzer.parseAndCorrelateToolMessages has cyclomatic complexity 32 (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.
D1 · Cyclomatic Complexity · live-preview.register (cyclomatic 32) · ×1
  • live-preview.register (cyclomatic 32) cli-tool/components/mods/ui/live-preview/hooks/live-preview.tsx:109 — live-preview.register has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 166, 123, 151, …). 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.
D1 · Cyclomatic Complexity · run_eval.run_single_query (cyclomatic 32) · ×1
  • run_eval.run_single_query (cyclomatic 32) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:35 — run_eval.run_single_query has cyclomatic complexity 32 (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.
D1 · Cyclomatic Complexity · rex-tty.register · ×1
  • rex-tty.register::pane (cyclomatic 31) cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts:134 — rex-tty.register::pane has cyclomatic complexity 31 (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.
D1 · Cyclomatic Complexity · rules.bashParts (cyclomatic 31) · ×1
  • rules.bashParts (cyclomatic 31) REDACTED:407 — rules.bashParts has cyclomatic complexity 31 (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.
D1 · Cyclomatic Complexity · rules.pushTargets (cyclomatic 30) · ×1
  • rules.pushTargets (cyclomatic 30) REDACTED:171 — rules.pushTargets has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · stack.pluginsSection (cyclomatic 29) · ×1
  • stack.pluginsSection (cyclomatic 29) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:720 — stack.pluginsSection has cyclomatic complexity 29 (threshold 15). Of this number, 15 points are the body's own statements and 14 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.
D1 · Cyclomatic Complexity · model-selection.recommend (cyclomatic 29) · ×1
  • model-selection.recommend (cyclomatic 29) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/model-selection.mjs:23 — model-selection.recommend has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · MarketplacePluginsList.MarketplacePluginsList (cyclomatic 29) · ×1
  • MarketplacePluginsList.MarketplacePluginsList (cyclomatic 29) dashboard/src/components/MarketplacePluginsList.tsx:36 — MarketplacePluginsList.MarketplacePluginsList has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 12 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 143, a function literal at line 50, a function literal at line 46, …). 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.
D1 · Cyclomatic Complexity · run_loop.run_loop (cyclomatic 28) · ×1
  • run_loop.run_loop (cyclomatic 28) cli-tool/components/skills/development/skill-development/scripts/run_loop.py:47 — run_loop.run_loop has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · AgentAnalyzer.analyzeAgentUsage (cyclomatic 27) · ×1
  • AgentAnalyzer.analyzeAgentUsage (cyclomatic 27) cli-tool/src/analytics/core/AgentAnalyzer.js:40 — AgentAnalyzer.analyzeAgentUsage has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 70, 55, 140). 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.
D1 · Cyclomatic Complexity · check_docs.main (cyclomatic 27) · ×1
  • check_docs.main (cyclomatic 27) docs-site/scripts/check_docs.py:64 — check_docs.main has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · HealthChecker.analyzeSettingsStructure (cyclomatic 26) · ×1
  • HealthChecker.analyzeSettingsStructure (cyclomatic 26) cli-tool/src/health-check.js:1204 — HealthChecker.analyzeSettingsStructure has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · enzyme_pathway_builder.optimize_pathway_conditions (cyclomatic 26) · ×1
  • enzyme_pathway_builder.optimize_pathway_conditions (cyclomatic 26) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:696 — enzyme_pathway_builder.optimize_pathway_conditions has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · validate_treatment_plan.display_validation_results (cyclomatic 26) · ×1
  • validate_treatment_plan.display_validation_results (cyclomatic 26) cli-tool/components/skills/scientific/treatment-plans/scripts/validate_treatment_plan.py:173 — validate_treatment_plan.display_validation_results 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.
D1 · Cyclomatic Complexity · ChatsMobile.handleConversationChange (cyclomatic 25) · ×1
  • ChatsMobile.handleConversationChange (cyclomatic 25) REDACTED:884 — ChatsMobile.handleConversationChange has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · index.html.getToolDetail (cyclomatic 25) · ×1
  • index.html.getToolDetail (cyclomatic 25) cli-tool/components/hooks/automation/plan-mode-game/index.html:902 — index.html.getToolDetail has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · JobsPreview.JobsPreview (cyclomatic 25) · ×1
  • JobsPreview.JobsPreview (cyclomatic 25) dashboard/src/components/JobsPreview.tsx:66 — JobsPreview.JobsPreview has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 6 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 115, a function literal at line 180, handleJobClick). 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.
D1 · Cyclomatic Complexity · MyComponentsView.ProjectTreeNode (cyclomatic 25) · ×1
  • MyComponentsView.ProjectTreeNode (cyclomatic 25) dashboard/src/components/MyComponentsView.tsx:228 — MyComponentsView.ProjectTreeNode has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to 2 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.
D1 · Cyclomatic Complexity · TrendingPage.getComponentTypeLabel (cyclomatic 25) · ×1
  • TrendingPage.getComponentTypeLabel (cyclomatic 25) docs/js/trending.js:478 — TrendingPage.getComponentTypeLabel has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · enzyme_pathway_builder.generate_pathway_report (cyclomatic 25) · ×1
  • enzyme_pathway_builder.generate_pathway_report (cyclomatic 25) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:805 — enzyme_pathway_builder.generate_pathway_report 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.
D1 · Cyclomatic Complexity · CitationValidator.validate_entry (cyclomatic 25) · ×1
  • CitationValidator.validate_entry (cyclomatic 25) cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:95 — CitationValidator.validate_entry 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.
D1 · Cyclomatic Complexity · prepare_batch_csv.validate_csv (cyclomatic 25) · ×1
  • prepare_batch_csv.validate_csv (cyclomatic 25) cli-tool/components/skills/scientific/diffdock/scripts/prepare_batch_csv.py:61 — prepare_batch_csv.validate_csv 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.
D1 · Cyclomatic Complexity · StateCalculator.determineConversationState (cyclomatic 24) · ×1
  • StateCalculator.determineConversationState (cyclomatic 24) cli-tool/src/analytics/core/StateCalculator.js:20 — StateCalculator.determineConversationState has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · session-chats.detail (cyclomatic 24) · ×1
  • session-chats.detail (cyclomatic 24) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:334 — session-chats.detail has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 351, 337). 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.
D1 · Cyclomatic Complexity · rules.selfProtection (cyclomatic 24) · ×1
  • rules.selfProtection (cyclomatic 24) REDACTED:742 — rules.selfProtection has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 3 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.
D1 · Cyclomatic Complexity · web_game_playwright_client.parseArgs (cyclomatic 24) · ×1
  • web_game_playwright_client.parseArgs (cyclomatic 24) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:5 — web_game_playwright_client.parseArgs 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.
D1 · Cyclomatic Complexity · TrendingView.TrendingView (cyclomatic 24) · ×1
  • TrendingView.TrendingView (cyclomatic 24) dashboard/src/components/TrendingView.tsx:54 — TrendingView.TrendingView has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 364, a function literal at line 273, a function literal at line 371, …). 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.
D1 · Cyclomatic Complexity · IndexPageManager.collectAvailableCategories (cyclomatic 24) · ×1
  • IndexPageManager.collectAvailableCategories (cyclomatic 24) docs/js/index-events.js:409 — IndexPageManager.collectAvailableCategories has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 7 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.
D1 · Cyclomatic Complexity · design_system.format_ascii_box (cyclomatic 24) · ×1
  • design_system.format_ascii_box (cyclomatic 24) cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:236 — design_system.format_ascii_box has cyclomatic complexity 24 (threshold 15). 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.
D1 · Cyclomatic Complexity · substructure_filter.main (cyclomatic 24) · ×1
  • substructure_filter.main (cyclomatic 24) cli-tool/components/skills/scientific/rdkit/scripts/substructure_filter.py:254 — substructure_filter.main has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · validateManifest (cyclomatic 24) · ×1
  • validateManifest (cyclomatic 24) cli-tool/src/external-skill.js:49 — validateManifest has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 3 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.
D1 · Cyclomatic Complexity · file-operations.downloadDirectoryFromGitHub (cyclomatic 23) · ×1
  • file-operations.downloadDirectoryFromGitHub (cyclomatic 23) cli-tool/src/file-operations.js:74 — file-operations.downloadDirectoryFromGitHub 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.
D1 · Cyclomatic Complexity · agent-detection.detectAgentName (cyclomatic 23) · ×1
  • agent-detection.detectAgentName (cyclomatic 23) cli-tool/src/agent-detection.js:54 — agent-detection.detectAgentName 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.
D1 · Cyclomatic Complexity · index.getAvailableAgentsFromGitHub (cyclomatic 23) · ×1
  • index.getAvailableAgentsFromGitHub (cyclomatic 23) cli-tool/src/index.js:1286 — index.getAvailableAgentsFromGitHub 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.
D1 · Cyclomatic Complexity · index.installIndividualPlugin (cyclomatic 23) · ×1
  • index.installIndividualPlugin (cyclomatic 23) cli-tool/src/index.js:1643 — index.installIndividualPlugin 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.
D1 · Cyclomatic Complexity · rules.sqlCode (cyclomatic 23) · ×1
  • rules.sqlCode (cyclomatic 23) REDACTED:50 — rules.sqlCode 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.
D1 · Cyclomatic Complexity · human-gate.register (cyclomatic 23) · ×1
  • human-gate.register (cyclomatic 23) cli-tool/components/mods/security/human-gate/hooks/human-gate.ts:19 — human-gate.register has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 46, 50, 32, …). 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.
D1 · Cyclomatic Complexity · rules.parseJev (cyclomatic 23) · ×1
  • rules.parseJev (cyclomatic 23) REDACTED:244 — rules.parseJev 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.
D1 · Cyclomatic Complexity · index.formatReport (cyclomatic 23) · ×1
  • index.formatReport (cyclomatic 23) cloudflare-workers/pulse/index.js:565 — index.formatReport 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.
D1 · Cyclomatic Complexity · sign-in.showInAppDialog (cyclomatic 23) · ×1
  • sign-in.showInAppDialog (cyclomatic 23) dashboard/src/lib/sign-in.ts:84 — sign-in.showInAppDialog has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (onKey, a function literal at line 142, close, …). 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.
D1 · Cyclomatic Complexity · SkillSlideView.SkillSlideView (cyclomatic 23) · ×1
  • SkillSlideView.SkillSlideView (cyclomatic 23) REDACTED:144 — SkillSlideView.SkillSlideView has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 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.
D1 · Cyclomatic Complexity · _Builder._ingest (cyclomatic 23) · ×1
  • _Builder._ingest (cyclomatic 23) cli-tool/components/hooks/monitoring/context-timeline.py:308 — _Builder._ingest 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.
D1 · Cyclomatic Complexity · subagent-read-only-guard.tokenize (cyclomatic 23) · ×1
  • subagent-read-only-guard.tokenize (cyclomatic 23) cli-tool/components/hooks/security/subagent-read-only-guard.py:123 — subagent-read-only-guard.tokenize 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.
D1 · Cyclomatic Complexity · subagent-read-only-guard.check_program (cyclomatic 23) · ×1
  • subagent-read-only-guard.check_program (cyclomatic 23) cli-tool/components/hooks/security/subagent-read-only-guard.py:253 — subagent-read-only-guard.check_program 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.
D1 · Cyclomatic Complexity · improve_description.improve_description (cyclomatic 23) · ×1
  • improve_description.improve_description (cyclomatic 23) cli-tool/components/skills/development/skill-development/scripts/improve_description.py:50 — improve_description.improve_description 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.
D1 · Cyclomatic Complexity · quick_validate.validate_skill (cyclomatic 23) · ×1
  • quick_validate.validate_skill (cyclomatic 23) cli-tool/components/skills/development/skill-development/scripts/quick_validate.py:12 — quick_validate.validate_skill 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.
D1 · Cyclomatic Complexity · ScientificSchematicGenerator._extract_image_from_response (cyclomatic 23) · ×1
  • ScientificSchematicGenerator._extract_image_from_response (cyclomatic 23) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:235 — ScientificSchematicGenerator._extract_image_from_response 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.
D1 · Cyclomatic Complexity · macos_window_info.swift.top-level code (cyclomatic 23) · ×1
  • macos_window_info.swift.top-level code (cyclomatic 23) cli-tool/components/skills/media/screenshot/scripts/macos_window_info.swift:38 — macos_window_info.swift.top-level code 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.
D1 · Cyclomatic Complexity · SessionAnalyzer.extractSessionsFromClaudeInfo (cyclomatic 22) · ×1
  • SessionAnalyzer.extractSessionsFromClaudeInfo (cyclomatic 22) cli-tool/src/analytics/core/SessionAnalyzer.js:305 — SessionAnalyzer.extractSessionsFromClaudeInfo has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 420, 378, 309, …). 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.
D1 · Cyclomatic Complexity · policy.route (cyclomatic 22) · ×1
  • policy.route (cyclomatic 22) cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts:334 — policy.route 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.
D1 · Cyclomatic Complexity · register.applyProfile (cyclomatic 22) · ×1
  • register.applyProfile (cyclomatic 22) cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:199 — register.applyProfile has cyclomatic complexity 22 (threshold 15). Of this number, 20 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.
D1 · Cyclomatic Complexity · audit.runAudit (cyclomatic 22) · ×1
  • audit.runAudit (cyclomatic 22) cli-tool/components/skills/web-development/roier-seo/scripts/audit.js:46 — audit.runAudit has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · secret-scanner.main (cyclomatic 22) · ×1
  • secret-scanner.main (cyclomatic 22) cli-tool/components/hooks/security/secret-scanner.py:295 — secret-scanner.main 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.
D1 · Cyclomatic Complexity · generate_report.generate_html (cyclomatic 22) · ×1
  • generate_report.generate_html (cyclomatic 22) cli-tool/components/skills/development/skill-development/scripts/generate_report.py:16 — generate_report.generate_html 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.
D1 · Cyclomatic Complexity · search_databases.main (cyclomatic 22) · ×1
  • search_databases.main (cyclomatic 22) cli-tool/components/skills/scientific/literature-review/scripts/search_databases.py:209 — search_databases.main 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.
D1 · Cyclomatic Complexity · SlideImageGenerator.generate_slide (cyclomatic 22) · ×1
  • SlideImageGenerator.generate_slide (cyclomatic 22) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:532 — SlideImageGenerator.generate_slide 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.
D1 · Cyclomatic Complexity · listSkillTree (cyclomatic 22) · ×1
  • listSkillTree (cyclomatic 22) cli-tool/src/external-skill.js:179 — listSkillTree 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.
D1 · Cyclomatic Complexity · catalog-browser.browseCatalog (cyclomatic 21) · ×1
  • catalog-browser.browseCatalog (cyclomatic 21) cli-tool/src/catalog-browser.js:212 — catalog-browser.browseCatalog has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 3 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.
D1 · Cyclomatic Complexity · install-ui.createInstallUI.runStep (cyclomatic 21) · ×1
  • install-ui.createInstallUI.runStep (cyclomatic 21) cli-tool/src/install-ui.js:216 — install-ui.createInstallUI.runStep has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 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.
D1 · Cyclomatic Complexity · chats.conversations (cyclomatic 21) · ×1
  • chats.conversations (cyclomatic 21) cli-tool/components/mods/productivity/session-chats/hooks/chats.ts:195 — chats.conversations has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · rules.parseRule (cyclomatic 21) · ×1
  • rules.parseRule (cyclomatic 21) REDACTED:194 — rules.parseRule 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.
D1 · Cyclomatic Complexity · stack.commandsSection (cyclomatic 21) · ×1
  • stack.commandsSection (cyclomatic 21) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:472 — stack.commandsSection has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (fileNode, a function literal at line 495, a function literal at line 496, …). 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.
D1 · Cyclomatic Complexity · index-events.showCategoryFilters (cyclomatic 21) · ×1
  • index-events.showCategoryFilters (cyclomatic 21) docs/js/index-events.js:1323 — index-events.showCategoryFilters has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · WorkflowManager.showGenerateModal (cyclomatic 21) · ×1
  • WorkflowManager.showGenerateModal (cyclomatic 21) docs/js/workflows-events.js:706 — WorkflowManager.showGenerateModal has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs 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.
D1 · Cyclomatic Complexity · api_validator.check_openapi_spec (cyclomatic 21) · ×1
  • api_validator.check_openapi_spec (cyclomatic 21) cli-tool/components/skills/development/api-patterns/scripts/api_validator.py:37 — api_validator.check_openapi_spec 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.
D1 · Cyclomatic Complexity · aggregate_benchmark.load_run_results (cyclomatic 21) · ×1
  • aggregate_benchmark.load_run_results (cyclomatic 21) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:67 — aggregate_benchmark.load_run_results 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.
D1 · Cyclomatic Complexity · enzyme_pathway_builder.infer_transformation_type (cyclomatic 21) · ×1
  • enzyme_pathway_builder.infer_transformation_type (cyclomatic 21) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:232 — enzyme_pathway_builder.infer_transformation_type 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.
D1 · Cyclomatic Complexity · SlideImageGenerator._extract_image_from_response (cyclomatic 21) · ×1
  • SlideImageGenerator._extract_image_from_response (cyclomatic 21) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:250 — SlideImageGenerator._extract_image_from_response 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.
D1 · Cyclomatic Complexity · geo_checker.check_page (cyclomatic 21) · ×1
  • geo_checker.check_page (cyclomatic 21) cli-tool/components/skills/utilities/geo-fundamentals/scripts/geo_checker.py:99 — geo_checker.check_page 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.
D1 · Cyclomatic Complexity · createInstallUI.runStep (cyclomatic 21) · ×1
  • createInstallUI.runStep (cyclomatic 21) cli-tool/src/install-ui.js:216 — createInstallUI.runStep has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 9 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.
D1 · Cyclomatic Complexity · StateCalculator.detectRealClaudeActivity (cyclomatic 20) · ×1
  • StateCalculator.detectRealClaudeActivity (cyclomatic 20) cli-tool/src/analytics/core/StateCalculator.js:179 — StateCalculator.detectRealClaudeActivity has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · ceiling.rulesFrom (cyclomatic 20) · ×1
  • ceiling.rulesFrom (cyclomatic 20) cli-tool/components/mods/enterprise/policy-ceiling/hooks/ceiling.ts:40 — ceiling.rulesFrom has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · web_game_playwright_client.doChoreography (cyclomatic 20) · ×1
  • web_game_playwright_client.doChoreography (cyclomatic 20) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:227 — web_game_playwright_client.doChoreography has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · CertificationsView.CertificationsView (cyclomatic 20) · ×1
  • CertificationsView.CertificationsView (cyclomatic 20) dashboard/src/components/CertificationsView.tsx:198 — CertificationsView.CertificationsView has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 6 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.
D1 · Cyclomatic Complexity · ComponentTerminal.buildScript (cyclomatic 20) · ×1
  • ComponentTerminal.buildScript (cyclomatic 20) dashboard/src/components/ComponentTerminal.tsx:96 — ComponentTerminal.buildScript has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · IndexPageManager.sortComponents (cyclomatic 20) · ×1
  • IndexPageManager.sortComponents (cyclomatic 20) docs/js/index-events.js:363 — IndexPageManager.sortComponents has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 382, 368, 375). 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.
D1 · Cyclomatic Complexity · OKRGenerator.generate_okr_dashboard (cyclomatic 20) · ×1
  • OKRGenerator.generate_okr_dashboard (cyclomatic 20) cli-tool/components/skills/business-marketing/product-strategist/scripts/okr_cascade_generator.py:216 — OKRGenerator.generate_okr_dashboard has cyclomatic complexity 20 (threshold 15). 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.
D1 · Cyclomatic Complexity · quick_validate.validate_skill (cyclomatic 20) · ×1
  • quick_validate.validate_skill (cyclomatic 20) cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:12 — quick_validate.validate_skill has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · generate_review.build_run (cyclomatic 20) · ×1
  • generate_review.build_run (cyclomatic 20) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:85 — generate_review.build_run 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.
D1 · Cyclomatic Complexity · text_to_speech._run_speak_batch (cyclomatic 20) · ×1
  • text_to_speech._run_speak_batch (cyclomatic 20) cli-tool/components/skills/media/speech/scripts/text_to_speech.py:354 — text_to_speech._run_speak_batch 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.
D1 · Cyclomatic Complexity · check_completeness.display_results (cyclomatic 20) · ×1
  • check_completeness.display_results (cyclomatic 20) cli-tool/components/skills/scientific/treatment-plans/scripts/check_completeness.py:127 — check_completeness.display_results has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · HealthChecker.generateRecommendations (cyclomatic 19) · ×1
  • HealthChecker.generateRecommendations (cyclomatic 19) cli-tool/src/health-check.js:1342 — HealthChecker.generateRecommendations has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 1356). 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.
D1 · Cyclomatic Complexity · index.installIndividualSkill (cyclomatic 19) · ×1
  • index.installIndividualSkill (cyclomatic 19) cli-tool/src/index.js:1413 — index.installIndividualSkill has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (downloadDirectory). 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.
D1 · Cyclomatic Complexity · index.installIndividualMod (cyclomatic 19) · ×1
  • index.installIndividualMod (cyclomatic 19) cli-tool/src/index.js:1803 — index.installIndividualMod 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.
D1 · Cyclomatic Complexity · index.installWorkflow (cyclomatic 19) · ×1
  • index.installWorkflow (cyclomatic 19) cli-tool/src/index.js:2198 — index.installWorkflow 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.
D1 · Cyclomatic Complexity · chess.attacked (cyclomatic 19) · ×1
  • chess.attacked (cyclomatic 19) cli-tool/components/mods/games/chess/hooks/chess.ts:111 — chess.attacked has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · catalog.parseTrending (cyclomatic 19) · ×1
  • catalog.parseTrending (cyclomatic 19) cli-tool/components/mods/productivity/aitmpl/hooks/catalog.ts:62 — catalog.parseTrending 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.
D1 · Cyclomatic Complexity · graph.tree (cyclomatic 19) · ×1
  • graph.tree (cyclomatic 19) cli-tool/components/mods/productivity/session-chats/hooks/graph.ts:91 — graph.tree has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 111, a function literal at line 102, visit). 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.
D1 · Cyclomatic Complexity · register.register · ×1
  • register.register::forkAt (cyclomatic 19) cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx:109 — register.register::forkAt 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.
D1 · Cyclomatic Complexity · profiles.planFor (cyclomatic 19) · ×1
  • profiles.planFor (cyclomatic 19) cli-tool/components/mods/productivity/ultra-config/hooks/profiles.ts:242 — profiles.planFor has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 246, 243). 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.
D1 · Cyclomatic Complexity · web_game_playwright_client.main (cyclomatic 19) · ×1
  • web_game_playwright_client.main (cyclomatic 19) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:262 — web_game_playwright_client.main 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.
D1 · Cyclomatic Complexity · index.collectDownloads (cyclomatic 19) · ×1
  • index.collectDownloads (cyclomatic 19) cloudflare-workers/pulse/index.js:216 — index.collectDownloads 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.
D1 · Cyclomatic Complexity · OKRGenerator.calculate_alignment_score (cyclomatic 19) · ×1
  • OKRGenerator.calculate_alignment_score (cyclomatic 19) cli-tool/components/skills/business-marketing/product-strategist/scripts/okr_cascade_generator.py:270 — OKRGenerator.calculate_alignment_score 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.
D1 · Cyclomatic Complexity · compound_cross_reference.get_kegg_info (cyclomatic 19) · ×1
  • compound_cross_reference.get_kegg_info (cyclomatic 19) cli-tool/components/skills/scientific/bioservices/scripts/compound_cross_reference.py:66 — compound_cross_reference.get_kegg_info 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.
D1 · Cyclomatic Complexity · enzyme_pathway_builder.calculate_pathway_feasibility (cyclomatic 19) · ×1
  • enzyme_pathway_builder.calculate_pathway_feasibility (cyclomatic 19) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:596 — enzyme_pathway_builder.calculate_pathway_feasibility 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.
D1 · Cyclomatic Complexity · filter_molecules.generate_summary (cyclomatic 19) · ×1
  • filter_molecules.generate_summary (cyclomatic 19) cli-tool/components/skills/scientific/medchem/scripts/filter_molecules.py:205 — filter_molecules.generate_summary 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.
D1 · Cyclomatic Complexity · filter_molecules.main (cyclomatic 19) · ×1
  • filter_molecules.main (cyclomatic 19) cli-tool/components/skills/scientific/medchem/scripts/filter_molecules.py:289 — filter_molecules.main 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.
D1 · Cyclomatic Complexity · visualize_graph.visualize_data (cyclomatic 19) · ×1
  • visualize_graph.visualize_data (cyclomatic 19) cli-tool/components/skills/scientific/torch_geometric/scripts/visualize_graph.py:27 — visualize_graph.visualize_data 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.
D1 · Cyclomatic Complexity · ChartCard.ChartCard (cyclomatic 18) · ×1
  • ChartCard.ChartCard (cyclomatic 18) cli-tool/analytics-ui/src/components/ChartCard.tsx:14 — ChartCard.ChartCard has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 27, 42, 64, …). 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.
D1 · Cyclomatic Complexity · Dashboard.DashboardView (cyclomatic 18) · ×1
  • Dashboard.DashboardView (cyclomatic 18) cli-tool/analytics-ui/src/islands/Dashboard.tsx:161 — Dashboard.DashboardView has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 180, a function literal at line 364, a function literal at line 193, …). 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.
D1 · Cyclomatic Complexity · universal-audit-log.register (cyclomatic 18) · ×1
  • universal-audit-log.register (cyclomatic 18) cli-tool/components/mods/observability/universal-audit-log/hooks/universal-audit-log.ts:63 — universal-audit-log.register has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 78, 106). 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.
D1 · Cyclomatic Complexity · audit-api.runAudit (cyclomatic 18) · ×1
  • audit-api.runAudit (cyclomatic 18) cli-tool/components/skills/web-development/roier-seo/scripts/audit-api.js:38 — audit-api.runAudit 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.
D1 · Cyclomatic Complexity · index.sendBroadcast (cyclomatic 18) · ×1
  • index.sendBroadcast (cyclomatic 18) cloudflare-workers/newsletter/index.js:428 — index.sendBroadcast has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · pending-action.parsePendingAction (cyclomatic 18) · ×1
  • pending-action.parsePendingAction (cyclomatic 18) dashboard/src/lib/pending-action.ts:42 — pending-action.parsePendingAction 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.
D1 · Cyclomatic Complexity · SkillSlideView.buildSlides (cyclomatic 18) · ×1
  • SkillSlideView.buildSlides (cyclomatic 18) REDACTED:63 — SkillSlideView.buildSlides 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.
D1 · Cyclomatic Complexity · WorkflowManager.highlightYamlLine (cyclomatic 18) · ×1
  • WorkflowManager.highlightYamlLine (cyclomatic 18) docs/js/workflows-events.js:881 — WorkflowManager.highlightYamlLine 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.
D1 · Cyclomatic Complexity · task_manager.update_task_status (cyclomatic 18) · ×1
  • task_manager.update_task_status (cyclomatic 18) cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:168 — task_manager.update_task_status 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.
D1 · Cyclomatic Complexity · transcribe_diarize.main (cyclomatic 18) · ×1
  • transcribe_diarize.main (cyclomatic 18) cli-tool/components/skills/media/transcribe/scripts/transcribe_diarize.py:189 — transcribe_diarize.main 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.
D1 · Cyclomatic Complexity · brenda_visualization.plot_michaelis_menten (cyclomatic 18) · ×1
  • brenda_visualization.plot_michaelis_menten (cyclomatic 18) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:471 — brenda_visualization.plot_michaelis_menten 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.
D1 · Cyclomatic Complexity · MetadataExtractor.metadata_to_bibtex (cyclomatic 18) · ×1
  • MetadataExtractor.metadata_to_bibtex (cyclomatic 18) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:283 — MetadataExtractor.metadata_to_bibtex 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.
D1 · Cyclomatic Complexity · phase_diagram_generator.generate_phase_diagram (cyclomatic 18) · ×1
  • phase_diagram_generator.generate_phase_diagram (cyclomatic 18) cli-tool/components/skills/scientific/pymatgen/scripts/phase_diagram_generator.py:48 — phase_diagram_generator.generate_phase_diagram 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.
D1 · Cyclomatic Complexity · structure_analyzer.analyze_structure (cyclomatic 18) · ×1
  • structure_analyzer.analyze_structure (cyclomatic 18) cli-tool/components/skills/scientific/pymatgen/scripts/structure_analyzer.py:36 — structure_analyzer.analyze_structure has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ScientificSchematicGenerator.generate_image (cyclomatic 18) · ×1
  • ScientificSchematicGenerator.generate_image (cyclomatic 18) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:342 — ScientificSchematicGenerator.generate_image 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.
D1 · Cyclomatic Complexity · ConversationAnalyzer.generateStatusSquares (cyclomatic 17) · ×1
  • ConversationAnalyzer.generateStatusSquares (cyclomatic 17) cli-tool/src/analytics/core/ConversationAnalyzer.js:626 — ConversationAnalyzer.generateStatusSquares has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 635, 668). 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.
D1 · Cyclomatic Complexity · SessionAnalyzer.extractSessions (cyclomatic 17) · ×1
  • SessionAnalyzer.extractSessions (cyclomatic 17) cli-tool/src/analytics/core/SessionAnalyzer.js:173 — SessionAnalyzer.extractSessions has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 240, 177, 216, …). 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.
D1 · Cyclomatic Complexity · ClaudeAnalytics.generateStatusSquares (cyclomatic 17) · ×1
  • ClaudeAnalytics.generateStatusSquares (cyclomatic 17) REDACTED:333 — ClaudeAnalytics.generateStatusSquares has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 342, 375). 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.
D1 · Cyclomatic Complexity · HealthChecker.checkMCPConfigurationSyntax (cyclomatic 17) · ×1
  • HealthChecker.checkMCPConfigurationSyntax (cyclomatic 17) cli-tool/src/health-check.js:650 — HealthChecker.checkMCPConfigurationSyntax 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.
D1 · Cyclomatic Complexity · component-content.filesFromContent (cyclomatic 17) · ×1
  • component-content.filesFromContent (cyclomatic 17) cli-tool/src/component-content.js:40 — component-content.filesFromContent 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.
D1 · Cyclomatic Complexity · detect.segments (cyclomatic 17) · ×1
  • detect.segments (cyclomatic 17) REDACTED:44 — detect.segments 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.
D1 · Cyclomatic Complexity · jev.readDecision (cyclomatic 17) · ×1
  • jev.readDecision (cyclomatic 17) cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/jev.ts:113 — jev.readDecision 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.
D1 · Cyclomatic Complexity · session-chats.reread (cyclomatic 17) · ×1
  • session-chats.reread (cyclomatic 17) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:399 — session-chats.reread has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 3 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.
D1 · Cyclomatic Complexity · vercel.readCommandStream (cyclomatic 17) · ×1
  • vercel.readCommandStream (cyclomatic 17) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/vercel.ts:208 — vercel.readCommandStream 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.
D1 · Cyclomatic Complexity · live-preview.capture (cyclomatic 17) · ×1
  • live-preview.capture (cyclomatic 17) cli-tool/components/mods/ui/live-preview/hooks/live-preview.tsx:66 — live-preview.capture 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.
D1 · Cyclomatic Complexity · trending-dashboard.html.renderLine (cyclomatic 17) · ×1
  • trending-dashboard.html.renderLine (cyclomatic 17) dashboard/public/trending-dashboard.html:244 — trending-dashboard.html.renderLine has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 6 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.
D1 · Cyclomatic Complexity · CertificationsView.FacetDropdown (cyclomatic 17) · ×1
  • CertificationsView.FacetDropdown (cyclomatic 17) dashboard/src/components/CertificationsView.tsx:87 — CertificationsView.FacetDropdown has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 132, 108, 114, …). 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.
D1 · Cyclomatic Complexity · ComponentPageManager.loadComponentFromURL (cyclomatic 17) · ×1
  • ComponentPageManager.loadComponentFromURL (cyclomatic 17) docs/js/component-page.js:20 — ComponentPageManager.loadComponentFromURL 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.
D1 · Cyclomatic Complexity · seo_checker.check_page (cyclomatic 17) · ×1
  • seo_checker.check_page (cyclomatic 17) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:96 — seo_checker.check_page has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · task_manager.parse_tasks_from_markdown (cyclomatic 17) · ×1
  • task_manager.parse_tasks_from_markdown (cyclomatic 17) cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:77 — task_manager.parse_tasks_from_markdown 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.
D1 · Cyclomatic Complexity · check_staleness.print_report (cyclomatic 17) · ×1
  • check_staleness.print_report (cyclomatic 17) cli-tool/components/skills/enterprise-communication/session-handoff/scripts/check_staleness.py:320 — check_staleness.print_report 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.
D1 · Cyclomatic Complexity · enzyme_pathway_builder.find_enzymes_for_transformation (cyclomatic 17) · ×1
  • enzyme_pathway_builder.find_enzymes_for_transformation (cyclomatic 17) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:274 — enzyme_pathway_builder.find_enzymes_for_transformation has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · enzyme_pathway_builder.find_pathway_for_product (cyclomatic 17) · ×1
  • enzyme_pathway_builder.find_pathway_for_product (cyclomatic 17) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:348 — enzyme_pathway_builder.find_pathway_for_product 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.
D1 · Cyclomatic Complexity · build_decision_tree.simple_algorithm_to_tikz (cyclomatic 17) · ×1
  • build_decision_tree.simple_algorithm_to_tikz (cyclomatic 17) cli-tool/components/skills/scientific/clinical-decision-support/scripts/build_decision_tree.py:102 — build_decision_tree.simple_algorithm_to_tikz 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.
D1 · Cyclomatic Complexity · analyze_results.print_summary (cyclomatic 17) · ×1
  • analyze_results.print_summary (cyclomatic 17) cli-tool/components/skills/scientific/diffdock/scripts/analyze_results.py:137 — analyze_results.print_summary 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.
D1 · Cyclomatic Complexity · generate_image.generate_image (cyclomatic 17) · ×1
  • generate_image.generate_image (cyclomatic 17) cli-tool/components/skills/scientific/generate-image/scripts/generate_image.py:75 — generate_image.generate_image 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.
D1 · Cyclomatic Complexity · external-skill.downloadExternalSkill (cyclomatic 16) · ×1
  • external-skill.downloadExternalSkill (cyclomatic 16) cli-tool/src/external-skill.js:258 — external-skill.downloadExternalSkill 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.
D1 · Cyclomatic Complexity · install-ui.createInstallUI.chooseLocations (cyclomatic 16) · ×1
  • install-ui.createInstallUI.chooseLocations (cyclomatic 16) cli-tool/src/install-ui.js:151 — install-ui.createInstallUI.chooseLocations has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · index.downloadModFromGitHub · ×1
  • index.downloadModFromGitHub::downloadDirectory (cyclomatic 16) cli-tool/src/index.js:1756 — index.downloadModFromGitHub::downloadDirectory 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.
D1 · Cyclomatic Complexity · index.installComponentFromWorkflow (cyclomatic 16) · ×1
  • index.installComponentFromWorkflow (cyclomatic 16) cli-tool/src/index.js:2477 — index.installComponentFromWorkflow 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.
D1 · Cyclomatic Complexity · admin-capability-lockdown.register (cyclomatic 16) · ×1
  • admin-capability-lockdown.register (cyclomatic 16) cli-tool/components/mods/enterprise/admin-capability-lockdown/hooks/admin-capability-lockdown.ts:41 — admin-capability-lockdown.register has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 63, 80, 115, …). 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.
D1 · Cyclomatic Complexity · policy-ceiling.register (cyclomatic 16) · ×1
  • policy-ceiling.register (cyclomatic 16) cli-tool/components/mods/enterprise/policy-ceiling/hooks/policy-ceiling.tsx:42 — policy-ceiling.register has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 80, 60, 114, …). 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.
D1 · Cyclomatic Complexity · register.claudeMoves (cyclomatic 16) · ×1
  • register.claudeMoves (cyclomatic 16) cli-tool/components/mods/games/chess/hooks/register.tsx:117 — register.claudeMoves has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · transcript.buildTimeline (cyclomatic 16) · ×1
  • transcript.buildTimeline (cyclomatic 16) cli-tool/components/mods/productivity/session-time-machine/hooks/transcript.ts:107 — transcript.buildTimeline has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 123, a function literal at line 113, endTurn). 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.
D1 · Cyclomatic Complexity · rules.segments (cyclomatic 16) · ×1
  • rules.segments (cyclomatic 16) REDACTED:104 — rules.segments 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.
D1 · Cyclomatic Complexity · large-edit-confirmation.register (cyclomatic 16) · ×1
  • large-edit-confirmation.register (cyclomatic 16) cli-tool/components/mods/security/large-edit-confirmation/hooks/large-edit-confirmation.ts:24 — large-edit-confirmation.register has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 35, 83). 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.
D1 · Cyclomatic Complexity · stack.skillsSection (cyclomatic 16) · ×1
  • stack.skillsSection (cyclomatic 16) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:414 — stack.skillsSection has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (fileNode, a function literal at line 416, a function literal at line 445, …). 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.
D1 · Cyclomatic Complexity · ValidationOrchestrator._formatComponentResult (cyclomatic 16) · ×1
  • ValidationOrchestrator._formatComponentResult (cyclomatic 16) cli-tool/src/validation/ValidationOrchestrator.js:216 — ValidationOrchestrator._formatComponentResult 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.
D1 · Cyclomatic Complexity · stack-link.decodeStack (cyclomatic 16) · ×1
  • stack-link.decodeStack (cyclomatic 16) dashboard/src/lib/stack-link.ts:137 — stack-link.decodeStack 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.
D1 · Cyclomatic Complexity · DataLoader.getTotalCounts (cyclomatic 16) · ×1
  • DataLoader.getTotalCounts (cyclomatic 16) docs/js/data-loader.js:362 — DataLoader.getTotalCounts 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.
D1 · Cyclomatic Complexity · script.displayDownloadStatistics (cyclomatic 16) · ×1
  • script.displayDownloadStatistics (cyclomatic 16) docs/js/script.js:1947 — script.displayDownloadStatistics has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs 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.
D1 · Cyclomatic Complexity · search-functionality.calculateMatchScore (cyclomatic 16) · ×1
  • search-functionality.calculateMatchScore (cyclomatic 16) docs/js/search-functionality.js:337 — search-functionality.calculateMatchScore 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.
D1 · Cyclomatic Complexity · implement_entity_connections.add_link_to_file (cyclomatic 16) · ×1
  • implement_entity_connections.add_link_to_file (cyclomatic 16) cli-tool/components/agents/obsidian-ops-team/Scripts/implement_entity_connections.py:43 — implement_entity_connections.add_link_to_file 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.
D1 · Cyclomatic Complexity · schema_validator.validate_prisma_schema (cyclomatic 16) · ×1
  • schema_validator.validate_prisma_schema (cyclomatic 16) cli-tool/components/skills/development/database-design/scripts/schema_validator.py:47 — schema_validator.validate_prisma_schema 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.
D1 · Cyclomatic Complexity · risk_calculator.interactive_mode (cyclomatic 16) · ×1
  • risk_calculator.interactive_mode (cyclomatic 16) cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:204 — risk_calculator.interactive_mode 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.
D1 · Cyclomatic Complexity · generate_survival_analysis.generate_report (cyclomatic 16) · ×1
  • generate_survival_analysis.generate_report (cyclomatic 16) cli-tool/components/skills/scientific/clinical-decision-support/scripts/generate_survival_analysis.py:257 — generate_survival_analysis.generate_report 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.
D1 · Cyclomatic Complexity · eda_analyzer.analyze_general_scientific (cyclomatic 16) · ×1
  • eda_analyzer.analyze_general_scientific (cyclomatic 16) cli-tool/components/skills/scientific/exploratory-data-analysis/scripts/eda_analyzer.py:251 — eda_analyzer.analyze_general_scientific 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.
D1 · Cyclomatic Complexity · enrichment_pipeline.enrichment_pipeline (cyclomatic 16) · ×1
  • enrichment_pipeline.enrichment_pipeline (cyclomatic 16) cli-tool/components/skills/scientific/gget/scripts/enrichment_pipeline.py:30 — enrichment_pipeline.enrichment_pipeline has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · style_configurator.interactive_mode (cyclomatic 16) · ×1
  • style_configurator.interactive_mode (cyclomatic 16) cli-tool/components/skills/scientific/matplotlib/scripts/style_configurator.py:277 — style_configurator.interactive_mode 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.
D1 · Cyclomatic Complexity · slides_to_pdf.combine_images_to_pdf (cyclomatic 16) · ×1
  • slides_to_pdf.combine_images_to_pdf (cyclomatic 16) cli-tool/components/skills/scientific/scientific-slides/scripts/slides_to_pdf.py:74 — slides_to_pdf.combine_images_to_pdf 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.
D1 · Cyclomatic Complexity · uniprot_client.main (cyclomatic 16) · ×1
  • uniprot_client.main (cyclomatic 16) cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py:233 — uniprot_client.main 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.
D1 · Cyclomatic Complexity · sora._augment_prompt_fields (cyclomatic 16) · ×1
  • sora._augment_prompt_fields (cyclomatic 16) cli-tool/components/skills/video/sora/scripts/sora.py:338 — sora._augment_prompt_fields has cyclomatic complexity 16 (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.
D1 · Cyclomatic Complexity · createInstallUI.chooseLocations (cyclomatic 16) · ×1
  • createInstallUI.chooseLocations (cyclomatic 16) cli-tool/src/install-ui.js:151 — createInstallUI.chooseLocations has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (render, a function literal at line 184, a function literal at line 164, …). 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.
D10 · Test Quality · Skipped test · ×1
  • Skipped test: should validate real frontend-developer agent as safe cli-tool/tests/validation/SemanticValidator.test.js:41 — Skipped — switched off by it.skip
D17 · Explicit Debt · TodoComment repeated across 12 files · ×1
  • TodoComment repeated across 12 files cli-tool/components/skills/enterprise-communication/risk-management-specialist/scripts/example.py:15 — The identical TodoComment appears in 12 files (12 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 12 independent debts. Fix the systemic cause once rather than file-by-file. Text: "# TODO: Add actual script logic here". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D2 · Cognitive Complexity · MobileAuditor.audit_file (cognitive 208) · ×1
  • MobileAuditor.audit_file (cognitive 208) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:81 — MobileAuditor.audit_file has cognitive complexity 208 (threshold 15). Drivers by points: if/else 96 (148 pts), boolean chains 43, loops 8 (11 pts), error handling 3 (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.
D2 · Cognitive Complexity · build_ownership_map.build_ownership_map (cognitive 189) · ×1
  • build_ownership_map.build_ownership_map (cognitive 189) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:421 — build_ownership_map.build_ownership_map has cognitive complexity 189 (threshold 15). Drivers by points: if/else 46 (111 pts), loops 17 (48 pts), boolean chains 12, ternaries 8 (12 pts), error handling 2 (6 pts) (nesting depth added 104). 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.
D2 · Cognitive Complexity · viewer.html.renderBenchmark (cognitive 181) · ×1
  • viewer.html.renderBenchmark (cognitive 181) cli-tool/components/skills/development/skill-development/eval-viewer/viewer.html:1114 — viewer.html.renderBenchmark has cognitive complexity 181 (threshold 15). Drivers by points: if/else 23 (58 pts), loops 12 (48 pts), ternaries 11 (46 pts), boolean chains 29 (nesting depth added 106). Of this number, 169 points are the body's own statements and 12 belong to 7 function items inside it that branch. 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.
D2 · Cognitive Complexity · setupRoutes (cognitive 180) · ×1
  • setupRoutes (cognitive 180) REDACTED:120 — setupRoutes has cognitive complexity 180 (threshold 15). Drivers by points: if/else 57 (97 pts), boolean chains 54, error handling 11 (14 pts), ternaries 10, loops 3 (5 pts) (nesting depth added 45). None of this is in the body itself: all 180 points belong to 48 function items inside it that branch (a function literal at line 520, a function literal at line 213, a function literal at line 607, …). 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.
D2 · Cognitive Complexity · jev-auto-mode.register (cognitive 162) · ×1
  • jev-auto-mode.register (cognitive 162) cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:121 — jev-auto-mode.register has cognitive complexity 162 (threshold 15). Drivers by points: if/else 54 (88 pts), ternaries 25 (45 pts), boolean chains 20, error handling 5 (7 pts), loops 1 (2 pts) (nesting depth added 57). Most of this is not in the body itself: 10 of the 162 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 187, a function literal at line 357, a function literal at line 330, …). 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.
D2 · Cognitive Complexity · jev-skill-suggestion.register (cognitive 159) · ×1
  • jev-skill-suggestion.register (cognitive 159) cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:130 — jev-skill-suggestion.register has cognitive complexity 159 (threshold 15). Drivers by points: if/else 52 (79 pts), ternaries 20 (33 pts), boolean chains 22, loops 8 (17 pts), error handling 7 (8 pts) (nesting depth added 50). Most of this is not in the body itself: 10 of the 159 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 248, a function literal at line 489, a function literal at line 288, …). 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.
D2 · Cognitive Complexity · jev-guardrails.register (cognitive 133) · ×1
  • jev-guardrails.register (cognitive 133) cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts:98 — jev-guardrails.register has cognitive complexity 133 (threshold 15). Drivers by points: if/else 41 (72 pts), ternaries 17 (23 pts), error handling 6 (14 pts), boolean chains 12, loops 6 (11 pts), match/switch 1 (nesting depth added 50). Most of this is not in the body itself: 14 of the 133 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 278, a function literal at line 173, setupLines, …). 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.
D2 · Cognitive Complexity · installIndividualSetting (cognitive 123) · ×1
  • installIndividualSetting (cognitive 123) cli-tool/src/index.js:553 — installIndividualSetting has cognitive complexity 123 (threshold 15). Drivers by points: if/else 41 (79 pts), boolean chains 20, error handling 4 (10 pts), ternaries 5 (10 pts), loops 2 (4 pts) (nesting depth added 51). Of this number, 103 points are the body's own statements and 20 belong to 5 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.
D2 · Cognitive Complexity · register.register (cognitive 113) · ×1
  • register.register (cognitive 113) cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx:159 — register.register has cognitive complexity 113 (threshold 15). Drivers by points: ternaries 49 (68 pts), if/else 26 (30 pts), boolean chains 12, error handling 2, loops 1 (nesting depth added 23). Most of this is not in the body itself: 7 of the 113 points are its own statements and the rest belongs to 23 function items inside it that branch (a function literal at line 261, a function literal at line 417, a function literal at line 399, …). 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.
D2 · Cognitive Complexity · register.register (cognitive 108) · ×1
  • register.register (cognitive 108) cli-tool/components/mods/games/chess/hooks/register.tsx:217 — register.register has cognitive complexity 108 (threshold 15). Drivers by points: ternaries 38 (54 pts), if/else 26 (33 pts), boolean chains 21 (nesting depth added 23). Most of this is not in the body itself: 7 of the 108 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 405, a function literal at line 433, a function literal at line 349, …). 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.
D2 · Cognitive Complexity · chess.pseudoMoves (cognitive 106) · ×1
  • chess.pseudoMoves (cognitive 106) cli-tool/components/mods/games/chess/hooks/chess.ts:147 — chess.pseudoMoves has cognitive complexity 106 (threshold 15). Drivers by points: if/else 18 (47 pts), ternaries 12 (31 pts), loops 6 (18 pts), boolean chains 10 (nesting depth added 60). Of this number, 96 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · session-chats.register (cognitive 104) · ×1
  • session-chats.register (cognitive 104) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:87 — session-chats.register has cognitive complexity 104 (threshold 15). Drivers by points: ternaries 26 (51 pts), if/else 24 (32 pts), boolean chains 17, error handling 3, loops 1 (nesting depth added 33). Most of this is not in the body itself: 3 of the 104 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 259, 173, 213, …). 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.
D2 · Cognitive Complexity · setupWebServer (cognitive 104) · ×1
  • setupWebServer (cognitive 104) REDACTED:609 — setupWebServer has cognitive complexity 104 (threshold 15). Drivers by points: if/else 32 (45 pts), boolean chains 32, error handling 17 (19 pts), ternaries 4 (5 pts), loops 2, other 1 (nesting depth added 16). None of this is in the body itself: all 104 points belong to 36 function literals inside it that branch (lines 904, 728, 979, …). 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.
D2 · Cognitive Complexity · turn-inspector.register (cognitive 102) · ×1
  • turn-inspector.register (cognitive 102) cli-tool/components/mods/ui/turn-inspector/hooks/turn-inspector.tsx:71 — turn-inspector.register has cognitive complexity 102 (threshold 15). Drivers by points: if/else 39 (52 pts), ternaries 26 (37 pts), boolean chains 10, loops 2, error handling 1 (nesting depth added 24). None of this is in the body itself: all 102 points belong to 15 function literals inside it that branch (lines 242, 213, 157, …). 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.
D2 · Cognitive Complexity · SkillExplorer.SkillExplorer (cognitive 100) · ×1
  • SkillExplorer.SkillExplorer (cognitive 100) REDACTED:144 — SkillExplorer.SkillExplorer has cognitive complexity 100 (threshold 15). Drivers by points: if/else 29 (38 pts), boolean chains 36, ternaries 8 (17 pts), loops 7 (9 pts) (nesting depth added 20). Of this number, 34 points are the body's own statements and 66 belong to 20 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.
D2 · Cognitive Complexity · file-operations.copyTemplateFiles (cognitive 98) · ×1
  • file-operations.copyTemplateFiles (cognitive 98) cli-tool/src/file-operations.js:373 — file-operations.copyTemplateFiles has cognitive complexity 98 (threshold 15). Drivers by points: if/else 30 (63 pts), error handling 5 (14 pts), boolean chains 11, loops 4 (10 pts) (nesting depth added 48). 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.
D2 · Cognitive Complexity · bluesky-feed.register (cognitive 97) · ×1
  • bluesky-feed.register (cognitive 97) cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:63 — bluesky-feed.register has cognitive complexity 97 (threshold 15). Drivers by points: if/else 29 (40 pts), ternaries 24 (35 pts), boolean chains 17, error handling 3 (5 pts) (nesting depth added 24). Most of this is not in the body itself: 1 of the 97 points is its own statement and the rest belongs to 12 function items inside it that branch (a function literal at line 237, a function literal at line 200, a function literal at line 162, …). 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.
D2 · Cognitive Complexity · prompt-cache-control.register (cognitive 94) · ×1
  • prompt-cache-control.register (cognitive 94) cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:171 — prompt-cache-control.register has cognitive complexity 94 (threshold 15). Drivers by points: ternaries 30 (44 pts), if/else 24 (32 pts), boolean chains 18 (nesting depth added 22). None of this is in the body itself: all 94 points belong to 14 function literals inside it that branch (lines 405, 360, 294, …). 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.
D2 · Cognitive Complexity · rules.gateFor (cognitive 94) · ×1
  • rules.gateFor (cognitive 94) REDACTED:268 — rules.gateFor has cognitive complexity 94 (threshold 15). Drivers by points: if/else 18 (62 pts), ternaries 3 (15 pts), loops 4 (9 pts), boolean chains 8 (nesting depth added 61). 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.
D2 · Cognitive Complexity · take_screenshot.main (cognitive 92) · ×1
  • take_screenshot.main (cognitive 92) cli-tool/components/skills/media/screenshot/scripts/take_screenshot.py:420 — take_screenshot.main has cognitive complexity 92 (threshold 15). Drivers by points: if/else 29 (46 pts), loops 8 (28 pts), boolean chains 18 (nesting depth added 37). 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.
D2 · Cognitive Complexity · ComponentGrid.ComponentGrid (cognitive 91) · ×1
  • ComponentGrid.ComponentGrid (cognitive 91) dashboard/src/components/ComponentGrid.tsx:41 — ComponentGrid.ComponentGrid has cognitive complexity 91 (threshold 15). Drivers by points: if/else 27 (32 pts), boolean chains 27, ternaries 22 (27 pts), error handling 3, loops 2 (nesting depth added 10). Of this number, 23 points are the body's own statements and 68 belong to 20 function items 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.
D2 · Cognitive Complexity · MyComponentsView.MyComponentsView (cognitive 91) · ×1
  • MyComponentsView.MyComponentsView (cognitive 91) dashboard/src/components/MyComponentsView.tsx:467 — MyComponentsView.MyComponentsView has cognitive complexity 91 (threshold 15). Drivers by points: ternaries 19 (45 pts), if/else 26 (30 pts), boolean chains 10, error handling 6 (nesting depth added 30). Of this number, 36 points are the body's own statements and 55 belong to 17 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.
D2 · Cognitive Complexity · index.installIndividualHook (cognitive 90) · ×1
  • index.installIndividualHook (cognitive 90) cli-tool/src/index.js:933 — index.installIndividualHook has cognitive complexity 90 (threshold 15). Drivers by points: if/else 36 (67 pts), ternaries 4 (8 pts), error handling 4 (6 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 39). Of this number, 69 points are the body's own statements and 21 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.
D2 · Cognitive Complexity · ceiling.apply (cognitive 90) · ×1
  • ceiling.apply (cognitive 90) cli-tool/components/mods/enterprise/policy-ceiling/hooks/ceiling.ts:85 — ceiling.apply has cognitive complexity 90 (threshold 15). Drivers by points: if/else 19 (40 pts), ternaries 17 (37 pts), boolean chains 7, loops 2 (6 pts) (nesting depth added 45). 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.
D2 · Cognitive Complexity · register.register (cognitive 90) · ×1
  • register.register (cognitive 90) cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:130 — register.register has cognitive complexity 90 (threshold 15). Drivers by points: ternaries 39 (53 pts), if/else 19 (20 pts), boolean chains 15, loops 2 (nesting depth added 15). Most of this is not in the body itself: 6 of the 90 points are its own statements and the rest belongs to 20 function literals inside it that branch (lines 201, 488, 464, …). 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.
D2 · Cognitive Complexity · stack-viewer.register (cognitive 90) · ×1
  • stack-viewer.register (cognitive 90) cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx:58 — stack-viewer.register has cognitive complexity 90 (threshold 15). Drivers by points: ternaries 35 (45 pts), if/else 21 (24 pts), boolean chains 15, error handling 2 (3 pts), loops 2 (3 pts) (nesting depth added 15). None of this is in the body itself: all 90 points belong to 11 function literals inside it that branch (lines 193, 315, 355, …). 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.
D2 · Cognitive Complexity · DataCache.parseAndCorrelateToolMessages (cognitive 87) · ×1
  • DataCache.parseAndCorrelateToolMessages (cognitive 87) cli-tool/src/analytics/data/DataCache.js:142 — DataCache.parseAndCorrelateToolMessages has cognitive complexity 87 (threshold 15). Drivers by points: if/else 13 (40 pts), ternaries 6 (23 pts), boolean chains 19, loops 3, error handling 1 (2 pts) (nesting depth added 45). Of this number, 86 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · jev-model-router.register (cognitive 81) · ×1
  • jev-model-router.register (cognitive 81) cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts:64 — jev-model-router.register has cognitive complexity 81 (threshold 15). Drivers by points: if/else 35 (44 pts), ternaries 11 (17 pts), boolean chains 12, error handling 4 (8 pts) (nesting depth added 19). Most of this is not in the body itself: 11 of the 81 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 252, a function literal at line 128, a function literal at line 212, …). 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.
D2 · Cognitive Complexity · stack.scanFiles (cognitive 81) · ×1
  • stack.scanFiles (cognitive 81) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:251 — stack.scanFiles has cognitive complexity 81 (threshold 15). Drivers by points: if/else 17 (46 pts), loops 13 (21 pts), ternaries 4 (8 pts), boolean chains 6 (nesting depth added 41). Of this number, 80 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D2 · Cognitive Complexity · run_eval.run_single_query (cognitive 79) · ×1
  • run_eval.run_single_query (cognitive 79) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:35 — run_eval.run_single_query has cognitive complexity 79 (threshold 15). Drivers by points: if/else 20 (66 pts), loops 3 (7 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 52). 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.
D2 · Cognitive Complexity · JobsView.JobsView (cognitive 78) · ×1
  • JobsView.JobsView (cognitive 78) dashboard/src/components/JobsView.tsx:88 — JobsView.JobsView has cognitive complexity 78 (threshold 15). Drivers by points: boolean chains 35, if/else 20 (23 pts), ternaries 13 (20 pts) (nesting depth added 10). Of this number, 23 points are the body's own statements and 55 belong to 14 function items 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.
D2 · Cognitive Complexity · createClaudeConfig (cognitive 76) · ×1
  • createClaudeConfig (cognitive 76) cli-tool/src/index.js:86 — createClaudeConfig has cognitive complexity 76 (threshold 15). Drivers by points: if/else 32 (38 pts), boolean chains 20, ternaries 5 (10 pts), loops 2 (7 pts), error handling 1 (nesting depth added 16). 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.
D2 · Cognitive Complexity · agent-flow.register (cognitive 75) · ×1
  • agent-flow.register (cognitive 75) cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:85 — agent-flow.register has cognitive complexity 75 (threshold 15). Drivers by points: ternaries 27 (33 pts), if/else 27 (31 pts), boolean chains 10, error handling 1 (nesting depth added 10). None of this is in the body itself: all 75 points belong to 16 function literals inside it that branch (lines 284, 256, 294, …). 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.
D2 · Cognitive Complexity · MarkdownViewer.MarkdownViewer (cognitive 74) · ×1
  • MarkdownViewer.MarkdownViewer (cognitive 74) REDACTED:80 — MarkdownViewer.MarkdownViewer has cognitive complexity 74 (threshold 15). Drivers by points: if/else 22 (31 pts), boolean chains 24, ternaries 8 (10 pts), loops 7 (9 pts) (nesting depth added 13). Of this number, 18 points are the body's own statements and 56 belong to 13 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.
D2 · Cognitive Complexity · vercel-deploys.register (cognitive 72) · ×1
  • vercel-deploys.register (cognitive 72) cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-deploys.tsx:71 — vercel-deploys.register has cognitive complexity 72 (threshold 15). Drivers by points: ternaries 20 (30 pts), if/else 19 (26 pts), boolean chains 11, loops 1 (4 pts), error handling 1 (nesting depth added 20). None of this is in the body itself: all 72 points belong to 14 function items inside it that branch (a function literal at line 198, a function literal at line 253, a function literal at line 239, …). 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.
D2 · Cognitive Complexity · hook-scanner.getHookDescription (cognitive 71) · ×1
  • hook-scanner.getHookDescription (cognitive 71) cli-tool/src/hook-scanner.js:110 — hook-scanner.getHookDescription has cognitive complexity 71 (threshold 15). Drivers by points: if/else 46, boolean chains 25. 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.
D2 · Cognitive Complexity · ComponentPageManager.renderComponentCode (cognitive 71) · ×1
  • ComponentPageManager.renderComponentCode (cognitive 71) docs/js/component-page.js:599 — ComponentPageManager.renderComponentCode has cognitive complexity 71 (threshold 15). Drivers by points: if/else 23 (49 pts), boolean chains 13, error handling 2 (4 pts), loops 1 (3 pts), match/switch 1 (2 pts) (nesting depth added 31). Of this number, 19 points are the body's own statements and 52 belong to 10 function literals inside it that branch. 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.
D2 · Cognitive Complexity · community_maintainers.main (cognitive 66) · ×1
  • community_maintainers.main (cognitive 66) cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:378 — community_maintainers.main has cognitive complexity 66 (threshold 15). Drivers by points: if/else 23 (44 pts), ternaries 5 (8 pts), loops 5 (7 pts), boolean chains 6, error handling 1 (nesting depth added 26). 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.
D2 · Cognitive Complexity · git-sidebar.register (cognitive 65) · ×1
  • git-sidebar.register (cognitive 65) cli-tool/components/mods/ui/git-sidebar/hooks/git-sidebar.tsx:101 — git-sidebar.register has cognitive complexity 65 (threshold 15). Drivers by points: if/else 23 (29 pts), ternaries 19 (24 pts), boolean chains 12 (nesting depth added 11). None of this is in the body itself: all 65 points belong to 9 function literals inside it that branch (lines 186, 244, 303, …). 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.
D2 · Cognitive Complexity · SaveToCollectionButton.SaveButton (cognitive 64) · ×1
  • SaveToCollectionButton.SaveButton (cognitive 64) dashboard/src/components/SaveToCollectionButton.tsx:60 — SaveToCollectionButton.SaveButton has cognitive complexity 64 (threshold 15). Drivers by points: if/else 22 (30 pts), ternaries 8 (16 pts), boolean chains 11, error handling 4 (6 pts), loops 1 (nesting depth added 18). Of this number, 21 points are the body's own statements and 43 belong to 13 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.
D2 · Cognitive Complexity · enzyme_pathway_builder.optimize_pathway_conditions (cognitive 64) · ×1
  • enzyme_pathway_builder.optimize_pathway_conditions (cognitive 64) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:696 — enzyme_pathway_builder.optimize_pathway_conditions has cognitive complexity 64 (threshold 15). Drivers by points: if/else 16 (44 pts), loops 6 (11 pts), error handling 2 (8 pts), boolean chains 1 (nesting depth added 39). 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.
D2 · Cognitive Complexity · server.server (cognitive 63) · ×1
  • server.server (cognitive 63) REDACTED:24 — server.server has cognitive complexity 63 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 16, ternaries 8 (16 pts), loops 3 (6 pts), error handling 2 (5 pts) (nesting depth added 19). Of this number, 45 points are the body's own statements and 18 belong to 7 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.
D2 · Cognitive Complexity · page-audit.auditDom (cognitive 63) · ×1
  • page-audit.auditDom (cognitive 63) cli-tool/components/skills/development/senior-frontend/scripts/page-audit.mjs:5 — page-audit.auditDom has cognitive complexity 63 (threshold 15). Drivers by points: if/else 22 (39 pts), boolean chains 17, loops 6 (7 pts) (nesting depth added 18). Of this number, 51 points are the body's own statements and 12 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.
D2 · Cognitive Complexity · (anonymous) (cognitive 63) · ×1
  • (anonymous) (cognitive 63) REDACTED:24 — (anonymous) has cognitive complexity 63 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 16, ternaries 8 (16 pts), loops 3 (6 pts), error handling 2 (5 pts) (nesting depth added 19). Of this number, 45 points are the body's own statements and 18 belong to 8 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.
D2 · Cognitive Complexity · utils.detectProject (cognitive 60) · ×1
  • utils.detectProject (cognitive 60) cli-tool/src/utils.js:4 — utils.detectProject has cognitive complexity 60 (threshold 15). Drivers by points: if/else 21 (43 pts), boolean chains 9, error handling 3 (8 pts) (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.
D2 · Cognitive Complexity · ConversationAnalyzer.parseAndCorrelateToolMessages (cognitive 60) · ×1
  • ConversationAnalyzer.parseAndCorrelateToolMessages (cognitive 60) cli-tool/src/analytics/core/ConversationAnalyzer.js:275 — ConversationAnalyzer.parseAndCorrelateToolMessages has cognitive complexity 60 (threshold 15). Drivers by points: if/else 9 (26 pts), ternaries 4 (16 pts), boolean chains 14, error handling 1 (2 pts), loops 2 (nesting depth added 30). 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.
D2 · Cognitive Complexity · OKRGenerator.generate_okr_dashboard (cognitive 59) · ×1
  • OKRGenerator.generate_okr_dashboard (cognitive 59) cli-tool/components/skills/business-marketing/product-strategist/scripts/okr_cascade_generator.py:216 — OKRGenerator.generate_okr_dashboard has cognitive complexity 59 (threshold 15). Drivers by points: loops 11 (37 pts), if/else 7 (21 pts), boolean chains 1 (nesting depth added 40). 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.
D2 · Cognitive Complexity · secret-scanner.main (cognitive 58) · ×1
  • secret-scanner.main (cognitive 58) cli-tool/components/hooks/security/secret-scanner.py:295 — secret-scanner.main has cognitive complexity 58 (threshold 15). Drivers by points: if/else 12 (37 pts), loops 5 (16 pts), boolean chains 4, error handling 1 (nesting depth added 36). 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.
D2 · Cognitive Complexity · aggregate_benchmark.load_run_results (cognitive 58) · ×1
  • aggregate_benchmark.load_run_results (cognitive 58) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:67 — aggregate_benchmark.load_run_results has cognitive complexity 58 (threshold 15). Drivers by points: if/else 11 (31 pts), error handling 4 (15 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 37). 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.
D2 · Cognitive Complexity · SkillReviewFlow.SkillReviewFlow (cognitive 57) · ×1
  • SkillReviewFlow.SkillReviewFlow (cognitive 57) dashboard/src/components/SkillReviewFlow.tsx:276 — SkillReviewFlow.SkillReviewFlow has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 25 (30 pts), if/else 11 (15 pts), boolean chains 8, loops 3 (4 pts) (nesting depth added 10). Most of this is not in the body itself: 3 of the 57 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 462, a function literal at line 442, a function literal at line 351, …). 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.
D2 · Cognitive Complexity · linear-tickets.register (cognitive 55) · ×1
  • linear-tickets.register (cognitive 55) cli-tool/components/mods/integrations/linear-tickets/hooks/linear-tickets.tsx:70 — linear-tickets.register has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 21 (30 pts), if/else 16 (18 pts), boolean chains 6, error handling 1 (nesting depth added 11). Most of this is not in the body itself: 1 of the 55 points is its own statement and the rest belongs to 12 function items inside it that branch (a function literal at line 190, a function literal at line 163, a function literal at line 99, …). 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.
D2 · Cognitive Complexity · run_loop.run_loop (cognitive 55) · ×1
  • run_loop.run_loop (cognitive 55) cli-tool/components/skills/development/skill-development/scripts/run_loop.py:47 — run_loop.run_loop has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (44 pts), ternaries 5 (9 pts), boolean chains 1, loops 1 (nesting depth added 25). 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.
D2 · Cognitive Complexity · ChatsMobile.handleConversationChange (cognitive 54) · ×1
  • ChatsMobile.handleConversationChange (cognitive 54) REDACTED:884 — ChatsMobile.handleConversationChange has cognitive complexity 54 (threshold 15). Drivers by points: if/else 8 (20 pts), ternaries 4 (17 pts), boolean chains 9, loops 3 (7 pts), error handling 1 (nesting depth added 29). Of this number, 53 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · rules.ruleMatches (cognitive 54) · ×1
  • rules.ruleMatches (cognitive 54) REDACTED:635 — rules.ruleMatches has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 18, ternaries 3 (6 pts) (nesting depth added 13). Of this number, 51 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · neon-branch-per-session.register (cognitive 53) · ×1
  • neon-branch-per-session.register (cognitive 53) cli-tool/components/mods/integrations/neon-branch-per-session/hooks/neon-branch-per-session.ts:60 — neon-branch-per-session.register has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 14 (22 pts), if/else 13 (14 pts), boolean chains 11, error handling 4 (6 pts) (nesting depth added 11). Most of this is not in the body itself: 4 of the 53 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 140, a function literal at line 80, a function literal at line 181, …). 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.
D2 · Cognitive Complexity · enzyme_pathway_builder.generate_pathway_report (cognitive 52) · ×1
  • enzyme_pathway_builder.generate_pathway_report (cognitive 52) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:805 — enzyme_pathway_builder.generate_pathway_report has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (30 pts), loops 9 (21 pts), boolean chains 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.
D2 · Cognitive Complexity · check_docs.main (cognitive 52) · ×1
  • check_docs.main (cognitive 52) docs-site/scripts/check_docs.py:64 — check_docs.main has cognitive complexity 52 (threshold 15). Drivers by points: if/else 11 (31 pts), loops 9 (16 pts), boolean chains 5 (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.
D2 · Cognitive Complexity · component-page.openValidationModal (cognitive 51) · ×1
  • component-page.openValidationModal (cognitive 51) docs/js/component-page.js:1371 — component-page.openValidationModal has cognitive complexity 51 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 21, match/switch 1 (2 pts), ternaries 1 (nesting depth added 12). Of this number, 18 points are the body's own statements and 33 belong to 7 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.
D2 · Cognitive Complexity · prompts.getStepConfig (cognitive 49) · ×1
  • prompts.getStepConfig (cognitive 49) cli-tool/src/prompts.js:79 — prompts.getStepConfig has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 14, ternaries 4 (8 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · stack.mcpSection (cognitive 48) · ×1
  • stack.mcpSection (cognitive 48) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:646 — stack.mcpSection has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 10 (15 pts), boolean chains 8, loops 4 (5 pts) (nesting depth added 18). Of this number, 34 points are the body's own statements and 14 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.
D2 · Cognitive Complexity · stack.pluginsSection (cognitive 48) · ×1
  • stack.pluginsSection (cognitive 48) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:720 — stack.pluginsSection has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 11 (17 pts), boolean chains 6, loops 4 (5 pts) (nesting depth added 19). Of this number, 31 points are the body's own statements and 17 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.
D2 · Cognitive Complexity · pudu-task.main (cognitive 48) · ×1
  • pudu-task.main (cognitive 48) cli-tool/components/skills/development/pudu-task-telemetry/scripts/pudu-task.mjs:51 — pudu-task.main has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 12, ternaries 5 (9 pts), error handling 4 (8 pts) (nesting depth added 12). Of this number, 20 points are the body's own statements and 28 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.
D2 · Cognitive Complexity · SearchModal.SearchModal (cognitive 48) · ×1
  • SearchModal.SearchModal (cognitive 48) dashboard/src/components/SearchModal.tsx:25 — SearchModal.SearchModal has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 14, ternaries 8 (nesting depth added 2). Most of this is not in the body itself: 7 of the 48 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 55, a function literal at line 145, a function literal at line 294, …). 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.
D2 · Cognitive Complexity · register.register (cognitive 46) · ×1
  • register.register (cognitive 46) cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:327 — register.register has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (20 pts), ternaries 13 (16 pts), boolean chains 7, error handling 2, loops 1 (nesting depth added 6). None of this is in the body itself: all 46 points belong to 9 function literals inside it that branch (lines 372, 451, 506, …). 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.
D2 · Cognitive Complexity · web_game_playwright_client.doChoreography (cognitive 46) · ×1
  • web_game_playwright_client.doChoreography (cognitive 46) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:227 — web_game_playwright_client.doChoreography has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 5 (20 pts), if/else 6 (15 pts), loops 4 (7 pts), boolean chains 4 (nesting depth added 27). Of this number, 43 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · ScientificSchematicGenerator._extract_image_from_response (cognitive 46) · ×1
  • ScientificSchematicGenerator._extract_image_from_response (cognitive 46) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:235 — ScientificSchematicGenerator._extract_image_from_response has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (38 pts), boolean chains 5, loops 1 (2 pts), error handling 1 (nesting depth added 24). 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.
D2 · Cognitive Complexity · index.getAvailableAgentsFromGitHub (cognitive 44) · ×1
  • index.getAvailableAgentsFromGitHub (cognitive 44) cli-tool/src/index.js:1286 — index.getAvailableAgentsFromGitHub has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 3 (8 pts), error handling 3 (5 pts), boolean chains 4, ternaries 1 (4 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.
D2 · Cognitive Complexity · index.installMultipleComponents (cognitive 44) · ×1
  • index.installMultipleComponents (cognitive 44) cli-tool/src/index.js:1979 — index.installMultipleComponents has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (19 pts), ternaries 9 (18 pts), error handling 2 (3 pts), boolean chains 2, loops 2 (nesting depth added 11). Of this number, 42 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · CartSidebar.CartSidebar (cognitive 44) · ×1
  • CartSidebar.CartSidebar (cognitive 44) dashboard/src/components/CartSidebar.tsx:33 — CartSidebar.CartSidebar has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (22 pts), ternaries 7 (9 pts), boolean chains 7, error handling 4 (5 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 8 of the 44 points are its own statements and the rest belongs to 12 function items inside it that branch (sendToComputer, generateCommand, saveAsCollection, …). 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.
D2 · Cognitive Complexity · ComponentPageManager.renderMetadataSection (cognitive 44) · ×1
  • ComponentPageManager.renderMetadataSection (cognitive 44) docs/js/component-page.js:382 — ComponentPageManager.renderMetadataSection has cognitive complexity 44 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 12, error handling 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.
D2 · Cognitive Complexity · search-functionality.loadComponentsForSearch (cognitive 44) · ×1
  • search-functionality.loadComponentsForSearch (cognitive 44) docs/js/search-functionality.js:133 — search-functionality.loadComponentsForSearch has cognitive complexity 44 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 17, loops 3 (8 pts), error handling 1 (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.
D2 · Cognitive Complexity · generate_review.build_run (cognitive 44) · ×1
  • generate_review.build_run (cognitive 44) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:85 — generate_review.build_run has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (27 pts), error handling 3 (10 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 25). 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.
D2 · Cognitive Complexity · prepare_batch_csv.validate_csv (cognitive 44) · ×1
  • prepare_batch_csv.validate_csv (cognitive 44) cli-tool/components/skills/scientific/diffdock/scripts/prepare_batch_csv.py:61 — prepare_batch_csv.validate_csv has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 7, loops 2 (4 pts), error handling 1 (nesting depth added 17). 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.
D2 · Cognitive Complexity · ComponentTerminal.ComponentTerminal (cognitive 43) · ×1
  • ComponentTerminal.ComponentTerminal (cognitive 43) dashboard/src/components/ComponentTerminal.tsx:318 — ComponentTerminal.ComponentTerminal has cognitive complexity 43 (threshold 15). Drivers by points: if/else 24 (29 pts), boolean chains 6, loops 3 (4 pts), ternaries 2 (4 pts) (nesting depth added 8). Most of this is not in the body itself: 3 of the 43 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 422, 351, 387, …). 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.
D2 · Cognitive Complexity · api_validator.check_openapi_spec (cognitive 43) · ×1
  • api_validator.check_openapi_spec (cognitive 43) cli-tool/components/skills/development/api-patterns/scripts/api_validator.py:37 — api_validator.check_openapi_spec has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (33 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (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.
D2 · Cognitive Complexity · SlideImageGenerator._extract_image_from_response (cognitive 43) · ×1
  • SlideImageGenerator._extract_image_from_response (cognitive 43) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:250 — SlideImageGenerator._extract_image_from_response has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (35 pts), boolean chains 5, loops 1 (2 pts), error handling 1 (nesting depth added 23). 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.
D2 · Cognitive Complexity · implement_entity_connections.implement_connections (cognitive 42) · ×1
  • implement_entity_connections.implement_connections (cognitive 42) cli-tool/components/agents/obsidian-ops-team/Scripts/implement_entity_connections.py:116 — implement_entity_connections.implement_connections has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (38 pts), boolean chains 2, loops 2 (nesting depth added 28). 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.
D2 · Cognitive Complexity · improve_description.improve_description (cognitive 42) · ×1
  • improve_description.improve_description (cognitive 42) cli-tool/components/skills/development/skill-development/scripts/improve_description.py:50 — improve_description.improve_description has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 5 (14 pts), loops 4 (10 pts), boolean chains 3 (nesting depth added 19). 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.
D2 · Cognitive Complexity · HealthChecker.checkMCPConfigurationSyntax (cognitive 41) · ×1
  • HealthChecker.checkMCPConfigurationSyntax (cognitive 41) cli-tool/src/health-check.js:650 — HealthChecker.checkMCPConfigurationSyntax has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (29 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 24). 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.
D2 · Cognitive Complexity · rules.bashParts (cognitive 41) · ×1
  • rules.bashParts (cognitive 41) REDACTED:407 — rules.bashParts has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 8, loops 3 (5 pts), ternaries 1 (3 pts) (nesting depth added 17). 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.
D2 · Cognitive Complexity · subagent-read-only-guard.tokenize (cognitive 41) · ×1
  • subagent-read-only-guard.tokenize (cognitive 41) cli-tool/components/hooks/security/subagent-read-only-guard.py:123 — subagent-read-only-guard.tokenize has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 23). 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.
D2 · Cognitive Complexity · CitationValidator.validate_entry (cognitive 41) · ×1
  • CitationValidator.validate_entry (cognitive 41) cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:95 — CitationValidator.validate_entry has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 17). 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.
D2 · Cognitive Complexity · substructure_filter.main (cognitive 41) · ×1
  • substructure_filter.main (cognitive 41) cli-tool/components/skills/scientific/rdkit/scripts/substructure_filter.py:254 — substructure_filter.main has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 5 (11 pts), ternaries 2, boolean chains 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.
D2 · Cognitive Complexity · generate_report.generate_html (cognitive 40) · ×1
  • generate_report.generate_html (cognitive 40) cli-tool/components/skills/development/skill-development/scripts/generate_report.py:16 — generate_report.generate_html has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 11 (23 pts), loops 7 (12 pts), if/else 4 (5 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.
D2 · Cognitive Complexity · build_decision_tree.simple_algorithm_to_tikz (cognitive 40) · ×1
  • build_decision_tree.simple_algorithm_to_tikz (cognitive 40) cli-tool/components/skills/scientific/clinical-decision-support/scripts/build_decision_tree.py:102 — build_decision_tree.simple_algorithm_to_tikz has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (35 pts), loops 2 (5 pts) (nesting depth added 26). 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.
D2 · Cognitive Complexity · file-operations.downloadDirectoryFromGitHub (cognitive 39) · ×1
  • file-operations.downloadDirectoryFromGitHub (cognitive 39) cli-tool/src/file-operations.js:74 — file-operations.downloadDirectoryFromGitHub has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 5, ternaries 2 (5 pts), error handling 2 (4 pts), loops 1 (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.
D2 · Cognitive Complexity · StateCalculator.determineConversationState (cognitive 39) · ×1
  • StateCalculator.determineConversationState (cognitive 39) cli-tool/src/analytics/core/StateCalculator.js:20 — StateCalculator.determineConversationState has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (34 pts), boolean chains 3, ternaries 1 (2 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.
D2 · Cognitive Complexity · detect.reasonFor (cognitive 39) · ×1
  • detect.reasonFor (cognitive 39) REDACTED:177 — detect.reasonFor has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 10, ternaries 2 (4 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · register.applyProfile (cognitive 39) · ×1
  • register.applyProfile (cognitive 39) cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:199 — register.applyProfile has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 3 (9 pts), boolean chains 4, error handling 1 (4 pts), ternaries 2 (nesting depth added 17). Of this number, 38 points are the body's own statements and 1 belongs 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.
D2 · Cognitive Complexity · rules.parseJev (cognitive 39) · ×1
  • rules.parseJev (cognitive 39) REDACTED:244 — rules.parseJev has cognitive complexity 39 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · _Builder._ingest (cognitive 39) · ×1
  • _Builder._ingest (cognitive 39) cli-tool/components/hooks/monitoring/context-timeline.py:308 — _Builder._ingest has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 9, loops 3 (7 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.
D2 · Cognitive Complexity · stack.hooksSection.scopes (cognitive 38) · ×1
  • stack.hooksSection.scopes (cognitive 38) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:595 — stack.hooksSection.scopes has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 7 (30 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 26). 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.
D2 · Cognitive Complexity · coderio-skill.main (cognitive 38) · ×1
  • coderio-skill.main (cognitive 38) cli-tool/components/skills/design-to-code/scripts/coderio-skill.mjs:100 — coderio-skill.main has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 16, ternaries 1 (2 pts), error handling 1, match/switch 1 (nesting depth added 9). Of this number, 33 points are the body's own statements and 5 belong to 4 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.
D2 · Cognitive Complexity · HealthChecker.analyzeSettingsStructure (cognitive 37) · ×1
  • HealthChecker.analyzeSettingsStructure (cognitive 37) cli-tool/src/health-check.js:1204 — HealthChecker.analyzeSettingsStructure has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 6, loops 2 (4 pts), ternaries 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.
D2 · Cognitive Complexity · chats.conversations (cognitive 37) · ×1
  • chats.conversations (cognitive 37) cli-tool/components/mods/productivity/session-chats/hooks/chats.ts:195 — chats.conversations has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 6 (10 pts), ternaries 4 (10 pts), boolean chains 3 (nesting depth added 18). Of this number, 31 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · index.formatReport (cognitive 37) · ×1
  • index.formatReport (cognitive 37) cloudflare-workers/pulse/index.js:565 — index.formatReport has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (27 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (3 pts) (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.
D2 · Cognitive Complexity · validate_treatment_plan.display_validation_results (cognitive 37) · ×1
  • validate_treatment_plan.display_validation_results (cognitive 37) cli-tool/components/skills/scientific/treatment-plans/scripts/validate_treatment_plan.py:173 — validate_treatment_plan.display_validation_results has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (23 pts), ternaries 5 (8 pts), loops 3 (6 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · analyzeAgentUsage (cognitive 37) · ×1
  • analyzeAgentUsage (cognitive 37) cli-tool/src/analytics/core/AgentAnalyzer.js:40 — analyzeAgentUsage has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 12, ternaries 4 (9 pts), loops 1 (nesting depth added 14). Most of this is not in the body itself: 6 of the 37 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 70, 55, 140, …). 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.
D2 · Cognitive Complexity · ComponentPageManager.renderSecurityValidation (cognitive 36) · ×1
  • ComponentPageManager.renderSecurityValidation (cognitive 36) docs/js/component-page.js:209 — ComponentPageManager.renderSecurityValidation has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 14, ternaries 1 (2 pts) (nesting depth added 4). Of this number, 25 points are the body's own statements and 11 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.
D2 · Cognitive Complexity · subagent-read-only-guard.check_git (cognitive 36) · ×1
  • subagent-read-only-guard.check_git (cognitive 36) cli-tool/components/hooks/security/subagent-read-only-guard.py:207 — subagent-read-only-guard.check_git has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 14, loops 3, ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · structure_analyzer.analyze_structure (cognitive 36) · ×1
  • structure_analyzer.analyze_structure (cognitive 36) cli-tool/components/skills/scientific/pymatgen/scripts/structure_analyzer.py:36 — structure_analyzer.analyze_structure has cognitive complexity 36 (threshold 15). Drivers by points: loops 6 (14 pts), if/else 7 (13 pts), error handling 3 (7 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · rules.sqlCode (cognitive 35) · ×1
  • rules.sqlCode (cognitive 35) REDACTED:50 — rules.sqlCode has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 2 (6 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 17). 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.
D2 · Cognitive Complexity · DailyNotesConnector.find_related_content (cognitive 35) · ×1
  • DailyNotesConnector.find_related_content (cognitive 35) cli-tool/components/agents/obsidian-ops-team/Scripts/daily_notes_connector.py:92 — DailyNotesConnector.find_related_content has cognitive complexity 35 (threshold 15). Drivers by points: if/else 5 (24 pts), loops 3 (9 pts), boolean chains 2 (nesting depth added 25). 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.
D2 · Cognitive Complexity · OKRGenerator.calculate_alignment_score (cognitive 35) · ×1
  • OKRGenerator.calculate_alignment_score (cognitive 35) cli-tool/components/skills/business-marketing/product-strategist/scripts/okr_cascade_generator.py:270 — OKRGenerator.calculate_alignment_score has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 5 (12 pts), boolean chains 2 (nesting depth added 17). 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.
D2 · Cognitive Complexity · enzyme_pathway_builder.find_enzymes_for_transformation (cognitive 35) · ×1
  • enzyme_pathway_builder.find_enzymes_for_transformation (cognitive 35) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:274 — enzyme_pathway_builder.find_enzymes_for_transformation has cognitive complexity 35 (threshold 15). Drivers by points: loops 6 (14 pts), if/else 4 (8 pts), error handling 3 (7 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 19). 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.
D2 · Cognitive Complexity · fda_examples.example_substance_lookup (cognitive 35) · ×1
  • fda_examples.example_substance_lookup (cognitive 35) cli-tool/components/skills/scientific/fda-database/scripts/fda_examples.py:144 — fda_examples.example_substance_lookup has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (32 pts), loops 1 (2 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · TrendingView.TrendingView (cognitive 34) · ×1
  • TrendingView.TrendingView (cognitive 34) dashboard/src/components/TrendingView.tsx:54 — TrendingView.TrendingView has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 12 (21 pts), if/else 7 (10 pts), boolean chains 3 (nesting depth added 12). Most of this is not in the body itself: 5 of the 34 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 364, a function literal at line 273, a function literal at line 371, …). 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.
D2 · Cognitive Complexity · generate_report.format_conversation_history (cognitive 34) · ×1
  • generate_report.format_conversation_history (cognitive 34) cli-tool/components/skills/scientific/biomni/scripts/generate_report.py:24 — generate_report.format_conversation_history has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 20). 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.
D2 · Cognitive Complexity · enzyme_pathway_builder.find_pathway_for_product (cognitive 34) · ×1
  • enzyme_pathway_builder.find_pathway_for_product (cognitive 34) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:348 — enzyme_pathway_builder.find_pathway_for_product has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 4 (10 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · enzyme_pathway_builder.calculate_pathway_feasibility (cognitive 34) · ×1
  • enzyme_pathway_builder.calculate_pathway_feasibility (cognitive 34) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:596 — enzyme_pathway_builder.calculate_pathway_feasibility has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 3 (7 pts), error handling 1 (2 pts) (nesting depth added 17). 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.
D2 · Cognitive Complexity · phase_diagram_generator.generate_phase_diagram (cognitive 34) · ×1
  • phase_diagram_generator.generate_phase_diagram (cognitive 34) cli-tool/components/skills/scientific/pymatgen/scripts/phase_diagram_generator.py:48 — phase_diagram_generator.generate_phase_diagram has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 6 (15 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · ScientificSchematicGenerator.generate_image (cognitive 34) · ×1
  • ScientificSchematicGenerator.generate_image (cognitive 34) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:342 — ScientificSchematicGenerator.generate_image has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 1 (4 pts), ternaries 1 (4 pts), boolean chains 2, error handling 2 (nesting depth added 17). 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.
D2 · Cognitive Complexity · macos_window_info.swift.top-level code (cognitive 34) · ×1
  • macos_window_info.swift.top-level code (cognitive 34) cli-tool/components/skills/media/screenshot/scripts/macos_window_info.swift:38 — macos_window_info.swift.top-level code has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 7, loops 1, ternaries 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.
D2 · Cognitive Complexity · register.scanInstalled (cognitive 33) · ×1
  • register.scanInstalled (cognitive 33) cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:97 — register.scanInstalled has cognitive complexity 33 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 5 (13 pts), ternaries 1 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · rules.parseRule (cognitive 33) · ×1
  • rules.parseRule (cognitive 33) REDACTED:194 — rules.parseRule has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (20 pts), error handling 1 (4 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · model-selection.recommend (cognitive 33) · ×1
  • model-selection.recommend (cognitive 33) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/model-selection.mjs:23 — model-selection.recommend has cognitive complexity 33 (threshold 15). Drivers by points: if/else 3 (11 pts), ternaries 6 (11 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 16). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · extract_form_field_info.get_field_info (cognitive 33) · ×1
  • extract_form_field_info.get_field_info (cognitive 33) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:47 — extract_form_field_info.get_field_info has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 4 (5 pts), error handling 1 (4 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.
D2 · Cognitive Complexity · generate_image.generate_image (cognitive 33) · ×1
  • generate_image.generate_image (cognitive 33) cli-tool/components/skills/scientific/generate-image/scripts/generate_image.py:75 — generate_image.generate_image has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (27 pts), loops 1 (4 pts), boolean chains 1, error handling 1 (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.
D2 · Cognitive Complexity · browseCatalog (cognitive 33) · ×1
  • browseCatalog (cognitive 33) cli-tool/src/catalog-browser.js:212 — browseCatalog has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 5 (9 pts), loops 4 (6 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 13). Of this number, 29 points are the body's own statements and 4 belong to 9 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.
D2 · Cognitive Complexity · index.installWorkflow (cognitive 32) · ×1
  • index.installWorkflow (cognitive 32) cli-tool/src/index.js:2198 — index.installWorkflow has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 6 (14 pts), boolean chains 1, error handling 1, ternaries 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.
D2 · Cognitive Complexity · certifications.validateItem (cognitive 32) · ×1
  • certifications.validateItem (cognitive 32) dashboard/src/lib/certifications.ts:191 — certifications.validateItem has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 13, loops 3 (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.
D2 · Cognitive Complexity · check_bounding_boxes.get_bounding_box_messages (cognitive 32) · ×1
  • check_bounding_boxes.get_bounding_box_messages (cognitive 32) cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py:15 — check_bounding_boxes.get_bounding_box_messages has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 19). 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.
D2 · Cognitive Complexity · text_to_speech._run_speak_batch (cognitive 32) · ×1
  • text_to_speech._run_speak_batch (cognitive 32) cli-tool/components/skills/media/speech/scripts/text_to_speech.py:354 — text_to_speech._run_speak_batch has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 5, loops 1, ternaries 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.
D2 · Cognitive Complexity · analyze_results.print_summary (cognitive 32) · ×1
  • analyze_results.print_summary (cognitive 32) cli-tool/components/skills/scientific/diffdock/scripts/analyze_results.py:137 — analyze_results.print_summary has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · substructure_filter.filter_molecules (cognitive 32) · ×1
  • substructure_filter.filter_molecules (cognitive 32) cli-tool/components/skills/scientific/rdkit/scripts/substructure_filter.py:111 — substructure_filter.filter_molecules has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 3 (7 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.
D2 · Cognitive Complexity · prompts.createPrompts (cognitive 31) · ×1
  • prompts.createPrompts (cognitive 31) cli-tool/src/prompts.js:278 — prompts.createPrompts has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 17, if/else 11, ternaries 3. Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 420, 323, 357, …). 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.
D2 · Cognitive Complexity · index.installIndividualPlugin (cognitive 31) · ×1
  • index.installIndividualPlugin (cognitive 31) cli-tool/src/index.js:1643 — index.installIndividualPlugin has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 5 (11 pts), boolean chains 3, error handling 2, loops 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.
D2 · Cognitive Complexity · rex-tty.register · ×1
  • rex-tty.register::pane (cognitive 31) cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts:134 — rex-tty.register::pane has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 11, if/else 6 (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.
D2 · Cognitive Complexity · task_manager.update_task_status (cognitive 31) · ×1
  • task_manager.update_task_status (cognitive 31) cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:168 — task_manager.update_task_status has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (26 pts), boolean chains 4, loops 1 (nesting depth added 17). 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.
D2 · Cognitive Complexity · PresentationValidator._check_pptx_content (cognitive 31) · ×1
  • PresentationValidator._check_pptx_content (cognitive 31) cli-tool/components/skills/scientific/scientific-slides/scripts/validate_presentation.py:181 — PresentationValidator._check_pptx_content has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 4 (10 pts), ternaries 2 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · geo_checker.check_page (cognitive 31) · ×1
  • geo_checker.check_page (cognitive 31) cli-tool/components/skills/utilities/geo-fundamentals/scripts/geo_checker.py:99 — geo_checker.check_page has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 1, error handling 1, ternaries 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · createInstallUI.runStep (cognitive 31) · ×1
  • createInstallUI.runStep (cognitive 31) cli-tool/src/install-ui.js:216 — createInstallUI.runStep has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 9 (17 pts), if/else 8 (9 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 9). Of this number, 23 points are the body's own statements and 8 belong to 9 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.
D2 · Cognitive Complexity · index.html.drawPixelChar (cognitive 30) · ×1
  • index.html.drawPixelChar (cognitive 30) cli-tool/components/hooks/automation/plan-mode-game/index.html:557 — index.html.drawPixelChar has cognitive complexity 30 (threshold 15). Drivers by points: loops 6 (14 pts), if/else 9 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 13). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D2 · Cognitive Complexity · chess.attacked (cognitive 30) · ×1
  • chess.attacked (cognitive 30) cli-tool/components/mods/games/chess/hooks/chess.ts:111 — chess.attacked has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 6 (9 pts), boolean chains 5, ternaries 1 (nesting depth added 13). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D2 · Cognitive Complexity · rules.pushTargets (cognitive 30) · ×1
  • rules.pushTargets (cognitive 30) REDACTED:171 — rules.pushTargets has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 5, ternaries 3 (4 pts), loops 3 (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.
D2 · Cognitive Complexity · audit.runAudit (cognitive 30) · ×1
  • audit.runAudit (cognitive 30) cli-tool/components/skills/web-development/roier-seo/scripts/audit.js:46 — audit.runAudit has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 8, error handling 1, 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.
D2 · Cognitive Complexity · design_system.format_ascii_box (cognitive 30) · ×1
  • design_system.format_ascii_box (cognitive 30) cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:236 — design_system.format_ascii_box has cognitive complexity 30 (threshold 15). Drivers by points: loops 9 (16 pts), if/else 13, boolean chains 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · compound_cross_reference.get_chembl_info (cognitive 30) · ×1
  • compound_cross_reference.get_chembl_info (cognitive 30) cli-tool/components/skills/scientific/bioservices/scripts/compound_cross_reference.py:222 — compound_cross_reference.get_chembl_info has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 1 (4 pts), boolean chains 1, error handling 1 (nesting depth added 16). 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.
D2 · Cognitive Complexity · fetch_gene_data.display_gene_info (cognitive 30) · ×1
  • fetch_gene_data.display_gene_info (cognitive 30) cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:157 — fetch_gene_data.display_gene_info has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 17). 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.
D2 · Cognitive Complexity · search_databases.format_search_results (cognitive 30) · ×1
  • search_databases.format_search_results (cognitive 30) cli-tool/components/skills/scientific/literature-review/scripts/search_databases.py:12 — search_databases.format_search_results has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 2 (4 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.
D2 · Cognitive Complexity · live-preview.register (cognitive 29) · ×1
  • live-preview.register (cognitive 29) cli-tool/components/mods/ui/live-preview/hooks/live-preview.tsx:109 — live-preview.register has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 7 (8 pts), boolean chains 7, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 166, 123, 151, …). 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.
D2 · Cognitive Complexity · coderio-skill.applyPropsAndStateToProtocol (cognitive 29) · ×1
  • coderio-skill.applyPropsAndStateToProtocol (cognitive 29) cli-tool/components/skills/design-to-code/scripts/coderio-skill.mjs:54 — coderio-skill.applyPropsAndStateToProtocol has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 17). 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.
D2 · Cognitive Complexity · JobsPreview.JobsPreview (cognitive 29) · ×1
  • JobsPreview.JobsPreview (cognitive 29) dashboard/src/components/JobsPreview.tsx:66 — JobsPreview.JobsPreview has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 10, if/else 4 (nesting depth added 5). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 115, a function literal at line 180, handleJobClick). 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.
D2 · Cognitive Complexity · fix_quoted_tags.fix_quoted_tags (cognitive 29) · ×1
  • fix_quoted_tags.fix_quoted_tags (cognitive 29) cli-tool/components/agents/obsidian-ops-team/Scripts/fix_quoted_tags.py:11 — fix_quoted_tags.fix_quoted_tags has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (20 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · implement_entity_connections.add_link_to_file (cognitive 29) · ×1
  • implement_entity_connections.add_link_to_file (cognitive 29) cli-tool/components/agents/obsidian-ops-team/Scripts/implement_entity_connections.py:43 — implement_entity_connections.add_link_to_file has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (24 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.
D2 · Cognitive Complexity · risk_calculator.interactive_mode (cognitive 29) · ×1
  • risk_calculator.interactive_mode (cognitive 29) cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py:204 — risk_calculator.interactive_mode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 5 (13 pts), boolean chains 1 (nesting depth added 17). 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.
D2 · Cognitive Complexity · quick_validate.validate_skill (cognitive 29) · ×1
  • quick_validate.validate_skill (cognitive 29) cli-tool/components/skills/development/skill-development/scripts/quick_validate.py:12 — quick_validate.validate_skill has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · task_manager.parse_tasks_from_markdown (cognitive 29) · ×1
  • task_manager.parse_tasks_from_markdown (cognitive 29) cli-tool/components/skills/development/task-execution-engine/scripts/task_manager.py:77 — task_manager.parse_tasks_from_markdown has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 3, loops 1 (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.
D2 · Cognitive Complexity · HealthChecker.checkHookCommands (cognitive 28) · ×1
  • HealthChecker.checkHookCommands (cognitive 28) cli-tool/src/health-check.js:1007 — HealthChecker.checkHookCommands has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2 (7 pts), loops 2 (4 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · rules.selfProtection (cognitive 28) · ×1
  • rules.selfProtection (cognitive 28) REDACTED:742 — rules.selfProtection has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 7, ternaries 1 (2 pts), loops 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 11 belong to 3 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.
D2 · Cognitive Complexity · SendToRepoModal.SendToRepoModal (cognitive 28) · ×1
  • SendToRepoModal.SendToRepoModal (cognitive 28) dashboard/src/components/SendToRepoModal.tsx:96 — SendToRepoModal.SendToRepoModal has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 12, if/else 11 (12 pts), error handling 2, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 176, loadRepos, a function literal at line 113, …). 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.
D2 · Cognitive Complexity · find_keyword_connections.find_keyword_connections (cognitive 28) · ×1
  • find_keyword_connections.find_keyword_connections (cognitive 28) cli-tool/components/agents/obsidian-ops-team/Scripts/find_keyword_connections.py:39 — find_keyword_connections.find_keyword_connections has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 5 (9 pts) (nesting depth added 17). 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.
D2 · Cognitive Complexity · subagent-read-only-guard.check_program (cognitive 28) · ×1
  • subagent-read-only-guard.check_program (cognitive 28) cli-tool/components/hooks/security/subagent-read-only-guard.py:253 — subagent-read-only-guard.check_program has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 4, loops 2 (3 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.
D2 · Cognitive Complexity · batch_id_converter.batch_convert (cognitive 28) · ×1
  • batch_id_converter.batch_convert (cognitive 28) cli-tool/components/skills/scientific/bioservices/scripts/batch_id_converter.py:94 — batch_id_converter.batch_convert has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 2 (6 pts), loops 3 (5 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.
D2 · Cognitive Complexity · SlideImageGenerator.generate_slide (cognitive 28) · ×1
  • SlideImageGenerator.generate_slide (cognitive 28) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:532 — SlideImageGenerator.generate_slide has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 5, boolean chains 4, loops 3 (4 pts), error handling 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.
D2 · Cognitive Complexity · listSkillTree (cognitive 28) · ×1
  • listSkillTree (cognitive 28) cli-tool/src/external-skill.js:179 — listSkillTree has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 5, ternaries 2, loops 1, other 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.
D2 · Cognitive Complexity · ClaudeAnalytics.getClaudeSessionInfo (cognitive 27) · ×1
  • ClaudeAnalytics.getClaudeSessionInfo (cognitive 27) REDACTED:1636 — ClaudeAnalytics.getClaudeSessionInfo has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 2 (4 pts), boolean chains 1, error handling 1, ternaries 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.
D2 · Cognitive Complexity · web_game_playwright_client.main (cognitive 27) · ×1
  • web_game_playwright_client.main (cognitive 27) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:262 — web_game_playwright_client.main has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 9). Of this number, 24 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.
D2 · Cognitive Complexity · validate_files.validate_files (cognitive 27) · ×1
  • validate_files.validate_files (cognitive 27) cli-tool/components/skills/scientific/deeptools/scripts/validate_files.py:76 — validate_files.validate_files has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 3 (6 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.
D2 · Cognitive Complexity · check_completeness.display_results (cognitive 27) · ×1
  • check_completeness.display_results (cognitive 27) cli-tool/components/skills/scientific/treatment-plans/scripts/check_completeness.py:127 — check_completeness.display_results has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13, loops 4 (7 pts), ternaries 6 (7 pts) (nesting depth added 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.
D2 · Cognitive Complexity · index.installComponentFromWorkflow (cognitive 26) · ×1
  • index.installComponentFromWorkflow (cognitive 26) cli-tool/src/index.js:2477 — index.installComponentFromWorkflow has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, error handling 2 (3 pts), loops 1 (3 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.
D2 · Cognitive Complexity · web_game_playwright_client.parseArgs (cognitive 26) · ×1
  • web_game_playwright_client.parseArgs (cognitive 26) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:5 — web_game_playwright_client.parseArgs has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 11, 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.
D2 · Cognitive Complexity · ValidationOrchestrator._formatComponentResult (cognitive 26) · ×1
  • ValidationOrchestrator._formatComponentResult (cognitive 26) cli-tool/src/validation/ValidationOrchestrator.js:216 — ValidationOrchestrator._formatComponentResult has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (7 pts), ternaries 4 (7 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · check_staleness.print_report (cognitive 26) · ×1
  • check_staleness.print_report (cognitive 26) cli-tool/components/skills/enterprise-communication/session-handoff/scripts/check_staleness.py:320 — check_staleness.print_report has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 3 (8 pts), ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · generate_survival_analysis.generate_report (cognitive 26) · ×1
  • generate_survival_analysis.generate_report (cognitive 26) cli-tool/components/skills/scientific/clinical-decision-support/scripts/generate_survival_analysis.py:257 — generate_survival_analysis.generate_report has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 4 (7 pts), error handling 2 (4 pts), loops 3 (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.
D2 · Cognitive Complexity · filter_molecules.generate_summary (cognitive 26) · ×1
  • filter_molecules.generate_summary (cognitive 26) cli-tool/components/skills/scientific/medchem/scripts/filter_molecules.py:205 — filter_molecules.generate_summary has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · security_scan.scan_code_patterns (cognitive 26) · ×1
  • security_scan.scan_code_patterns (cognitive 26) cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:236 — security_scan.scan_code_patterns has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (10 pts), error handling 1 (3 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.
D2 · Cognitive Complexity · SessionAnalyzer.extractSessionsFromClaudeInfo (cognitive 25) · ×1
  • SessionAnalyzer.extractSessionsFromClaudeInfo (cognitive 25) cli-tool/src/analytics/core/SessionAnalyzer.js:305 — SessionAnalyzer.extractSessionsFromClaudeInfo has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (8 pts), ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 420, 378, 309, …). 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.
D2 · Cognitive Complexity · catalog.parseTrending (cognitive 25) · ×1
  • catalog.parseTrending (cognitive 25) cli-tool/components/mods/productivity/aitmpl/hooks/catalog.ts:62 — catalog.parseTrending has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 6 (8 pts), boolean chains 5, loops 2 (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.
D2 · Cognitive Complexity · jev.readDecision (cognitive 25) · ×1
  • jev.readDecision (cognitive 25) cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/jev.ts:113 — jev.readDecision has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 5 (8 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (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.
D2 · Cognitive Complexity · session-chats.detail (cognitive 25) · ×1
  • session-chats.detail (cognitive 25) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:334 — session-chats.detail has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (17 pts), if/else 5, boolean chains 3 (nesting depth added 3). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 351, 337). 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.
D2 · Cognitive Complexity · stack.hooksSection (cognitive 25) · ×1
  • stack.hooksSection (cognitive 25) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:588 — stack.hooksSection has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (17 pts), boolean chains 3, loops 2 (3 pts), if/else 1 (2 pts) (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.
D2 · Cognitive Complexity · index.formatReport (cognitive 25) · ×1
  • index.formatReport (cognitive 25) cloudflare-workers/daily-health-report/index.js:193 — index.formatReport has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (8 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 11). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · stack-link.decodeStack (cognitive 25) · ×1
  • stack-link.decodeStack (cognitive 25) dashboard/src/lib/stack-link.ts:137 — stack-link.decodeStack has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 2 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · _Builder.update (cognitive 25) · ×1
  • _Builder.update (cognitive 25) cli-tool/components/hooks/monitoring/context-timeline.py:278 — _Builder.update has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 4 (10 pts), error handling 1 (4 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.
D2 · Cognitive Complexity · schema_validator.validate_prisma_schema (cognitive 25) · ×1
  • schema_validator.validate_prisma_schema (cognitive 25) cli-tool/components/skills/development/database-design/scripts/schema_validator.py:47 — schema_validator.validate_prisma_schema has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (6 pts), boolean chains 4, error handling 1 (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.
D2 · Cognitive Complexity · i18n_checker.check_hardcoded_strings (cognitive 25) · ×1
  • i18n_checker.check_hardcoded_strings (cognitive 25) cli-tool/components/skills/development/i18n-localization/scripts/i18n_checker.py:131 — i18n_checker.check_hardcoded_strings has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 4 (6 pts), error handling 1 (2 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · SessionAnalyzer.extractSessions (cognitive 24) · ×1
  • SessionAnalyzer.extractSessions (cognitive 24) cli-tool/src/analytics/core/SessionAnalyzer.js:173 — SessionAnalyzer.extractSessions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 9, loops 1 (nesting depth added 6). Of this number, 12 points are the body's own statements and 12 belong to 4 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.
D2 · Cognitive Complexity · catalog-browser.detectProjectTags (cognitive 24) · ×1
  • catalog-browser.detectProjectTags (cognitive 24) cli-tool/src/catalog-browser.js:113 — catalog-browser.detectProjectTags has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (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.
D2 · Cognitive Complexity · policy.route (cognitive 24) · ×1
  • policy.route (cognitive 24) cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts:334 — policy.route has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 6 (8 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · session-chats.reread (cognitive 24) · ×1
  • session-chats.reread (cognitive 24) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:399 — session-chats.reread has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (6 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 9). Of this number, 21 points are the body's own statements and 3 belong to 3 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.
D2 · Cognitive Complexity · IndexPageManager.collectAvailableCategories (cognitive 24) · ×1
  • IndexPageManager.collectAvailableCategories (cognitive 24) docs/js/index-events.js:409 — IndexPageManager.collectAvailableCategories has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 14, if/else 9 (10 pts) (nesting depth added 1). Of this number, 14 points are the body's own statements and 10 belong to 7 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.
D2 · Cognitive Complexity · quick_validate.validate_skill (cognitive 24) · ×1
  • quick_validate.validate_skill (cognitive 24) cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:12 — quick_validate.validate_skill has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 2, error handling 1 (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.
D2 · Cognitive Complexity · GoogleScholarSearcher.search (cognitive 24) · ×1
  • GoogleScholarSearcher.search (cognitive 24) cli-tool/components/skills/scientific/citation-management/scripts/search_google_scholar.py:47 — GoogleScholarSearcher.search has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, error handling 2 (4 pts), ternaries 1 (3 pts), loops 1 (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.
D2 · Cognitive Complexity · enrichment_pipeline.enrichment_pipeline (cognitive 24) · ×1
  • enrichment_pipeline.enrichment_pipeline (cognitive 24) cli-tool/components/skills/scientific/gget/scripts/enrichment_pipeline.py:30 — enrichment_pipeline.enrichment_pipeline has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 5 (7 pts), error handling 3 (5 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · security_scan.scan_dependencies (cognitive 24) · ×1
  • security_scan.scan_dependencies (cognitive 24) cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:97 — security_scan.scan_dependencies has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (4 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 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.
D2 · Cognitive Complexity · agents.getAvailableAgents (cognitive 23) · ×1
  • agents.getAvailableAgents (cognitive 23) cli-tool/src/agents.js:11 — agents.getAvailableAgents has cognitive complexity 23 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 3 (9 pts), boolean chains 1, error handling 1 (nesting depth added 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · external-skill.downloadExternalSkill (cognitive 23) · ×1
  • external-skill.downloadExternalSkill (cognitive 23) cli-tool/src/external-skill.js:258 — external-skill.downloadExternalSkill has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (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.
D2 · Cognitive Complexity · install-ui.createInstallUI.runStep (cognitive 23) · ×1
  • install-ui.createInstallUI.runStep (cognitive 23) cli-tool/src/install-ui.js:216 — install-ui.createInstallUI.runStep has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 8 (9 pts), boolean chains 3, error handling 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · vercel.readCommandStream (cognitive 23) · ×1
  • vercel.readCommandStream (cognitive 23) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/vercel.ts:208 — vercel.readCommandStream has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, error handling 1 (2 pts), loops 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.
D2 · Cognitive Complexity · audit-api.runAudit (cognitive 23) · ×1
  • audit-api.runAudit (cognitive 23) cli-tool/components/skills/web-development/roier-seo/scripts/audit-api.js:38 — audit-api.runAudit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 8, error handling 1, loops 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.
D2 · Cognitive Complexity · MyComponentsView.ProjectTreeNode (cognitive 23) · ×1
  • MyComponentsView.ProjectTreeNode (cognitive 23) dashboard/src/components/MyComponentsView.tsx:228 — MyComponentsView.ProjectTreeNode has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (13 pts), boolean chains 8, if/else 2 (nesting depth added 2). Of this number, 21 points are the body's own statements and 2 belong to 2 function items 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.
D2 · Cognitive Complexity · DailyNotesConnector.process_daily_note (cognitive 23) · ×1
  • DailyNotesConnector.process_daily_note (cognitive 23) cli-tool/components/agents/obsidian-ops-team/Scripts/daily_notes_connector.py:164 — DailyNotesConnector.process_daily_note has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (6 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · secret-scanner.scan_file (cognitive 23) · ×1
  • secret-scanner.scan_file (cognitive 23) cli-tool/components/hooks/security/secret-scanner.py:201 — secret-scanner.scan_file has cognitive complexity 23 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 pts), ternaries 1 (4 pts), boolean chains 2, error handling 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.
D2 · Cognitive Complexity · claude_digest.parse_session_file (cognitive 23) · ×1
  • claude_digest.parse_session_file (cognitive 23) cli-tool/components/skills/enterprise-communication/daily-meeting-update/scripts/claude_digest.py:105 — claude_digest.parse_session_file has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, error handling 2 (3 pts), loops 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.
D2 · Cognitive Complexity · validate_handoff.print_report (cognitive 23) · ×1
  • validate_handoff.print_report (cognitive 23) cli-tool/components/skills/enterprise-communication/session-handoff/scripts/validate_handoff.py:237 — validate_handoff.print_report has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12, loops 5 (10 pts), boolean chains 1 (nesting depth added 5). 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.
D2 · Cognitive Complexity · generate_report.markdown_to_html_simple (cognitive 23) · ×1
  • generate_report.markdown_to_html_simple (cognitive 23) cli-tool/components/skills/scientific/biomni/scripts/generate_report.py:197 — generate_report.markdown_to_html_simple has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (22 pts), 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.
D2 · Cognitive Complexity · terminology_validator.main (cognitive 23) · ×1
  • terminology_validator.main (cognitive 23) cli-tool/components/skills/scientific/clinical-reports/scripts/terminology_validator.py:71 — terminology_validator.main has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (9 pts), error handling 1, ternaries 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.
D2 · Cognitive Complexity · slides_to_pdf.get_image_files (cognitive 23) · ×1
  • slides_to_pdf.get_image_files (cognitive 23) cli-tool/components/skills/scientific/scientific-slides/scripts/slides_to_pdf.py:31 — slides_to_pdf.get_image_files has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (8 pts) (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.
D2 · Cognitive Complexity · slides_to_pdf.combine_images_to_pdf (cognitive 23) · ×1
  • slides_to_pdf.combine_images_to_pdf (cognitive 23) cli-tool/components/skills/scientific/scientific-slides/scripts/slides_to_pdf.py:74 — slides_to_pdf.combine_images_to_pdf has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (4 pts), error handling 2 (3 pts), loops 2 (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.
D2 · Cognitive Complexity · community_maintainers.load_community_files (cognitive 23) · ×1
  • community_maintainers.load_community_files (cognitive 23) cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:226 — community_maintainers.load_community_files has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 2 (3 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.
D2 · Cognitive Complexity · security_scan.scan_configuration (cognitive 23) · ×1
  • security_scan.scan_configuration (cognitive 23) cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:296 — security_scan.scan_configuration has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (7 pts), error handling 1 (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.
D2 · Cognitive Complexity · validateManifest (cognitive 23) · ×1
  • validateManifest (cognitive 23) cli-tool/src/external-skill.js:49 — validateManifest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 10, other 2 (nesting depth added 2). Of this number, 21 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · ConversationAnalyzer.generateStatusSquares (cognitive 22) · ×1
  • ConversationAnalyzer.generateStatusSquares (cognitive 22) cli-tool/src/analytics/core/ConversationAnalyzer.js:626 — ConversationAnalyzer.generateStatusSquares has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 6 (nesting depth added 5). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 635, 668). 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.
D2 · Cognitive Complexity · ClaudeAnalytics.generateStatusSquares (cognitive 22) · ×1
  • ClaudeAnalytics.generateStatusSquares (cognitive 22) REDACTED:333 — ClaudeAnalytics.generateStatusSquares has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 6 (nesting depth added 5). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 342, 375). 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.
D2 · Cognitive Complexity · index.downloadModFromGitHub · ×1
  • index.downloadModFromGitHub::downloadDirectory (cognitive 22) cli-tool/src/index.js:1756 — index.downloadModFromGitHub::downloadDirectory has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, ternaries 2 (4 pts), loops 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.
D2 · Cognitive Complexity · index.installIndividualMod (cognitive 22) · ×1
  • index.installIndividualMod (cognitive 22) cli-tool/src/index.js:1803 — index.installIndividualMod has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, loops 2, ternaries 2, error handling 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, 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.
D2 · Cognitive Complexity · chess.san (cognitive 22) · ×1
  • chess.san (cognitive 22) cli-tool/components/mods/games/chess/hooks/chess.ts:264 — chess.san has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 9). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · register.register · ×1
  • register.register::forkAt (cognitive 22) cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx:109 — register.register::forkAt has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (14 pts), boolean chains 5, if/else 2 (3 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.
D2 · Cognitive Complexity · SkillSlideView.SkillSlideView (cognitive 22) · ×1
  • SkillSlideView.SkillSlideView (cognitive 22) REDACTED:144 — SkillSlideView.SkillSlideView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9, ternaries 8, boolean chains 5. Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 166, 178, 268). 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.
D2 · Cognitive Complexity · DataLoader.getTotalCounts (cognitive 22) · ×1
  • DataLoader.getTotalCounts (cognitive 22) docs/js/data-loader.js:362 — DataLoader.getTotalCounts has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (14 pts), boolean chains 7, if/else 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.
D2 · Cognitive Complexity · WorkflowManager.highlightYamlLine (cognitive 22) · ×1
  • WorkflowManager.highlightYamlLine (cognitive 22) docs/js/workflows-events.js:881 — WorkflowManager.highlightYamlLine has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · context-monitor.parse_context_from_transcript (cognitive 22) · ×1
  • context-monitor.parse_context_from_transcript (cognitive 22) cli-tool/components/settings/statusline/context-monitor.py:59 — context-monitor.parse_context_from_transcript has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), error handling 2 (3 pts), boolean chains 1, loops 1, ternaries 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.
D2 · Cognitive Complexity · context-monitor.get_session_metrics (cognitive 22) · ×1
  • context-monitor.get_session_metrics (cognitive 22) cli-tool/components/settings/statusline/context-monitor.py:191 — context-monitor.get_session_metrics has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 3 (5 pts), boolean chains 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.
D2 · Cognitive Complexity · user_story_generator.main (cognitive 22) · ×1
  • user_story_generator.main (cognitive 22) cli-tool/components/skills/business-marketing/agile-product-owner/scripts/user_story_generator.py:328 — user_story_generator.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (9 pts), ternaries 1 (2 pts), boolean chains 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.
D2 · Cognitive Complexity · claude_digest.get_sessions_for_date (cognitive 22) · ×1
  • claude_digest.get_sessions_for_date (cognitive 22) cli-tool/components/skills/enterprise-communication/daily-meeting-update/scripts/claude_digest.py:217 — claude_digest.get_sessions_for_date has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (3 pts), ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · enzyme_pathway_builder.suggest_enzyme_substitutions (cognitive 22) · ×1
  • enzyme_pathway_builder.suggest_enzyme_substitutions (cognitive 22) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:533 — enzyme_pathway_builder.suggest_enzyme_substitutions has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 2 (6 pts), error handling 3 (5 pts), if/else 4 (5 pts), loops 3 (5 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.
D2 · Cognitive Complexity · doi_to_bibtex.main (cognitive 22) · ×1
  • doi_to_bibtex.main (cognitive 22) cli-tool/components/skills/scientific/citation-management/scripts/doi_to_bibtex.py:99 — doi_to_bibtex.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (16 pts), error handling 3 (6 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.
D2 · Cognitive Complexity · ensembl_query.main (cognitive 22) · ×1
  • ensembl_query.main (cognitive 22) cli-tool/components/skills/scientific/ensembl-database/scripts/ensembl_query.py:314 — ensembl_query.main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (9 pts), 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.
D2 · Cognitive Complexity · eda_analyzer.analyze_bioinformatics (cognitive 22) · ×1
  • eda_analyzer.analyze_bioinformatics (cognitive 22) cli-tool/components/skills/scientific/exploratory-data-analysis/scripts/eda_analyzer.py:335 — eda_analyzer.analyze_bioinformatics has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 2 (4 pts), error handling 2, loops 1 (2 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.
D2 · Cognitive Complexity · fda_examples.example_veterinary_analysis (cognitive 22) · ×1
  • fda_examples.example_veterinary_analysis (cognitive 22) cli-tool/components/skills/scientific/fda-database/scripts/fda_examples.py:252 — fda_examples.example_veterinary_analysis has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (8 pts), boolean chains 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.
D2 · Cognitive Complexity · extract_metadata.extract_metadata_text (cognitive 22) · ×1
  • extract_metadata.extract_metadata_text (cognitive 22) cli-tool/components/skills/scientific/pydicom/scripts/extract_metadata.py:38 — extract_metadata.extract_metadata_text has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 6 (8 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.
D2 · Cognitive Complexity · visualize_graph.visualize_data (cognitive 22) · ×1
  • visualize_graph.visualize_data (cognitive 22) cli-tool/components/skills/scientific/torch_geometric/scripts/visualize_graph.py:27 — visualize_graph.visualize_data has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4, ternaries 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, 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.
D2 · Cognitive Complexity · sora._get_status (cognitive 22) · ×1
  • sora._get_status (cognitive 22) cli-tool/components/skills/video/sora/scripts/sora.py:382 — sora._get_status has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (6 pts), boolean chains 2, ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · Dashboard.DashboardView (cognitive 21) · ×1
  • Dashboard.DashboardView (cognitive 21) cli-tool/analytics-ui/src/islands/Dashboard.tsx:161 — Dashboard.DashboardView has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 5, if/else 5 (nesting depth added 4). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 180, a function literal at line 364, a function literal at line 193, …). 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.
D2 · Cognitive Complexity · ClaudeAnalytics.loadAgents (cognitive 21) · ×1
  • ClaudeAnalytics.loadAgents (cognitive 21) REDACTED:1336 — ClaudeAnalytics.loadAgents has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (4 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 7). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · agent-detection.detectAgentName (cognitive 21) · ×1
  • agent-detection.detectAgentName (cognitive 21) cli-tool/src/agent-detection.js:54 — agent-detection.detectAgentName has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, boolean chains 6, ternaries 1 (2 pts), error handling 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.
D2 · Cognitive Complexity · register.claudeMoves (cognitive 21) · ×1
  • register.claudeMoves (cognitive 21) cli-tool/components/mods/games/chess/hooks/register.tsx:117 — register.claudeMoves has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 8). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D2 · Cognitive Complexity · register.toolColor (cognitive 21) · ×1
  • register.toolColor (cognitive 21) cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx:52 — register.toolColor has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (21 pts) (nesting depth added 15). 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.
D2 · Cognitive Complexity · rules.words (cognitive 21) · ×1
  • rules.words (cognitive 21) REDACTED:130 — rules.words has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · stack.commandsSection (cognitive 21) · ×1
  • stack.commandsSection (cognitive 21) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:472 — stack.commandsSection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, loops 3, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (fileNode, a function literal at line 495, a function literal at line 496, …). 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.
D2 · Cognitive Complexity · ollama-adapter.chat (cognitive 21) · ×1
  • ollama-adapter.chat (cognitive 21) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/ollama-adapter.mjs:91 — ollama-adapter.chat has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 3, loops 2 (3 pts), boolean chains 2, error handling 2 (nesting depth added 7). Of this number, 15 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · index.collectDownloads (cognitive 21) · ×1
  • index.collectDownloads (cognitive 21) cloudflare-workers/pulse/index.js:216 — index.collectDownloads has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, loops 3 (6 pts), if/else 3, error handling 1 (nesting depth added 3). 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.
D2 · Cognitive Complexity · sign-in.showInAppDialog (cognitive 21) · ×1
  • sign-in.showInAppDialog (cognitive 21) dashboard/src/lib/sign-in.ts:84 — sign-in.showInAppDialog has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10, boolean chains 4, ternaries 3 (4 pts), error handling 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (onKey, a function literal at line 142, close, …). 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.
D2 · Cognitive Complexity · MarketplacePluginsList.MarketplacePluginsList (cognitive 21) · ×1
  • MarketplacePluginsList.MarketplacePluginsList (cognitive 21) dashboard/src/components/MarketplacePluginsList.tsx:36 — MarketplacePluginsList.MarketplacePluginsList has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 15, if/else 4, ternaries 2. Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 143, a function literal at line 46, a function literal at line 50, …). 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.
D2 · Cognitive Complexity · WorkflowManager.showGenerateModal (cognitive 21) · ×1
  • WorkflowManager.showGenerateModal (cognitive 21) docs/js/workflows-events.js:706 — WorkflowManager.showGenerateModal has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · EnhancedTagStandardizer.process_file (cognitive 21) · ×1
  • EnhancedTagStandardizer.process_file (cognitive 21) cli-tool/components/agents/obsidian-ops-team/Scripts/enhance_tag_standardizer.py:267 — EnhancedTagStandardizer.process_file has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (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.
D2 · Cognitive Complexity · moc_generator.main (cognitive 21) · ×1
  • moc_generator.main (cognitive 21) cli-tool/components/agents/obsidian-ops-team/Scripts/moc_generator.py:240 — moc_generator.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (6 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · parse_keyword_connections.main (cognitive 21) · ×1
  • parse_keyword_connections.main (cognitive 21) cli-tool/components/agents/obsidian-ops-team/Scripts/parse_keyword_connections.py:58 — parse_keyword_connections.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 5 (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.
D2 · Cognitive Complexity · i18n_checker.check_locale_completeness (cognitive 21) · ×1
  • i18n_checker.check_locale_completeness (cognitive 21) cli-tool/components/skills/development/i18n-localization/scripts/i18n_checker.py:70 — i18n_checker.check_locale_completeness has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (4 pts), error handling 1 (3 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.
D2 · Cognitive Complexity · PubMedSearcher._extract_metadata_from_xml (cognitive 21) · ×1
  • PubMedSearcher._extract_metadata_from_xml (cognitive 21) cli-tool/components/skills/scientific/citation-management/scripts/search_pubmed.py:154 — PubMedSearcher._extract_metadata_from_xml has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (3 pts), error handling 1 (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.
D2 · Cognitive Complexity · format_adverse_events.format_ae_summary_table (cognitive 21) · ×1
  • format_adverse_events.format_ae_summary_table (cognitive 21) cli-tool/components/skills/scientific/clinical-reports/scripts/format_adverse_events.py:17 — format_adverse_events.format_ae_summary_table has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (6 pts), loops 3 (4 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · generate_market_visuals.main (cognitive 21) · ×1
  • generate_market_visuals.main (cognitive 21) cli-tool/components/skills/scientific/market-research-reports/scripts/generate_market_visuals.py:400 — generate_market_visuals.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
D2 · Cognitive Complexity · query_template.search_templates (cognitive 21) · ×1
  • query_template.search_templates (cognitive 21) cli-tool/components/skills/scientific/venue-templates/scripts/query_template.py:81 — query_template.search_templates has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 2 (3 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.
D2 · Cognitive Complexity · community_maintainers.iter_commits_from_json (cognitive 21) · ×1
  • community_maintainers.iter_commits_from_json (cognitive 21) cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:261 — community_maintainers.iter_commits_from_json has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, 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.
D2 · Cognitive Complexity · install-ui.createInstallUI.chooseLocations (cognitive 20) · ×1
  • install-ui.createInstallUI.chooseLocations (cognitive 20) cli-tool/src/install-ui.js:151 — install-ui.createInstallUI.chooseLocations has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (11 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 4). Of this number, 14 points are the body's own statements and 6 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, 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.
D2 · Cognitive Complexity · admin-capability-lockdown.register (cognitive 20) · ×1
  • admin-capability-lockdown.register (cognitive 20) cli-tool/components/mods/enterprise/admin-capability-lockdown/hooks/admin-capability-lockdown.ts:41 — admin-capability-lockdown.register has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 2 (5 pts), boolean chains 2, ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 63, 80, 115, …). 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.
D2 · Cognitive Complexity · transcript.buildTimeline (cognitive 20) · ×1
  • transcript.buildTimeline (cognitive 20) cli-tool/components/mods/productivity/session-time-machine/hooks/transcript.ts:107 — transcript.buildTimeline has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 2, ternaries 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 20 points belong to 3 function items inside it that branch (a function literal at line 123, a function literal at line 113, endTurn). 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.
D2 · Cognitive Complexity · profiles.planFor (cognitive 20) · ×1
  • profiles.planFor (cognitive 20) cli-tool/components/mods/productivity/ultra-config/hooks/profiles.ts:242 — profiles.planFor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (8 pts), boolean chains 3 (nesting depth added 6). 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 246, 243). 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.
D2 · Cognitive Complexity · rules.segments (cognitive 20) · ×1
  • rules.segments (cognitive 20) REDACTED:104 — rules.segments has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 5, loops 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.
D2 · Cognitive Complexity · rules.parseConfig (cognitive 20) · ×1
  • rules.parseConfig (cognitive 20) REDACTED:137 — rules.parseConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 1, error handling 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · pending-action.parsePendingAction (cognitive 20) · ×1
  • pending-action.parsePendingAction (cognitive 20) dashboard/src/lib/pending-action.ts:42 — pending-action.parsePendingAction has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, ternaries 1 (2 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.
D2 · Cognitive Complexity · SkillSlideView.buildSlides (cognitive 20) · ×1
  • SkillSlideView.buildSlides (cognitive 20) REDACTED:63 — SkillSlideView.buildSlides has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 2, 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.
D2 · Cognitive Complexity · ComponentPageManager.setupEventListeners (cognitive 20) · ×1
  • ComponentPageManager.setupEventListeners (cognitive 20) docs/js/component-page.js:882 — ComponentPageManager.setupEventListeners has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2 (nesting depth added 9). 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 917, 884). 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.
D2 · Cognitive Complexity · DailyNotesConnector.generate_report (cognitive 20) · ×1
  • DailyNotesConnector.generate_report (cognitive 20) cli-tool/components/agents/obsidian-ops-team/Scripts/daily_notes_connector.py:221 — DailyNotesConnector.generate_report has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 5 (8 pts), error handling 1 (3 pts) (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.
D2 · Cognitive Complexity · TagStandardizer.analyze_existing_tags (cognitive 20) · ×1
  • TagStandardizer.analyze_existing_tags (cognitive 20) cli-tool/components/agents/obsidian-ops-team/Scripts/tag_standardizer.py:253 — TagStandardizer.analyze_existing_tags has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (5 pts), error handling 1 (2 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.
D2 · Cognitive Complexity · _Handler.do_GET (cognitive 20) · ×1
  • _Handler.do_GET (cognitive 20) cli-tool/components/hooks/monitoring/context-timeline.py:982 — _Handler.do_GET has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 2 (5 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.
D2 · Cognitive Complexity · extract_form_structure.extract_form_structure (cognitive 20) · ×1
  • extract_form_structure.extract_form_structure (cognitive 20) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:20 — extract_form_structure.extract_form_structure has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (11 pts), if/else 3 (8 pts), boolean chains 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · setup_environment.save_api_keys (cognitive 20) · ×1
  • setup_environment.save_api_keys (cognitive 20) cli-tool/components/skills/scientific/biomni/scripts/setup_environment.py:125 — setup_environment.save_api_keys has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 12). 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.
D2 · Cognitive Complexity · extract_metadata.main (cognitive 20) · ×1
  • extract_metadata.main (cognitive 20) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:487 — extract_metadata.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (17 pts), error handling 1 (2 pts), loops 1 (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.
D2 · Cognitive Complexity · CareValidator.print_report (cognitive 20) · ×1
  • CareValidator.print_report (cognitive 20) cli-tool/components/skills/scientific/clinical-reports/scripts/validate_case_report.py:217 — CareValidator.print_report has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), loops 4 (8 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). 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.
D2 · Cognitive Complexity · batch_sequence_analysis.analyze_sequences (cognitive 20) · ×1
  • batch_sequence_analysis.analyze_sequences (cognitive 20) cli-tool/components/skills/scientific/gget/scripts/batch_sequence_analysis.py:36 — batch_sequence_analysis.analyze_sequences has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), error handling 3 (7 pts), loops 2 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · filter_molecules.main (cognitive 20) · ×1
  • filter_molecules.main (cognitive 20) cli-tool/components/skills/scientific/medchem/scripts/filter_molecules.py:289 — filter_molecules.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18 (20 pts) (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.
D2 · Cognitive Complexity · uniprot_client.main (cognitive 20) · ×1
  • uniprot_client.main (cognitive 20) cli-tool/components/skills/scientific/uniprot-database/scripts/uniprot_client.py:233 — uniprot_client.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (4 pts), loops 1 (2 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.
D2 · Cognitive Complexity · security_scan.scan_secrets (cognitive 20) · ×1
  • security_scan.scan_secrets (cognitive 20) cli-tool/components/skills/security/vulnerability-scanner/scripts/security_scan.py:181 — security_scan.scan_secrets has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (6 pts), error handling 1 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · filesFromContent (cognitive 20) · ×1
  • filesFromContent (cognitive 20) cli-tool/src/component-content.js:40 — filesFromContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, loops 1, ternaries 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.
D2 · Cognitive Complexity · fetch (cognitive 20) · ×1
  • fetch (cognitive 20) cloudflare-workers/newsletter/index.js:56 — fetch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 2 (4 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 7). Of this number, 19 points are the body's own statements and 1 belongs 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.
D2 · Cognitive Complexity · ChartCard.ChartCard (cognitive 19) · ×1
  • ChartCard.ChartCard (cognitive 19) cli-tool/analytics-ui/src/components/ChartCard.tsx:14 — ChartCard.ChartCard has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 4 (6 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 27, 42, 64, …). 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.
D2 · Cognitive Complexity · HealthChecker.generateRecommendations (cognitive 19) · ×1
  • HealthChecker.generateRecommendations (cognitive 19) cli-tool/src/health-check.js:1342 — HealthChecker.generateRecommendations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 9 (nesting depth added 1). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 1356). 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.
D2 · Cognitive Complexity · external-skill.findLegalFiles (cognitive 19) · ×1
  • external-skill.findLegalFiles (cognitive 19) cli-tool/src/external-skill.js:224 — external-skill.findLegalFiles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · catalog-lookup.resolveItems (cognitive 19) · ×1
  • catalog-lookup.resolveItems (cognitive 19) cli-tool/src/catalog-lookup.js:133 — catalog-lookup.resolveItems has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 2, error handling 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.
D2 · Cognitive Complexity · graph.tree (cognitive 19) · ×1
  • graph.tree (cognitive 19) cli-tool/components/mods/productivity/session-chats/hooks/graph.ts:91 — graph.tree has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (4 pts), loops 4, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 111, a function literal at line 102, visit). 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.
D2 · Cognitive Complexity · register.undoLast (cognitive 19) · ×1
  • register.undoLast (cognitive 19) cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:265 — register.undoLast has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (3 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · index.sendBroadcast (cognitive 19) · ×1
  • index.sendBroadcast (cognitive 19) cloudflare-workers/newsletter/index.js:428 — index.sendBroadcast has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), error handling 1 (2 pts) (nesting depth added 2). Of this number, 14 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · trending-dashboard.html.renderLine (cognitive 19) · ×1
  • trending-dashboard.html.renderLine (cognitive 19) dashboard/public/trending-dashboard.html:244 — trending-dashboard.html.renderLine has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, loops 3, ternaries 3 (nesting depth added 3). Of this number, 12 points are the body's own statements and 7 belong to 6 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.
D2 · Cognitive Complexity · CertificationsView.CertificationsView (cognitive 19) · ×1
  • CertificationsView.CertificationsView (cognitive 19) dashboard/src/components/CertificationsView.tsx:198 — CertificationsView.CertificationsView has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 6, if/else 5. Of this number, 11 points are the body's own statements and 8 belong to 6 function items 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.
D2 · Cognitive Complexity · SkillExplorer.buildTree (cognitive 19) · ×1
  • SkillExplorer.buildTree (cognitive 19) REDACTED:105 — SkillExplorer.buildTree has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (6 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 8). Of this number, 10 points are the body's own statements and 9 belong to 3 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.
D2 · Cognitive Complexity · context-timeline._wal_reaper (cognitive 19) · ×1
  • context-timeline._wal_reaper (cognitive 19) cli-tool/components/hooks/monitoring/context-timeline.py:411 — context-timeline._wal_reaper has cognitive complexity 19 (threshold 15). Drivers by points: error handling 3 (9 pts), loops 3 (6 pts), if/else 1 (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.
D2 · Cognitive Complexity · subagent-read-only-guard.split_commands (cognitive 19) · ×1
  • subagent-read-only-guard.split_commands (cognitive 19) cli-tool/components/hooks/security/subagent-read-only-guard.py:176 — subagent-read-only-guard.split_commands has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (6 pts), boolean chains 2, loops 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.
D2 · Cognitive Complexity · seo_checker.main (cognitive 19) · ×1
  • seo_checker.main (cognitive 19) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:148 — seo_checker.main has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 5 (7 pts), ternaries 2 (nesting depth added 7). 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.
D2 · Cognitive Complexity · image_gen._run_generate_batch (cognitive 19) · ×1
  • image_gen._run_generate_batch (cognitive 19) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:477 — image_gen._run_generate_batch has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts), error handling 1, ternaries 1 (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.
D2 · Cognitive Complexity · take_screenshot.capture_linux (cognitive 19) · ×1
  • take_screenshot.capture_linux (cognitive 19) cli-tool/components/skills/media/screenshot/scripts/take_screenshot.py:369 — take_screenshot.capture_linux has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 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.
D2 · Cognitive Complexity · eda_analyzer.analyze_general_scientific (cognitive 19) · ×1
  • eda_analyzer.analyze_general_scientific (cognitive 19) cli-tool/components/skills/scientific/exploratory-data-analysis/scripts/eda_analyzer.py:251 — eda_analyzer.analyze_general_scientific has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (16 pts), error handling 2, if/else 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.
D2 · Cognitive Complexity · OpenAlexClient.sample_works (cognitive 19) · ×1
  • OpenAlexClient.sample_works (cognitive 19) cli-tool/components/skills/scientific/openalex-database/scripts/openalex_client.py:238 — OpenAlexClient.sample_works has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (5 pts), ternaries 1 (3 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.
D2 · Cognitive Complexity · benchmark_model.run_benchmark (cognitive 19) · ×1
  • benchmark_model.run_benchmark (cognitive 19) cli-tool/components/skills/scientific/torch_geometric/scripts/benchmark_model.py:221 — benchmark_model.run_benchmark has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), error handling 1 (3 pts), ternaries 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.
D2 · Cognitive Complexity · ProcessDetector.enrichWithRunningProcesses (cognitive 18) · ×1
  • ProcessDetector.enrichWithRunningProcesses (cognitive 18) cli-tool/src/analytics/core/ProcessDetector.js:104 — ProcessDetector.enrichWithRunningProcesses has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 8). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · index.installIndividualMCP (cognitive 18) · ×1
  • index.installIndividualMCP (cognitive 18) cli-tool/src/index.js:462 — index.installIndividualMCP has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (2 pts), error handling 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.
D2 · Cognitive Complexity · index.installExternalSkill (cognitive 18) · ×1
  • index.installExternalSkill (cognitive 18) cli-tool/src/index.js:1550 — index.installExternalSkill has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), ternaries 1 (2 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.
D2 · Cognitive Complexity · index.parseLoopReferencedComponents (cognitive 18) · ×1
  • index.parseLoopReferencedComponents (cognitive 18) cli-tool/src/index.js:1611 — index.parseLoopReferencedComponents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · prompt-cache-control.readSettings (cognitive 18) · ×1
  • prompt-cache-control.readSettings (cognitive 18) cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:136 — prompt-cache-control.readSettings has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 7, error handling 1 (2 pts), loops 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.
D2 · Cognitive Complexity · human-gate.register (cognitive 18) · ×1
  • human-gate.register (cognitive 18) cli-tool/components/mods/security/human-gate/hooks/human-gate.ts:19 — human-gate.register has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 5, boolean chains 3, error handling 1 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 46, 32, 50, …). 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.
D2 · Cognitive Complexity · stack.scanPluginRoot (cognitive 18) · ×1
  • stack.scanPluginRoot (cognitive 18) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:185 — stack.scanPluginRoot has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (8 pts), loops 4 (7 pts), boolean chains 2, if/else 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.
D2 · Cognitive Complexity · stack.skillsSection (cognitive 18) · ×1
  • stack.skillsSection (cognitive 18) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:414 — stack.skillsSection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, ternaries 4, loops 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (fileNode, a function literal at line 416, a function literal at line 445, …). 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.
D2 · Cognitive Complexity · security-headers.parseCspReports (cognitive 18) · ×1
  • security-headers.parseCspReports (cognitive 18) dashboard/src/lib/security-headers.ts:112 — security-headers.parseCspReports has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · middleware.onRequest (cognitive 18) · ×1
  • middleware.onRequest (cognitive 18) dashboard/src/middleware.ts:27 — middleware.onRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · ComponentPageManager.loadComponentFromURL (cognitive 18) · ×1
  • ComponentPageManager.loadComponentFromURL (cognitive 18) docs/js/component-page.js:20 — ComponentPageManager.loadComponentFromURL has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, error handling 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.
D2 · Cognitive Complexity · search-functionality.initializeSearchFromURL (cognitive 18) · ×1
  • search-functionality.initializeSearchFromURL (cognitive 18) docs/js/search-functionality.js:675 — search-functionality.initializeSearchFromURL has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (18 pts) (nesting depth added 10). Of this number, 9 points are the body's own statements and 9 belong to 2 function items inside it that branch. 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.
D2 · Cognitive Complexity · DailyNotesConnector.find_temporal_connections (cognitive 18) · ×1
  • DailyNotesConnector.find_temporal_connections (cognitive 18) cli-tool/components/agents/obsidian-ops-team/Scripts/daily_notes_connector.py:126 — DailyNotesConnector.find_temporal_connections has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (4 pts), ternaries 1 (4 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.
D2 · Cognitive Complexity · seo_checker.check_page (cognitive 18) · ×1
  • seo_checker.check_page (cognitive 18) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:96 — seo_checker.check_page has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), error handling 1, loops 1 (nesting depth added 2). 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.
D2 · Cognitive Complexity · mobile_audit.main (cognitive 18) · ×1
  • mobile_audit.main (cognitive 18) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:631 — mobile_audit.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 2 (6 pts), ternaries 2 (3 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.
D2 · Cognitive Complexity · schema_validator.main (cognitive 18) · ×1
  • schema_validator.main (cognitive 18) cli-tool/components/skills/development/database-design/scripts/schema_validator.py:94 — schema_validator.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (6 pts), ternaries 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.
D2 · Cognitive Complexity · devops_utils.main (cognitive 18) · ×1
  • devops_utils.main (cognitive 18) cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py:330 — devops_utils.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (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.
D2 · Cognitive Complexity · utils.parse_skill_md (cognitive 18) · ×1
  • utils.parse_skill_md (cognitive 18) cli-tool/components/skills/development/skill-development/scripts/utils.py:7 — utils.parse_skill_md has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (6 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · transcribe_diarize.main (cognitive 18) · ×1
  • transcribe_diarize.main (cognitive 18) cli-tool/components/skills/media/transcribe/scripts/transcribe_diarize.py:189 — transcribe_diarize.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, loops 2 (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.
D2 · Cognitive Complexity · biorxiv_search.main (cognitive 18) · ×1
  • biorxiv_search.main (cognitive 18) cli-tool/components/skills/scientific/biorxiv-database/scripts/biorxiv_search.py:301 — biorxiv_search.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 1 (2 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.
D2 · Cognitive Complexity · batch_id_converter.print_mapping_summary (cognitive 18) · ×1
  • batch_id_converter.print_mapping_summary (cognitive 18) cli-tool/components/skills/scientific/bioservices/scripts/batch_id_converter.py:202 — batch_id_converter.print_mapping_summary has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (2 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.
D2 · Cognitive Complexity · compound_cross_reference.get_kegg_info (cognitive 18) · ×1
  • compound_cross_reference.get_kegg_info (cognitive 18) cli-tool/components/skills/scientific/bioservices/scripts/compound_cross_reference.py:66 — compound_cross_reference.get_kegg_info has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, error handling 1, loops 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.
D2 · Cognitive Complexity · compound_cross_reference.get_chebi_info (cognitive 18) · ×1
  • compound_cross_reference.get_chebi_info (cognitive 18) cli-tool/components/skills/scientific/bioservices/scripts/compound_cross_reference.py:172 — compound_cross_reference.get_chebi_info has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (4 pts), boolean chains 3, error handling 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.
D2 · Cognitive Complexity · brenda_visualization.plot_michaelis_menten (cognitive 18) · ×1
  • brenda_visualization.plot_michaelis_menten (cognitive 18) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:471 — brenda_visualization.plot_michaelis_menten has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, boolean chains 4, ternaries 3, error handling 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.
D2 · Cognitive Complexity · MetadataExtractor.extract_from_arxiv (cognitive 18) · ×1
  • MetadataExtractor.extract_from_arxiv (cognitive 18) cli-tool/components/skills/scientific/citation-management/scripts/extract_metadata.py:213 — MetadataExtractor.extract_from_arxiv has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (7 pts), loops 1 (2 pts), error handling 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.
D2 · Cognitive Complexity · create_cohort_tables.generate_efficacy_table (cognitive 18) · ×1
  • create_cohort_tables.generate_efficacy_table (cognitive 18) cli-tool/components/skills/scientific/clinical-decision-support/scripts/create_cohort_tables.py:197 — create_cohort_tables.generate_efficacy_table has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 3 (5 pts), ternaries 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.
D2 · Cognitive Complexity · search_databases.main (cognitive 18) · ×1
  • search_databases.main (cognitive 18) cli-tool/components/skills/scientific/literature-review/scripts/search_databases.py:209 — search_databases.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, error handling 1, 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.
D2 · Cognitive Complexity · calculate_scores.interactive_mode (cognitive 18) · ×1
  • calculate_scores.interactive_mode (cognitive 18) cli-tool/components/skills/scientific/scholar-evaluation/scripts/calculate_scores.py:245 — calculate_scores.interactive_mode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), error handling 1 (3 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.
D2 · Cognitive Complexity · ScientificSchematicGenerator.review_image (cognitive 18) · ×1
  • ScientificSchematicGenerator.review_image (cognitive 18) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:420 — ScientificSchematicGenerator.review_image has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, loops 1 (2 pts), ternaries 2, error handling 1 (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.
D2 · Cognitive Complexity · SlideImageGenerator.review_image (cognitive 18) · ×1
  • SlideImageGenerator.review_image (cognitive 18) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:404 — SlideImageGenerator.review_image has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, loops 1 (2 pts), ternaries 2, error handling 1 (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.
D2 · Cognitive Complexity · createInstallUI.chooseLocations (cognitive 18) · ×1
  • createInstallUI.chooseLocations (cognitive 18) cli-tool/src/install-ui.js:151 — createInstallUI.chooseLocations has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (render, a function literal at line 184, a function literal at line 164, …). 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.
D2 · Cognitive Complexity · sendToDatabase (cognitive 18) · ×1
  • sendToDatabase (cognitive 18) cli-tool/src/tracking-service.js:121 — sendToDatabase has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), boolean chains 4, error handling 2 (4 pts), other 3, ternaries 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.
D2 · Cognitive Complexity · index.installIndividualSkill · ×1
  • index.installIndividualSkill::downloadDirectory (cognitive 17) cli-tool/src/index.js:1437 — index.installIndividualSkill::downloadDirectory has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 2 (4 pts), ternaries 1 (2 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · policy.readWide (cognitive 17) · ×1
  • policy.readWide (cognitive 17) cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts:499 — policy.readWide has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), loops 2 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · policy.decide (cognitive 17) · ×1
  • policy.decide (cognitive 17) cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts:615 — policy.decide has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (6 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · rules.globToRegex (cognitive 17) · ×1
  • rules.globToRegex (cognitive 17) REDACTED:368 — rules.globToRegex has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, loops 1, ternaries 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.
D2 · Cognitive Complexity · large-edit-confirmation.register (cognitive 17) · ×1
  • large-edit-confirmation.register (cognitive 17) cli-tool/components/mods/security/large-edit-confirmation/hooks/large-edit-confirmation.ts:24 — large-edit-confirmation.register has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), error handling 4 (5 pts), ternaries 3 (4 pts), boolean chains 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 35, 83). 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.
D2 · Cognitive Complexity · stack.showValue (cognitive 17) · ×1
  • stack.showValue (cognitive 17) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:821 — stack.showValue has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 6, boolean chains 2 (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.
D2 · Cognitive Complexity · model-selection.candidates (cognitive 17) · ×1
  • model-selection.candidates (cognitive 17) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/model-selection.mjs:4 — model-selection.candidates has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 2 (5 pts), boolean chains 2, error handling 1 (2 pts), 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.
D2 · Cognitive Complexity · viewer.html.renderGrades (cognitive 17) · ×1
  • viewer.html.renderGrades (cognitive 17) cli-tool/components/skills/development/skill-development/eval-viewer/viewer.html:858 — viewer.html.renderGrades has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 5, if/else 2 (3 pts), 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.
D2 · Cognitive Complexity · ValidationOrchestrator.validateComponent (cognitive 17) · ×1
  • ValidationOrchestrator.validateComponent (cognitive 17) cli-tool/src/validation/ValidationOrchestrator.js:33 — ValidationOrchestrator.validateComponent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · FileTreeSidebar.buildTree (cognitive 17) · ×1
  • FileTreeSidebar.buildTree (cognitive 17) dashboard/src/components/FileTreeSidebar.tsx:22 — FileTreeSidebar.buildTree has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 8). Of this number, 10 points are the body's own statements and 7 belong to 3 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.
D2 · Cognitive Complexity · IndexPageManager.sortComponents (cognitive 17) · ×1
  • IndexPageManager.sortComponents (cognitive 17) docs/js/index-events.js:363 — IndexPageManager.sortComponents has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (7 pts) (nesting depth added 2). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 382, 368, 375). 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.
D2 · Cognitive Complexity · script.displayDownloadStatistics (cognitive 17) · ×1
  • script.displayDownloadStatistics (cognitive 17) docs/js/script.js:1947 — script.displayDownloadStatistics has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8 (nesting depth added 1). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · search-functionality.calculateMatchScore (cognitive 17) · ×1
  • search-functionality.calculateMatchScore (cognitive 17) docs/js/search-functionality.js:337 — search-functionality.calculateMatchScore has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 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.
D2 · Cognitive Complexity · TrendingPage.getComponentTypeLabel (cognitive 17) · ×1
  • TrendingPage.getComponentTypeLabel (cognitive 17) docs/js/trending.js:478 — TrendingPage.getComponentTypeLabel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 8. 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.
D2 · Cognitive Complexity · DesignSystemGenerator._select_best_match (cognitive 17) · ×1
  • DesignSystemGenerator._select_best_match (cognitive 17) cli-tool/components/skills/creative-design/ui-ux-pro-max/scripts/design_system.py:116 — DesignSystemGenerator._select_best_match has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 4 (6 pts), boolean chains 2, ternaries 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.
D2 · Cognitive Complexity · api_validator.main (cognitive 17) · ×1
  • api_validator.main (cognitive 17) cli-tool/components/skills/development/api-patterns/scripts/api_validator.py:162 — api_validator.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 4 (6 pts), boolean chains 1, ternaries 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.
D2 · Cognitive Complexity · atlas_text_to_speech._request_json (cognitive 17) · ×1
  • atlas_text_to_speech._request_json (cognitive 17) cli-tool/components/skills/media/speech/scripts/atlas_text_to_speech.py:119 — atlas_text_to_speech._request_json has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (4 pts), boolean chains 1, loops 1, ternaries 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.
D2 · Cognitive Complexity · CitationValidator.detect_duplicates (cognitive 17) · ×1
  • CitationValidator.detect_duplicates (cognitive 17) cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:239 — CitationValidator.detect_duplicates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5 (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.
D2 · Cognitive Complexity · CitationValidator.validate_file (cognitive 17) · ×1
  • CitationValidator.validate_file (cognitive 17) cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:303 — CitationValidator.validate_file has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (7 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.
D2 · Cognitive Complexity · dicom_to_image.convert_dicom_to_image (cognitive 17) · ×1
  • dicom_to_image.convert_dicom_to_image (cognitive 17) cli-tool/components/skills/scientific/pydicom/scripts/dicom_to_image.py:52 — dicom_to_image.convert_dicom_to_image has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 2 (4 pts), boolean chains 3, ternaries 2 (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.
D2 · Cognitive Complexity · SlideImageGenerator.generate_image (cognitive 17) · ×1
  • SlideImageGenerator.generate_image (cognitive 17) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:325 — SlideImageGenerator.generate_image has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 3 (5 pts), loops 1 (2 pts), ternaries 1 (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.
D2 · Cognitive Complexity · sora._cmd_create_and_poll (cognitive 17) · ×1
  • sora._cmd_create_and_poll (cognitive 17) cli-tool/components/skills/video/sora/scripts/sora.py:655 — sora._cmd_create_and_poll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 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.
D2 · Cognitive Complexity · file-operations.downloadFileFromGitHub (cognitive 16) · ×1
  • file-operations.downloadFileFromGitHub (cognitive 16) cli-tool/src/file-operations.js:18 — file-operations.downloadFileFromGitHub has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, error handling 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.
D2 · Cognitive Complexity · StateCalculator.detectRealClaudeActivity (cognitive 16) · ×1
  • StateCalculator.detectRealClaudeActivity (cognitive 16) cli-tool/src/analytics/core/StateCalculator.js:179 — StateCalculator.detectRealClaudeActivity has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · ConversationAnalyzer.extractToolUsage (cognitive 16) · ×1
  • ConversationAnalyzer.extractToolUsage (cognitive 16) cli-tool/src/analytics/core/ConversationAnalyzer.js:567 — ConversationAnalyzer.extractToolUsage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5 (nesting depth added 6). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 572, 596, 581). 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.
D2 · Cognitive Complexity · DataCache.getCachedComputation (cognitive 16) · ×1
  • DataCache.getCachedComputation (cognitive 16) cli-tool/src/analytics/data/DataCache.js:292 — DataCache.getCachedComputation has cognitive complexity 16 (threshold 15). Drivers by points: error handling 2 (5 pts), if/else 3 (5 pts), boolean chains 3, loops 2 (3 pts) (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.
D2 · Cognitive Complexity · ceiling.rulesFrom (cognitive 16) · ×1
  • ceiling.rulesFrom (cognitive 16) cli-tool/components/mods/enterprise/policy-ceiling/hooks/ceiling.ts:40 — ceiling.rulesFrom has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 7, if/else 2. Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · detect.segments (cognitive 16) · ×1
  • detect.segments (cognitive 16) REDACTED:44 — detect.segments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · detect.unwrap (cognitive 16) · ×1
  • detect.unwrap (cognitive 16) REDACTED:111 — detect.unwrap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 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.
D2 · Cognitive Complexity · rules.evaluate (cognitive 16) · ×1
  • rules.evaluate (cognitive 16) REDACTED:690 — rules.evaluate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, loops 1, ternaries 1 (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.
D2 · Cognitive Complexity · policy.route (cognitive 16) · ×1
  • policy.route (cognitive 16) cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts:253 — policy.route has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · turns.stepEnded (cognitive 16) · ×1
  • turns.stepEnded (cognitive 16) cli-tool/components/mods/ui/turn-inspector/hooks/turns.ts:172 — turns.stepEnded has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · web_game_playwright_client.captureScreenshot (cognitive 16) · ×1
  • web_game_playwright_client.captureScreenshot (cognitive 16) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js:177 — web_game_playwright_client.captureScreenshot has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (5 pts), error handling 1 (2 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.
D2 · Cognitive Complexity · ollama-adapter.validateRequest (cognitive 16) · ×1
  • ollama-adapter.validateRequest (cognitive 16) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/ollama-adapter.mjs:58 — ollama-adapter.validateRequest has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, loops 2, ternaries 2. 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.
D2 · Cognitive Complexity · index-events.showCategoryFilters (cognitive 16) · ×1
  • index-events.showCategoryFilters (cognitive 16) docs/js/index-events.js:1323 — index-events.showCategoryFilters has cognitive complexity 16 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 5, boolean chains 3, match/switch 1 (2 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.
D2 · Cognitive Complexity · LinkSuggester.suggest_links_by_entities (cognitive 16) · ×1
  • LinkSuggester.suggest_links_by_entities (cognitive 16) cli-tool/components/agents/obsidian-ops-team/Scripts/link_suggester.py:91 — LinkSuggester.suggest_links_by_entities has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (8 pts), if/else 2 (7 pts), boolean chains 1 (nesting depth added 10). 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.
D2 · Cognitive Complexity · LinkSuggester.suggest_links_by_keywords (cognitive 16) · ×1
  • LinkSuggester.suggest_links_by_keywords (cognitive 16) cli-tool/components/agents/obsidian-ops-team/Scripts/link_suggester.py:120 — LinkSuggester.suggest_links_by_keywords has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 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.
D2 · Cognitive Complexity · MOCGenerator.organize_files_by_topic (cognitive 16) · ×1
  • MOCGenerator.organize_files_by_topic (cognitive 16) cli-tool/components/agents/obsidian-ops-team/Scripts/moc_generator.py:141 — MOCGenerator.organize_files_by_topic has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 4 (7 pts), error handling 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.
D2 · Cognitive Complexity · ReviewAnalyzer.identify_issues (cognitive 16) · ×1
  • ReviewAnalyzer.identify_issues (cognitive 16) cli-tool/components/skills/business-marketing/app-store-optimization/review_analyzer.py:175 — ReviewAnalyzer.identify_issues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 4 (6 pts), ternaries 1 (3 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.
D2 · Cognitive Complexity · InterviewAnalyzer._extract_key_quotes (cognitive 16) · ×1
  • InterviewAnalyzer._extract_key_quotes (cognitive 16) cli-tool/components/skills/business-marketing/product-manager-toolkit/scripts/customer_interview_analyzer.py:191 — InterviewAnalyzer._extract_key_quotes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · vuln_prioritizer.interactive_mode (cognitive 16) · ×1
  • vuln_prioritizer.interactive_mode (cognitive 16) cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:254 — vuln_prioritizer.interactive_mode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 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.
D2 · Cognitive Complexity · take_screenshot.macos_window_ids (cognitive 16) · ×1
  • take_screenshot.macos_window_ids (cognitive 16) cli-tool/components/skills/media/screenshot/scripts/take_screenshot.py:277 — take_screenshot.macos_window_ids has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 2 (5 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · enzyme_pathway_builder.infer_transformation_type (cognitive 16) · ×1
  • enzyme_pathway_builder.infer_transformation_type (cognitive 16) cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:232 — enzyme_pathway_builder.infer_transformation_type has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 6. 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.
D2 · Cognitive Complexity · notebook_operations.list_notebooks (cognitive 16) · ×1
  • notebook_operations.list_notebooks (cognitive 16) cli-tool/components/skills/scientific/labarchive-integration/scripts/notebook_operations.py:69 — notebook_operations.list_notebooks has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 3 (4 pts), loops 1 (2 pts), error handling 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.
D2 · Cognitive Complexity · generate_market_visuals.generate_visual (cognitive 16) · ×1
  • generate_market_visuals.generate_visual (cognitive 16) cli-tool/components/skills/scientific/market-research-reports/scripts/generate_market_visuals.py:324 — generate_market_visuals.generate_visual has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 2, boolean chains 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, 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.
D2 · Cognitive Complexity · style_configurator.interactive_mode (cognitive 16) · ×1
  • style_configurator.interactive_mode (cognitive 16) cli-tool/components/skills/scientific/matplotlib/scripts/style_configurator.py:277 — style_configurator.interactive_mode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 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.
D2 · Cognitive Complexity · model_diagnostics.check_diagnostics (cognitive 16) · ×1
  • model_diagnostics.check_diagnostics (cognitive 16) cli-tool/components/skills/scientific/pymc/scripts/model_diagnostics.py:23 — model_diagnostics.check_diagnostics has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 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.
D2 · Cognitive Complexity · geo_checker.main (cognitive 16) · ×1
  • geo_checker.main (cognitive 16) cli-tool/components/skills/utilities/geo-fundamentals/scripts/geo_checker.py:222 — geo_checker.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (5 pts), loops 3 (5 pts), ternaries 4 (5 pts), boolean chains 1 (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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (20 members, 38 shared lines) · ×1
  • Near-duplicate member family (20 members, 38 shared lines) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:72 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:72-111 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:72-111 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:72-111 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:72-111 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:72-111 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:72-111 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:72-111 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:72-111 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:72-111 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:72-111 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:72-111 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:72-111 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:72-111 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:72-111 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:72-111 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:72-111 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:72-111 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:72-111 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:72-111 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:72-111 — These 20 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 20 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 20 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 48 shared lines) · ×1
  • Near-duplicate member family (5 members, 48 shared lines) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:35 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py:35-96 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py:35-96 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:35-96 | cli-tool/components/skills/document-processing/pdf/scripts/fill_pdf_form_with_annotations.py:35-96 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_pdf_form_with_annotations.py:29-97 — These 5 members are variants of one another: a block of 48 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 67 shared lines) · ×1
  • Near-duplicate member family (4 members, 67 shared lines) cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:13 — cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:13-86 | cli-tool/components/skills/development/skill-creator/scripts/quick_validate.py:13-94 | cli-tool/components/skills/development/skill-development/scripts/quick_validate.py:13-94 | cli-tool/components/skills/productivity/skill-creator/scripts/quick_validate.py:13-94 — These 4 members are variants of one another: a block of 67 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 38 shared lines) · ×1
  • Near-duplicate member family (3 members, 38 shared lines) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:260 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:260-306 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:260-306 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:260-306 — These 3 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member pair (61 shared lines) · ×1
  • Near-duplicate member pair (61 shared lines) cli-rust/src/commands/install.rs:229 — cli-rust/src/commands/install.rs:229-359 | cli-rust/src/commands/install.rs:396-505 — These two members are variants of one another: 61 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (40 shared lines) · ×1
  • Near-duplicate member pair (40 shared lines) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:343 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:343-418 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:326-402 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) cli-tool/components/settings/statusline/context-monitor.py:15 — cli-tool/components/settings/statusline/context-monitor.py:15-56 | cli-tool/components/settings/statusline/deadline-countdown.py:17-54 — These two members are one piece of code written twice and then edited apart: 35 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 · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (7 members, 50+ identical tokens) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:70 — cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:70-156 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:160-232 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:236-308 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:312-390 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:394-468 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:472-578 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:619-678 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) cli-tool/components/skills/scientific/string-database/scripts/string_api.py:78 — cli-tool/components/skills/scientific/string-database/scripts/string_api.py:78-122 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:131-171 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:179-215 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:221-254 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:261-296 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:302-334 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:236 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:236-314 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:251-306 — These two members are one piece of code written twice and then edited apart: 56 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 (118 corresponding lines) · ×1
  • Edited copy of a member (118 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:66 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:66-203 | cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py:13-130 — These two members are one piece of code written twice and then edited apart: 118 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 (109 corresponding lines) · ×1
  • Edited copy of a member (109 corresponding lines) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:423 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:423-571 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:407-515 — These two members are one piece of code written twice and then edited apart: 109 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 (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:168 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:168-196 | cli-tool/components/skills/video/sora/scripts/sora.py:339-374 — These two members are one piece of code written twice and then edited apart: 29 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 (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:149 — cli-tool/components/skills/business-marketing/seo-fundamentals/scripts/seo_checker.py:149-215 | cli-tool/components/skills/development/database-design/scripts/schema_validator.py:95-168 — These two members are one piece of code written twice and then edited apart: 67 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 (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) cli-rust/src/commands/install.rs:39 — cli-rust/src/commands/install.rs:39-85 | cli-rust/src/commands/install.rs:91-139 — These two members are one piece of code written twice and then edited apart: 47 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 (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:28 — cli-tool/components/skills/scientific/citation-management/scripts/format_bibtex.py:28-76 | cli-tool/components/skills/scientific/citation-management/scripts/validate_citations.py:44-93 — These two members are one piece of code written twice and then edited apart: 49 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 (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:350 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:350-371 | cli-tool/components/skills/video/sora/scripts/sora.py:243-264 — These two members are one piece of code written twice and then edited apart: 22 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 (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:59 — cli-tool/components/skills/git/star-history-chart/scripts/generate_star_history.py:59-94 | scripts/generate_star_history.py:33-68 — These two members are one piece of code written twice and then edited apart: 36 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 (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) cli-tool/components/skills/scientific/clinical-reports/scripts/check_deidentification.py:311 — cli-tool/components/skills/scientific/clinical-reports/scripts/check_deidentification.py:311-340 | cli-tool/components/skills/scientific/clinical-reports/scripts/validate_case_report.py:287-328 — These two members are one piece of code written twice and then edited apart: 30 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 (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) cli-tool/components/skills/scientific/rdkit/scripts/molecular_properties.py:104 — cli-tool/components/skills/scientific/rdkit/scripts/molecular_properties.py:104-142 | cli-tool/components/skills/scientific/rdkit/scripts/similarity_search.py:59-92 — These two members are one piece of code written twice and then edited apart: 34 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 (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:343 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:343-381 | cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:307-347 — These two members are one piece of code written twice and then edited apart: 39 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 copies of one member (3 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:57 — cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:57-84 | cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:88-122 | cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:126-154 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 50+ corresponding lines) cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:110 — cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:110-159 | cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:162-217 | cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:220-272 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) cli-tool/components/skills/media/speech/scripts/atlas_text_to_speech.py:344 — cli-tool/components/skills/media/speech/scripts/atlas_text_to_speech.py:344-360 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:240-260 — 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 (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) cli-tool/components/skills/scientific/clinical-reports/scripts/extract_clinical_data.py:68 — cli-tool/components/skills/scientific/clinical-reports/scripts/extract_clinical_data.py:68-96 | cli-tool/components/skills/scientific/clinical-reports/scripts/format_adverse_events.py:71-97 — These two members are one piece of code written twice and then edited apart: 27 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) cli-tool/components/skills/scientific/biorxiv-database/scripts/biorxiv_search.py:149 — cli-tool/components/skills/scientific/biorxiv-database/scripts/biorxiv_search.py:149-180 | cli-tool/components/skills/scientific/biorxiv-database/scripts/biorxiv_search.py:190-229 — 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 copies of one member (3 members, 42+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 42+ corresponding lines) cli-tool/components/skills/scientific/pytorch-lightning/scripts/quick_trainer_setup.py:127 — cli-tool/components/skills/scientific/pytorch-lightning/scripts/quick_trainer_setup.py:127-176 | cli-tool/components/skills/scientific/pytorch-lightning/scripts/quick_trainer_setup.py:189-237 | cli-tool/components/skills/scientific/pytorch-lightning/scripts/quick_trainer_setup.py:251-292 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) cli-tool/components/skills/scientific/pytdc/scripts/benchmark_evaluation.py:291 — cli-tool/components/skills/scientific/pytdc/scripts/benchmark_evaluation.py:291-323 | cli-tool/components/skills/scientific/pytdc/scripts/molecular_generation.py:361-400 — These two members are one piece of code written twice and then edited apart: 33 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:158 — cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:158-183 | cli-tool/components/skills/scientific/kegg-database/scripts/kegg_api.py:187-212 — These two members are one piece of code written twice and then edited apart: 26 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 copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) cli-tool/components/skills/scientific/fda-database/scripts/fda_query.py:264 — cli-tool/components/skills/scientific/fda-database/scripts/fda_query.py:264-273 | cli-tool/components/skills/scientific/fda-database/scripts/fda_query.py:316-327 | cli-tool/components/skills/scientific/fda-database/scripts/fda_query.py:333-341 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) cli-tool/components/skills/scientific/openalex-database/scripts/openalex_client.py:301 — cli-tool/components/skills/scientific/openalex-database/scripts/openalex_client.py:301-321 | cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:181-205 — 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.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:27 — cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:27-42 | cli-tool/components/skills/scientific/literature-review/scripts/verify_citations.py:45-67 — These two members are one piece of code written twice and then edited apart: 16 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 (7 corresponding lines) · ×1
  • Edited copy of a member (7 corresponding lines) REDACTED:22 — REDACTED:22-31 | cli-tool/components/skills/ai-research/post-training-grpo-rl-training/templates/basic_grpo_training.py:79-85 — These two members are one piece of code written twice and then edited apart: 7 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 (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) REDACTED:328 — REDACTED:328-331 | cli-tool/components/skills/ai-research/post-training-grpo-rl-training/templates/basic_grpo_training.py:67-70 — These two members are one piece of code written twice and then edited apart: 4 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 (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) cli-tool/components/skills/business-marketing/ceo-advisor/scripts/strategy_analyzer.py:108 — cli-tool/components/skills/business-marketing/ceo-advisor/scripts/strategy_analyzer.py:108-121 | cli-tool/components/skills/business-marketing/cto-advisor/scripts/tech_debt_analyzer.py:115-128 — These two members are one piece of code written twice and then edited apart: 14 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 copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:329 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:329-332 | cli-tool/components/skills/development/jupyter-notebook/scripts/new_notebook.py:11-14 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:233-236 | cli-tool/components/skills/video/sora/scripts/sora.py:222-225 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) cli-tool/components/skills/scientific/exploratory-data-analysis/scripts/eda_analyzer.py:152 — cli-tool/components/skills/productivity/notebooklm/scripts/cleanup_manager.py:132-137 | cli-tool/components/skills/scientific/exploratory-data-analysis/scripts/eda_analyzer.py:152-157 — These two members are one piece of code written twice and then edited apart: 6 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 (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:59 — cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:59-66 | cli-tool/components/skills/scientific/brenda-database/scripts/enzyme_pathway_builder.py:67-76 — These two members are one piece of code written twice and then edited apart: 8 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 · Duplicated block (139 lines × 3) · ×1
  • Duplicated block (139 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:43 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:43-181 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:43-181 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:43-181 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_eval.py` and `cli-tool/components/skills/development/skill-development/scripts/run_eval.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 262 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (106 lines × 3) · ×1
  • Duplicated block (106 lines × 3) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:68 — cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py:68-173 | cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:68-173 | cli-tool/components/skills/productivity/skill-creator/scripts/aggregate_benchmark.py:68-173 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py` and `cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 337 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (180 lines × 3) · ×1
  • Duplicated block (180 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_loop.py:62 — cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:62-241 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:62-241 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:62-241 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_loop.py` and `cli-tool/components/skills/development/skill-development/scripts/run_loop.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 333 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (80 lines × 3) · ×1
  • Duplicated block (80 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:388 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:388-467 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:388-467 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:388-467 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (64–78 lines × 2) · ×1
  • Duplicated block (64–78 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:446 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:446-523 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:413-476 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D4 · Code Duplication · Duplicated block (60–75 lines × 5) · ×1
  • Duplicated block (60–75 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:48 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_field_info.py:48-107 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/extract_form_field_info.py:63-137 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (86 lines × 2) · ×1
  • Duplicated block (86 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:317 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:317-402 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:317-402 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (68 lines × 4) · ×1
  • Duplicated block (68 lines × 4) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:21 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_structure.py:21-88 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_structure.py:21-88 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:21-88 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_structure.py:21-88 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_structure.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_structure.py` as WHOLE FILES: 100% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (73 lines × 3) · ×1
  • Duplicated block (73 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_loop.py:252 — cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:252-324 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:252-324 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:252-324 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_loop.py` and `cli-tool/components/skills/development/skill-development/scripts/run_loop.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 333 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (62 lines × 3) · ×1
  • Duplicated block (62 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:195 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:195-256 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:195-256 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:195-256 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_eval.py` and `cli-tool/components/skills/development/skill-development/scripts/run_eval.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 262 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (60 lines × 2) · ×1
  • Duplicated block (60 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:135 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:135-194 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:135-194 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (59 lines × 3) · ×1
  • Duplicated block (59 lines × 3) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:339 — cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py:339-397 | cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:339-397 | cli-tool/components/skills/productivity/skill-creator/scripts/aggregate_benchmark.py:339-397 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py` and `cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 337 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (39–55 lines × 2) · ×1
  • Duplicated block (39–55 lines × 2) cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py:33 — cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py:33-87 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:683-721 — 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.
D4 · Code Duplication · Duplicated block (41–53 lines × 2) · ×1
  • Duplicated block (41–53 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:181 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:181-233 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:208-248 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (51 lines × 4) · ×1
  • Duplicated block (51 lines × 4) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:20 — cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:20-70 | cli-tool/components/skills/development/skill-creator/scripts/package_skill.py:43-93 | cli-tool/components/skills/development/skill-development/scripts/package_skill.py:43-93 | cli-tool/components/skills/productivity/skill-creator/scripts/package_skill.py:43-93 — before extracting anything, compare `cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py` and `cli-tool/components/skills/development/skill-creator/scripts/package_skill.py` as WHOLE FILES: 93% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (51 lines × 3) · ×1
  • Duplicated block (51 lines × 3) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:228 — cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py:228-278 | cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:228-278 | cli-tool/components/skills/productivity/skill-creator/scripts/aggregate_benchmark.py:228-278 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py` and `cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 337 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×1
  • Duplicated block (50 lines × 2) cli-tool/components/skills/scientific/research-lookup/research_lookup.py:197 — cli-tool/components/skills/scientific/research-lookup/research_lookup.py:197-246 | cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:197-246 — before extracting anything, compare `cli-tool/components/skills/scientific/research-lookup/research_lookup.py` and `cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 328 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (49 lines × 3) · ×1
  • Duplicated block (49 lines × 3) cli-tool/components/skills/development/skill-development/scripts/improve_description.py:195 — cli-tool/components/skills/development/skill-creator/scripts/improve_description.py:195-243 | cli-tool/components/skills/development/skill-development/scripts/improve_description.py:195-243 | cli-tool/components/skills/productivity/skill-creator/scripts/improve_description.py:195-243 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/improve_description.py` and `cli-tool/components/skills/development/skill-development/scripts/improve_description.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (37–46 lines × 2) · ×1
  • Duplicated block (37–46 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:144 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:144-180 | cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py:72-117 — before extracting anything, compare `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py` and `cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 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 `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:144` 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.
D4 · Code Duplication · Duplicated block (41–44 lines × 5) · ×1
  • Duplicated block (41–44 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:12 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/document-processing/pdf/scripts/fill_fillable_fields.py:12-52 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_fillable_fields.py:13-56 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:236 — cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:236-279 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:312-355 — 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.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) REDACTED:91 — REDACTED:91-133 | REDACTED:91-133 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (30–42 lines × 6) · ×1
  • Duplicated block (30–42 lines × 6) cli-tool/components/skills/scientific/string-database/scripts/string_api.py:78 — cli-tool/components/skills/scientific/string-database/scripts/string_api.py:78-119 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:131-169 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:179-212 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:221-251 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:261-293 | cli-tool/components/skills/scientific/string-database/scripts/string_api.py:302-331 — all 6 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. 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. 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.
D4 · Code Duplication · Duplicated block (40 lines × 4) · ×1
  • Duplicated block (40 lines × 4) cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:45 — cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:45-84 | cli-tool/components/skills/development/skill-creator/scripts/quick_validate.py:45-84 | cli-tool/components/skills/development/skill-development/scripts/quick_validate.py:45-84 | cli-tool/components/skills/productivity/skill-creator/scripts/quick_validate.py:45-84 — before extracting anything, compare `cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py` and `cli-tool/components/skills/development/skill-creator/scripts/quick_validate.py` as WHOLE FILES: 94% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (40 lines × 3) · ×1
  • Duplicated block (40 lines × 3) cli-tool/components/skills/development/skill-development/scripts/utils.py:8 — cli-tool/components/skills/development/skill-creator/scripts/utils.py:8-47 | cli-tool/components/skills/development/skill-development/scripts/utils.py:8-47 | cli-tool/components/skills/productivity/skill-creator/scripts/utils.py:8-47 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/utils.py` and `cli-tool/components/skills/development/skill-development/scripts/utils.py` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (38–39 lines × 2) · ×1
  • Duplicated block (38–39 lines × 2) cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:17 — cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:17-55 | cli-tool/components/skills/scientific/openalex-database/scripts/query_helpers.py:63-100 — 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.
D4 · Code Duplication · Duplicated block (35–39 lines × 2) · ×1
  • Duplicated block (35–39 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:38 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:38-76 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:50-84 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (48 lines × 3) · ×1
  • Duplicated block (48 lines × 3) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:177 — cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py:177-224 | cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:177-224 | cli-tool/components/skills/productivity/skill-creator/scripts/aggregate_benchmark.py:177-224 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py` and `cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 337 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (24–38 lines × 2) · ×1
  • Duplicated block (24–38 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:236 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:236-273 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:251-274 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (32–38 lines × 2) · ×1
  • Duplicated block (32–38 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:525 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:525-562 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:479-510 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (33–37 lines × 2) · ×1
  • Duplicated block (33–37 lines × 2) cli-tool/components/settings/statusline/context-monitor.py:15 — cli-tool/components/settings/statusline/context-monitor.py:15-51 | cli-tool/components/settings/statusline/deadline-countdown.py:17-49 — 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.
D4 · Code Duplication · Duplicated block (30–35 lines × 5) · ×1
  • Duplicated block (30–35 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:67 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py:67-96 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py:67-96 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:67-96 | cli-tool/components/skills/document-processing/pdf/scripts/fill_pdf_form_with_annotations.py:67-96 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_pdf_form_with_annotations.py:63-97 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py:67` 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.
D4 · Code Duplication · Duplicated block (2–35 lines × 6) · ×1
  • Duplicated block (2–35 lines × 6) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:268 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:268-302 | cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:169-170 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:268-302 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:169-170 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:268-302 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:169-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. 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.
D4 · Code Duplication · Duplicated block (34 lines × 3) · ×1
  • Duplicated block (34 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:214 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:214-247 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:214-247 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:214-247 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (29–32 lines × 2) · ×1
  • Duplicated block (29–32 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:141 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:141-172 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:171-199 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (54 lines × 3) · ×1
  • Duplicated block (54 lines × 3) cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:282 — cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py:282-335 | cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py:282-335 | cli-tool/components/skills/productivity/skill-creator/scripts/aggregate_benchmark.py:282-335 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/aggregate_benchmark.py` and `cli-tool/components/skills/development/skill-development/scripts/aggregate_benchmark.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 337 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (25–28 lines × 5) · ×1
  • Duplicated block (25–28 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:20 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_field_info.py:20-44 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/extract_form_field_info.py:23-50 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (27 lines × 4) · ×1
  • Duplicated block (27 lines × 4) cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:13 — cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py:13-39 | cli-tool/components/skills/development/skill-creator/scripts/quick_validate.py:13-39 | cli-tool/components/skills/development/skill-development/scripts/quick_validate.py:13-39 | cli-tool/components/skills/productivity/skill-creator/scripts/quick_validate.py:13-39 — before extracting anything, compare `cli-tool/components/skills/development/skill-creation-guide/scripts/quick_validate.py` and `cli-tool/components/skills/development/skill-creator/scripts/quick_validate.py` as WHOLE FILES: 94% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (25–27 lines × 2) · ×1
  • Duplicated block (25–27 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:86 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:86-112 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py:85-109 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:86` 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.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:343 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:343-369 | cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:307-333 — 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.
D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:256 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:256-281 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:256-281 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:256-281 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:24 — cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:24-49 | cli-tool/components/skills/scientific/gene-database/scripts/query_gene.py:66-89 — 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.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) cli-tool/components/skills/development/skill-development/scripts/improve_description.py:61 — cli-tool/components/skills/development/skill-creator/scripts/improve_description.py:61-85 | cli-tool/components/skills/development/skill-development/scripts/improve_description.py:61-85 | cli-tool/components/skills/productivity/skill-creator/scripts/improve_description.py:61-85 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/improve_description.py` and `cli-tool/components/skills/development/skill-development/scripts/improve_description.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×1
  • Duplicated block (23–25 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:133 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:133-157 | cli-tool/components/skills/scientific/deepchem/scripts/transfer_learning.py:71-93 — 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:127 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:127-151 | cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py:39-63 — before extracting anything, compare `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py` and `cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 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 `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:127` 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.
D4 · Code Duplication · Duplicated block (24 lines × 20) · ×1
  • Duplicated block (24 lines × 20) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:72 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:72-95 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:72-95 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:72-95 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:72-95 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:72-95 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:72-95 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:72-95 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:72-95 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:72-95 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:72-95 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:72-95 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:72-95 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:72-95 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:72-95 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:72-95 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:72-95 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:72-95 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:72-95 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:72-95 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:72-95 — before extracting anything, compare `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py` and `cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) REDACTED:64 — REDACTED:64-87 | REDACTED:64-87 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (22–24 lines × 2) · ×1
  • Duplicated block (22–24 lines × 2) cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:128 — cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:128-151 | cli-tool/components/skills/scientific/deepchem/scripts/graph_neural_network.py:212-233 — 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.
D4 · Code Duplication · Duplicated block (15–24 lines × 2) · ×1
  • Duplicated block (15–24 lines × 2) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:317 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:317-340 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:309-323 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 388 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (18–23 lines × 5) · ×1
  • Duplicated block (18–23 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:35 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py:35-52 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py:35-52 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:35-52 | cli-tool/components/skills/document-processing/pdf/scripts/fill_pdf_form_with_annotations.py:35-52 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_pdf_form_with_annotations.py:32-54 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (41–42 lines × 5) · ×1
  • Duplicated block (41–42 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py:16 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/document-processing/pdf-official/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/document-processing/pdf-processing/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/document-processing/pdf/scripts/check_bounding_boxes.py:16-56 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/check_bounding_boxes.py:19-60 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/check_bounding_boxes.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/check_bounding_boxes.py` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21 lines × 4) · ×1
  • Duplicated block (21 lines × 4) cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:86 — cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py:86-106 | cli-tool/components/skills/development/skill-creator/scripts/package_skill.py:112-132 | cli-tool/components/skills/development/skill-development/scripts/package_skill.py:112-132 | cli-tool/components/skills/productivity/skill-creator/scripts/package_skill.py:112-132 — before extracting anything, compare `cli-tool/components/skills/development/skill-creation-guide/scripts/package_skill.py` and `cli-tool/components/skills/development/skill-creator/scripts/package_skill.py` as WHOLE FILES: 93% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) cli-tool/components/skills/scientific/rdkit/scripts/similarity_search.py:59 — cli-tool/components/skills/scientific/rdkit/scripts/similarity_search.py:59-79 | cli-tool/components/skills/scientific/rdkit/scripts/substructure_filter.py:68-88 — 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.
D4 · Code Duplication · Duplicated block (20 lines × 15) · ×1
  • Duplicated block (20 lines × 15) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:42 — cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:42-61 | cli-tool/components/skills/development/senior-computer-vision/scripts/inference_optimizer.py:42-61 | cli-tool/components/skills/development/senior-computer-vision/scripts/vision_model_trainer.py:42-61 | cli-tool/components/skills/development/senior-data-engineer/scripts/data_quality_validator.py:42-61 | cli-tool/components/skills/development/senior-data-engineer/scripts/etl_performance_optimizer.py:42-61 | cli-tool/components/skills/development/senior-data-engineer/scripts/pipeline_orchestrator.py:42-61 | cli-tool/components/skills/development/senior-data-scientist/scripts/experiment_designer.py:42-61 | cli-tool/components/skills/development/senior-data-scientist/scripts/feature_engineering_pipeline.py:42-61 | cli-tool/components/skills/development/senior-data-scientist/scripts/model_evaluation_suite.py:42-61 | cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:42-61 | cli-tool/components/skills/development/senior-ml-engineer/scripts/model_deployment_pipeline.py:42-61 | cli-tool/components/skills/development/senior-ml-engineer/scripts/rag_system_builder.py:42-61 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:42-61 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:42-61 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:42-61 — before extracting anything, compare `cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py` and `cli-tool/components/skills/development/senior-computer-vision/scripts/inference_optimizer.py` as WHOLE FILES: 90% 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 2 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 3) · ×1
  • Duplicated block (19–20 lines × 3) cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:77 — cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:77-95 | cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:53-72 | cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py:24-42 — before extracting anything, compare `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py` and `cli-tool/components/skills/security/security-ownership-map/scripts/run_ownership_map.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 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 `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:77` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli-tool/components/skills/security/security-ownership-map/scripts/build_ownership_map.py:75` calls `add_argument` and `cli-tool/components/skills/security/security-ownership-map/scripts/community_maintainers.py:53` 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:590 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:590-609 | cli-tool/components/skills/video/sora/scripts/sora.py:603-621 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:590` 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.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:27 — cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:27-46 | cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:83-100 — 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 `cli-tool/components/skills/development/lint-and-validate/scripts/type_coverage.py:27` 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.
D4 · Code Duplication · Duplicated block (19 lines × 15) · ×1
  • Duplicated block (19 lines × 15) cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:69 — cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py:69-87 | cli-tool/components/skills/development/senior-computer-vision/scripts/inference_optimizer.py:69-87 | cli-tool/components/skills/development/senior-computer-vision/scripts/vision_model_trainer.py:69-87 | cli-tool/components/skills/development/senior-data-engineer/scripts/data_quality_validator.py:69-87 | cli-tool/components/skills/development/senior-data-engineer/scripts/etl_performance_optimizer.py:69-87 | cli-tool/components/skills/development/senior-data-engineer/scripts/pipeline_orchestrator.py:69-87 | cli-tool/components/skills/development/senior-data-scientist/scripts/experiment_designer.py:69-87 | cli-tool/components/skills/development/senior-data-scientist/scripts/feature_engineering_pipeline.py:69-87 | cli-tool/components/skills/development/senior-data-scientist/scripts/model_evaluation_suite.py:69-87 | cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:69-87 | cli-tool/components/skills/development/senior-ml-engineer/scripts/model_deployment_pipeline.py:69-87 | cli-tool/components/skills/development/senior-ml-engineer/scripts/rag_system_builder.py:69-87 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:69-87 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:69-87 | cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:69-87 — before extracting anything, compare `cli-tool/components/skills/development/senior-computer-vision/scripts/dataset_pipeline_builder.py` and `cli-tool/components/skills/development/senior-computer-vision/scripts/inference_optimizer.py` as WHOLE FILES: 90% 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 2 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 5) · ×1
  • Duplicated block (17–18 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/create_validation_image.py:10 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/document-processing/pdf-official/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/document-processing/pdf-processing/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/document-processing/pdf/scripts/create_validation_image.py:10-26 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/create_validation_image.py:13-30 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/create_validation_image.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/create_validation_image.py` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) cli-tool/components/skills/scientific/clinical-decision-support/scripts/build_decision_tree.py:171 — cli-tool/components/skills/scientific/clinical-decision-support/scripts/build_decision_tree.py:171-188 | cli-tool/components/skills/scientific/clinical-decision-support/scripts/build_decision_tree.py:191-208 — 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.
D4 · Code Duplication · Duplicated block (8–17 lines × 4) · ×1
  • Duplicated block (8–17 lines × 4) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:132 — cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:132-140 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:155-162 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:237-253 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:314-321 — 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.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:56 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/document-processing/pdf/scripts/fill_fillable_fields.py:56-71 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_fillable_fields.py:60-75 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (20 lines × 4) · ×1
  • Duplicated block (20 lines × 4) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:92 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_structure.py:92-111 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_structure.py:92-111 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_structure.py:92-111 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_structure.py:92-111 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_structure.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_structure.py` as WHOLE FILES: 100% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 20) · ×1
  • Duplicated block (15 lines × 20) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:23 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:23-37 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:23-37 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:23-37 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:23-37 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:23-37 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:23-37 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:23-37 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:23-37 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:23-37 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:23-37 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:23-37 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:23-37 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:23-37 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:23-37 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:23-37 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:23-37 — before extracting anything, compare `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py` and `cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 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.
D4 · Code Duplication · Duplicated block (4–15 lines × 4) · ×1
  • Duplicated block (4–15 lines × 4) cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:210 — cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:210-224 | cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:249-252 | cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:259-262 | cli-tool/components/skills/business-marketing/app-store-optimization/aso_scorer.py:296-309 — 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. 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.
D4 · Code Duplication · Duplicated block (14 lines × 20) · ×1
  • Duplicated block (14 lines × 20) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:98 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:98-111 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:98-111 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:98-111 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:98-111 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:98-111 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:98-111 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:98-111 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:98-111 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:98-111 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:98-111 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:98-111 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:98-111 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:98-111 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:98-111 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:98-111 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:98-111 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:98-111 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:98-111 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:98-111 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:98-111 — before extracting anything, compare `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py` and `cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 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 `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:98` 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.
D4 · Code Duplication · Duplicated block (7–14 lines × 9) · ×1
  • Duplicated block (7–14 lines × 9) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:117 — cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:117-130 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:139-147 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:227-233 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:320-328 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:335-341 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:477-484 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:502-509 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:520-526 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:533-540 — all 9 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 `cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:117` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 5) · ×1
  • Duplicated block (13–14 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/convert_pdf_to_images.py:10 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/convert_pdf_to_images.py:10-22 | cli-tool/components/skills/document-processing/pdf-official/scripts/convert_pdf_to_images.py:10-22 | cli-tool/components/skills/document-processing/pdf-processing/scripts/convert_pdf_to_images.py:10-22 | cli-tool/components/skills/document-processing/pdf/scripts/convert_pdf_to_images.py:10-22 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/convert_pdf_to_images.py:11-24 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/convert_pdf_to_images.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/convert_pdf_to_images.py` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11–14 lines × 4) · ×1
  • Duplicated block (11–14 lines × 4) cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:84 — cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:84-97 | cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:793-805 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py:83-94 | cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image_ai.py:717-727 — before extracting anything, compare `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py` and `cli-tool/components/skills/scientific/scientific-slides/scripts/generate_slide_image.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:84` 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, `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic.py:83` calls `add_argument` and `cli-tool/components/skills/scientific/scientific-schematics/scripts/generate_schematic_ai.py:792` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:69 — cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py:69-82 | cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py:69-82 | cli-tool/components/skills/productivity/skill-creator/eval-viewer/generate_review.py:69-82 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/eval-viewer/generate_review.py` and `cli-tool/components/skills/development/skill-development/eval-viewer/generate_review.py` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×1
  • Duplicated block (13 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:75 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/document-processing/pdf/scripts/fill_fillable_fields.py:75-87 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/fill_fillable_fields.py:91-103 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_fillable_fields.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_fillable_fields.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9–13 lines × 3) · ×1
  • Duplicated block (9–13 lines × 3) cli-tool/components/skills/scientific/bioservices/scripts/compound_cross_reference.py:249 — cli-tool/components/skills/scientific/bioservices/scripts/compound_cross_reference.py:249-261 | cli-tool/components/skills/scientific/venue-templates/scripts/query_template.py:140-148 | cli-tool/components/skills/scientific/venue-templates/scripts/query_template.py:182-190 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:804 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:804-816 | cli-tool/components/skills/video/sora/scripts/sora.py:843-854 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:54 — cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:54-66 | cli-tool/components/skills/scientific/simpy/scripts/resource_monitor.py:81-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (12 lines × 20) · ×1
  • Duplicated block (12 lines × 20) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:48 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:48-59 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:48-59 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:48-59 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:48-59 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:48-59 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:48-59 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:48-59 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:48-59 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:48-59 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:48-59 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:48-59 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:48-59 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:48-59 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:48-59 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:48-59 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:48-59 — before extracting anything, compare `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py` and `cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 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.
D4 · Code Duplication · Duplicated block (9–12 lines × 5) · ×1
  • Duplicated block (9–12 lines × 5) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:130 — cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:130-139 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:153-161 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:244-252 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:312-320 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:340-351 — all 5 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 `cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:153` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:307` calls `search` and `cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:152` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:652 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:652-663 | cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:722-732 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 7) · ×1
  • Duplicated block (11 lines × 7) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:140 — cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:140-150 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:216-226 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:292-302 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:374-384 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:452-462 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:562-572 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:662-672 — all 7 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.
D4 · Code Duplication · Duplicated block (8–11 lines × 3) · ×1
  • Duplicated block (8–11 lines × 3) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:162 — cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:162-169 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:182-189 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:342-352 — 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 `cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:182` 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.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) cli-tool/components/skills/development/skill-development/scripts/generate_report.py:17 — cli-tool/components/skills/development/skill-creator/scripts/generate_report.py:17-38 | cli-tool/components/skills/development/skill-development/scripts/generate_report.py:17-38 | cli-tool/components/skills/productivity/skill-creator/scripts/generate_report.py:17-38 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/generate_report.py` and `cli-tool/components/skills/development/skill-development/scripts/generate_report.py` as WHOLE FILES: 100% 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 2 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/development/skill-creator/scripts/generate_report.py:17` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×1
  • Duplicated block (9–10 lines × 5) cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:137 — cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:137-146 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:318-327 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:474-483 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:517-525 | cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:583-592 — all 5 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 `cli-tool/components/skills/creative-design/mobile-design/scripts/mobile_audit.py:474` 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.
D4 · Code Duplication · Duplicated block (4–9 lines × 3) · ×1
  • Duplicated block (4–9 lines × 3) cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:69 — cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:69-77 | cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:107-115 | cli-tool/components/skills/scientific/gene-database/scripts/fetch_gene_data.py:147-150 — 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. 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. 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.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:270 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:270-277 | cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:259-266 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:270-277 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:259-266 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:270-277 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:259-266 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:257` calls `add_argument` and `cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:269` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×1
  • Duplicated block (7–8 lines × 3) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:496 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:496-503 | cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:547-553 | cli-tool/components/skills/video/sora/scripts/sora.py:482-488 — before extracting anything, compare `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py` and `cli-tool/components/skills/video/sora/scripts/sora.py` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:556` calls `get` and `cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:506` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:130 — cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:130-136 | cli-tool/components/skills/analytics/google-analytics/scripts/analyze.py:188-195 — 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:334 — cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:334-340 | cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py:426-431 — 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.
D4 · Code Duplication · Duplicated block (4–7 lines × 4) · ×1
  • Duplicated block (4–7 lines × 4) cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:102 — cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:102-105 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:281-287 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:363-369 | cli-tool/components/skills/scientific/brenda-database/scripts/brenda_visualization.py:437-440 — 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. 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.
D4 · Code Duplication · Duplicated block (2–7 lines × 5) · ×1
  • Duplicated block (2–7 lines × 5) cli-tool/components/skills/development/skill-development/scripts/run_loop.py:250 — cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:250-251 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:250-251 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:250-251 | cli-tool/components/skills/scientific/etetoolkit/scripts/quick_visualize.py:164-170 | cli-tool/components/skills/scientific/pufferlib/scripts/train_template.py:171-179 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_loop.py` and `cli-tool/components/skills/development/skill-development/scripts/run_loop.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 333 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `cli-tool/components/skills/scientific/etetoolkit/scripts/quick_visualize.py:164` 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.
D4 · Code Duplication · Duplicated block (8 lines × 20) · ×1
  • Duplicated block (8 lines × 20) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:62 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:62-69 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:62-69 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:62-69 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:62-69 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:62-69 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:62-69 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:62-69 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:62-69 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:62-69 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:62-69 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:62-69 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:62-69 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:62-69 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:62-69 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:62-69 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:62-69 — before extracting anything, compare `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py` and `cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 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.
D4 · Code Duplication · Duplicated block (3–6 lines × 9) · ×1
  • Duplicated block (3–6 lines × 9) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:265 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:265-267 | cli-tool/components/skills/development/skill-creator/scripts/run_loop.py:251-253 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:265-267 | cli-tool/components/skills/development/skill-development/scripts/run_loop.py:251-253 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:265-267 | cli-tool/components/skills/productivity/skill-creator/scripts/run_loop.py:251-253 | cli-tool/components/skills/scientific/pufferlib/scripts/train_template.py:170-175 | cli-tool/components/skills/scientific/pufferlib/scripts/train_template.py:217-224 | cli-tool/components/skills/scientific/torch_geometric/scripts/benchmark_model.py:293-298 — there are 9 copies across 8 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:350 — cli-tool/components/skills/creative-design/imagegen/scripts/image_gen.py:350-357 | cli-tool/components/skills/media/speech/scripts/text_to_speech.py:240-247 | cli-tool/components/skills/video/sora/scripts/sora.py:243-250 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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.
D4 · Code Duplication · Duplicated block (6 lines × 20) · ×1
  • Duplicated block (6 lines × 20) cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:40 — cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py:40-45 | cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py:40-45 | cli-tool/components/skills/development/senior-architect/scripts/project_architect.py:40-45 | cli-tool/components/skills/development/senior-backend/scripts/api_load_tester.py:40-45 | cli-tool/components/skills/development/senior-backend/scripts/api_scaffolder.py:40-45 | cli-tool/components/skills/development/senior-backend/scripts/database_migration_tool.py:40-45 | cli-tool/components/skills/development/senior-devops/scripts/deployment_manager.py:40-45 | cli-tool/components/skills/development/senior-devops/scripts/pipeline_generator.py:40-45 | cli-tool/components/skills/development/senior-devops/scripts/terraform_scaffolder.py:40-45 | cli-tool/components/skills/development/senior-fullstack/scripts/code_quality_analyzer.py:40-45 | cli-tool/components/skills/development/senior-fullstack/scripts/fullstack_scaffolder.py:40-45 | cli-tool/components/skills/development/senior-fullstack/scripts/project_scaffolder.py:40-45 | cli-tool/components/skills/development/senior-qa/scripts/coverage_analyzer.py:40-45 | cli-tool/components/skills/development/senior-qa/scripts/e2e_test_scaffolder.py:40-45 | cli-tool/components/skills/development/senior-secops/scripts/compliance_checker.py:40-45 | cli-tool/components/skills/development/senior-secops/scripts/security_scanner.py:40-45 | cli-tool/components/skills/development/senior-secops/scripts/vulnerability_assessor.py:40-45 | cli-tool/components/skills/development/senior-security/scripts/pentest_automator.py:40-45 | cli-tool/components/skills/development/senior-security/scripts/security_auditor.py:40-45 | cli-tool/components/skills/development/senior-security/scripts/threat_modeler.py:40-45 — before extracting anything, compare `cli-tool/components/skills/development/senior-architect/scripts/architecture_diagram_generator.py` and `cli-tool/components/skills/development/senior-architect/scripts/dependency_analyzer.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) cli-tool/components/skills/development/skill-development/scripts/run_eval.py:23 — cli-tool/components/skills/development/skill-creator/scripts/run_eval.py:23-32 | cli-tool/components/skills/development/skill-development/scripts/run_eval.py:23-32 | cli-tool/components/skills/productivity/skill-creator/scripts/run_eval.py:23-32 — before extracting anything, compare `cli-tool/components/skills/development/skill-creator/scripts/run_eval.py` and `cli-tool/components/skills/development/skill-development/scripts/run_eval.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 262 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:10 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py:10-16 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py:10-16 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:10-16 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_field_info.py:10-16 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/extract_form_field_info.py:13-19 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:111 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py:111-115 | cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py:111-115 | cli-tool/components/skills/document-processing/pdf-processing/scripts/extract_form_field_info.py:111-115 | cli-tool/components/skills/document-processing/pdf/scripts/extract_form_field_info.py:111-115 | cli-tool/components/skills/scientific/document-skills/pdf/scripts/extract_form_field_info.py:141-145 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/extract_form_field_info.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/extract_form_field_info.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:11 — cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py:11-20 | cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py:11-20 | cli-tool/components/skills/document-processing/pdf-processing/scripts/fill_pdf_form_with_annotations.py:11-20 | cli-tool/components/skills/document-processing/pdf/scripts/fill_pdf_form_with_annotations.py:11-20 — before extracting anything, compare `cli-tool/components/skills/document-processing/pdf-anthropic/scripts/fill_pdf_form_with_annotations.py` and `cli-tool/components/skills/document-processing/pdf-official/scripts/fill_pdf_form_with_annotations.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) cli-tool/components/skills/business-marketing/app-store-optimization/ab_test_planner.py:225 — cli-tool/components/skills/business-marketing/app-store-optimization/ab_test_planner.py:225-275 | cli-tool/components/skills/business-marketing/app-store-optimization/ab_test_planner.py:282-327 — These two members are one piece of code written twice and then edited apart: 46 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 · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) scripts/generate_components_json.py:656 — scripts/generate_components_json.py:656-680 | scripts/generate_components_json.py:934-959 — 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.
D4 · Code Duplication · Duplicated block (20–22 lines × 2) · ×1
  • Duplicated block (20–22 lines × 2) cli-tool/components/skills/business-marketing/app-store-optimization/ab_test_planner.py:225 — cli-tool/components/skills/business-marketing/app-store-optimization/ab_test_planner.py:225-246 | cli-tool/components/skills/business-marketing/app-store-optimization/ab_test_planner.py:282-301 — 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 2) · ×1
  • Duplicated block (6–8 lines × 2) cli-tool/components/sandbox/e2b/e2b-launcher.py:73 — cli-tool/components/sandbox/e2b/e2b-launcher.py:73-80 | cli-tool/components/sandbox/e2b/e2b-monitor.py:209-214 — 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.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 257 JVM, Python, JavaScript/TypeScript, Rust production file(s) this check read across 18 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; Rust: the log and tracing crates (info!/warn!/error!, #[instrument]), slog, env_logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
R10 · Code Duplication · Forked directory tree (30 identical files, ~2909 lines × 2 trees) · ×1
  • Forked directory tree (30 identical files, ~2909 lines × 2 trees) cli-tool/components/skills/creative-design/remotion-best-practices/rules/extract-frames.md:1 — cli-tool/components/skills/creative-design/remotion-best-practices/rules/ and cli-tool/components/skills/video/remotion/references/ are near-verbatim copies of each other: 30 files are byte-identical under the same relative paths (~2909 lines; the trees hold 31 and 31 files). That is one structural fact, not 30 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.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (45 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (45 clone groups) cli-tool/components/mods/games/chess/hooks/jev.ts:18 — 45 duplicated blocks under cli-tool/components/mods/ have copies in at least two of the sibling directories enterprise, games, integrations, observability, productivity, security (+1 more sibling(s) not listed) — 42 of them are reported below, and 3 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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.
R10 · Code Duplication · Duplication concentrated across 13 sibling directories (45 clone groups) · ×1
  • Duplication concentrated across 13 sibling directories (45 clone groups) cli-tool/components/mods/games/cc-arcade/hooks/games/doom.ts:14 — 45 of the duplicated blocks reported below have copies in at least two of the sibling directories 2048, cc-arcade, diff-invaders, doom, flappy, invaders (+7 more sibling(s) not listed) under cli-tool/components/mods/games/. That concentration is one structural fact, not 45 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 45 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.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (12 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (12 clone groups) cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:65 — 12 duplicated blocks under cli-tool/components/mods/integrations/ have copies in at least two of the sibling directories bluesky-feed, linear-tickets, neon-branch-per-session, vercel-deploys — 10 of them are reported below, and 2 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (9 clone groups) cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:83 — 9 duplicated blocks under cli-tool/components/mods/ui/ have copies in at least two of the sibling directories agent-flow, git-sidebar, live-preview, stack-viewer, turn-inspector — 8 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (8 clone groups) cli-tool/components/mods/security/jev-auto-mode/hooks/judge.ts:20 — 8 of the duplicated blocks reported below have copies in at least two of the sibling directories block-destructive-commands, jev-auto-mode, jev-guardrails, jev-vercel-sandbox, large-edit-confirmation, protected-paths-guard (+1 more sibling(s) not listed) under cli-tool/components/mods/security/. That concentration is one structural fact, not 8 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 8 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.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (5 clone groups) cli-tool/analytics-ui/public/services/WebSocketService.js:5 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories analytics-ui, src under cli-tool/. That concentration is one structural fact, not 5 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 5 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.
R10 · Code Duplication · Wholesale file copy (602 identical lines × 2 files) · ×1
  • Wholesale file copy (602 identical lines × 2 files) cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:28 — cli-tool/components/skills/document-processing/pptx/scripts/html2pptx.js:28 · cli-tool/components/skills/scientific/document-skills/pptx/scripts/html2pptx.js:28 — these 2 files are line-for-line copies of one another — 602 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 · Wholesale file copy (248 identical lines × 2 files) · ×1
  • Wholesale file copy (248 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/games/doom.ts:14 — cli-tool/components/mods/games/cc-arcade/hooks/games/doom.ts:14 · cli-tool/components/mods/games/doom/hooks/games/doom.ts:14 — these 2 files are line-for-line copies of one another — 248 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 · Wholesale file copy (246 identical lines × 2 files) · ×1
  • Wholesale file copy (246 identical lines × 2 files) cli-tool/analytics-ui/public/services/WebSocketService.js:5 — cli-tool/analytics-ui/public/services/WebSocketService.js:5 · cli-tool/src/analytics-web/services/WebSocketService.js:5 — these 2 files are line-for-line copies of one another — 246 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 · Wholesale file copy (214 identical lines × 2 files) · ×1
  • Wholesale file copy (214 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/doom.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/doom.tsx:2 · cli-tool/components/mods/games/doom/hooks/boards/doom.tsx:2 — these 2 files are line-for-line copies of one another — 214 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 · Wholesale file copy (186 identical lines × 2 files) · ×1
  • Wholesale file copy (186 identical lines × 2 files) cli-tool/analytics-ui/public/services/DataService.js:5 — cli-tool/analytics-ui/public/services/DataService.js:5 · cli-tool/src/analytics-web/services/DataService.js:5 — these 2 files are line-for-line copies of one another — 186 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 · Wholesale file copy (116 identical lines × 2 files) · ×1
  • Wholesale file copy (116 identical lines × 2 files) cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/charts-bar-chart.tsx:1 — cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/charts-bar-chart.tsx:1 · cli-tool/components/skills/video/remotion/references/assets/charts/bar-chart.tsx:1 — these 2 files are line-for-line copies of one another — 116 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 · Wholesale file copy (101 identical lines × 2 files) · ×1
  • Wholesale file copy (101 identical lines × 2 files) cli-tool/analytics-ui/public/services/StateService.js:5 — cli-tool/analytics-ui/public/services/StateService.js:5 · cli-tool/src/analytics-web/services/StateService.js:5 — these 2 files are line-for-line copies of one another — 101 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 (97 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (97 matched lines × 2 locations) cli-tool/src/index.js:576 — cli-tool/src/index.js:576 · cli-tool/src/index.js:955 — the two spans are one implementation copied and then locally edited — 671 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (96 identical lines × 2 files) · ×1
  • Wholesale file copy (96 identical lines × 2 files) cli-tool/components/skills/development/writing-skills/render-graphs.js:16 — cli-tool/components/skills/development/writing-skills/render-graphs.js:16 · cli-tool/components/skills/productivity/writing-skills/render-graphs.js:16 — these 2 files are line-for-line copies of one another — 96 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 (85 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (85 matched lines × 2 locations) cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:83 — cli-tool/components/mods/ui/agent-flow/hooks/agent-flow.tsx:83 · cli-tool/components/mods/ui/git-sidebar/hooks/git-sidebar.tsx:99 — the two spans are one implementation copied and then locally edited — 682 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.
R10 · Code Duplication · Wholesale file copy (74 identical lines × 2 files) · ×1
  • Wholesale file copy (74 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/minesweeper.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/minesweeper.tsx:2 · cli-tool/components/mods/games/minesweeper/hooks/boards/minesweeper.tsx:2 — these 2 files are line-for-line copies of one another — 74 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 (71 lines × 2 locations) · ×1
  • Duplicated block (71 lines × 2 locations) REDACTED:333 — REDACTED:333 · cli-tool/src/analytics/core/ConversationAnalyzer.js:626 — 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.
R10 · Code Duplication · Duplicated block (70 lines × 2 locations) · ×1
  • Duplicated block (70 lines × 2 locations) REDACTED:447 — REDACTED:447 · cli-tool/src/analytics/core/ConversationAnalyzer.js:779 — 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.
R10 · Code Duplication · Duplicated block with local edits (67 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (67 matched lines × 2 locations) REDACTED:627 — REDACTED:627 · REDACTED:1036 — the two spans are one implementation copied and then locally edited — 402 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (66 identical lines × 2 files) · ×1
  • Wholesale file copy (66 identical lines × 2 files) cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-word-highlight.tsx:1 — cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-word-highlight.tsx:1 · cli-tool/components/skills/video/remotion/references/assets/text-animations-word-highlight.tsx:1 — 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.
R10 · Code Duplication · Wholesale file copy (64 identical lines × 4 files) · ×1
  • Wholesale file copy (64 identical lines × 4 files) cloudflare-workers/crons/sentry.js:15 — cloudflare-workers/crons/sentry.js:15 · cloudflare-workers/docs-monitor/sentry.js:15 · cloudflare-workers/newsletter/sentry.js:15 · cloudflare-workers/pulse/sentry.js:15 — these 4 files are line-for-line copies of one another — 64 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 · Wholesale file copy (63 identical lines × 2 files) · ×1
  • Wholesale file copy (63 identical lines × 2 files) cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-typewriter.tsx:6 — cli-tool/components/skills/creative-design/remotion-best-practices/rules/assets/text-animations-typewriter.tsx:6 · cli-tool/components/skills/video/remotion/references/assets/text-animations-typewriter.tsx:6 — 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.
R10 · Code Duplication · Duplicated block with local edits (60 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (60 matched lines × 2 locations) cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:65 — cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx:65 · cli-tool/components/mods/integrations/linear-tickets/hooks/linear-tickets.tsx:73 — the two spans are one implementation copied and then locally edited — 449 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.
R10 · Code Duplication · Wholesale file copy (59 identical lines × 2 files) · ×1
  • Wholesale file copy (59 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/pong.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/pong.tsx:2 · cli-tool/components/mods/games/pong/hooks/boards/pong.tsx:2 — these 2 files are line-for-line copies of one another — 59 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 · Wholesale file copy (57 identical lines × 2 files) · ×1
  • Wholesale file copy (57 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/flappy.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/flappy.tsx:2 · cli-tool/components/mods/games/flappy/hooks/boards/flappy.tsx:2 — these 2 files are line-for-line copies of one another — 57 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 (57 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (57 matched lines × 2 locations) cli-tool/components/skills/creative-design/claude-d3js-skill/assets/chart-template.jsx:5 — cli-tool/components/skills/creative-design/claude-d3js-skill/assets/chart-template.jsx:5 · cli-tool/components/skills/creative-design/claude-d3js-skill/assets/interactive-template.jsx:7 — the two spans are one implementation copied and then locally edited — 422 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.
R10 · Code Duplication · Wholesale file copy (55 identical lines × 2 files) · ×1
  • Wholesale file copy (55 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/tetris.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/tetris.tsx:2 · cli-tool/components/mods/games/tetris/hooks/boards/tetris.tsx:2 — 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.
R10 · Code Duplication · Duplicated block with local edits (55 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (55 matched lines × 2 locations) cli-tool/src/analytics/core/ConversationAnalyzer.js:267 — cli-tool/src/analytics/core/ConversationAnalyzer.js:267 · cli-tool/src/analytics/data/DataCache.js:134 — the two spans are one implementation copied and then locally edited — 426 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.
R10 · Code Duplication · Duplicated block (54 lines × 2 locations) · ×1
  • Duplicated block (54 lines × 2 locations) cli-tool/components/mods/games/cc-arcade/hooks/boards/snake.tsx:8 — cli-tool/components/mods/games/cc-arcade/hooks/boards/snake.tsx:8 · cli-tool/components/mods/games/snake/hooks/boards/snake.tsx:8 — 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.
R10 · Code Duplication · Duplicated block with local edits (54 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (54 matched lines × 2 locations) cli-tool/src/analytics/core/SessionAnalyzer.js:173 — cli-tool/src/analytics/core/SessionAnalyzer.js:173 · cli-tool/src/analytics/core/SessionAnalyzer.js:305 — the two spans are one implementation copied and then locally edited — 401 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (52 lines × 6 locations) · ×1
  • Duplicated block (52 lines × 6 locations) cli-tool/components/mods/games/2048/hooks/register.tsx:12 — cli-tool/components/mods/games/2048/hooks/register.tsx:12 · cli-tool/components/mods/games/flappy/hooks/register.tsx:12 · cli-tool/components/mods/games/invaders/hooks/register.tsx:12 · cli-tool/components/mods/games/pong/hooks/register.tsx:12 · +2 more site(s) not listed — the 6 copies are spread across 6 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 · Wholesale file copy (52 identical lines × 2 files) · ×1
  • Wholesale file copy (52 identical lines × 2 files) cli-tool/components/mods/games/cc-arcade/hooks/boards/pet.tsx:2 — cli-tool/components/mods/games/cc-arcade/hooks/boards/pet.tsx:2 · cli-tool/components/mods/games/pet/hooks/boards/pet.tsx:2 — these 2 files are line-for-line copies of one another — 52 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 (47 lines × 2 locations) · ×1
  • Duplicated block (47 lines × 2 locations) cli-tool/components/mods/games/2048/hooks/boards/twenty48.tsx:10 — cli-tool/components/mods/games/2048/hooks/boards/twenty48.tsx:10 · cli-tool/components/mods/games/cc-arcade/hooks/boards/twenty48.tsx:10 — 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.
R10 · Code Duplication · Duplicated block (40 lines × 2 locations) · ×1
  • Duplicated block (40 lines × 2 locations) dashboard/src/components/JsonViewer.tsx:124 — dashboard/src/components/JsonViewer.tsx:124 · dashboard/src/components/JsonViewer.tsx:197 — 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.
R11 · Import Boundaries · Boundary violation [package · ×1
  • Boundary violation [package:test-cross-package-internals] dashboard/tests/download-client-signals.test.ts:11 — dashboard/tests/download-client-signals.test.ts:11 reaches past another workspace package's public entry into its internals with a relative path (../../cli-tool/src/agent-detection.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
R2 · Cyclomatic Complexity · Complex function createClaudeConfig (cyclomatic 93, cognitive 76) · ×1
  • Complex function createClaudeConfig (cyclomatic 93, cognitive 76) cli-tool/src/index.js:86 — createClaudeConfig has cyclomatic complexity 93 and cognitive complexity 76; 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 getHookDescription (cyclomatic 74, cognitive 71) · ×1
  • Complex function getHookDescription (cyclomatic 74, cognitive 71) cli-tool/src/hook-scanner.js:110 — getHookDescription has cyclomatic complexity 74 and cognitive complexity 71; 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 installIndividualSetting (cyclomatic 59, cognitive 103) · ×1
  • Complex function installIndividualSetting (cyclomatic 59, cognitive 103) cli-tool/src/index.js:553 — installIndividualSetting has cyclomatic complexity 59 and cognitive complexity 103; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 59, cognitive 84) · ×1
  • Complex function (anonymous) (cyclomatic 59, cognitive 84) cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:248 — (anonymous) has cyclomatic complexity 59 and cognitive complexity 84; 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.
R2 · Cyclomatic Complexity · Complex function pseudoMoves (cyclomatic 49, cognitive 97) · ×1
  • Complex function pseudoMoves (cyclomatic 49, cognitive 97) cli-tool/components/mods/games/chess/hooks/chess.ts:147 — pseudoMoves has cyclomatic complexity 49 and cognitive complexity 97; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 49, cognitive 68) · ×1
  • Complex function (anonymous) (cyclomatic 49, cognitive 68) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:1100 — (anonymous) has cyclomatic complexity 49 and cognitive complexity 68; 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.
R2 · Cyclomatic Complexity · Complex function apply (cyclomatic 48, cognitive 91) · ×1
  • Complex function apply (cyclomatic 48, cognitive 91) cli-tool/components/mods/enterprise/policy-ceiling/hooks/ceiling.ts:85 — apply has cyclomatic complexity 48 and cognitive complexity 91; 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.
R2 · Cyclomatic Complexity · Complex function scanFiles (cyclomatic 48, cognitive 88) · ×1
  • Complex function scanFiles (cyclomatic 48, cognitive 88) cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:251 — scanFiles has cyclomatic complexity 48 and cognitive complexity 88; 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.
R2 · Cyclomatic Complexity · Complex function copyTemplateFiles (cyclomatic 45, cognitive 98) · ×1
  • Complex function copyTemplateFiles (cyclomatic 45, cognitive 98) cli-tool/src/file-operations.js:373 — copyTemplateFiles has cyclomatic complexity 45 and cognitive complexity 98; 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.
R2 · Cyclomatic Complexity · Complex function parseAndCorrelateToolMessages (cyclomatic 45, cognitive 85) · ×1
  • Complex function parseAndCorrelateToolMessages (cyclomatic 45, cognitive 85) cli-tool/src/analytics/data/DataCache.js:142 — parseAndCorrelateToolMessages has cyclomatic complexity 45 and cognitive complexity 85; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 45, cognitive 43) · ×1
  • Complex function (anonymous) (cyclomatic 45, cognitive 43) REDACTED:520 — (anonymous) has cyclomatic complexity 45 and cognitive complexity 43; 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 (anonymous) (cyclomatic 43, cognitive 83) · ×1
  • Complex function (anonymous) (cyclomatic 43, cognitive 83) cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:187 — (anonymous) has cyclomatic complexity 43 and cognitive complexity 83; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 42, cognitive 51) · ×1
  • Complex function (anonymous) (cyclomatic 42, cognitive 51) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:992 — (anonymous) has cyclomatic complexity 42 and cognitive complexity 51; 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.
R2 · Cyclomatic Complexity · Complex function getStepConfig (cyclomatic 42, cognitive 49) · ×1
  • Complex function getStepConfig (cyclomatic 42, cognitive 49) cli-tool/src/prompts.js:79 — getStepConfig has cyclomatic complexity 42 and cognitive complexity 49; 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.
R2 · Cyclomatic Complexity · Complex function reasonFor (cyclomatic 42, cognitive 42) · ×1
  • Complex function reasonFor (cyclomatic 42, cognitive 42) REDACTED:177 — reasonFor has cyclomatic complexity 42 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 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.
R2 · Cyclomatic Complexity · Complex function installIndividualHook (cyclomatic 41, cognitive 69) · ×1
  • Complex function installIndividualHook (cyclomatic 41, cognitive 69) cli-tool/src/index.js:933 — installIndividualHook has cyclomatic complexity 41 and cognitive complexity 69; 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.
R2 · Cyclomatic Complexity · Complex function ruleMatches (cyclomatic 39, cognitive 49) · ×1
  • Complex function ruleMatches (cyclomatic 39, cognitive 49) REDACTED:635 — ruleMatches has cyclomatic complexity 39 and cognitive complexity 49; 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.
R2 · Cyclomatic Complexity · Complex function validateRequest (cyclomatic 38, cognitive 22) · ×1
  • Complex function validateRequest (cyclomatic 38, cognitive 22) cli-tool/components/skills/development/pudu-task-telemetry/scripts/lib/ollama-adapter.mjs:58 — validateRequest has cyclomatic complexity 38 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.
R2 · Cyclomatic Complexity · Complex function gateFor (cyclomatic 36, cognitive 97) · ×1
  • Complex function gateFor (cyclomatic 36, cognitive 97) REDACTED:268 — gateFor has cyclomatic complexity 36 and cognitive complexity 97; 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.
R2 · Cyclomatic Complexity · Complex function SkillExplorer (cyclomatic 36, cognitive 30) · ×1
  • Complex function SkillExplorer (cyclomatic 36, cognitive 30) REDACTED:144 — SkillExplorer has cyclomatic complexity 36 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 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 detectProject (cyclomatic 35, cognitive 60) · ×1
  • Complex function detectProject (cyclomatic 35, cognitive 60) cli-tool/src/utils.js:4 — detectProject has cyclomatic complexity 35 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.
R2 · Cyclomatic Complexity · Complex function pane (cyclomatic 35, cognitive 41) · ×1
  • Complex function pane (cyclomatic 35, cognitive 41) cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts:134 — pane has cyclomatic complexity 35 and cognitive complexity 41; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 34, cognitive 67) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 67) cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts:278 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 67; 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.
R2 · Cyclomatic Complexity · Complex function pump (cyclomatic 34, cognitive 56) · ×1
  • Complex function pump (cyclomatic 34, cognitive 56) cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts:440 — pump has cyclomatic complexity 34 and cognitive complexity 56; 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.
R2 · Cyclomatic Complexity · Complex function auditDom (cyclomatic 34, cognitive 50) · ×1
  • Complex function auditDom (cyclomatic 34, cognitive 50) cli-tool/components/skills/development/senior-frontend/scripts/page-audit.mjs:5 — auditDom has cyclomatic complexity 34 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 34, cognitive 45) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 45) REDACTED:24 — (anonymous) has cyclomatic complexity 34 and cognitive complexity 45; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 33, cognitive 51) · ×1
  • Complex function (anonymous) (cyclomatic 33, cognitive 51) cli-tool/components/mods/ui/git-sidebar/hooks/git-sidebar.tsx:186 — (anonymous) has cyclomatic complexity 33 and cognitive complexity 51; 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.
R2 · Cyclomatic Complexity · Complex function bashParts (cyclomatic 33, cognitive 49) · ×1
  • Complex function bashParts (cyclomatic 33, cognitive 49) REDACTED:407 — bashParts has cyclomatic complexity 33 and cognitive complexity 49; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 33, cognitive 47) · ×1
  • Complex function (anonymous) (cyclomatic 33, cognitive 47) cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts:173 — (anonymous) has cyclomatic complexity 33 and cognitive complexity 47; 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.
R2 · Cyclomatic Complexity · Complex function installMultipleComponents (cyclomatic 33, cognitive 41) · ×1
  • Complex function installMultipleComponents (cyclomatic 33, cognitive 41) cli-tool/src/index.js:1979 — installMultipleComponents has cyclomatic complexity 33 and cognitive complexity 41; 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 33, cognitive 36) · ×1
  • Complex function (anonymous) (cyclomatic 33, cognitive 36) dashboard/src/components/ComponentGrid.tsx:602 — (anonymous) has cyclomatic complexity 33 and cognitive complexity 36; 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.
R2 · Cyclomatic Complexity · Complex function ComponentGrid (cyclomatic 33, cognitive 28) · ×1
  • Complex function ComponentGrid (cyclomatic 33, cognitive 28) dashboard/src/components/ComponentGrid.tsx:41 — ComponentGrid has cyclomatic complexity 33 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 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 parseAndCorrelateToolMessages (cyclomatic 32, cognitive 60) · ×1
  • Complex function parseAndCorrelateToolMessages (cyclomatic 32, cognitive 60) cli-tool/src/analytics/core/ConversationAnalyzer.js:275 — parseAndCorrelateToolMessages has cyclomatic complexity 32 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.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 32, cognitive 33) · ×1
  • Complex function main (cyclomatic 32, cognitive 33) cli-tool/components/skills/design-to-code/scripts/coderio-skill.mjs:100 — main has cyclomatic complexity 32 and cognitive complexity 33; 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.
R3 · Large Files · cli-tool/src/index.js · ×1
  • cli-tool/src/index.js: 2425 lines of code cli-tool/src/index.js:1 — cli-tool/src/index.js has 2425 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 · REDACTED · ×1
  • REDACTED: 1742 lines of code REDACTED:1 — REDACTED has 1742 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 · cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx · ×1
  • cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx: 1285 lines of code cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx:1 — cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx has 1285 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 · cli-tool/src/health-check.js · ×1
  • cli-tool/src/health-check.js: 1244 lines of code cli-tool/src/health-check.js:1 — cli-tool/src/health-check.js has 1244 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 · dashboard/src/components/MyComponentsView.tsx · ×1
  • dashboard/src/components/MyComponentsView.tsx: 1036 lines of code dashboard/src/components/MyComponentsView.tsx:1 — dashboard/src/components/MyComponentsView.tsx has 1036 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 · REDACTED · ×1
  • REDACTED: 1024 lines of code REDACTED:1 — REDACTED has 1024 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 · cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts · ×1
  • cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts: 886 lines of code cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts:1 — cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts has 886 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 · cli-tool/src/analytics/core/ConversationAnalyzer.js · ×1
  • cli-tool/src/analytics/core/ConversationAnalyzer.js: 875 lines of code cli-tool/src/analytics/core/ConversationAnalyzer.js:1 — cli-tool/src/analytics/core/ConversationAnalyzer.js has 875 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 · cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts · ×1
  • cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts: 866 lines of code cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts:1 — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts has 866 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 · dashboard/src/components/ComponentGrid.tsx · ×1
  • dashboard/src/components/ComponentGrid.tsx: 838 lines of code dashboard/src/components/ComponentGrid.tsx:1 — dashboard/src/components/ComponentGrid.tsx has 838 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 · REDACTED · ×1
  • REDACTED: 741 lines of code REDACTED:1 — REDACTED has 741 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 · cloudflare-workers/pulse/index.js · ×1
  • cloudflare-workers/pulse/index.js: 679 lines of code cloudflare-workers/pulse/index.js:1 — cloudflare-workers/pulse/index.js has 679 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 · dashboard/src/components/JobsView.tsx · ×1
  • dashboard/src/components/JobsView.tsx: 658 lines of code dashboard/src/components/JobsView.tsx:1 — dashboard/src/components/JobsView.tsx has 658 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 · cli-tool/src/file-operations.js · ×1
  • cli-tool/src/file-operations.js: 643 lines of code cli-tool/src/file-operations.js:1 — cli-tool/src/file-operations.js has 643 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 · REDACTED · ×1
  • REDACTED: 610 lines of code REDACTED:1 — REDACTED has 610 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 · cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx · ×1
  • cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx: 608 lines of code cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx:1 — cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx has 608 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 · cli-tool/src/analytics/data/DataCache.js · ×1
  • cli-tool/src/analytics/data/DataCache.js: 587 lines of code cli-tool/src/analytics/data/DataCache.js:1 — cli-tool/src/analytics/data/DataCache.js has 587 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 · cli-tool/src/analytics/core/SessionAnalyzer.js · ×1
  • cli-tool/src/analytics/core/SessionAnalyzer.js: 583 lines of code cli-tool/src/analytics/core/SessionAnalyzer.js:1 — cli-tool/src/analytics/core/SessionAnalyzer.js has 583 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 · cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx · ×1
  • cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx: 582 lines of code cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx:1 — cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx has 582 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 · cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts · ×1
  • cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts: 575 lines of code cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts:1 — cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts has 575 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 · cli-tool/analytics-ui/src/islands/Dashboard.tsx · ×1
  • cli-tool/analytics-ui/src/islands/Dashboard.tsx: 570 lines of code cli-tool/analytics-ui/src/islands/Dashboard.tsx:1 — cli-tool/analytics-ui/src/islands/Dashboard.tsx has 570 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 · cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts · ×1
  • cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts: 544 lines of code cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:1 — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts 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.
R3 · Large Files · cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx · ×1
  • cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx: 522 lines of code cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx:1 — cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx has 522 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 · cli-tool/components/mods/games/chess/hooks/register.tsx · ×1
  • cli-tool/components/mods/games/chess/hooks/register.tsx: 517 lines of code cli-tool/components/mods/games/chess/hooks/register.tsx:1 — cli-tool/components/mods/games/chess/hooks/register.tsx has 517 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 · cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx · ×1
  • cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx: 516 lines of code cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx:1 — cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx has 516 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 · dashboard/src/components/ComponentTerminal.tsx · ×1
  • dashboard/src/components/ComponentTerminal.tsx: 514 lines of code dashboard/src/components/ComponentTerminal.tsx:1 — dashboard/src/components/ComponentTerminal.tsx has 514 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 · dashboard/src/components/SkillReviewFlow.tsx · ×1
  • dashboard/src/components/SkillReviewFlow.tsx: 512 lines of code dashboard/src/components/SkillReviewFlow.tsx:1 — dashboard/src/components/SkillReviewFlow.tsx has 512 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 · cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx · ×1
  • cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx: 496 lines of code cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:1 — cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx has 496 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 · dashboard/public/blog/js/blog-loader.js · ×1
  • dashboard/public/blog/js/blog-loader.js: 491 lines of code dashboard/public/blog/js/blog-loader.js:1 — dashboard/public/blog/js/blog-loader.js has 491 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 · cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx · ×1
  • cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx: 483 lines of code cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx:1 — cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx has 483 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 · cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts · ×1
  • cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts: 483 lines of code cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts:1 — cli-tool/components/mods/security/jev-guardrails/hooks/policy.ts has 483 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 · REDACTED · ×1
  • REDACTED: 482 lines of code REDACTED:1 — REDACTED has 482 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 · cli-tool/analytics-ui/public/services/WebSocketService.js · ×1
  • cli-tool/analytics-ui/public/services/WebSocketService.js: 476 lines of code cli-tool/analytics-ui/public/services/WebSocketService.js:1 — cli-tool/analytics-ui/public/services/WebSocketService.js has 476 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 · cli-tool/src/analytics-web/services/WebSocketService.js · ×1
  • cli-tool/src/analytics-web/services/WebSocketService.js: 476 lines of code cli-tool/src/analytics-web/services/WebSocketService.js:1 — cli-tool/src/analytics-web/services/WebSocketService.js has 476 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 · cli-tool/src/analytics/notifications/WebSocketServer.js · ×1
  • cli-tool/src/analytics/notifications/WebSocketServer.js: 475 lines of code cli-tool/src/analytics/notifications/WebSocketServer.js:1 — cli-tool/src/analytics/notifications/WebSocketServer.js has 475 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 · cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts · ×1
  • cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts: 466 lines of code cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts:1 — cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts has 466 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 · cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx · ×1
  • cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx: 466 lines of code cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx:1 — cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx has 466 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 · dashboard/src/components/TrendingView.tsx · ×1
  • dashboard/src/components/TrendingView.tsx: 460 lines of code dashboard/src/components/TrendingView.tsx:1 — dashboard/src/components/TrendingView.tsx 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 · cloudflare-workers/newsletter/index.js · ×1
  • cloudflare-workers/newsletter/index.js: 454 lines of code cloudflare-workers/newsletter/index.js:1 — cloudflare-workers/newsletter/index.js has 454 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 · REDACTED · ×1
  • REDACTED: 450 lines of code REDACTED:1 — REDACTED has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~1362 LoC) · ×1
  • Dead file (~1362 LoC) cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~1101 LoC) · ×1
  • Dead file (~1101 LoC) dashboard/src/components/MyComponentsView.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~900 LoC) · ×1
  • Dead file (~900 LoC) dashboard/src/components/ComponentGrid.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~702 LoC) · ×1
  • Dead file (~702 LoC) dashboard/src/components/JobsView.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~649 LoC) · ×1
  • Dead file (~649 LoC) REDACTED — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~631 LoC) · ×1
  • Dead file (~631 LoC) cli-tool/components/mods/productivity/aitmpl/hooks/register.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~611 LoC) · ×1
  • Dead file (~611 LoC) cli-tool/analytics-ui/src/islands/Dashboard.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~570 LoC) · ×1
  • Dead file (~570 LoC) cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~559 LoC) · ×1
  • Dead file (~559 LoC) cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~558 LoC) · ×1
  • Dead file (~558 LoC) cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/register.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~557 LoC) · ×1
  • Dead file (~557 LoC) dashboard/src/components/ComponentTerminal.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~543 LoC) · ×1
  • Dead file (~543 LoC) cli-tool/components/mods/games/chess/hooks/register.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~542 LoC) · ×1
  • Dead file (~542 LoC) dashboard/src/components/SkillReviewFlow.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~528 LoC) · ×1
  • Dead file (~528 LoC) cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~527 LoC) · ×1
  • Dead file (~527 LoC) REDACTED — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~514 LoC) · ×1
  • Dead file (~514 LoC) cli-tool/components/mods/productivity/session-chats/hooks/session-chats.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~496 LoC) · ×1
  • Dead file (~496 LoC) cli-tool/components/mods/ui/stack-viewer/hooks/stack-viewer.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~452 LoC) · ×1
  • Dead file (~452 LoC) cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~445 LoC) · ×1
  • Dead file (~445 LoC) dashboard/src/components/CertificationsView.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~441 LoC) · ×1
  • Dead file (~441 LoC) cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~429 LoC) · ×1
  • Dead file (~429 LoC) dashboard/src/components/CartSidebar.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~419 LoC) · ×1
  • Dead file (~419 LoC) cli-tool/components/mods/productivity/session-time-machine/hooks/register.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~384 LoC) · ×1
  • Dead file (~384 LoC) cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.ts — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~365 LoC) · ×1
  • Dead file (~365 LoC) dashboard/src/components/SaveToCollectionButton.tsx — no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/components/ComponentGrid.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
R7 · Dead Code · Dead file (~356 LoC) · ×1
  • Dead file (~356 LoC) cli-tool/components/skills/creative-design/develop-web-game/scripts/web_game_playwright_client.js — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~354 LoC) · ×1
  • Dead file (~354 LoC) dashboard/src/components/MarketplacePluginsList.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~345 LoC) · ×1
  • Dead file (~345 LoC) dashboard/src/components/SearchModal.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~341 LoC) · ×1
  • Dead file (~341 LoC) cli-tool/components/mods/productivity/jev-model-router/hooks/jev-model-router.ts — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~335 LoC) · ×1
  • Dead file (~335 LoC) cli-tool/components/skills/development/typescript-expert/references/utility-types.ts — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~328 LoC) · ×1
  • Dead file (~328 LoC) cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx — no import path from any entry point (125 application, 31 tooling, 102 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
R7 · Dead Code · Dead file (~318 LoC) · ×1
  • Dead file (~318 LoC) dashboard/src/lib/data.ts — no import path from any entry point (125 application, 31 tooling, 102 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (dashboard/src/components/CartSidebar.tsx, dashboard/src/components/ComponentGrid.tsx, dashboard/src/components/SearchModal.tsx and 3 more) — 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
R7 · Dead Code · Dead file (~317 LoC) · ×1
  • Dead file (~317 LoC) cli-tool/components/mods/integrations/rex-tty/hooks/rex-tty.ts — no import path from any entry point (125 application, 31 tooling, 102 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
R8 · Dependency Hygiene · Unused dependency 'gpt-tokenizer' · ×1
  • Unused dependency 'gpt-tokenizer' dashboard/package.json:27 — Declared in dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity cli-tool/components/skills/creative-design/algorithmic-art/templates/viewer.html:23 — `https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.7.0/p5.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 23 such include(s) across the repository's markup.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) REDACTED:286 — `catch (parseError)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Minor — 245 finding(s)
D24 · Comment Value · redundant comment · ×84
  • redundant comment cli-tool/analytics-ui/public/services/DataService.js:278 — "Clear conversation state cache" repeats the code it sits on: 4 of its 4 words (clear, conversation, state, cache) are already in `this.clearCacheEntry('/api/conversation-state');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/analytics-ui/public/services/DataService.js:294 — "Notify listeners about the new message" repeats the code it sits on: 4 of its 4 words (notify, listeners, new, message) are already in `this.notifyListeners('new_message', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/analytics-ui/src/lib/api.ts:159 — "Normalize dailyActivity → heatmapData" repeats the code it sits on: 4 of its 5 words (daily, activity, heatmap, data) are already in `return {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js:78 — "Set default timeout" repeats the code it sits on: 3 of its 3 words (set, default, timeout) are already in `page.setDefaultTimeout(options.timeout || 30000);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js:218 — "Wait for navigation or success indicator" repeats the code it sits on: 4 of its 4 words (wait, navigation, success, indicator) are already in `await Promise.race([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/components/skills/utilities/playwright-skill/run.js:196 — "Get code to execute" repeats the code it sits on: 3 of its 3 words (get, code, execute) are already in `const rawCode = getCodeToExecute();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/components/skills/utilities/playwright-skill/run.js:204 — "Write code to temp file" repeats the code it sits on: 4 of its 4 words (write, code, temp, file) are already in `fs.writeFileSync(tempFile, code, 'utf8');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/agents.js:149 — "Find the agent by name in the available agents" repeats the code it sits on: 4 of its 5 words (find, agent, name, agents) are already in `const agent = allAgents.find(a => a.name === agentName);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics-web/services/DataService.js:278 — "Clear conversation state cache" repeats the code it sits on: 4 of its 4 words (clear, conversation, state, cache) are already in `this.clearCacheEntry('/api/conversation-state');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics-web/services/DataService.js:294 — "Notify listeners about the new message" repeats the code it sits on: 4 of its 4 words (notify, listeners, new, message) are already in `this.notifyListeners('new_message', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:373 — 10 comments in this file only repeat the code they sit on (lines 373, 471, 488, 623, 1171, 1179, 1274, 1502, 1678, 1950), for example "Check for tool_use blocks in array content". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/AgentAnalyzer.js:147 — "Sort timeline by timestamp" repeats the code it sits on: 3 of its 3 words (sort, timeline, timestamp) are already in `agentTimeline.sort((a, b) => new Date(a.timestamp) - new Date(b.timestamp));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/ConversationAnalyzer.js:36 — 6 comments in this file only repeat the code they sit on (lines 36, 52, 318, 666, 803, 820), for example "Load active projects". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/FileWatcher.js:54 — "Extract conversation ID from file path" repeats the code it sits on: 5 of its 5 words (extract, conversation, id, file, path) are already in `const conversationId = this.extractConversationId(filePath);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/FileWatcher.js:168 — "Get previous activity" repeats the code it sits on: 3 of its 3 words (get, previous, activity) are already in `const previousActivity = this.fileActivity.get(conversationId) || {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/SessionAnalyzer.js:197 — "Sort all messages by timestamp" repeats the code it sits on: 3 of its 3 words (sort, messages, timestamp) are already in `allMessages.sort((a, b) => new Date(a.timestamp) - new Date(b.timestamp));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/SessionAnalyzer.js:266 — "Session is active if current time is within this window" repeats the code it sits on: 4 of its 5 words (session, active, current, window) are already in `session.isActive = now >= currentWindowStart && now < windowEnd;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/SessionAnalyzer.js:329 — "Sort all messages by timestamp" repeats the code it sits on: 3 of its 3 words (sort, messages, timestamp) are already in `allMessages.sort((a, b) => new Date(a.timestamp) - new Date(b.timestamp));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/StateCalculator.js:154 — "Sort messages by timestamp" repeats the code it sits on: 3 of its 3 words (sort, messages, timestamp) are already in `const sortedMessages = messages.sort((a, b) => new Date(a.timestamp) - new Date(b.timestamp));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/core/StateCalculator.js:187 — "Sort messages by timestamp" repeats the code it sits on: 3 of its 3 words (sort, messages, timestamp) are already in `const sortedMessages = messages.sort((a, b) => new Date(a.timestamp) - new Date(b.timestamp));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/data/DataCache.js:93 — "Also cache the file stats" repeats the code it sits on: 3 of its 3 words (cache, file, stats) are already in `this.caches.fileStats.set(filepath, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/data/DataCache.js:197 — "Attach tool result to the tool use entry" repeats the code it sits on: 4 of its 5 words (tool, result, use, entry) are already in `if (!toolUseEntry.toolResults)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/notifications/NotificationManager.js:443 — "10x throttle time" repeats the code it sits on: 3 of its 3 words (10, throttle, time) are already in `const maxAge = this.defaultThrottleTime * 10;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/notifications/WebSocketServer.js:114 — "Send any queued messages" repeats the code it sits on: 3 of its 3 words (send, queued, messages) are already in `this.sendQueuedMessages(clientId);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment cli-tool/src/analytics/utils/PerformanceMonitor.js:251 — "Check memory threshold" repeats the code it sits on: 3 of its 3 words (check, memory, threshold) are already in `if (memUsage.heapUsed > this.options.memoryThreshold)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 59 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts:502 — `!answers || !which || typeof which.choice !== 'string'` appears character-identically in 2 files — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts, cli-tool/components/mods/productivity/jev-skill-typeahead/hooks/jev.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 cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts:259 — `!e.text.trim() || /^\/\S/.test(e.text.trim())` appears character-identically in 2 files — cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/jev-skill-suggestion.ts, cli-tool/components/mods/security/jev-guardrails/hooks/jev-guardrails.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 dashboard/src/pages/api/collections/[id].ts:27 — `!name || typeof name !== 'string' || name.trim().length === 0` appears character-identically in 2 files — dashboard/src/pages/api/collections/[id].ts, dashboard/src/pages/api/collections/index.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:168 — `!parent || parent.nodeName === 'CODE' || parent.nodeName === 'PRE'` appears character-identically in 2 files — 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 dashboard/public/blog/js/blog-loader.js:466 — `!prevBtn || !nextBtn || !this.featuredCarousel` appears character-identically in 2 files — dashboard/public/blog/js/blog-loader.js, docs/blog/js/blog-loader.js. 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:129 — `!previewRef.current || mode !== 'preview'` appears character-identically in 2 files — 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 REDACTED:97 — `!searchQuery.trim() || searchQuery.length < 2` appears character-identically in 2 files — 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 dashboard/public/blog/js/blog-loader.js:394 — `!this.featuredCarousel || !this.featuredArticles || this.featuredArticles.length === 0` appears character-identically in 2 files — dashboard/public/blog/js/blog-loader.js, docs/blog/js/blog-loader.js. 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 dashboard/public/blog/js/blog-loader.js:231 — `!this.filteredArticles || this.filteredArticles.length === 0` appears character-identically in 2 files — dashboard/public/blog/js/blog-loader.js, docs/blog/js/blog-loader.js. 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 cli-tool/analytics-ui/public/services/DataService.js:249 — `!this.webSocketService || !this.realTimeEnabled` appears character-identically in 2 files — cli-tool/analytics-ui/public/services/DataService.js, cli-tool/src/analytics-web/services/DataService.js. 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:57 — `c === '\\' && quote === '"' && i + 1 < command.length` appears character-identically in 2 files — 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 cloudflare-workers/crons/sentry.js:111 — `checkInId || crypto.randomUUID().replace(/-/g, '')` appears character-identically in 4 files — cloudflare-workers/crons/sentry.js, cloudflare-workers/docs-monitor/sentry.js, cloudflare-workers/newsletter/sentry.js, cloudflare-workers/pulse/sentry.js. 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 docs/js/generate-search-data.js:38 — `component.tags || [component.category].filter(Boolean)` appears character-identically in 2 files — docs/js/generate-search-data.js, docs/js/search-functionality.js. 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 docs/js/component-page.js:1180 — `componentPath.endsWith('.md') || componentPath.endsWith('.json')` appears character-identically in 2 files — docs/js/component-page.js, docs/js/search-functionality.js. 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:356 — `content.includes('[Tool:') || content.includes('tool_use')` appears character-identically in 2 files — REDACTED, cli-tool/src/analytics/core/ConversationAnalyzer.js. 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:361 — `content.includes('error') || content.includes('Error') || content.includes('failed')` appears character-identically in 2 files — REDACTED, cli-tool/src/analytics/core/ConversationAnalyzer.js. 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:1835 — `conversation.toolUsage?.totalToolCalls || 0` appears character-identically in 2 files — 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 cli-tool/analytics-ui/public/services/WebSocketService.js:141 — `data.messageId && this.pendingMessages.has(data.messageId)` appears character-identically in 2 files — cli-tool/analytics-ui/public/services/WebSocketService.js, cli-tool/src/analytics-web/services/WebSocketService.js. 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 docs/js/generate-search-data.js:16 — `data[category] && Array.isArray(data[category])` appears character-identically in 2 files — docs/js/generate-search-data.js, docs/js/search-functionality.js. 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 dashboard/public/blog/js/blog-loader.js:340 — `difficultyConfig[difficulty] || difficultyConfig.basic` appears character-identically in 2 files — dashboard/public/blog/js/blog-loader.js, docs/blog/js/blog-loader.js. 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 cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts:159 — `e.agentId === undefined && e.text.trim()` appears character-identically in 2 files — cli-tool/components/mods/security/jev-auto-mode/hooks/jev-auto-mode.ts, cli-tool/components/mods/security/jev-vercel-sandbox/hooks/jev-vercel-sandbox.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:258 — `e.key === 'Enter' && searchResults[selectedIdx]` appears character-identically in 2 files — 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 cli-tool/components/mods/games/chess/hooks/register.tsx:350 — `e.plugin !== $.plugin.name || e.requestId !== PANE` appears character-identically in 11 files — cli-tool/components/mods/games/chess/hooks/register.tsx, cli-tool/components/mods/integrations/bluesky-feed/hooks/bluesky-feed.tsx, cli-tool/components/mods/integrations/linear-tickets/hooks/linear-tickets.tsx, cli-tool/components/mods/integrations/vercel-deploys/hooks/vercel-deploys.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:112 — `entry.text.toLowerCase().includes(q) && !seen.has(entry.headingId)` appears character-identically in 2 files — 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 cloudflare-workers/crons/index.js:21 — `env.DASHBOARD_URL || 'https://www.aitmpl.com'` appears character-identically in 3 files — cloudflare-workers/crons/index.js, cloudflare-workers/daily-health-report/index.js, cloudflare-workers/newsletter/index.js. 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.
  • + 15 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:152 — `error` at line 152 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:156 — `error` at line 156 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:160 — `error` at line 160 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:177 — `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.
  • Interpolated log message defeats structured logging cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:186 — `info` at line 186 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:195 — `warning` at line 195 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:201 — `error` at line 201 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:284 — `info` at line 284 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:291 — `error` at line 291 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:295 — `error` at line 295 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 cli-tool/components/skills/document-processing/pdf-processing-pro/scripts/analyze_form.py:299 — `error` at line 299 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 cli-tool/components/skills/document-processing/docx-official/scripts/accept_changes.py:117 — `warning` 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.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 cli-tool/components/skills/document-processing/docx/scripts/accept_changes.py:117 — `warning` 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.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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:32 — `info` at line 32 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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:60 — `error` 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.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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/agent_orchestrator.py:96 — `error` at line 96 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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:32 — `info` at line 32 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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:60 — `error` 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.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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/prompt_optimizer.py:96 — `error` at line 96 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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:32 — `info` at line 32 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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:60 — `error` 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.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 cli-tool/components/skills/development/senior-prompt-engineer/scripts/rag_evaluator.py:96 — `error` at line 96 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 cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:32 — `info` at line 32 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 cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:60 — `error` 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.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 cli-tool/components/skills/development/senior-ml-engineer/scripts/ml_monitoring_suite.py:96 — `error` at line 96 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.
  • + 15 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×21
  • Silent fallback default on parse failure REDACTED:28 — `get_input` returns `{}` when `(json.JSONDecodeError, ValueError)` 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 REDACTED:28 — `get_input` returns `{}` when `(json.JSONDecodeError, ValueError)` 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 cli-tool/components/skills/document-processing/docx-official/scripts/office/helpers/simplify_redlines.py:133 — `get_tracked_change_authors` returns `{}` when `ET.ParseError` 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 cli-tool/components/skills/document-processing/docx-official/scripts/office/helpers/simplify_redlines.py:168 — `_get_authors_from_docx` returns `{}` when `(zipfile.BadZipFile, ET.ParseError)` 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 cli-tool/components/skills/document-processing/docx/scripts/office/helpers/simplify_redlines.py:133 — `get_tracked_change_authors` returns `{}` when `ET.ParseError` 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 cli-tool/components/skills/document-processing/docx/scripts/office/helpers/simplify_redlines.py:168 — `_get_authors_from_docx` returns `{}` when `(zipfile.BadZipFile, ET.ParseError)` 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 cli-tool/components/skills/document-processing/pptx-official/scripts/office/helpers/simplify_redlines.py:133 — `get_tracked_change_authors` returns `{}` when `ET.ParseError` 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 cli-tool/components/skills/document-processing/pptx-official/scripts/office/helpers/simplify_redlines.py:168 — `_get_authors_from_docx` returns `{}` when `(zipfile.BadZipFile, ET.ParseError)` 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 cli-tool/components/skills/document-processing/pptx/scripts/office/helpers/simplify_redlines.py:133 — `get_tracked_change_authors` returns `{}` when `ET.ParseError` 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 cli-tool/components/skills/document-processing/pptx/scripts/office/helpers/simplify_redlines.py:168 — `_get_authors_from_docx` returns `{}` when `(zipfile.BadZipFile, ET.ParseError)` 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 cli-tool/components/skills/document-processing/xlsx-official/scripts/office/helpers/simplify_redlines.py:133 — `get_tracked_change_authors` returns `{}` when `ET.ParseError` 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 cli-tool/components/skills/document-processing/xlsx-official/scripts/office/helpers/simplify_redlines.py:168 — `_get_authors_from_docx` returns `{}` when `(zipfile.BadZipFile, ET.ParseError)` 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 cli-tool/components/skills/document-processing/xlsx/scripts/office/helpers/simplify_redlines.py:133 — `get_tracked_change_authors` returns `{}` when `ET.ParseError` 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 cli-tool/components/skills/document-processing/xlsx/scripts/office/helpers/simplify_redlines.py:168 — `_get_authors_from_docx` returns `{}` when `(zipfile.BadZipFile, ET.ParseError)` 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 cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:81 — `to_int` returns `0` when `(TypeError, ValueError)` 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 cli-tool/components/skills/security/security-ownership-map/scripts/query_ownership.py:88 — `to_float` returns `0.0` when `(TypeError, ValueError)` 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 scripts/external_skills.py:394 — `_json_keys` returns `[]` when `(OSError, ValueError)` 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 scripts/generate_claude_jobs.py:236 — `domain_company` returns `''` when `ValueError` 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 scripts/generate_claude_jobs.py:483 — `remoteok_salary` returns `''` when `(TypeError, ValueError)` 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 scripts/generate_claude_jobs.py:821 — `load_discovered_boards` returns `[]` when `(OSError, ValueError)` 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 scripts/skillspector_catalog.py:218 — `previous_results` returns `{}` when `(OSError, ValueError)` 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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×19
  • Silent fallback default in catch cli-tool/components/settings/statusline/context-monitor.py:55 — `get_git_status` 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 cli-tool/components/settings/statusline/deadline-countdown.py:53 — `get_git_info` 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 cli-tool/components/skills/enterprise-communication/session-handoff/scripts/list_handoffs.py:50 — `check_completion_status` swallows every exception into `return 'Unknown'` — 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 cli-tool/src/agents.js:200 — `getInstalledAgents` 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 cli-tool/src/analytics/core/ConversationAnalyzer.js:886 — `findTodoFiles` 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 REDACTED:167 — `findTodoFiles` 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 cli-tool/src/tracking-service.js:195 — `getCliVersion` swallows every exception into `return 'unknown'` — 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 cli-tool/src/external-skill.js:121 — `githubErrorMessage` 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 cli-tool/src/catalog-lookup.js:143 — `resolveItems` swallows every exception into `return -1` — 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 cli-tool/src/plugin-install.js:305 — `sameNameElsewhere` 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 cli-tool/src/tui.js:22 — `getVersion` swallows every exception into `return '1.0.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 cli-tool/src/error-reporting.js:153 — `getCliVersion` swallows every exception into `return 'unknown'` — 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 cli-tool/components/mods/integrations/pi-agent-for-claude/hooks/register.ts:584 — `transcriptOf` 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 cli-tool/components/mods/observability/prompt-cache-control/hooks/prompt-cache-control.tsx:166 — `readGlobalConfig` 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 cli-tool/components/mods/productivity/jev-skill-suggestion/hooks/policy.ts:273 — `installPathsOf` 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 cli-tool/components/mods/ui/turn-inspector/hooks/turn-inspector.tsx:417 — `safeJson` 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 cloudflare-workers/newsletter/index.js:400 — `broadcastAlreadySentToday` 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.
  • Silent fallback default in catch dashboard/src/components/AddToStackButton.tsx:24 — `readCart` 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 dashboard/src/components/JobsView.tsx:79 — `timeAgo` 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.
D34 · Knowledge Freshness · Orphaned file · ×6
  • Orphaned file cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.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 cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.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 cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.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 cli-tool/components/skills/creative-design/executing-marketing-campaigns/scripts/marketing_utils.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 cli-tool/components/skills/productivity/nowait/scripts/nowait_processor.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 cli-tool/components/skills/business-marketing/product-decision-agent/scripts/quality_gate.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.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×6
  • Hand-rolled JSON/XML parsing via regex cli-tool/components/skills/productivity/skill-creator/scripts/improve_description.py:146 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex cli-tool/components/skills/productivity/skill-creator/scripts/improve_description.py:175 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex cli-tool/components/skills/development/skill-development/scripts/improve_description.py:146 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex cli-tool/components/skills/development/skill-development/scripts/improve_description.py:175 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex cli-tool/components/skills/development/skill-creator/scripts/improve_description.py:146 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex cli-tool/components/skills/development/skill-creator/scripts/improve_description.py:175 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Python code already uses a real parser in the same package; use it here too.
D30 · Dependency Vulnerabilities · Low CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×5
  • README/code drift cli-tool/components/skills/creative-design/marp-slide/README.md:58 — cli-tool/components/skills/creative-design/marp-slide/README.md links to `image.png`, but `cli-tool/components/skills/creative-design/marp-slide/image.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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 cli-tool/components/skills/development/react-dev/README.md:48 — cli-tool/components/skills/development/react-dev/README.md names React 18, but the manifest declares `react` ^19.2.4. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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 cli-tool/components/skills/development/react-useeffect/README.md:299 — cli-tool/components/skills/development/react-useeffect/README.md names React 18, but the manifest declares `react` ^19.2.4. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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 cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/README.md:9 — cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/README.md links to `papers.md`, but `cli-tool/components/skills/ai-research/mechanistic-interpretability-saelens/references/papers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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 cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/README.md:9 — cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/README.md links to `papers.md`, but `cli-tool/components/skills/ai-research/mechanistic-interpretability-transformer-lens/references/papers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×3
  • Projects may be oversized for their cohesion cli-tool/package.json:1 — `cli-tool` (114049 LoC, 1354 module-visible types across 306 directories) overshoots its size bounds. 3 of 19 build unit(s) (Cargo, Python, npm) overshoot their size bounds, lowering Project Cohesion to 6.8/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 package.json:1 — `(repository root)` (19202 LoC, 121 module-visible types across 34 directories) overshoots its size bounds. 3 of 19 build unit(s) (Cargo, Python, npm) overshoot their size bounds, lowering Project Cohesion to 6.8/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 dashboard/package.json:1 — `dashboard` (15288 LoC, 185 module-visible types across 34 directories) overshoots its size bounds. 3 of 19 build unit(s) (Cargo, Python, npm) overshoot their size bounds, lowering Project Cohesion to 6.8/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.
D10 · Test Quality · Mock-dominated test · ×2
  • Mock-dominated test: should handle real-time data refresh cli-tool/tests/unit/DataService.test.js:221 — This test sets up 3 test doubles (for example `jest.spyOn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should handle real-time state changes cli-tool/tests/unit/DataService.test.js:237 — This test sets up 3 test doubles (for example `jest.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 6 of 702 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 702 of the 1158 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: cli-tool/components/skills/development/security-compliance/scripts/vuln_prioritizer.py, cli-tool/components/skills/development/devops-iac-engineer/scripts/devops_utils.py, cli-tool/components/skills/development/security-compliance/scripts/risk_calculator.py, cli-tool/components/skills/creative-design/executing-marketing-campaigns/scripts/marketing_utils.py, cli-tool/components/skills/productivity/nowait/scripts/nowait_processor.py, cli-tool/components/skills/business-marketing/product-decision-agent/scripts/quality_gate.py. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P3 · Security & performance tooling · Dependabot does not watch cargo/pip · ×1
  • Dependabot does not watch cargo/pip REDACTED:2 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `cargo`, `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
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 23/82 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 — 6/9 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.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~3.5 `!` null assertions per 1k TypeScript source lines — 176 assertion(s) across the 50721 source line(s) of the 262 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: cli-tool/components/mods/games/tool-defense/hooks/games/defense.ts (15), REDACTED (14), cli-tool/components/mods/ui/stack-viewer/hooks/stack.ts (13). 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.
Minor — 12 finding(s)
D12 · Dependency Hygiene · Outdated · ×7
  • Outdated: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
  • Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
  • Outdated: open — `open` is locked at 5.3.5 but 5.4.5 is the current stable release on crates.io, and it already satisfies the `"5"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p open` and commit the updated REDACTED.
  • Outdated: owo-colors — `owo-colors` is locked at 4.3.0 but 4.4.0 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p owo-colors` and commit the updated REDACTED.
  • Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
  • Outdated: serde_json — `serde_json` is locked at 1.0.150 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
  • Outdated: uuid — `uuid` is locked at 1.23.3 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in cli-rust/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
D24 · Comment Value · doc comments repeat the names · ×5
  • doc comments repeat the names cli-tool/analytics-ui/public/services/DataService.js:29 — 7 of 62 documented parameters and 20 of 89 summaries in `analytics-ui` only repeat the member or parameter name (e.g. "Remove event listener" for `removeEventListener`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names cli-tool/components/mods/productivity/jev-model-router/hooks/policy.ts:146 — 58 of 468 documented parameters and 63 of 1628 summaries in `claude-code-templates` only repeat the member or parameter name (e.g. "The request headers." for `requestHeaders`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names dashboard/public/blog/js/blog-loader.js:117 — 0 of 6 documented parameters and 4 of 139 summaries in `claude-code-templates-dashboard` only repeat the member or parameter name (e.g. "Apply filters and sorting" for `applyFiltersAndSort`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names cloudflare-workers/docs-monitor/index.js:189 — 0 of 5 documented parameters and 1 of 6 summaries in `claude-docs-monitor` only repeat the member or parameter name (e.g. "Send notification to Telegram" for `sendTelegramNotification`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js:228 — 2 of 34 documented parameters and 3 of 22 summaries in `playwright-skill` only repeat the member or parameter name (e.g. "Scroll page" for `scrollPage`). 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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-94a34c5c4c5c4ef0a55d042a2f1aad8d/history.json --exit-code 0 --source .0—
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-94a34c5c4c5c4ef0a55d042a2f1aad8d/tree.json --exit-code 0 --source .5artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .151artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .60artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .13artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `cli-tool/components/mods/productivity/subagent-tuner/hooks/register.tsx`, `cli-tool/components/mods/productivity/ultra-config/hooks/register.tsx`, `cli-tool/components/mods/types/claude-code.d.ts`, `cli-tool/components/skills/creative-design/ui-design-system/scripts/design_token_generator.py`, `cli-tool/components/skills/development/typescript-expert/references/utility-types.ts`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e2e8-6762-78ea-8924-4041a312e25b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md